From: Ben Hutchings <ben@decadent.org.uk>
To: stable <stable@vger.kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
Subject: [stable 3.18+] block/sd: Fix device-imposed transfer length limits
Date: Fri, 01 Jan 2016 19:51:35 +0000 [thread overview]
Message-ID: <1451677895.28485.3.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
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.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names taken.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next reply other threads:[~2016-01-01 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 19:51 Ben Hutchings [this message]
2016-01-01 20:30 ` [stable 3.18+] block/sd: Fix device-imposed transfer length limits Holger Hoffstätte
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=1451677895.28485.3.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=martin.petersen@oracle.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).