From: Kamal Mostafa <kamal@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: gregkh@linuxfoundation.org, luis.henriques@canonical.com,
sasha.levin@oracle.com, kamal.mostafa@canonical.com,
jslaby@suse.cz, peter@hurleysoftware.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [v3.12.y][v3.13.y-ckt][3.14.y][3.16.y-ckt][3.18.y][3.19.y][V2][PATCH 0/1] n_tty: Fix read buffer overwrite when no newline
Date: Fri, 01 May 2015 08:57:50 -0700 [thread overview]
Message-ID: <1430495870.25872.14.camel@fourier> (raw)
In-Reply-To: <cover.1429130715.git.joseph.salisbury@canonical.com>
On Thu, 2015-04-16 at 14:57 -0400, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit fb5ef9e7da39968fec6d6f37f20a23d23740c75e
> in the next v3.12.y, v3.13.y-ckt, v3.14.y, 3.16.y-ckt, 3.18.y, and 3.19.y stable releases.
> It was included mainline as of v4.0-rc1. It has been tested and confirmed to resolve
> http://bugs.launchpad.net/bugs/1381005 . This bug was introduced in v3.12-rc1 when
> commit 24a89d1 was applied. This commit is not needed in stable kernels prior to
> v3.12.y.
>
>
> commit fb5ef9e7da39968fec6d6f37f20a23d23740c75e
> Author: Peter Hurley <peter@hurleysoftware.com>
> Date: Fri Jan 16 15:05:39 2015 -0500
>
> n_tty: Fix read buffer overwrite when no newline
>
>
> This commit does not apply cleanly to the kernels versions mentined, so I performed
> a backport, which is in email 1/1.
>
> The 3.12.y and 3.13.y-ckt stable releases first need a cherry pick of commit
> 5c32d12378313e0096ea0d450462aa638a90fb6e. This is because in commit 5c32d123
> n_tty_receive_buf and n_tty_receive_buf2 were merged into n_tty_receive_buf_common,
> which is where the backport makes the needed changes.
>
>
> Sincerely,
>
> Joseph Salisbury
>
> Peter Hurley (1):
> n_tty: Fix read buffer overwrite when no newline
>
> drivers/tty/n_tty.c | 106 +++++++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 79 insertions(+), 27 deletions(-)
>
Queued up for 3.13-stable. Thanks, Joseph and Peter!
-Kamal
prev parent reply other threads:[~2015-05-01 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 18:57 [v3.12.y][v3.13.y-ckt][3.14.y][3.16.y-ckt][3.18.y][3.19.y][V2][PATCH 0/1] n_tty: Fix read buffer overwrite when no newline Joseph Salisbury
2015-04-16 18:57 ` [v3.12.y][v3.13.y-ckt][3.14.y][3.16.y-ckt][3.18.y][3.19.y][V2][PATCH 1/1] " Joseph Salisbury
2015-04-21 16:15 ` [v3.12.y][v3.13.y-ckt][3.14.y][3.16.y-ckt][3.18.y][3.19.y][V2][PATCH 0/1] " Jiri Slaby
2015-04-22 13:18 ` Luis Henriques
2015-04-22 13:18 ` Luis Henriques
2015-05-01 15:57 ` Kamal Mostafa [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=1430495870.25872.14.camel@fourier \
--to=kamal@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=joseph.salisbury@canonical.com \
--cc=jslaby@suse.cz \
--cc=kamal.mostafa@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=peter@hurleysoftware.com \
--cc=sasha.levin@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 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.