From: Mark Brown <broonie@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Ian Abbott <abbotti@mev.co.uk>,
linux-spi <linux-spi@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
"3.8+" <stable@vger.kernel.org>
Subject: Re: [PATCH] spi: spidev: fix possible arithmetic overflow for multi-transfer message
Date: Mon, 23 May 2016 12:15:21 +0100 [thread overview]
Message-ID: <20160523111521.GQ8206@sirena.org.uk> (raw)
In-Reply-To: <CAKdAkRTEWthr6+FjkyukKN0-1YDAziy91Ww+tTOOE4MGkH2k1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Sat, May 21, 2016 at 09:50:35AM -0700, Dmitry Torokhov wrote:
> On Mon, Mar 23, 2015 at 10:50 AM, Ian Abbott <abbotti@mev.co.uk> wrote:
> > `spidev_message()` sums the lengths of the individual SPI transfers to
> > determine the overall SPI message length. It restricts the total
> > length, returning an error if too long, but it does not check for
As documented in SubmittingPatches please send patches to the
maintainers for the code you would like to change. The normal kernel
workflow is that people apply patches from their inboxes, if they aren't
copied they are likely to not see the patch at all and it is much more
difficult to apply patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-23 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 17:50 [PATCH] spi: spidev: fix possible arithmetic overflow for multi-transfer message Ian Abbott
2015-03-23 18:50 ` Mark Brown
2015-03-23 19:29 ` Ian Abbott
2015-03-23 21:01 ` Mark Brown
2016-05-21 16:50 ` Dmitry Torokhov
2016-05-23 10:20 ` Ian Abbott
2016-05-23 17:04 ` Dmitry Torokhov
2016-05-23 11:15 ` Mark Brown [this message]
2016-05-23 11:23 ` Ian Abbott
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=20160523111521.GQ8206@sirena.org.uk \
--to=broonie@kernel.org \
--cc=abbotti@mev.co.uk \
--cc=dan.carpenter@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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