From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/2] xfs: fix buffer use after free on unpin abort
Date: Mon, 21 Jun 2021 09:16:42 -0400 [thread overview]
Message-ID: <20210621131644.128177-1-bfoster@redhat.com> (raw)
v2:
- Split assert in patch 2.
v1: https://lore.kernel.org/linux-xfs/20210511135257.878743-1-bfoster@redhat.com/
- Rework patch 1 to hold conditionally in the abort case and document
the underlying design flaw.
- Add patch 2 to remove some unused code.
rfc: https://lore.kernel.org/linux-xfs/20210503121816.561340-1-bfoster@redhat.com/
Brian Foster (2):
xfs: hold buffer across unpin and potential shutdown processing
xfs: remove dead stale buf unpin handling code
fs/xfs/xfs_buf_item.c | 58 +++++++++++++++++--------------------------
1 file changed, 23 insertions(+), 35 deletions(-)
--
2.26.3
next reply other threads:[~2021-06-21 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 13:16 Brian Foster [this message]
2021-06-21 13:16 ` [PATCH v2 1/2] xfs: hold buffer across unpin and potential shutdown processing Brian Foster
2021-06-21 13:16 ` [PATCH v2 2/2] xfs: remove dead stale buf unpin handling code Brian Foster
2021-06-21 16:57 ` [PATCH v2 0/2] xfs: fix buffer use after free on unpin abort Darrick J. Wong
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=20210621131644.128177-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--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