[lkml]   [2018]   [Dec]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn
On Sat, Dec 22, 2018 at 11:20 PM Linus Torvalds
<> wrote:
> Eric, this is entirely unacceptable.

i would like to point out that I send a revert for this in *July*
before any kernel with this change
was released for the exact same reason. But I was ignored and no one
came to argumentative aid:

To be fair, no one apart from me was pointing out that it actually
breaks people including systemd folks
even though I was bringing it up with them. I even tried to fix all of
userspace after this got NACKED
( ).


> On Sat, Dec 22, 2018 at 12:58 PM Gabriel C <> wrote:
> >
> > Added some people to CC that might want to see this..
> Thanks.
> > > Here's an email that was sent to lkml about the subject:
> > >
> > >
> > >
> > > I link also this, quoting the last of it:
> > >
> > >
> > >
> > > It has never been the case that mknod on a device node will guarantee
> > > that you even can open the device node. The applications that regress
> > > are broken. It doesn't mean we shouldn't be bug compatible, but we darn
> > > well should document very clearly the bugs we are being bug compatible with.
> Yeah, this is complete garbage.
> We have very clear rules in the kernel: if some change breaks existing
> setups, it is ABSOLUTELY NEVER the application that is broken.
> It is the kernel.
> There is absolutely zero gray areas here. Eric, your behavior is
> entirely out of line, and now we apparently have a regression that
> goes back to June that I was not told about because of your incorrect
> stance.
> Eric, I want to make this 1000% clear: there are no user space bugs.
> If it used to work, then user space was clearly doing the right thing.
> The fact that you tried to several times claim it was buggy user space
> is a serious breach of trust. You KNOW this is the case.
> Seriously. There are no excuses.
> That commit is now reverted in my tree, and furthermore I will not
> take any pull requests from you until you have made it clear that you
> comprehend this very fundamental issue.
> Why did it take so long for this issue to be elevated to me?
> Linus

 \ /
  Last update: 2018-12-22 23:51    [W:0.051 / U:3.712 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site