From: Luis Henriques <luis.henriques@canonical.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
stable <stable@vger.kernel.org>,
containers@lists.linux-foundation.org
Subject: Re: [stable] Locked mount and loopback mount fixes
Date: Mon, 11 May 2015 12:19:01 +0100 [thread overview]
Message-ID: <20150511111901.GD16635@ares.olymp> (raw)
In-Reply-To: <AD3FF3AE-4EC2-4239-97C6-96A1818E8856@xmission.com>
On Sun, May 10, 2015 at 09:23:01PM -0500, Eric W. Biederman wrote:
>
>
> On May 10, 2015 12:59:51 PM CDT, Ben Hutchings <ben@decadent.org.uk> wrote:
> >Why were these not cc'd to stable? Was this an oversight, or are they
> >simply not needed for fixing any known bugs?
>
> An oversight.
>
> On their own they don't matter but other patches cc'd to stable do depend on them for correct operation.
>
> The fact most of these changes depends on fs_pin likely limits how far they may be bsckported.
>
> >commit cd4a40174b71acd021877341684d8bb1dc8ea4ae
> >Author: Eric W. Biederman <ebiederm@xmission.com>
> >Date: Wed Jan 7 14:28:26 2015 -0600
> >
> > mnt: Fail collect_mounts when applied to unmounted mounts
> >
Thanks, I'm queuing this one for the 3.16 kernel (the 2nd commit
doesn't seem to be applicable to his kernel).
Cheers,
--
Lu�s
> >commit 820f9f147dcce2602eefd9b575bbbd9ea14f0953
> >Author: Eric W. Biederman <ebiederm@xmission.com>
> >Date: Thu Apr 2 16:35:48 2015 -0500
> >
> > fs_pin: Allow for the possibility that m_list or s_list go unused.
>
> Eric
>
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-11 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 17:59 [stable] Locked mount and loopback mount fixes Ben Hutchings
2015-05-11 2:23 ` Eric W. Biederman
[not found] ` <AD3FF3AE-4EC2-4239-97C6-96A1818E8856-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2015-05-11 11:19 ` Luis Henriques
2015-05-11 11:19 ` Luis Henriques [this message]
[not found] ` <20150511111901.GD16635-YD9HeJR0N8hLdv8CNEAgDg@public.gmane.org>
2015-05-11 13:55 ` Eric W. Biederman
2015-05-11 13:55 ` Eric W. Biederman
[not found] ` <1431280791.2233.50.camel-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2015-05-11 2:23 ` Eric W. Biederman
2015-05-11 14:04 ` Eric W. Biederman
2015-05-11 14:04 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2015-05-10 17:59 Ben Hutchings
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=20150511111901.GD16635@ares.olymp \
--to=luis.henriques@canonical.com \
--cc=ben@decadent.org.uk \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.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 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.