From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: oleksandr@natalenko.name, hch@lst.de, vbabka@suse.cz,
stable@vger.kernel.org, linux-xfs@vger.kernel.org, hch@lst.de
Subject: Re: [PATCHSET] xfs: random fixes for 6.18
Date: Wed, 22 Oct 2025 13:32:56 +0200 [thread overview]
Message-ID: <176113277643.82207.1441469219564358238.b4-ty@kernel.org> (raw)
In-Reply-To: <176107133959.4152072.11526530466991879614.stgit@frogsfrogsfrogs>
On Tue, 21 Oct 2025 11:29:50 -0700, Darrick J. Wong wrote:
> Random fixes for 6.18.
>
> If you're going to start using this code, I strongly recommend pulling
> from my git trees, which are linked below.
>
> This has been running on the djcloud for months with no problems. Enjoy!
> Comments and questions are, as always, welcome.
>
> [...]
Applied to for-next, thanks!
[1/4] xfs: don't set bt_nr_sectors to a negative number
commit: bd721ec7dedcc24ced51559e42a39140b59dfd08
[2/4] xfs: always warn about deprecated mount options
commit: 630785bfbe12c3ee3ebccd8b530a98d632b7e39d
[3/4] xfs: loudly complain about defunct mount options
commit: 3e7ec343f066cb3b6916239680ab6ad44537b453
[4/4] xfs: fix locking in xchk_nlinks_collect_dir
commit: f477af0cfa0487eddec66ffe10fd9df628ba6f52
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2025-10-22 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 18:29 [PATCHSET] xfs: random fixes for 6.18 Darrick J. Wong
2025-10-21 18:29 ` [PATCH 1/4] xfs: don't set bt_nr_sectors to a negative number Darrick J. Wong
2025-10-21 18:30 ` [PATCH 2/4] xfs: always warn about deprecated mount options Darrick J. Wong
2025-10-22 8:00 ` Carlos Maiolino
2025-10-22 16:12 ` Darrick J. Wong
2025-10-21 18:30 ` [PATCH 3/4] xfs: loudly complain about defunct " Darrick J. Wong
2025-10-22 4:16 ` Christoph Hellwig
2025-10-21 18:30 ` [PATCH 4/4] xfs: fix locking in xchk_nlinks_collect_dir Darrick J. Wong
2025-10-22 4:16 ` Christoph Hellwig
2025-10-22 11:32 ` Carlos Maiolino [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=176113277643.82207.1441469219564358238.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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