From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: gregkh@linuxfoundation.org, luis.henriques@canonical.com,
sasha.levin@oracle.com, kamal.mostafa@canonical.com,
jslaby@suse.cz
Cc: peter@hurleysoftware.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [3.14.y][3.16.y-ckt][3.18.y][3.19.y][PATCH 0/1] n_tty: Fix read buffer overwrite when no newline
Date: Wed, 15 Apr 2015 13:39:02 -0400 [thread overview]
Message-ID: <cover.1428325695.git.joseph.salisbury@canonical.com> (raw)
Hello,
Please consider including upstream commit fb5ef9e7da39968fec6d6f37f20a23d23740c75e
in the next v3.14.y, 3.16.y-ckt, 3.18.y, and 3.19.y stable releases. It was
included upstream 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 kernel versions mentined, so I performed
a backport, which is in email 1/1.
The 3.12.y and 3.13.y-ckt upstrem kernels can't use the cherry pick of fb5ef9e7
becuase smp_load_acquire was not introduced until 3.14-rc1. I'll look into
alternative way that this bug could be fixed in 3.12.y and 3.13.y-ckt.
Sincerely,
Joseph Salisbury
Peter Hurley (1):
n_tty: Fix read buffer overwrite when no newline
drivers/tty/n_tty.c | 108 +++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 81 insertions(+), 27 deletions(-)
--
2.1.0
next reply other threads:[~2015-04-15 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 17:39 Joseph Salisbury [this message]
2015-04-15 17:39 ` [3.14.y][3.16.y-ckt][3.18.y][3.19.y][PATCH 1/1] n_tty: Fix read buffer overwrite when no newline Joseph Salisbury
2015-04-15 18:25 ` Peter Hurley
2015-04-15 18:55 ` Joseph Salisbury
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=cover.1428325695.git.joseph.salisbury@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=gregkh@linuxfoundation.org \
--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 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).