From: Willy Tarreau <w@1wt.eu>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: stable@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 2.6.32-4.0] sg_start_req(): make sure that there's not too many elements in iovec
Date: Sat, 1 Aug 2015 19:33:22 +0200 [thread overview]
Message-ID: <20150801173322.GA22770@1wt.eu> (raw)
In-Reply-To: <1438449959.3225.18.camel@decadent.org.uk>
On Sat, Aug 01, 2015 at 06:25:59PM +0100, Ben Hutchings wrote:
> From: Al Viro <viro@zeniv.linux.org.uk>
>
> commit 451a2886b6bf90e2fb378f7c46c655450fb96e81 upstream.
(...)
> It looks like this bug was introduced in 2.6.28 by commit 10db10d144c0
> ("sg: convert the indirect IO path to use the block layer"), so the fix
> is needed for all stable branches.
Patch queued for 2.6.32, thanks Ben.
willy
next prev parent reply other threads:[~2015-08-01 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 17:25 [PATCH 2.6.32-4.0] sg_start_req(): make sure that there's not too many elements in iovec Ben Hutchings
2015-08-01 17:33 ` Willy Tarreau [this message]
2015-08-03 9:56 ` Jiri Slaby
2015-08-10 9:26 ` Luis Henriques
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=20150801173322.GA22770@1wt.eu \
--to=w@1wt.eu \
--cc=ben@decadent.org.uk \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).