All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8
Date: Wed, 22 Jan 2014 11:52:08 +1100	[thread overview]
Message-ID: <20140122115208.6a2b3909@notabene.brown> (raw)
In-Reply-To: <1390242438.587.16.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

On Mon, 20 Jan 2014 19:27:18 +0100 Ian Kumlien <ian.kumlien@gmail.com> wrote:

> On mån, 2014-01-20 at 14:37 +1100, NeilBrown wrote:
> > 
> > Thanks - that extra info is quite useful.  Knowing that nothing else unusual
> > is happening can be quite valuable (and I don't like to assume).
> > 
> > I haven't found anything that would clearly cause your crash, but I have
> > found something that looks wrong and conceivably could.
> > 
> > Could you please try this patch on top of what you are currently using?  By
> > the look of it you get a crash at least every day, often more often.  So if
> > this produces a day with no crashes, that would be promising.
> > 
> > The important aspect of the patch is that it moves the "atomic_inc" of
> > "sh->count" back under the protection of ->device_lock in the case when some
> > other thread might be using the same 'sh'.
> 
> I have been unable to trip this up, so this was it!
> 
> Tested-by: Ian Kumlien <ian.kumlien@gmail.com>
> 
> I hope this hits stable ASAP ;)

I've push it out into my for-next branch.
I'll probably send a pull request to Linus tomorrow.
It has some chance of getting into a -stable branch next week (though I'm not
really sure of the schedule).

Thanks again for testing and reporting!

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-01-22  0:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 22:00 [BUG] at drivers/md/raid5.c:291! kernel 3.13-rc8 Ian Kumlien
2014-01-19 23:21 ` Richard Weinberger
2014-01-20  0:38 ` NeilBrown
2014-01-20  0:49   ` Ian Kumlien
2014-01-20  3:37     ` NeilBrown
2014-01-20  9:22       ` Ian Kumlien
2014-01-20 18:27       ` Ian Kumlien
2014-01-20 18:27         ` Ian Kumlien
2014-01-22  0:52         ` NeilBrown [this message]
2014-01-23  0:00           ` Ian Kumlien

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=20140122115208.6a2b3909@notabene.brown \
    --to=neilb@suse.de \
    --cc=ian.kumlien@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.