From: Carlos Maiolino <cem@kernel.org>
To: ruansy.fnst@fujitsu.com, akpm@linux-foundation.org,
djwong@kernel.org, Haoxiang Li <lihaoxiang@isrc.iscas.ac.cn>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] xfs: fix a resource leak in xfs_alloc_buftarg()
Date: Tue, 07 Apr 2026 15:38:19 +0200 [thread overview]
Message-ID: <177556909933.105112.828032873209479746.b4-ty@kernel.org> (raw)
In-Reply-To: <20260401040241.560314-1-lihaoxiang@isrc.iscas.ac.cn>
On Wed, 01 Apr 2026 12:02:41 +0800, Haoxiang Li wrote:
> In the error path, call fs_put_dax() to drop the DAX
> device reference.
>
>
Applied to for-next, thanks!
[1/1] xfs: fix a resource leak in xfs_alloc_buftarg()
commit: 29a7b2614357393b176ef06ba5bc3ff5afc8df69
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-04-07 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 4:02 [PATCH] xfs: fix a resource leak in xfs_alloc_buftarg() Haoxiang Li
2026-04-01 4:21 ` Darrick J. Wong
2026-04-07 13:38 ` 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=177556909933.105112.828032873209479746.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=djwong@kernel.org \
--cc=lihaoxiang@isrc.iscas.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ruansy.fnst@fujitsu.com \
--cc=stable@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