Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-24 Thread Greg KH
On Sun, Dec 23, 2018 at 12:54:11PM +0200, Thomas Backlund wrote: > Den 23-12-2018 kl. 01:28, skrev Linus Torvalds: > > On Sat, Dec 22, 2018 at 3:07 PM Christian Brauner > > wrote: > > > > > > However, for this case should I resend the revert? > > > > Since I was pointed at the original email

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-23 Thread Thomas Backlund
Den 23-12-2018 kl. 01:28, skrev Linus Torvalds: On Sat, Dec 22, 2018 at 3:07 PM Christian Brauner 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

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Ellie Reeves
Hi, I would like to thank you all for reacting to this issue so quickly, and I am really sorry for sending the message several time. I thought there was a problem with the way it was formatted or some such, hence why I sent it several times, because none of the messages seemed to get through.

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Gabriel C
Am So., 23. Dez. 2018 um 00:02 Uhr schrieb Linus Torvalds : > > On Sat, Dec 22, 2018 at 2:49 PM Christian Brauner > wrote: > > > > 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

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Linus Torvalds
On Sat, Dec 22, 2018 at 3:07 PM Christian Brauner 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

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Christian Brauner
On Sun, Dec 23, 2018 at 12:02 AM Linus Torvalds wrote: > > On Sat, Dec 22, 2018 at 2:49 PM Christian Brauner > wrote: > > > > 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

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Linus Torvalds
On Sat, Dec 22, 2018 at 2:49 PM Christian Brauner wrote: > > 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 Seriously, the "we

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Christian Brauner
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: -

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Linus Torvalds
Eric, this is entirely unacceptable. 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: > > > > https://lkml.org/lkml/2018/7/5/742 > > > > I link also this, quoting the

Re: [BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Gabriel C
Added some people to CC that might want to see this.. Am Sa., 22. Dez. 2018 um 19:14 Uhr schrieb Ellie Reeves : > > Hi, > first off, allow me to express that this is my first time ever writing > on such a mailing list, and that if something is unclear or you would > need more information, just

[BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Ellie Reeves
Hi, first off, allow me to express that this is my first time ever writing on such a mailing list, and that if something is unclear or you would need more information, just let me know. I write to this list in hoping to see this change reverted. The linux kernel always said it would avoid

[BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Ellie Revves
Hi, first off, allow me to express that this is my first time ever writing on such a mailing list, and that if something is unclear or you would need more information, just let me know. I write to this list in hoping to see this change reverted. The linux kernel always said it would avoid

[BREAKAGE] Since 4.18, kernel sets SB_I_NODEV implicitly on userns mounts, breaking systemd-nspawn

2018-12-22 Thread Ellie Reeves
Hi, first off, allow me to express that this is my first time ever writing on such a mailing list, and that if something is unclear or you would need more information, just let me know. I write to this list in hoping to see this change reverted. The linux kernel always said it would avoid