On Sun, Mar 2, 2008 at 11:38 PM, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
quoted text
>
> On Thursday 28 February 2008 04:41, Kevin Coffman wrote:
>  > On Mon, Feb 25, 2008 at 10:46 PM, Nick Piggin <nickpiggin@yahoo.com.au>
>  wrote:
>  > > On Wednesday 20 February 2008 09:01, Alexey Dobriyan wrote:
>  > > > On Tue, Feb 19, 2008 at 11:47:11PM +0300,  wrote:
>  > >  > > > Are you reproducing it simply by running the
>  > >  > > > ftest03 binary directly from the shell? How many times between
>  > >  > > > oopses? It is multi-process but no threads, so races should be
>  > >  > > > minimal down this path -- can you get an strace of the failing
>  > >  > > > process?
>  > >  >
>  > >  > Speaking of multi-proceseness, changing MAXCHILD to 1, nchild to 1,
>  > >  > AFAICS, generates one child which oopses the very same way (in
>  > >  > parallel with generic LTP) But, lowering MAXIOVCNT to 8 generates no
>  > >  > oops.
>  > >
>  > >  Thanks, I was able to reproduce quite easily with these settings.
>  > >  I think I have the correct patch now (at least it isn't triggerable
>  > >  any more here).
>  > >
>  > >  Thanks,
>  > >  Nick
>  >
>  > Hi Nick,
>  > With this patch, I'm getting "bad data" errors while running the
>  > connectathon tests from a Solaris NFS client to my Linux server.  (The
>  > failing test writes a "big" file (1MB) and reads it back, verifying
>  > the data read back is correct.)  Let me know if I can provide more
>  > details.
>
>  Hmm, thanks for testing... Could it be caused by other bugs introduced
>  in the kernel you are testing? Is the failing test using writev to
>  write the file? Do you have any indication of the pattern of corruption?
>

Well, all I did was apply your patch and re-run the same tests I've
been running successfully.   (I'm still sitting at 2.6.25-rc1 right
now).  Sorry, I don't have details about the corruption.  I'm home
sick today, but I'll try to get more details when I get back in the
office.

K.C.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/