mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ed Cashin <ecashin@coraid.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>, Josh Boyer <jwboyer@redhat.com>,
	"mitko@banksoft-bg.com" <mitko@banksoft-bg.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-team@fedoraproject.org" <kernel-team@fedoraproject.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ed Cashin <ecashin@coraid.com>
Subject: Re: Oops on aoe module removal
Date: Sun, 13 Jan 2013 08:23:43 -0600	[thread overview]
Message-ID: <EA664C14-1CAC-4F04-8E27-4544DA3CC3BE@coraid.com> (raw)
In-Reply-To: <1358055265.4514.67.camel@deadeye.wl.decadent.org.uk>

On Jan 13, 2013, at 12:34 AM, Ben Hutchings wrote:
...
[Nice info on stable maintainers, thanks.]
...
> Given that aoe is basically unchanged between Linux 2.6.32 and 3.6 I
> agree that the one patch should be sufficient.  However your previous
> patch was lacking a signoff or much of a commit message, so please do
> re-post it with those.  The commit message should include a reference to
> the corresponding mainline commit as you identified above.

OK.  Got it:

  [PATCH <= 3.6.y] aoe: do not call bdi_init after blk_alloc_queue
  http://thread.gmane.org/gmane.linux.kernel.stable/38957

That particular change (for <= 3.6.y)  is not derived from the mainline 
commit you mention, but the other patch for 3.7.y is, and I included a 
reference to the mainline commit in the changelog message for the 
3.7.y fix.

  [PATCH 3.7.y] aoe: merge 0a41409c5180 to avoid list corruption from extra bdi_init
  http://thread.gmane.org/gmane.linux.kernel.stable/38909

-- 
  Ed Cashin
  ecashin@coraid.com



      reply	other threads:[~2013-01-13 14:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 13:25 Josh Boyer
2013-01-03 14:02 ` Ed Cashin
2013-01-03 14:09   ` Jens Axboe
2013-01-03 14:12     ` Jens Axboe
2013-01-03 15:28       ` Ed Cashin
2013-01-03 15:34         ` Jens Axboe
2013-01-03 18:15           ` Ed Cashin
2013-01-03 19:28             ` Ed Cashin, Ed Cashin
2013-01-03 19:45               ` Jens Axboe
2013-01-03 19:57                 ` Ed Cashin
2013-01-03 20:50                   ` Ed Cashin
2013-01-03 21:00                     ` Josh Boyer
2013-01-04 12:35                       ` Josh Boyer
2013-01-03 21:20                     ` Ed Cashin
2013-01-13  5:34                       ` Ben Hutchings
2013-01-13 14:23                         ` Ed Cashin [this message]

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=EA664C14-1CAC-4F04-8E27-4544DA3CC3BE@coraid.com \
    --to=ecashin@coraid.com \
    --cc=axboe@kernel.dk \
    --cc=ben@decadent.org.uk \
    --cc=jwboyer@redhat.com \
    --cc=kernel-team@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitko@banksoft-bg.com \
    --cc=peterz@infradead.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®