From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Joe Peterson" <joe@skyrush.com>
Cc: "Alan Cox" <alan@redhat.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"David Newall" <davidn@davidnewall.com>,
"Willy Tarreau" <w@1wt.eu>,
"Harald Dunkel" <harald.dunkel@t-online.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: su gets stuck for root
Date: Sat, 14 Jun 2008 09:45:17 +0200 [thread overview]
Message-ID: <19f34abd0806140045l259bcb93ie4b7bfa2d73bd4d@mail.gmail.com> (raw)
In-Reply-To: <485323C5.4030002@skyrush.com>
On Sat, Jun 14, 2008 at 3:49 AM, Joe Peterson <joe@skyrush.com> wrote:
> Vegard Nossum wrote:
>> I think knowing the pgrps of the above processes (there is possibly
>> one more involved, stty?) would be useful; try:
>>
>> $ ps -eo pid,pgrp,tpgid,user,args
>
> OK, I performed this test again (getting the su to hang), and here is
> the info:
[snip]
> scorpius ~ # ps -eo pid,pgrp,tpgid,user,args | grep 7036
> 6902 6902 7036 root /bin/login --
> 6922 6922 7036 root -bash
> 7036 7036 7036 foo su foo
> 7037 7037 7036 foo bash
> 7042 7037 7036 foo stty -ixany
So this clearly shows what's wrong; 7036 is the "controlling process"
group id. But only "su foo" is in this group, the bash and stty
processes have their own group, 7037.
On my own system, when I do "su", I get this:
2891 2891 2892 root su temp
2892 2892 2892 temp bash
...and here the "bash" process is in the right group, 2892, while "su"
is the one in the background!
Can you try to run strace on the su to see where things go wrong, i.e.
$ strace -f -e trace=process su foo
...and we're only interested in what happens up to the point where it
hangs. That should hopefully tell us which process is doing the wrong
thing. In either case, as Alan pointed out, this seems unlikely to be
a kernel problem.
[snip]
>> so can you please look for anything like that in your login scripts or
>> shell rc files?
>
> I do use stty in my .bashrc (that's why this happens), but I do not put
> it in the background.
Yeah, most likely the process that calls stty is first put in the
background itself (or never brought to the foreground?). But I don't
know why... when you get the trace, we can compare and find out where
it deviates.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-06-14 7:45 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 1:31 Joe Peterson
2008-06-02 5:12 ` Harald Dunkel
2008-06-02 5:32 ` Willy Tarreau
2008-06-02 5:55 ` Joe Peterson
2008-06-02 8:10 ` Alan Cox
2008-06-02 9:01 ` David Newall
2008-06-02 9:20 ` Alan Cox
2008-06-02 10:16 ` Vegard Nossum
2008-06-02 10:39 ` Vegard Nossum
2008-06-02 10:52 ` Alan Cox
2008-06-02 10:57 ` Vegard Nossum
2008-06-02 12:28 ` Alan Cox
2008-06-02 14:31 ` Vegard Nossum
2008-06-02 10:50 ` Alan Cox
2008-06-17 15:32 ` Joe Peterson
2008-06-02 15:26 ` Joe Peterson
2008-06-02 15:51 ` Alan Cox
2008-06-02 16:03 ` Joe Peterson
2008-06-04 14:43 ` Joe Peterson
2008-06-04 15:16 ` Alan Cox
2008-06-04 16:52 ` Joe Peterson
2008-06-04 17:10 ` Alan Cox
2008-06-04 20:32 ` Joe Peterson
2008-06-11 14:04 ` Joe Peterson
2008-06-12 11:52 ` Vegard Nossum
2008-06-14 1:49 ` Joe Peterson
2008-06-14 7:45 ` Vegard Nossum [this message]
2008-06-14 17:43 ` Joe Peterson
2008-06-14 20:34 ` Vegard Nossum
2008-06-14 20:52 ` Joe Peterson
2008-06-14 21:26 ` Vegard Nossum
2008-06-14 21:34 ` Joe Peterson
2008-07-02 18:03 ` tty session leader issue (was Re: 2.6.25.3: su gets stuck for root) Joe Peterson
2008-07-02 19:21 ` markus reichelt
2008-07-06 14:08 ` Tim Connors
2008-07-06 16:44 ` Alan Cox
2008-07-06 18:49 ` tty session leader issue [cause now known!] " Joe Peterson
2008-06-02 5:42 ` 2.6.25.3: su gets stuck for root Joe Peterson
-- strict thread matches above, loose matches on Subject: below --
2008-05-13 6:17 Harald Dunkel
2008-05-13 6:47 ` Vegard Nossum
2008-05-13 17:43 ` Harald Dunkel
2008-05-13 19:46 ` Willy Tarreau
2008-05-14 4:55 ` Harald Dunkel
2008-05-14 5:46 ` Willy Tarreau
2008-05-14 7:34 ` Vegard Nossum
2008-05-14 17:05 ` Harald Dunkel
2008-05-14 17:17 ` Vegard Nossum
2008-05-14 17:35 ` Alan Cox
2008-05-18 17:56 ` Harald Dunkel
2008-05-18 17:51 ` Alan Cox
2008-05-20 19:01 ` Harald Dunkel
2008-05-20 19:12 ` david
2008-05-20 20:26 ` Harald Dunkel
2008-05-20 20:38 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0806140045l259bcb93ie4b7bfa2d73bd4d@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=davidn@davidnewall.com \
--cc=harald.dunkel@t-online.de \
--cc=joe@skyrush.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome