public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Yuto Ohnuki <ytohnuki@amazon.com>
To: <dgc@kernel.org>
Cc: <bfoster@redhat.com>, <cem@kernel.org>, <darrick.wong@oracle.com>,
	<dchinner@redhat.com>, <linux-kernel@vger.kernel.org>,
	<linux-xfs@vger.kernel.org>, <stable@vger.kernel.org>,
	<syzbot+652af2b3c5569c4ab63c@syzkaller.appspotmail.com>,
	<ytohnuki@amazon.com>
Subject: Re: [PATCH v2] xfs: fix use-after-free of log items during AIL pushing
Date: Sun, 8 Mar 2026 18:35:33 +0000	[thread overview]
Message-ID: <20260308183532.36096-2-ytohnuki@amazon.com> (raw)
In-Reply-To: <aan6eeNwMnBcRzhn@dread>

> I think this should be broken up into separate commits. Certainly
> the unmount changes should be a standalone commit...

Hi Dave, thank you for the detailed review.

I've split the patch into 4 separate commits in v3 and addressed
your other feedback:

- Unmount reorder as a standalone patch
- Loop body factored into xfsaild_process_logitem() as a
  separate refactoring patch
- Passed ailp instead of dev to tracepoints
- Moved xfs_ail_push_class after xfs_log_item_class events
- Moved UAF-unsafe comments to after xfs_buf_relse()
- Added header comment on xfsaild_push_item() for lifetime rules

v3: https://lore.kernel.org/all/20260308182804.33127-6-ytohnuki@amazon.com/

Please let me know if I've misunderstood any of your points.

Yuto



Amazon Web Services EMEA SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg, R.C.S. Luxembourg B186284

Amazon Web Services EMEA SARL, Irish Branch, One Burlington Plaza, Burlington Road, Dublin 4, Ireland, branch registration number 908705




      reply	other threads:[~2026-03-08 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 18:58 [PATCH v2] xfs: fix use-after-free of log items during AIL pushing Yuto Ohnuki
2026-03-05 21:49 ` Dave Chinner
2026-03-08 18:35   ` Yuto Ohnuki [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=20260308183532.36096-2-ytohnuki@amazon.com \
    --to=ytohnuki@amazon.com \
    --cc=bfoster@redhat.com \
    --cc=cem@kernel.org \
    --cc=darrick.wong@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=dgc@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+652af2b3c5569c4ab63c@syzkaller.appspotmail.com \
    /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