This is on s390/zSeries 31bit Linux. I am unsure about other archs.
        Any idea why syslog12 would hang? It completes the 1st pass but stalls at the others.
---------------------------
osatest2:~/ltp/testcases/kernel/syscalls/syslog # ./syslog12
Executing1 tn: 0
Executing2 tn: 0
Executing3 tn: 0
syslog12    1  PASS  :  syslog() failed as expected for invalid type/command : errno 22
Executing1 tn: 1
Executing2 tn: 1
syslog12    2  BROK  :  Unexpected signal 2 received.
syslog12    3  BROK  :  Remaining cases broken
syslog12    4  BROK  :  Remaining cases broken
syslog12    5  BROK  :  Remaining cases broken
syslog12    6  BROK  :  Remaining cases broken
syslog12    7  BROK  :  Remaining cases broken
------------------------------
        This is me running it from the commandline and hitting ^C when it hangs.
        Here's is the code snippit w/ my printfs;
       

   for (testno = 0; testno < TST_TOTAL; ++testno) {
                        printf("Executing1 tn: %d\n", testno);

                        if( tdat[testno].setup && tdat[testno].setup() ) {
                                /* Setup failed, skip this testcase */
                                continue;
                        }
                        printf("Executing2 tn: %d\n", testno);

                        TEST(syslog(tdat[testno].type, tdat[testno].buf,
                                        tdat[testno].len));

                        printf("Executing3 tn: %d\n", testno);

        So it appears it is actually hanging on the call to syslog(). My only thoughts are that syslog() is blocking or that there's an issue w/ the signals.
        Wondering if anyone's noticed this or has thoughts.
        j

Actually, I think I have a good guess;

static struct test_case_t  tdat[] = {
        { 100, &buf, 0, EINVAL, NULL, NULL, "invalid type/command" },
        { 2, (char *) -1, 1, EFAULT, NULL, NULL, "buffer outside program's "
                "accessible  address space" },

        The above if the buffer used to define the parms for each test. Entry #1 (counting at 0) the one it's hanging on seems to be testing for the retcode when passing an invalid memory address. -1 in most archs is invalid but for s390 it's valid because of the way kernel and application code are each in separate memory zones.
        I know this has come up before in other testcases, anyone know how/if it was fixed? I remember talk of unmemorymapping an address as the only reliable way to fix this.
        j


Jay Huie
 wjhuie@us.ibm.com
 zSeries Linux System Test
 Phone: 845-435-8164

Sent by:        ltp-list-admin@lists.sourceforge.net

To:        Robert Williamson/Austin/IBM@IBMUS
cc:        ltp-announce@lists.sourceforge.net, ltp-list@lists.sourceforge.net
Subject:        Re: [LTP] LTP Project Management Changes




Wrong link for Patches Tracker...here is the correct one:

http://sourceforge.net/tracker/?group_id=3382&atid=303382

- Robbie

Robert V. Williamson <robbiew@us.ibm.com>
Linux Test Project
IBM Linux Technology Center
Phone: (512) 838-9295   T/L: 678-9295
Fax: (512) 838-4603
Web: http://ltp.sourceforge.net
IRC: #ltp on freenode.irc.net
====================
"Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former." -Albert Einstein



Robert
Williamson/Austin/IBM@IBM        To:       ltp-list@lists.sourceforge.net, ltp-announce@lists.sourceforge.net
US                               cc:
Sent by:                         Subject:  [LTP] LTP Project Management Changes
ltp-list-admin@lists.sour
ceforge.net



05/14/2003 11:27 AM





In an attempt to maintain some type of order in the project, I think we
should utilize the Bugs, Patches, and Feature Request Trackers on the
sourceforge site.  Using these tools will allow us (maintainers) a way to
prioritize what we need to do and allow users to keep track of project
progress.

So from now on if you want to complai....I mean report a bug/defect use the
Bugs Tracker (http://sourceforge.net/tracker/?group_id=3382&atid=103382).
If you want to request a feature change or enhancement to the test suite
use the RFE Tracker
(http://sourceforge.net/tracker/?group_id=3382&atid=353382). Finally, if
you want to submit a patch or fix use the Patches Tracker
(http://sourceforge.net/tracker/index.php).

Please not that this is not saying that bugs, feature requests, or patches
sent to the mailing list, or our (maintainers) email address, will be
completely ignored.  However, expect low priority if you have not
documented your bug, request, or patch in the associated tracker.


- Robbie

Robert V. Williamson <robbiew@us.ibm.com>
Linux Test Project
IBM Linux Technology Center
Phone: (512) 838-9295   T/L: 678-9295
Fax: (512) 838-4603
Web: http://ltp.sourceforge.net
IRC: #ltp on freenode.irc.net
====================
"Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former." -Albert Einstein




-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list






-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/ltp-list