Skip to contentSkip to conversation

testcase pidns20, pidns21 on pid namespace

PATCH Subrata Modak 3 participants 4 messages Jun 23, 2009 – Nov 11, 2009 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 33 lines · Subrata Modak

Thanks Suka,

Quoted 30 lines · Sukadev Bhattiprolu

Subrata Modak [[email protected]] wrote:

| 
| > > pidns21:
| > >    The pidns21.c testcase verifies that container-init is terminated
| > >    by SIGUSR1 when:
| > >       - a handler is specified for SIGUSR1,
| > >       - container-init blocks SIGUSR1,
| > >       - parent queues SIGUSR1 and
| > >       - handler for SIGUSR1 is set to system default before SIGUSR1 is 
| > > unblocked.

I know I had acked this test before, but back then the actual implementation of the signal semantics in the kernel were not complete.

To simplify the implementation of the semantics, it was decided that SIGKILL/SIGSTOP would be the only reliable signals from a parent container. IOW, container-init would ignore SIGUSR1 or SIGINT, SIGQUIT etc even if sent from a parent container.

See patchset/discussion:

	http://lkml.org/lkml/2009/1/17/131

(which is not yet merged, but appears to be close to consensus)

The rationale for this simplification is that any serious 'container-init' would explicitly SIG_IGN all signals that it is not interested in. So the only signals that would be in SIG_DFL state would be SIGKILL/SIGSTOP.

Quoted 7 lines
Quoted 2 lines

Effectively, testcase pidns21 will fail if/when the above patchset (specifically, patch 5/6) is merged.

Gowri,

Kindly update this test when the patch makes into next stable kernel release.

Suka/Gowri,

Are we still looking into these tests ?

Regards--
Subrata

Quoted 11 lines

Regards--
Subrata

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA

(quoted diff) +0 -3
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
Quoted 5 lines

http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

#6 lore raw
Quoted 41 lines · Subrata Modak
Quoted 39 lines · Subrata Modak

Thanks Suka,

Quoted 25 lines · Sukadev Bhattiprolu

Subrata Modak [[email protected]] wrote:

| 
| > > pidns21:
| > >    The pidns21.c testcase verifies that container-init is terminated
| > >    by SIGUSR1 when:
| > >       - a handler is specified for SIGUSR1,
| > >       - container-init blocks SIGUSR1,
| > >       - parent queues SIGUSR1 and
| > >       - handler for SIGUSR1 is set to system default before SIGUSR1 is 
| > > unblocked.

I know I had acked this test before, but back then the actual implementation of the signal semantics in the kernel were not complete.

To simplify the implementation of the semantics, it was decided that SIGKILL/SIGSTOP would be the only reliable signals from a parent container. IOW, container-init would ignore SIGUSR1 or SIGINT, SIGQUIT etc even if sent from a parent container.

See patchset/discussion:

	http://lkml.org/lkml/2009/1/17/131

(which is not yet merged, but appears to be close to consensus)

Quoted 8 lines

The rationale for this simplification is that any serious 'container-init' would explicitly SIG_IGN all signals that it is not interested in. So the only signals that would be in SIG_DFL state would be SIGKILL/SIGSTOP.

Effectively, testcase pidns21 will fail if/when the above patchset (specifically, patch 5/6) is merged.

Gowri,

Quoted 8 lines
Quoted 3 lines

Kindly update this test when the patch makes into next stable kernel release.

Suka/Gowri,

Are we still looking into these tests ?

Anyone still looking into it ? Still i am getting failure for pidns21 with latest ltp release.

-Rishi

Quoted 23 lines

Regards--
Subrata

Quoted 10 lines

Regards--
Subrata

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA

(quoted diff) +0 -3
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
Quoted 6 lines

http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

------------------------------------------------------------------------------

Quoted 9 lines

Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

#7 lore raw
Quoted 46 lines · Rishikesh
Quoted 45 lines · Subrata Modak
Quoted 42 lines · Subrata Modak

Thanks Suka,

Quoted 25 lines · Sukadev Bhattiprolu

Subrata Modak [[email protected]] wrote:

| 
| > > pidns21:
| > >    The pidns21.c testcase verifies that container-init is terminated
| > >    by SIGUSR1 when:
| > >       - a handler is specified for SIGUSR1,
| > >       - container-init blocks SIGUSR1,
| > >       - parent queues SIGUSR1 and
| > >       - handler for SIGUSR1 is set to system default before SIGUSR1 is 
| > > unblocked.

I know I had acked this test before, but back then the actual implementation of the signal semantics in the kernel were not complete.

To simplify the implementation of the semantics, it was decided that SIGKILL/SIGSTOP would be the only reliable signals from a parent container. IOW, container-init would ignore SIGUSR1 or SIGINT, SIGQUIT etc even if sent from a parent container.

See patchset/discussion:

	http://lkml.org/lkml/2009/1/17/131

(which is not yet merged, but appears to be close to consensus)

Quoted 8 lines

The rationale for this simplification is that any serious 'container-init' would explicitly SIG_IGN all signals that it is not interested in. So the only signals that would be in SIG_DFL state would be SIGKILL/SIGSTOP.

Effectively, testcase pidns21 will fail if/when the above patchset (specifically, patch 5/6) is merged.

Gowri,

Kindly update this test when the patch makes into next stable kernel release.

Quoted 8 lines
Quoted 4 lines

Suka/Gowri,

Are we still looking into these tests ?

Anyone still looking into it ? Still i am getting failure for pidns21 with latest ltp release.

The patch in question is upstream, so pidns21.c will always fail and should be removed from ltp.

It's worth testing that the container init survives SIGUSR1 from a child, but whether it survives or dies from a parent we don't particularly care.

-serge

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

#8 lore raw
Quoted 53 lines · Serge E. Hallyn
Quoted 52 lines · Rishikesh
Quoted 49 lines · Subrata Modak
Quoted 34 lines · Subrata Modak

Thanks Suka,

Quoted 30 lines · Sukadev Bhattiprolu

Subrata Modak [[email protected]] wrote:

| 
| > > pidns21:
| > >    The pidns21.c testcase verifies that container-init is terminated
| > >    by SIGUSR1 when:
| > >       - a handler is specified for SIGUSR1,
| > >       - container-init blocks SIGUSR1,
| > >       - parent queues SIGUSR1 and
| > >       - handler for SIGUSR1 is set to system default before SIGUSR1 is 
| > > unblocked.

I know I had acked this test before, but back then the actual implementation of the signal semantics in the kernel were not complete.

To simplify the implementation of the semantics, it was decided that SIGKILL/SIGSTOP would be the only reliable signals from a parent container. IOW, container-init would ignore SIGUSR1 or SIGINT, SIGQUIT etc even if sent from a parent container.

See patchset/discussion:

	http://lkml.org/lkml/2009/1/17/131

(which is not yet merged, but appears to be close to consensus)

The rationale for this simplification is that any serious 'container-init' would explicitly SIG_IGN all signals that it is not interested in. So the only signals that would be in SIG_DFL state would be SIGKILL/SIGSTOP.

Quoted 8 lines
Quoted 3 lines

Effectively, testcase pidns21 will fail if/when the above patchset (specifically, patch 5/6) is merged.

Gowri,

Kindly update this test when the patch makes into next stable kernel release.

Suka/Gowri,

Are we still looking into these tests ?

Quoted 5 lines
Quoted 2 lines

Anyone still looking into it ? Still i am getting failure for pidns21 with latest ltp release.

The patch in question is upstream, so pidns21.c will always fail and should be removed from ltp.

Ok. I did that just now.

Regards--
Subrata

Quoted 6 lines

It's worth testing that the container init survives SIGUSR1 from a child, but whether it survives or dies from a parent we don't particularly care.

-serge

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list