From: Jeff Moyer <jmoyer@redhat.com>
To: "Ken Chen" <kenchen@google.com>
Cc: "Zach Brown" <zach.brown@oracle.com>,
akpm@linux-foundation.org, linux-aio@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] convert aio event reap to use atomic-op instead of spin_lock
Date: Thu, 12 Apr 2007 08:06:28 -0400 [thread overview]
Message-ID: <x49ejmp3igr.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <b040c32a0704120029u423bfd39pfa0479c3c678ebe2@mail.gmail.com> (Ken Chen's message of "Thu, 12 Apr 2007 00:29:28 -0700")
==> On Thu, 12 Apr 2007 00:29:28 -0700, "Ken Chen" <kenchen@google.com> said:
Ken> On 4/11/07, Ken Chen <kenchen@google.com> wrote:
Ken> > On 4/11/07, Zach Brown <zach.brown@oracle.com> wrote:
Ken> > > First, I'll NAK this and all AIO patches until the patch
Ken> description > > says that it's been run through the regression
Ken> tests that we've started > > collecting in autotest. They're
Ken> trivial to run, never fear:
Ken> >
Ken> > OK. I will run those regression tests.
Ken> Unfortunately, the aio_dio_bugs test in autotest has bug in it
Ken> :-( We need stress test the "test code".
Ken> on stock 2.6.21-rc6 kernel:
Ken> [rock-me-baby]$ cd autotest/tests/aio_dio_bugs/src
Ken> [rock-me-baby]$ make [rock-me-baby]$
Ken> ./aio-free-ring-with-bogus-nr-pages
Ken> aio-free-ring-with-bogus-nr-pages: Error: io_setup returned -22,
Ken> expected -ENOMEM
Ken> hmm??? The problem is that the test code forgot to initialized
Ken> ctx variable and in the kernel, sys_io_setup returns EINVAL if
Ken> user address contain none-zero value.
Zach had already sent a fix for that. I wonder why it didn't go in.
I didn't see any response to Zach's request for code that actually
tests out the shared ring buffer. Do you have such code?
-Jeff
next prev parent reply other threads:[~2007-04-12 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 23:53 [patch] convert aio event reap to use atomic-op instead of spin_lock Ken Chen
2007-04-11 5:18 ` Andrew Morton
2007-04-11 16:54 ` Ken Chen
2007-04-11 18:15 ` Zach Brown
2007-04-11 18:29 ` Ken Chen
2007-04-11 18:00 ` Zach Brown
2007-04-11 19:11 ` Andrew Morton
2007-04-11 19:34 ` Zach Brown
2007-04-11 19:28 ` Ken Chen
2007-04-11 19:44 ` Zach Brown
2007-04-11 19:45 ` Benjamin LaHaise
2007-04-11 19:52 ` Zach Brown
2007-04-11 20:03 ` Benjamin LaHaise
2007-04-12 7:29 ` Ken Chen
2007-04-12 12:06 ` Jeff Moyer [this message]
2007-04-13 0:57 ` Ken Chen
2007-04-13 1:08 ` Ken Chen
2007-04-12 7:50 ` Ken Chen
2007-04-12 14:31 ` Benjamin LaHaise
2007-04-12 15:13 ` Benjamin LaHaise
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=x49ejmp3igr.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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