Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Miklos Szeredi <mszeredi@redhat.com>,
	stable <stable@vger.kernel.org>,
	overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] ovl: support the FS_IOC_FS[SG]ETXATTR ioctls" failed to apply to 5.1-stable tree
Date: Sat, 22 Jun 2019 21:03:45 -0400	[thread overview]
Message-ID: <20190623010345.GJ2226@sasha-vm> (raw)
In-Reply-To: <CAOQ4uxiTTuOESvZ2Y5cSebqKs+qeU3q6ZMReBDro0Qv7aRBhpw@mail.gmail.com>

On Fri, Jun 21, 2019 at 11:15:47AM +0300, Amir Goldstein wrote:
>On Thu, Jun 13, 2019 at 11:49 AM Amir Goldstein <amir73il@gmail.com> wrote:
>>
>> On Sun, Jun 9, 2019 at 12:45 PM <gregkh@linuxfoundation.org> wrote:
>> >
>> >
>> > The patch below does not apply to the 5.1-stable tree.
>> > If someone wants it applied there, or to any other stable or longterm
>> > tree, then please email the backport, including the original git commit
>> > id to <stable@vger.kernel.org>.
>> >
>> > thanks,
>> >
>> > greg k-h
>> >
>>
>> FYI, the failure to apply this patch would be resolved after you
>> picked up "ovl: check the capability before cred overridden" for
>> stable, please hold off from taking this patch just yet, because
>> it has a bug, whose fix wasn't picked upstream yet.
>>
>
>Greg,
>
>Please apply these patches to stable 4.19.
>They fix a docker regression (project quotas feature).
>
>b21d9c435f93 ovl: support the FS_IOC_FS[SG]ETXATTR ioctls
>941d935ac763 ovl: fix wrong flags check in FS_IOC_FS[SG]ETXATTR ioctls
>
>They apply cleanly and tested on v4.19.53.

I've queued these for 4.19.

>While at it, I also tested that the following patches apply cleanly and solve
>relevant issues on v4.19.53, but they are not clear stable candidates.
>
>1) /proc/locks shows incorrect ino. Only reported by xfstests (so far):
>6dde1e42f497 ovl: make i_ino consistent with st_ino in more cases

And this.

>2) Fix output of `modinfo overlay`:
>253e74833911 ovl: fix typo in MODULE_PARM_DESC

But not this one. Maybe we should be including these in stable trees
since the risk factor is low and it fixes something user-visible, but
our current rules object this this kind of patches so I've left it out.

>3) Disallow bogus layer combinations.
>syzbot has started to produce repros that create bogus layer combinations.
>So far it has only been able to reproduce a WARN_ON, which has already
>been fixed in stable, by  acf3062a7e1c ("ovl: relax WARN_ON()..."), but
>other real bugs could be lurking if those setups are allowed.
>We decided to detect and error on these setups on mount, to stop syzbot
>(and attackers) from trying to attack overlayfs this way.
>To stop syzbot from mutating this class of repros on stable kernel you
>MAY apply these 3 patches, but in any case, I would wait a while to see
>if more bugs are reported on master.
>Although this solves a problem dating before 4.19, I have no plans
>of backporting these patches further back.
>
>146d62e5a586 ovl: detect overlapping layers
>9179c21dc6ed ovl: don't fail with disconnected lower NFS
>1dac6f5b0ed2 ovl: fix bogus -Wmaybe-unitialized warning

I've queued these 3 for 4.19.

--
Thanks,
Sasha

  reply	other threads:[~2019-06-23  1:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09  9:45 FAILED: patch "[PATCH] ovl: support the FS_IOC_FS[SG]ETXATTR ioctls" failed to apply to 5.1-stable tree gregkh
2019-06-13  8:49 ` Amir Goldstein
2019-06-21  8:15   ` Amir Goldstein
2019-06-23  1:03     ` Sasha Levin [this message]
2019-06-23 20:29       ` Greg KH
2019-06-24  0:34         ` Sasha Levin
2019-06-24  4:52           ` Amir Goldstein
2019-07-24 11:57             ` Greg KH
2019-07-24 13:46               ` Amir Goldstein
2019-09-19 19:04                 ` Greg KH
2019-07-11 14:14       ` overlayfs regression in master and stable trees Amir Goldstein
2019-07-11 15:41         ` Greg KH

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=20190623010345.GJ2226@sasha-vm \
    --to=sashal@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=mszeredi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox