From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
stable@vger.kernel.org
Subject: [ 0/1] 3.4.33-stable review
Date: Mon, 18 Feb 2013 10:24:55 -0800 [thread overview]
Message-ID: <20130218181454.615592566@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 3.4.33 release.
There is 1 patch in this series, which will be posted as a response to
this one. If anyone has any issues with it being applied, please let me
know.
Responses should be made by Wed Feb 20 18:13:44 UTC 2013.
Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.4.33-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 3.4.33-rc1
Alexandre SIMON <Alexandre.Simon@univ-lorraine.fr>
printk: fix buffer overflow when calling log_prefix function from call_console_drivers
-------------
Diffstat:
Makefile | 4 ++--
include/linux/syslog.h | 6 ++++++
kernel/printk.c | 13 ++++++++++++-
3 files changed, 20 insertions(+), 3 deletions(-)
next reply other threads:[~2013-02-18 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:24 Greg Kroah-Hartman [this message]
2013-02-18 18:24 ` [ 1/1] printk: fix buffer overflow when calling log_prefix function from call_console_drivers Greg Kroah-Hartman
2013-02-20 13:02 ` Satoru Takeuchi
2013-02-20 13:43 ` Alexandre SIMON
2013-02-20 15:56 ` Satoru Takeuchi
2013-02-19 2:50 ` [ 0/1] 3.4.33-stable review Shuah Khan
2013-02-20 2:51 ` Greg Kroah-Hartman
2013-02-20 3:31 ` Shuah Khan
2013-02-20 13:09 ` Satoru Takeuchi
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=20130218181454.615592566@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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.