From: Willy Tarreau <w@1wt.eu>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [ 0/9] 2.6.32.63-longterm review
Date: Sat, 14 Jun 2014 21:12:50 +0200 [thread overview]
Message-ID: <20140614191250.106515056@1wt.eu> (raw)
Message-ID: <57d1129d02f4fc14423dd66474950cb7@local> (raw)
[ sorry for those who receive this series twice, I had an issue with
the first attempt that prevented it from reaches the mailing lists ]
This is the start of the longterm review cycle for the 2.6.32.63 release.
All patches will be posted as a response to this one. If anyone has any
issue with these being applied, please let me know. If anyone is a
maintainer of the proper subsystem, and wants to add a Signed-off-by: line
to the patch, please respond with it.
Responses should be made within 72 hours. Anything received after that time
might be too late. If someone wants a bit more time for a deeper review,
please let me know.
The whole patch series can be found in one patch at :
kernel.org/pub/linux/kernel/v2.6/longterm-review/patch-2.6.32.63-rc1.gz
The shortlog and diffstat are appended below.
Thanks,
Willy
include/linux/ethtool.h | 4 +-
kernel/auditsc.c | 25 +++--
kernel/futex.c | 243 +++++++++++++++++++++++++++++++++++----------
net/core/ethtool.c | 17 +++-
net/core/sysctl_net_core.c | 3 +-
net/ipv4/sysctl_net_ipv4.c | 3 +-
6 files changed, 228 insertions(+), 67 deletions(-)
next reply other threads:[~2014-06-14 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57d1129d02f4fc14423dd66474950cb7@local>
2014-06-14 19:12 ` Willy Tarreau [this message]
2014-06-14 19:12 ` [ 1/9] ethtool: Report link-down while interface is down Willy Tarreau
2014-06-14 19:12 ` [ 2/9] futex: Add another early deadlock detection check Willy Tarreau
2014-06-14 19:12 ` [ 3/9] futex: Prevent attaching to kernel threads Willy Tarreau
2014-06-14 19:12 ` [ 4/9] futex-prevent-requeue-pi-on-same-futex.patch futex: Willy Tarreau
2014-06-14 19:12 ` [ 5/9] futex: Validate atomic acquisition in Willy Tarreau
2014-06-14 19:12 ` [ 6/9] futex: Always cleanup owner tid in unlock_pi Willy Tarreau
2014-06-14 19:12 ` [ 7/9] futex: Make lookup_pi_state more robust Willy Tarreau
2014-06-14 19:12 ` [ 8/9] auditsc: audit_krule mask accesses need bounds checking Willy Tarreau
2014-06-14 19:12 ` [ 9/9] net: fix regression introduced in 2.6.32.62 by sysctl Willy Tarreau
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=20140614191250.106515056@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®