Messages in this thread | | | Date | Wed, 27 Feb 2008 12:41:57 -0500 | From | "Kevin Coffman" <> | Subject | Re: 2.6.24-sha1: RIP [<ffffffff802596c8>] iov_iter_advance+0x38/0x70 |
| |
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.
K.C.
| |