From: Willy Tarreau <w@1wt.eu>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: Vegard Nossum <vegard.nossum@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: su gets stuck for root
Date: Wed, 14 May 2008 07:46:34 +0200 [thread overview]
Message-ID: <20080514054634.GA2645@1wt.eu> (raw)
In-Reply-To: <482A70BC.3010607@t-online.de>
On Wed, May 14, 2008 at 06:55:24AM +0200, Harald Dunkel wrote:
> Willy Tarreau wrote:
> >
> >even as root ? Because if you run strace on "su" as a user, you will
> >lose the setuid which may change the conditions.
> >
>
> It gets stuck _only_ if I am root. Running su without root permission
> is no problem.
OK. That's quite strange.
> As written before, If I kick out the "stty intr '^C'" from root's
> .bashrc, then the second su succeeds. Running the stty command
> manually in this new shell is no problem.
>
> Can you reproduce this problem? It doesn't need XWindow or any
> special user. Simply login as root on tty2, and run "su". If it
> gets stuck, then you could login on tty3 and kill -9 ### the blocking
> stty.
I tried (I'm on 2.6.25.1). But neither "su", "su willy" nor "stty intr ^C"
caused such a problem unfortunately.
You may want to ask several people to test in the same environment as
yours (same distro, etc...) in order to find whether it's a user-land
bug or a kernel bug. Most likely it's a kernel bug or side effect which
is triggered by your version of su or stty.
> Regards
>
> Harri
Willy
next prev parent reply other threads:[~2008-05-14 5:46 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 6:17 2.6.25.3: su gets stuck for root 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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-06-02 5:42 ` Joe Peterson
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=20080514054634.GA2645@1wt.eu \
--to=w@1wt.eu \
--cc=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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