public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Patrick Mau <mau@oscar.ping.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hang in 2.6.23-rc5
Date: Wed, 5 Sep 2007 19:11:45 +0200	[thread overview]
Message-ID: <20070905191145.31003be2@hyperion.delvare> (raw)
In-Reply-To: <20070903063904.GA1935@oscar.prima.de>

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

  parent reply	other threads:[~2007-09-05 17:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02 18:42 Hang in 2.6.23-rc5 daryll q
2007-09-02 19:05 ` charles gagalac
2007-09-02 20:38   ` Alessandro Suardi
2007-09-02 21:26     ` Satyam Sharma
2007-09-02 21:29     ` FD Cami
2007-09-02 21:46       ` Alexey Dobriyan
2007-09-02 22:45         ` Satyam Sharma
2007-09-02 23:10           ` Alessandro Suardi
2007-09-03  6:39           ` Patrick Mau
2007-09-04  9:32             ` Romano Giannetti
2007-09-05 17:11             ` Jean Delvare [this message]
2007-09-05 22:02               ` Satyam Sharma
2007-09-08  9:37           ` FD Cami
2007-09-03 21:04         ` Robert Fitzsimons
2007-09-02 22:05     ` Richard Mittendorfer
2007-09-02 22:14       ` Jesper Juhl
  -- strict thread matches above, loose matches on Subject: below --
2007-09-02 20:21 Andrew

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=20070905191145.31003be2@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mau@oscar.ping.de \
    /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