From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: jeffm@suse.com, jack@suse.cz, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] reiserfs: fix extended attributes on the root directory" failed to apply to 4.9-stable tree
Date: Sun, 15 Dec 2019 21:25:11 -0500 [thread overview]
Message-ID: <20191216022511.GC17708@sasha-vm> (raw)
In-Reply-To: <1576430119239212@kroah.com>
On Sun, Dec 15, 2019 at 06:15:19PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-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
>
>------------------ original commit in Linus's tree ------------------
>
>From 60e4cf67a582d64f07713eda5fcc8ccdaf7833e6 Mon Sep 17 00:00:00 2001
>From: Jeff Mahoney <jeffm@suse.com>
>Date: Thu, 24 Oct 2019 10:31:27 -0400
>Subject: [PATCH] reiserfs: fix extended attributes on the root directory
>
>Since commit d0a5b995a308 (vfs: Add IOP_XATTR inode operations flag)
>extended attributes haven't worked on the root directory in reiserfs.
>
>This is due to reiserfs conditionally setting the sb->s_xattrs handler
>array depending on whether it located or create the internal privroot
>directory. It necessarily does this after the root inode is already
>read in. The IOP_XATTR flag is set during inode initialization, so
>it never gets set on the root directory.
>
>This commit unconditionally assigns sb->s_xattrs and clears IOP_XATTR on
>internal inodes. The old return values due to the conditional assignment
>are handled via open_xa_root, which now returns EOPNOTSUPP as the VFS
>would have done.
>
>Link: https://lore.kernel.org/r/20191024143127.17509-1-jeffm@suse.com
>CC: stable@vger.kernel.org
>Fixes: d0a5b995a308 ("vfs: Add IOP_XATTR inode operations flag")
>Signed-off-by: Jeff Mahoney <jeffm@suse.com>
>Signed-off-by: Jan Kara <jack@suse.cz>
Just a simple conflict due to bc98a42c1f7d ("VFS: Convert sb->s_flags &
MS_RDONLY to sb_rdonly(sb)"). Fixed and queued up.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-12-16 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 17:15 FAILED: patch "[PATCH] reiserfs: fix extended attributes on the root directory" failed to apply to 4.9-stable tree gregkh
2019-12-16 2:25 ` Sasha Levin [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=20191216022511.GC17708@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jeffm@suse.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