From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: agartrell@fb.com, "davem@davemloft.net" <davem@davemloft.net>,
mst@redhat.com, jasowang@redhat.com, herbert@gondor.apana.org.au,
viro@zeniv.linux.org.uk, Ben Hutchings <ben@decadent.org.uk>,
xii@google.com, vyasevich@gmail.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: [PATCH][v3.19.y] tun: return proper error code from tun_do_read
Date: Tue, 28 Apr 2015 16:27:31 -0400 [thread overview]
Message-ID: <553FED33.8020406@canonical.com> (raw)
Hello,
Please consider including mainline commit
957f094f221f81e457133b1f4c4d95ffa49ff731 in the next v3.19.y release.
It was included in the mainline tree as of v4.0-rc1. It has been tested
and confirmed to resolve:
http://bugs.launchpad.net/bugs/1448942
And upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=90901
The bug was introduce in v3.19-rc1 by commit 9b067034d0, so it is not
needed in any other stable kernels.
commit 957f094f221f81e457133b1f4c4d95ffa49ff731
Author: Alex Gartrell <agartrell@fb.com>
Date: Thu Dec 25 23:22:49 2014 -0800
tun: return proper error code from tun_do_read
Sincerely,
Joseph Salisbury
next reply other threads:[~2015-04-28 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:27 Joseph Salisbury [this message]
2015-04-28 21:15 ` [PATCH][v3.19.y] tun: return proper error code from tun_do_read Josh Boyer
2015-04-28 21:18 ` 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=553FED33.8020406@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=agartrell@fb.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vyasevich@gmail.com \
--cc=xii@google.com \
/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).