LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: 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: Wed, 20 Feb 2008 01:01:06 +0300	[thread overview]
Message-ID: <20080219220106.GB1756@martell.zuzino.mipt.ru> (raw)
In-Reply-To: <20080219204711.GA1756@martell.zuzino.mipt.ru>

On Tue, Feb 19, 2008 at 11:47:11PM +0300,  wrote:
> On Wed, Feb 13, 2008 at 03:42:02PM +1100, Nick Piggin wrote:
> > On Wednesday 13 February 2008 11:17, Nick Piggin wrote:
> > > On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote:
> > 
> > > > It's a trivial dumb module which does nothing but loads and unloads.
> > > > I redid ftest03 later without any suspicious activity and it oopsed the
> > > > same way.
> > >
> > > Ah crap. Hmm, maybe I didn't consider all cases with my last patch to
> > > that code... is there an easy way to get the ftest03 source and run
> > > it?
> > 
> > OK I didn't realise it is a test from ltp.
> > 
> > But I can't reproduce it for the life of me with the latest git kernel
> > and latest ltp tarball.
> > 
> > Is it easy to reproduce?
> 
> Well, yes. SMP, non-preemptible kernel, (and maxcpus=1 really helps!)
> 
> 	while true; do
> 		./ftest03
> 	done
> 
> This alone seems stable, but starting whole LTP in parallel downs the box
> very quickly.
> 
> > 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.

  reply	other threads:[~2008-02-19 22:01 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 [this message]
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
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=20080219220106.GB1756@martell.zuzino.mipt.ru \
    --to=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).