Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org, Andrey Albershteyn <aalbersh@kernel.org>
Cc: djwong@kernel.org
Subject: Re: [PATCH] xfs: fix inverted clearance of inode junk flags
Date: Mon, 03 Aug 2026 15:22:50 +0200	[thread overview]
Message-ID: <178576337047.315832.6359146679525353677.b4-ty@kernel.org> (raw)
In-Reply-To: <20260722091801.503245-1-aalbersh@kernel.org>

On Wed, 22 Jul 2026 11:17:59 +0200, Andrey Albershteyn wrote:
> sashiko.dev noticed that these checks clear all the valid flags instead
> of invalid. This probably was never hit as it only executed on invalid
> flag presence.
> 
> 

Applied to for-next, thanks!

[1/1] xfs: fix inverted clearance of inode junk flags
      commit: fb082235c67551d526704e07a4efb82ac3a9ba48

Best regards,
-- 
Carlos Maiolino <cem@kernel.org>


      parent reply	other threads:[~2026-08-03 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  9:17 [PATCH] xfs: fix inverted clearance of inode junk flags Andrey Albershteyn
2026-07-22 15:31 ` Darrick J. Wong
2026-08-03 13:22 ` Carlos Maiolino [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=178576337047.315832.6359146679525353677.b4-ty@kernel.org \
    --to=cem@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@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