From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, allison.henderson@oracle.com
Subject: Re: [PATCHSET 0/4] xfs: last bit of LARP and other fixes for 5.19
Date: Mon, 23 May 2022 08:59:11 +1000 [thread overview]
Message-ID: <20220522225911.GO1098723@dread.disaster.area> (raw)
In-Reply-To: <165323326679.78754.13346434666230687214.stgit@magnolia>
On Sun, May 22, 2022 at 08:27:46AM -0700, Darrick J. Wong wrote:
> Hi all,
>
> Here's one last round of fixes for UAF bugs and memory leaks that I
> found while testing the logged xattr code. The first patch is a bug for
> a memory leak in quotacheck that has been popping up here and there for
> the last 10 years, and the rest are previously seen patches rebased
> against where I /think/ Dave's current internal testing tree is right
> now, based on his request on IRC Friday night.
The merge window has opened now, so I'm going to pull the critical
LARP bug fixes out of this (patch 2 and 3) because they are the ones
I've been waiting on to publish for-next before an initial pull
request. I'll plan the rest for 2nd late merge window pull request
once we've got the main bulk merged later this week.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2022-05-22 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 15:27 [PATCHSET 0/4] xfs: last bit of LARP and other fixes for 5.19 Darrick J. Wong
2022-05-22 15:27 ` [PATCH 1/4] xfs: purge dquots after inode walk fails during quotacheck Darrick J. Wong
2022-05-22 15:27 ` [PATCH 2/4] xfs: do not use logged xattr updates on V4 filesystems Darrick J. Wong
2022-05-23 5:51 ` Dave Chinner
2022-05-22 15:28 ` [PATCH 3/4] xfs: share xattr name and value buffers when logging xattr updates Darrick J. Wong
2022-05-23 5:59 ` Dave Chinner
2022-05-22 15:28 ` [PATCH 4/4] xfs: allow ->create_intent to return negative errnos Darrick J. Wong
2022-05-22 22:59 ` Dave Chinner [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=20220522225911.GO1098723@dread.disaster.area \
--to=david@fromorbit.com \
--cc=allison.henderson@oracle.com \
--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