From: Thomas Backlund <tmb@mageia.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
<christian.brauner@canonical.com>
Cc: <nix.or.die@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
<ellierevves@gmail.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, <seth.forshee@canonical.com>,
<stable@vger.kernel.org>, <gregkh@linuxfoundation.org>
Subject: Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn
Date: Sun, 23 Dec 2018 12:54:11 +0200 [thread overview]
Message-ID: <828415b6-9fee-96bd-b6b0-fd4450df97a8@mageia.org> (raw)
In-Reply-To: <CAHk-=wg8Qrh4nvFbWttz6zPMeRKO2Twv57vZfGaQ6odsjYFEnQ@mail.gmail.com>
Den 23-12-2018 kl. 01:28, skrev Linus Torvalds:
> On Sat, Dec 22, 2018 at 3:07 PM Christian Brauner
> <christian.brauner@canonical.com> wrote:
>>
>> However, for this case should I resend the revert?
>
> Since I was pointed at the original email thread, I just picked it up
> from there directly. It still applied cleanly, nothing had changed in
> that area.
>
> Linus
>
This should also be picked up for 4.19 lts
Greg, it's now upstream as:
From 94f82008ce30e2624537d240d64ce718255e0b80 Mon Sep 17 00:00:00 2001
From: Christian Brauner <christian@brauner.io>
Date: Thu, 5 Jul 2018 17:51:20 +0200
Subject: Revert "vfs: Allow userns root to call mknod on owned filesystems."
--
Thomas
next prev parent reply other threads:[~2018-12-23 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 11:39 Ellie Reeves
2018-12-22 20:57 ` Gabriel C
2018-12-22 22:20 ` Linus Torvalds
2018-12-22 22:48 ` Christian Brauner
2018-12-22 23:01 ` Linus Torvalds
2018-12-22 23:07 ` Christian Brauner
2018-12-22 23:28 ` Linus Torvalds
2018-12-23 10:54 ` Thomas Backlund [this message]
2018-12-24 8:08 ` Greg KH
2018-12-22 23:32 ` Gabriel C
2018-12-23 4:12 ` Ellie Reeves
-- strict thread matches above, loose matches on Subject: below --
2018-12-22 14:36 Ellie Reeves
2018-12-22 10:44 Ellie Revves
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=828415b6-9fee-96bd-b6b0-fd4450df97a8@mageia.org \
--to=tmb@mageia.org \
--cc=christian.brauner@canonical.com \
--cc=ebiederm@xmission.com \
--cc=ellierevves@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=seth.forshee@canonical.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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®