From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jann@thejh.net, stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "exec: Ensure mm->user_ns contains the execed files" has been added to the 4.4-stable tree
Date: Thu, 05 Jan 2017 09:51:51 +1300 [thread overview]
Message-ID: <87eg0i1rbs.fsf@xmission.com> (raw)
In-Reply-To: <20170104105800.GA2875@kroah.com> (Greg KH's message of "Wed, 4 Jan 2017 11:58:00 +0100")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Wed, Jan 04, 2017 at 11:32:41AM +0100, Greg KH wrote:
>> On Wed, Jan 04, 2017 at 11:05:53AM +0100, gregkh@linuxfoundation.org wrote:
>> >
>> > This is a note to let you know that I've just added the patch titled
>> >
>> > exec: Ensure mm->user_ns contains the execed files
>> >
>> > to the 4.4-stable tree which can be found at:
>> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>> >
>> > The filename of the patch is:
>> > exec-ensure-mm-user_ns-contains-the-execed-files.patch
>> > and it can be found in the queue-4.4 subdirectory.
>> >
>> > If you, or anyone else, feels it should not be added to the stable tree,
>> > please let <stable@vger.kernel.org> know about it.
>>
>> Oops, nope, this broke the build too, now dropped.
>
> And I've now fixed it, sorry for the noise...
When I have several patches that have dependencies like this is there
something I can do to make backporting them easier?
Eric
next prev parent reply other threads:[~2017-01-04 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 10:05 Patch "exec: Ensure mm->user_ns contains the execed files" has been added to the 4.4-stable tree gregkh
2017-01-04 10:32 ` Greg KH
2017-01-04 10:58 ` Greg KH
2017-01-04 20:51 ` Eric W. Biederman [this message]
2017-01-04 21:12 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-01-04 10:57 gregkh
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=87eg0i1rbs.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jann@thejh.net \
--cc=stable-commits@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;
as well as URLs for NNTP newsgroup(s).