From: Chuck Lever <chuck.lever@oracle.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Frank van der Linden <fllinden@amazon.com>,
Bruce Fields <bfields@fieldses.org>,
stable@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v3 01/10] xattr: break delegations in {set,remove}xattr
Date: Fri, 10 Jul 2020 10:08:12 -0400 [thread overview]
Message-ID: <75E4D727-E962-466A-AC40-AB047E1EF5AE@oracle.com> (raw)
In-Reply-To: <20200710140308.9C810207BB@mail.kernel.org>
Hi Sasha-
> On Jul 10, 2020, at 10:03 AM, Sasha Levin <sashal@kernel.org> wrote:
>
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.7.6, v5.4.49, v4.19.130, v4.14.186, v4.9.228, v4.4.228.
>
> v5.7.6: Build OK!
> v5.4.49: Build OK!
> v4.19.130: Build OK!
> v4.14.186: Build OK!
> v4.9.228: Build OK!
> v4.4.228: Failed to apply! Possible dependencies:
> 5d6c31910bc07 ("xattr: Add __vfs_{get,set,remove}xattr helpers")
> 6b2553918d8b4 ("replace ->follow_link() with new method that could stay in RCU mode")
> aa80deab33a8f ("namei: page_getlink() and page_follow_link_light() are the same thing")
> cd3417c8fc950 ("kill free_page_put_link()")
> ce23e64013348 ("->getxattr(): pass dentry and inode as separate arguments")
> fceef393a5381 ("switch ->get_link() to delayed_call, kill ->put_link()")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
I've updated the "cc: stable" tag in my testing branch to include "# v4.9+".
--
Chuck Lever
next prev parent reply other threads:[~2020-07-10 14:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 22:39 [PATCH v3 00/10] server side user xattr support (RFC 8276) Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 01/10] xattr: break delegations in {set,remove}xattr Frank van der Linden
2020-06-25 20:39 ` Frank van der Linden
2020-07-14 17:11 ` Frank van der Linden
2020-07-01 19:33 ` Sasha Levin
2020-07-10 14:03 ` Sasha Levin
2020-07-10 14:08 ` Chuck Lever [this message]
2020-06-23 22:39 ` [PATCH v3 02/10] xattr: add a function to check if a namespace is supported Frank van der Linden
2020-06-25 20:41 ` Frank van der Linden
2020-07-14 17:13 ` Frank van der Linden
2020-07-14 18:46 ` Linus Torvalds
2020-07-28 14:17 ` Chuck Lever
2020-07-28 14:33 ` Al Viro
2020-07-29 12:23 ` Chuck Lever
2020-06-23 22:39 ` [PATCH v3 03/10] nfs,nfsd: NFSv4.2 extended attribute protocol definitions Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 04/10] nfsd: split off the write decode code in to a separate function Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 05/10] nfsd: add defines for NFSv4.2 extended attribute support Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 06/10] nfsd: define xattr functions to call in to their vfs counterparts Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 07/10] nfsd: take xattr bits in to account for permission checks Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 08/10] nfsd: add structure definitions for xattr requests / responses Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 09/10] nfsd: implement the xattr functions and en/decode logic Frank van der Linden
2020-06-23 22:39 ` [PATCH v3 10/10] nfsd: add fattr support for user extended attributes Frank van der Linden
2020-06-25 16:50 ` [PATCH v3 00/10] server side user xattr support (RFC 8276) J. Bruce Fields
2020-06-25 17:13 ` Frank van der Linden
2020-06-25 16:53 ` J. Bruce Fields
2020-06-25 17:39 ` Frank van der Linden
2020-06-25 20:07 ` J. Bruce Fields
2020-07-04 14:37 ` Chuck Lever
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=75E4D727-E962-466A-AC40-AB047E1EF5AE@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--cc=fllinden@amazon.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.