public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <djwong@kernel.org>
Cc: <amir73il@gmail.com>, <ayudutta@amazon.com>, <kkexu@amazon.com>,
	<kuniyu@amazon.com>, <linux-xfs@vger.kernel.org>,
	<lrumancik@google.com>, <pbonzini@redhat.com>,
	<sandeen@redhat.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH stable 5.15] xfs: remove incorrect ASSERT in xfs_rename
Date: Fri, 8 Jul 2022 09:36:32 -0700	[thread overview]
Message-ID: <20220708163632.65870-1-kuniyu@amazon.com> (raw)
In-Reply-To: <YshTjclKanmcBsUW@magnolia>

From:   "Darrick J. Wong" <djwong@kernel.org>
Date:   Fri, 8 Jul 2022 08:55:57 -0700
> 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.) ;)
> 
> ...and of course the first thing that happens is that I mix up the 5.10
> and 5.15 patches.
> 
> Amir is the 5.10 maintainer, Leah is the 5.15 maintainer.  Sorry about
> the mixup.  /me pours himself a third(!) cup of coffee.

Thank you for taking a look!

And sorry that I'm not familiar with xfs workflow and didn't know each
version has dedicated maintainers.

Is there a doc like Documentation/process/maintainer-netdev.rst as both of
Amir and Leah seem not listed in the xfs entry of MAINTAINERS...?

  reply	other threads:[~2022-07-08 16:37 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 [this message]
2022-07-08 16:51       ` Darrick J. Wong
2022-07-08 17:04         ` Kuniyuki Iwashima
2022-07-08 18:38   ` Leah Rumancik

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=20220708163632.65870-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=amir73il@gmail.com \
    --cc=ayudutta@amazon.com \
    --cc=djwong@kernel.org \
    --cc=kkexu@amazon.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lrumancik@google.com \
    --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