linux-kernel - Re: [PATCH] loop.c: kernel_thread() retval check

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: <18d709710608272152g4995e492k7e832178ac30bfa0@mail.gmail.com>
Date:	Mon, 28 Aug 2006 01:52:47 -0300
From:	"Julio Auto" <mindvortex@...il.com>
To:	"Solar Designer" <solar@...nwall.com>
Cc:	"Willy Tarreau" <w@....eu>, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH] loop.c: kernel_thread() retval check - 2.6.17.9

On 8/28/06, Solar Designer <solar@...nwall.com> wrote:
> I think that testing this on a single machine is fine, but it is
> preferable that you also check for any resource leaks.  That is, replace
> the kernel_thread() call with -EAGAIN, then run losetup in a loop and
> see whether the system possibly leaks a resource.  I did apply this sort
> of testing to my original 2.4 patch.
>

That was exactly the approach I took. :)


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