From: Christoph Hellwig <hch@infradead.org>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
kjell.m.randa@gmail.com, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix di_onlink checking for V1/V2 inodes
Date: Wed, 21 Aug 2024 22:31:15 -0700 [thread overview]
Message-ID: <ZsbNIxrlympxO8hn@infradead.org> (raw)
In-Reply-To: <87r0ah6saj.fsf@debian-BULLSEYE-live-builder-AMD64>
On Thu, Aug 22, 2024 at 10:55:05AM +0530, Chandan Babu R wrote:
> On Wed, Aug 21, 2024 at 10:04:42 PM -0700, Darrick J. Wong wrote:
> > On Mon, Aug 12, 2024 at 10:46:59PM -0700, Christoph Hellwig wrote:
> >> Looks good:
> >>
> >> Reviewed-by: Christoph Hellwig <hch@lst.de>
> >
> > Hey Chandan, I just realized this didn't get merged yet, even though
> > there's a user complaint about this. Can we get this staged for 6.11,
> > please?
>
> Sorry, I missed this patch. I have started running tests on "v6.11-rc4 +
> <this patch>". However, the earliest I could send the pull request is
> sometime next week.
FYI, we'll also need to to fix the new RT discard support as it
currently is broken when the RT device does not support discard.
Either my series or (maybe?) the patch Darrick just sent, I'm
going to give it a spin now.
next prev parent reply other threads:[~2024-08-22 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 22:40 [PATCH] xfs: fix di_onlink checking for V1/V2 inodes Darrick J. Wong
2024-08-13 5:46 ` Christoph Hellwig
2024-08-22 5:04 ` Darrick J. Wong
2024-08-22 5:25 ` Chandan Babu R
2024-08-22 5:31 ` Christoph Hellwig [this message]
2024-08-22 5:40 ` Chandan Babu R
2024-08-22 5:05 ` [PATCH] xfs: add a test for v1 inodes with nonzero nlink and onlink fields Darrick J. Wong
2024-08-22 6:32 ` Christoph Hellwig
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=ZsbNIxrlympxO8hn@infradead.org \
--to=hch@infradead.org \
--cc=chandanbabu@kernel.org \
--cc=djwong@kernel.org \
--cc=kjell.m.randa@gmail.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