public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Willy Tarreau <wtarreau@hera.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] loop.c: kernel_thread() retval check
Date: Mon, 21 Aug 2006 02:34:42 +0400	[thread overview]
Message-ID: <20060820223442.GA21960@openwall.com> (raw)
In-Reply-To: <1156097717.4051.26.camel@localhost.localdomain>

Alan,

On Sun, Aug 20, 2006 at 07:15:17PM +0100, Alan Cox wrote:
> Acked-by: Alan Cox <alan@redhat.com>

Thanks.

> but should go into 2.6-mm and be tested in 2.6-mm before 2.4 backport.

Unfortunately, I do not intend to prepare/test/submit a revision of the
patch for 2.6-mm, and I might only work on a 2.6 patch in a few months
from now.  Unless someone else takes care of this, the fix is likely to
get dropped on the floor.

Do you really think that getting this fix into 2.4 should be delayed
like that?  Please note that the patch affects error path only and that
without the patch things misbehave badly whenever the error occurs.
I really don't think the patch can make things worse, even if it were
buggy (although it's been tested with the error path triggered
specifically on 2.4).

Alexander

  reply	other threads:[~2006-08-20 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19 23:46 [PATCH] loop.c: kernel_thread() retval check Solar Designer
2006-08-20  7:21 ` Willy Tarreau
2006-08-20 14:32   ` Solar Designer
2006-08-20 18:15 ` Alan Cox
2006-08-20 22:34   ` Solar Designer [this message]
2006-08-20 23:11     ` Alan Cox
2006-08-20 22:58       ` Willy Tarreau
2006-08-21  1:59         ` Julio Auto
2006-08-21  2:32           ` Solar Designer
2006-08-21  2:47             ` Julio Auto

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=20060820223442.GA21960@openwall.com \
    --to=solar@openwall.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wtarreau@hera.kernel.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