From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: David Sterba <dsterba@suse.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] btrfs: zoned: fix leak of zone_info in btrfs_get_dev_zone_info
Date: Fri, 10 Dec 2021 13:34:10 +0000 [thread overview]
Message-ID: <PH0PR04MB74165B94DDB22C86EA4069569B719@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20211210114432.GO28560@twin.jikos.cz
On 10/12/2021 12:50, David Sterba wrote:
> On Fri, Dec 10, 2021 at 03:32:00AM -0800, Johannes Thumshirn wrote:
>> Some error paths of btrfs_get_dev_zone_info do not free zone_info,
>> so assign zone_info to device->zone_info as soon as we've successfully
>> allocated it, so it wiill get freed by the error handling.
>>
>> a411e32badc4 ("btrfs: zoned: cache reported zone during mount")
>
> As this patch is still in misc-next I'll fold the fixup, thanks.
>
Thanks
prev parent reply other threads:[~2021-12-10 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 11:32 [PATCH] btrfs: zoned: fix leak of zone_info in btrfs_get_dev_zone_info Johannes Thumshirn
2021-12-10 11:44 ` David Sterba
2021-12-10 13:34 ` Johannes Thumshirn [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=PH0PR04MB74165B94DDB22C86EA4069569B719@PH0PR04MB7416.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=dan.carpenter@oracle.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).