From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>, stable <stable@vger.kernel.org>
Subject: Re: Patch "ovl: fix missing upper fs freeze protection on copy up for ioctl" has been added to the 4.19-stable tree
Date: Thu, 13 Jun 2019 09:48:54 +0200 [thread overview]
Message-ID: <20190613074854.GC19685@kroah.com> (raw)
In-Reply-To: <CAOQ4uxjKKJduAkomNHxo=T1i4-FVUJ_JABkXfpjz2qt=DAHTZA@mail.gmail.com>
On Mon, Jun 10, 2019 at 11:28:46PM +0300, Amir Goldstein wrote:
> > > This patch is fine for stable, but I have a process question.
> > > All these patches from overlayfs 5.2-rc1 are also v4.9 stable candidates:
> > >
> > > 1. acf3062a7e1c - ovl: relax WARN_ON() for overlapping layers use case
> > > 2. 98487de318a6 - ovl: check the capability before cred overridden
> > > 3. d989903058a8 - ovl: do not generate duplicate fsnotify events for "fake" path
> > > 4. 9e46b840c705 - ovl: support stacked SEEK_HOLE/SEEK_DATA
> > >
> > > #2 wasn't properly marked for stable, but the other are marked with
> > > Fixes: and Reported-by:
> > >
> > > Are those marks not sufficient to get selected for stable trees these days?
> >
> > Not by default, no. Sometimes they might get picked up if we get bored,
> > or the auto-bot notices them.
> >
> > > I must admit that #1 in borderline stable. Not sure if eliminating an unjust
> > > WARN_ON qualified, but syzbot did report a bug..
> >
> > syzbot things are good to fix in stable kernels, so that syzbot can
> > continue to find real things in stable kernels. So yes, that is fine to
> > backport.
> >
> > > Just asking in order to improve the process, but in any case,
> > > please pick those patches for v4.9+ (unless anyone objects?)
> > > They all already have LTP/xfstests/syzkaller tests that cover them.
> >
> > I'll queue them up for the next round after this, thanks.
> >
>
> Hi Greg,
>
> I forgot to follow up on those patches.
> Now I look at linux-4.19.y, I only see patch #1 (ovl: relax WARN_ON()..)
> and not the 3 other patches I listed as stable candidates.
> Was there any issue with those patches?
Sorry, didn't get to them.
I did now, and they all do not apply to all kernel versions. Most of
them do not go back to 4.14 or 4.9 as the code just isn't there.
So, after this next round of kernel releases, can you send backported
versions of any missing patches so that we are sure to apply them
correctly?
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-13 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1558603746191117@kroah.com>
2019-05-23 19:51 ` Patch "ovl: fix missing upper fs freeze protection on copy up for ioctl" has been added to the 4.19-stable tree Amir Goldstein
2019-05-23 19:57 ` Greg KH
2019-06-10 20:28 ` Amir Goldstein
2019-06-13 7:48 ` Greg KH [this message]
2019-06-13 8:37 ` Amir Goldstein
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=20190613074854.GC19685@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vgoyal@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).