From: "Julio Auto" <mindvortex@gmail.com>
To: "Solar Designer" <solar@openwall.com>
Cc: "Willy Tarreau" <w@1wt.eu>, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] loop.c: kernel_thread() retval check - 2.6.17.9
Date: Mon, 28 Aug 2006 01:52:47 -0300 [thread overview]
Message-ID: <18d709710608272152g4995e492k7e832178ac30bfa0@mail.gmail.com> (raw)
In-Reply-To: <20060828035556.GA27902@openwall.com>
On 8/28/06, Solar Designer <solar@openwall.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
prev parent reply other threads:[~2006-08-28 4:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 6:41 Julio Auto
2006-08-28 3:55 ` Solar Designer
2006-08-28 4:41 ` Andrew Morton
2006-08-28 5:03 ` Julio Auto
2006-08-28 12:50 ` Serge E. Hallyn
2006-08-28 4:52 ` Julio Auto [this message]
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=18d709710608272152g4995e492k7e832178ac30bfa0@mail.gmail.com \
--to=mindvortex@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solar@openwall.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®