From: Leah Rumancik <leah.rumancik@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
stable@vger.kernel.org, linux-xfs@vger.kernel.org,
Ke Xu <kkexu@amazon.com>, Ayushman Dutta <ayudutta@amazon.com>,
Eric Sandeen <sandeen@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH stable 5.15] xfs: remove incorrect ASSERT in xfs_rename
Date: Fri, 8 Jul 2022 11:38:02 -0700 [thread overview]
Message-ID: <Ysh5inAXa/ox9nO0@google.com> (raw)
In-Reply-To: <YshTJZVNkXpbGKsv@magnolia>
On Fri, Jul 08, 2022 at 08:54:13AM -0700, Darrick J. Wong wrote:
> On Thu, Jul 07, 2022 at 03:58:35PM -0700, Kuniyuki Iwashima wrote:
> > From: Eric Sandeen <sandeen@redhat.com>
> >
> > commit e445976537ad139162980bee015b7364e5b64fff upstream.
> >
> > Ayushman Dutta reported our 5.10 kernel hit the warning. It was because
> > the original commit misses a Fixes tag and was not backported to the stable
> > tree. The fix is merged in 5.16, so please backport it to 5.15 first.
> >
> > This ASSERT in xfs_rename is a) incorrect, because
> > (RENAME_WHITEOUT|RENAME_NOREPLACE) is a valid combination, and
> > b) unnecessary, because actual invalid flag combinations are already
> > handled at the vfs level in do_renameat2() before we get called.
> > So, remove it.
> >
> > Reported-by: Paolo Bonzini <pbonzini@redhat.com>
> > Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> > Reviewed-by: Darrick J. Wong <djwong@kernel.org>
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > Fixes: 7dcf5c3e4527 ("xfs: add RENAME_WHITEOUT support")
> > Reported-by: Ayushman Dutta <ayudutta@amazon.com>
> > Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
>
> Looks good to me, but you really ought to send 5.10 patches to the 5.10
> XFS maintainer (Amir, now cc'd). (Yes, this is a recent change.) ;)
>
> Acked-by: Darrick J. Wong <djwong@kernel.org>
>
> --D
This patch is actually part of the next set of 10 patches being testing
for the 5.15 branch :) It would have been going out in the next week or
two, but since this is such a minor change, we can just go ahead with it.
- Leah
>
> > ---
> > I will send another patch for 4.9 - 5.4 because of a conflict with idmapped
> > mount changes.
> > ---
> > fs/xfs/xfs_inode.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> > index 2477e301fa82..c19f3ca605af 100644
> > --- a/fs/xfs/xfs_inode.c
> > +++ b/fs/xfs/xfs_inode.c
> > @@ -3128,7 +3128,6 @@ xfs_rename(
> > * appropriately.
> > */
> > if (flags & RENAME_WHITEOUT) {
> > - ASSERT(!(flags & (RENAME_NOREPLACE | RENAME_EXCHANGE)));
> > error = xfs_rename_alloc_whiteout(mnt_userns, target_dp, &wip);
> > if (error)
> > return error;
> > --
> > 2.30.2
> >
prev parent reply other threads:[~2022-07-08 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 22:58 [PATCH stable 5.15] xfs: remove incorrect ASSERT in xfs_rename Kuniyuki Iwashima
2022-07-08 15:54 ` Darrick J. Wong
2022-07-08 15:55 ` Darrick J. Wong
2022-07-08 16:36 ` Kuniyuki Iwashima
2022-07-08 16:51 ` Darrick J. Wong
2022-07-08 17:04 ` Kuniyuki Iwashima
2022-07-08 18:38 ` Leah Rumancik [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=Ysh5inAXa/ox9nO0@google.com \
--to=leah.rumancik@gmail.com \
--cc=amir73il@gmail.com \
--cc=ayudutta@amazon.com \
--cc=djwong@kernel.org \
--cc=kkexu@amazon.com \
--cc=kuniyu@amazon.com \
--cc=linux-xfs@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sandeen@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