From: Davidlohr Bueso <dave@stgolabs.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Fabian Frederick <fabf@skynet.be>,
Davidlohr Bueso <dbueso@suse.de>,
Manfred Spraul <manfred@colorfullife.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH V2 linux-next] ipc/msg.c: fix memory leak in do_msgsnd()
Date: Mon, 1 Aug 2016 12:10:24 -0700 [thread overview]
Message-ID: <20160801191024.GD31421@linux-80c1.suse> (raw)
In-Reply-To: <20160801122437.GB18162@kroah.com>
On Mon, 01 Aug 2016, Greg KH wrote:
>This is not the correct way to submit patches for inclusion in the
>stable kernel tree. Please read Documentation/stable_kernel_rules.txt
>for how to do this properly.
I introduced this issue in 53dad6d3a8e (ipc: fix race with LSMs)
How about:
Cc: stable@kernel.org # v3.12
Thanks,
Davidlohr
next prev parent reply other threads:[~2016-08-01 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 11:40 [PATCH V2 linux-next] ipc/msg.c: fix memory leak in do_msgsnd() Fabian Frederick
2016-08-01 12:24 ` Greg KH
2016-08-01 19:10 ` Davidlohr Bueso [this message]
2016-08-01 18:57 ` Davidlohr Bueso
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=20160801191024.GD31421@linux-80c1.suse \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=dbueso@suse.de \
--cc=fabf@skynet.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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