linux-kernel - Re: [PATCH] loop.c: kernel

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1156115468.4051.80.camel@localhost.localdomain>
Date:	Mon, 21 Aug 2006 00:11:08 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Solar Designer <solar@...nwall.com>
Cc:	Willy Tarreau <wtarreau@...a.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] loop.c: kernel_thread() retval check

Ar Llu, 2006-08-21 am 02:34 +0400, ysgrifennodd Solar Designer:
> Alan,
> 
> On Sun, Aug 20, 2006 at 07:15:17PM +0100, Alan Cox wrote:
> > Acked-by: Alan Cox <alan@...hat.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? 

I have no problem with it going into 2.4. Someone should forward port it
- but there should be plenty of people on the lists to do that.

-
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/