From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: stable@vger.kernel.org
Subject: Re: [stable 3.18+] block/sd: Fix device-imposed transfer length limits
Date: Fri, 1 Jan 2016 20:30:15 +0000 (UTC) [thread overview]
Message-ID: <pan.2016.01.01.20.30.15@googlemail.com> (raw)
In-Reply-To: 1451677895.28485.3.camel@decadent.org.uk
On Fri, 01 Jan 2016 19:51:35 +0000, Ben Hutchings wrote:
> Please pick the following commit for 3.18-stable and later stable
> branches:
>
> commit ca369d51b3e1649be4a72addd6d6a168cfb3f537
> Author: Martin K. Petersen <martin.petersen@oracle.com>
> Date: Fri Nov 13 16:46:48 2015 -0500
>
> block/sd: Fix device-imposed transfer length limits
>
> It fixes a regression that was introduced in 4.2 and then backported to
> those stable branches.
Just a heads-up that this will require some additional backporting love,
since it breaks compilation of older md due to (I think) commit
8ae126660fddbe ("block: kill merge_bvec_fn() completely").
I tried to merge this into my 4.1++ (because SMR drama) but offhand
didn't know how to fix the conflict in md, so maybe someone more familiar
with the block layer/bio merging can help.
-h
prev parent reply other threads:[~2016-01-01 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 19:51 [stable 3.18+] block/sd: Fix device-imposed transfer length limits Ben Hutchings
2016-01-01 20:30 ` Holger Hoffstätte [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=pan.2016.01.01.20.30.15@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).