From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] xfs: lock dquot buffer before detaching dquot from b_li_list
Date: Tue, 14 Jan 2025 07:53:40 -0800 [thread overview]
Message-ID: <20250114155340.GI1306365@frogsfrogsfrogs> (raw)
In-Reply-To: <bolbaetzmiqadzz4jdnz3xbugwyqnqmrskpicbvbs5ltrmfr5f@e7vvfbdb3shf>
On Tue, Jan 14, 2025 at 11:45:48AM +0100, Carlos Maiolino wrote:
> On Mon, Jan 13, 2025 at 08:21:34AM -0800, Darrick J. Wong wrote:
> > On Mon, Jan 13, 2025 at 01:33:07PM +0100, Carlos Maiolino wrote:
> > > On Wed, 08 Jan 2025 16:54:02 -0800, Darrick J. Wong wrote:
> > > > We have to lock the buffer before we can delete the dquot log item from
> > > > the buffer's log item list.
> > > >
> > > >
> > >
> > > Applied to next-rc, thanks!
> > >
> > > [1/1] xfs: lock dquot buffer before detaching dquot from b_li_list
> > > commit: 4e7dfb45fe08b2b54d7fe2499fab0eeaa42004ad
> >
> > Um... you already pushed this to Linus, why is it queued again?
> > (albeit with the same commit id so I don't think it matters)
>
> I rushed to push this patch to -rc7 so I didn't end up sending a TY message to
> it. It was still on my b4 stack when I sent the last TY batch.
>
> Which reminds me I should update the message, as the TY is going after I push to
> for-next, no to next-rc :).
Ah, ok. Carry on! :)
--D
>
> >
> > --D
> >
> > > Best regards,
> > > --
> > > Carlos Maiolino <cem@kernel.org>
> > >
> > >
> >
>
prev parent reply other threads:[~2025-01-14 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 0:54 [PATCH] xfs: lock dquot buffer before detaching dquot from b_li_list Darrick J. Wong
2025-01-09 6:08 ` Christoph Hellwig
2025-01-09 7:17 ` Darrick J. Wong
2025-01-09 7:35 ` Christoph Hellwig
2025-01-13 12:33 ` Carlos Maiolino
2025-01-13 16:21 ` Darrick J. Wong
2025-01-14 10:45 ` Carlos Maiolino
2025-01-14 15:53 ` Darrick J. Wong [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=20250114155340.GI1306365@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.