linux-kernel - Re: Hang in 2.6.23-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070905191145.31003be2@hyperion.delvare>
Date:	Wed, 5 Sep 2007 19:11:45 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Patrick Mau <mau@...ar.ping.de>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Hang in 2.6.23-rc5

On Mon, 3 Sep 2007 08:39:04 +0200, Patrick Mau wrote:
> On Mon, Sep 03, 2007 at 04:15:01AM +0530, Satyam Sharma wrote:
> > That's my impression as well. That's way too core/busy a codepath to have
> > a bug in. As I said earlier, almost anybody testing -rc5 is sure to hit
> > this within a few hours (probably less) -- sad, it greatly erodes from the
> > usefulness of -rc5 as a release candidate.
> 
> The above patch also fixed my problems using NFS mounted home directories.
> 
> I already applied it yesterday without giving any feedback, so I just
> thought I should comment.
> 
> In addition I totally agree with Satyam's comment above: either
> anybody is testing rc's these days, or people simply stopped reporting.

I've hit the problem, found this thread, found the proposed patch and
tried it. Presumably others did the same. It's not easy to report a
hang which leaves no message in the logs and happens at random,
infrequent times. It takes time to gather enough information to make a
useful report. And it takes time to make sure that the patch actually
fixed the problem, too.

(Satyam's estimation that everybody would hit the bug within an hour
doesn't match my experience, I had "only" 2 freezes in 60 hours or so.)

> My concern is that we have to live with a git tree that has this
> problem, because core developers are unavailable and nobody has the
> authority to commit this fix. (That was already posted before).

The fix appears to be in the tree already, so you needn't worry.

-- 
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/