LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Kevin Coffman" <kwc@citi.umich.edu>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: "Alexey Dobriyan" <adobriyan@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-sha1: RIP [<ffffffff802596c8>] iov_iter_advance+0x38/0x70
Date: Mon, 3 Mar 2008 08:30:51 -0500	[thread overview]
Message-ID: <4d569c330803030530j76a47249ic4e3eb2d86283d6f@mail.gmail.com> (raw)
In-Reply-To: <200803031538.35271.nickpiggin@yahoo.com.au>

On Sun, Mar 2, 2008 at 11:38 PM, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> 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.

  reply	other threads:[~2008-03-03 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 14:00 Alexey Dobriyan
2008-02-10 17:46 ` Alexey Dobriyan
2008-02-12 22:04 ` Andrew Morton
2008-02-12 22:27   ` Alexey Dobriyan
2008-02-13  0:17     ` Nick Piggin
2008-02-13  4:42       ` Nick Piggin
2008-02-19 20:47         ` Alexey Dobriyan
2008-02-19 22:01           ` Alexey Dobriyan
2008-02-26  3:46             ` Nick Piggin
2008-02-27 17:41               ` Kevin Coffman
2008-03-03  4:38                 ` Nick Piggin
2008-03-03 13:30                   ` Kevin Coffman [this message]
2008-03-03 16:41                     ` Nick Piggin
2008-02-19  1:20     ` Nick Piggin
2008-02-19 19:22       ` Kevin Coffman

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=4d569c330803030530j76a47249ic4e3eb2d86283d6f@mail.gmail.com \
    --to=kwc@citi.umich.edu \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --subject='Re: 2.6.24-sha1: RIP [<ffffffff802596c8>] iov_iter_advance+0x38/0x70' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).