All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinpu Wang <jinpu.wang@profitbricks.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>,
	Michael Wang <yun.wang@profitbricks.com>
Subject: Re: [PATCH 0/2] bio order fix backport for 4.4
Date: Thu, 6 Apr 2017 09:50:32 +0200	[thread overview]
Message-ID: <CAMGffEnq2omRWodpmra-Rj=iT_fX_kTOEScJA_Y82yt93NW7og@mail.gmail.com> (raw)
In-Reply-To: <20170406074323.GH14752@kroah.com>

On Thu, Apr 6, 2017 at 9:43 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Mon, Apr 03, 2017 at 11:41:17AM +0200, Jack Wang wrote:
>> From: Jack Wang <jinpu.wang@profitbricks.com>
>>
>> Hi,
>>
>> Please consider apply both fix for bio order, it fixes dead lock in
>> MD/DRBD.
>>
>> I backported to 4.4, and also tested on 4.4.50.
>>
>> Both patches apply cleanly on 4.4.59.
>
> Any reason these shouldn't also go into 4.10 and 4.9-stable?  They look
> like they belong there, and I don't want patches in 4.4 that are not in
> other stable trees, that wouldn't make any sense and would cause
> regressions when people upgrade.
>
> thanks,
>
> greg k-h

Thanks, Greg,

It makes sense to apply to also 4.9 and 4.10.

-- 
Jack Wang
Linux Kernel Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Tel:       +49 30 577 008  042
Fax:      +49 30 577 008 299
Email:    jinpu.wang@profitbricks.com
URL:      https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss

      reply	other threads:[~2017-04-06  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  9:41 [PATCH 0/2] bio order fix backport for 4.4 Jack Wang
2017-04-03  9:41 ` [PATCH 1/2] blk: improve order of bio handling in generic_make_request() Jack Wang
2017-04-03  9:41 ` [PATCH 2/2] blk: Ensure users for current->bio_list can see the full list Jack Wang
2017-04-06  7:43 ` [PATCH 0/2] bio order fix backport for 4.4 Greg KH
2017-04-06  7:50   ` Jinpu Wang [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='CAMGffEnq2omRWodpmra-Rj=iT_fX_kTOEScJA_Y82yt93NW7og@mail.gmail.com' \
    --to=jinpu.wang@profitbricks.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=yun.wang@profitbricks.com \
    /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.