From: Greg KH <gregkh@linuxfoundation.org>
To: Niklas Cassel <niklas.cassel@axis.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Miklos Szeredi <mszeredi@redhat.com>,
stable <stable@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] ovl: hash directory inodes for fsnotify" failed to apply to 4.14-stable tree
Date: Wed, 21 Feb 2018 12:42:58 +0100 [thread overview]
Message-ID: <20180221114258.GD6555@kroah.com> (raw)
In-Reply-To: <20180215154431.GA26404@axis.com>
On Thu, Feb 15, 2018 at 04:44:31PM +0100, Niklas Cassel wrote:
> On Thu, Feb 15, 2018 at 05:02:32PM +0200, Amir Goldstein wrote:
> > On Thu, Feb 15, 2018 at 4:31 PM, <gregkh@linuxfoundation.org> wrote:
> > >
> > > The patch below does not apply to the 4.14-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>.
> > >
> >
> > Hi Niklas,
> >
> > The conflict resolution of this patch for v4.14 is trivial (just dropping last
> > hunk of inode.c patch), but I no means to test this right now.
> >
> > Are you able and/or interested to test the attached backport path for
> > stable kernel v4.14?
> >
> > I have posted an LTP test (inotify07) to test this fix if anyone else
> > is interested in testing:
> > https://github.com/linux-test-project/ltp/pull/246
> >
> > Thanks,
> > Amir.
>
> Hello Amir,
>
> I have already backported+verified the fix to v4.13 in one of our internal
> trees.
>
> Like you said, I simply dropped the last hunk of the patch that modfied
> inode.c, i.e. I simply ignored this hunk of the patch:
>
> @@ -685,7 +702,7 @@ struct inode *ovl_get_inode(struct dentry *dentry, struct dentry *upperdentry,
> ovl_set_flag(OVL_IMPURE, inode);
>
> /* Check for non-merge dir that may have whiteouts */
> - if (S_ISDIR(realinode->i_mode)) {
> + if (is_dir) {
> struct ovl_entry *oe = dentry->d_fsdata;
>
> if (((upperdentry && lowerdentry) || oe->numlower > 1) ||
>
Ok, last hunk dropped, thanks.
greg k-h
prev parent reply other threads:[~2018-02-21 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <151870507410538@kroah.com>
2018-02-15 15:02 ` FAILED: patch "[PATCH] ovl: hash directory inodes for fsnotify" failed to apply to 4.14-stable tree Amir Goldstein
2018-02-15 15:44 ` Niklas Cassel
2018-02-21 11:42 ` Greg KH [this message]
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=20180221114258.GD6555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=niklas.cassel@axis.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