public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: Unknown <borg@uu3.net>,
	linux-kernel@vger.kernel.org, dann frazier <dannf@debian.org>
Subject: Re: PROBLEM: 2.4.36.1 hangs.
Date: Sun, 24 Feb 2008 19:28:39 +0100	[thread overview]
Message-ID: <20080224182839.GA31199@1wt.eu> (raw)
In-Reply-To: <47C1B374.6030502@plouf.fr.eu.org>

On Sun, Feb 24, 2008 at 07:12:04PM +0100, Pascal Hambourg wrote:
> Hello,
> 
> Willy Tarreau wrote :
> >
> >On Fri, Feb 22, 2008 at 03:08:30PM +0100, Unknown wrote:
> >
> >>2) 2.4.36.1 hangs during compilation of lighttpd-1.4.18.
> >>  It is probably during ext2_readdir() but I cannot confirm that..
> >>  Currently it only happens during compilation of lighttpd-1.4.18, always
> >>  in the same place. [...]
> 
> I experience the same problem when executing "ls /etc".
> 
> >OK, could you please try to revert the attached patch (patch -Rp1) to see 
> >if
> >this fixes the problem for you ? Please keep Dann and me in CC as it's not
> >easy to spot 2.4-related threads on LKML these days!
> >
> >----
> >
> >commit c30306fb287323591c854a0982d9fa5351859b45
> >Author: dann frazier <dannf@debian.org>
> >Date:   Mon Jan 21 17:13:06 2008 -0700
> >
> >    ext2_readdir() filp->f_pos fix
> 
> The patch didn't revert cleanly because of the two subsequent 
> ext2-related patches, so I had to revert the three of them. It fixed the 
> problem. Then I applied only the "ext2_readdir() filp->f_pos fix" patch 
> again and the problem came back. HTH.

OK thanks very much Pascal.

I'm reverting the patch for the moment and will release 2.4.36.2 without
it.

Dann, it looks like the backport of the fix causes more trouble than it
attempts to fix :-/

(Un)fortunately I had no problem here, so I think it's not that easy to
reproduce the issue. If the fix is too hard to get right and the risk
of vulnerability very low, don't you think we should simply leave it
unfixed, at least until we really understand the nature of the problem ?

Thanks,
Willy


  reply	other threads:[~2008-02-24 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 14:08 PROBLEM: 2.4.36.1 hangs Unknown
2008-02-23  8:30 ` Willy Tarreau
2008-02-24 18:12   ` Pascal Hambourg
2008-02-24 18:28     ` Willy Tarreau [this message]
2008-02-26  7:36   ` Glen Nakamura
2008-02-26  8:16     ` Willy Tarreau
2008-02-26 10:13       ` dann frazier
2008-02-26 10:27         ` Willy Tarreau
2008-02-26 13:54         ` Pascal Hambourg

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=20080224182839.GA31199@1wt.eu \
    --to=w@1wt.eu \
    --cc=borg@uu3.net \
    --cc=dannf@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pascal.mail@plouf.fr.eu.org \
    /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