mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] block: clear ia_ranges on sysfs registration failure
Date: Mon, 17 Aug 2026 00:46:17 -0700	[thread overview]
Message-ID: <aoK8STazvF366Qwo@infradead.org> (raw)
In-Reply-To: <20260814220448.4085032-1-shuangpeng.kernel@gmail.com>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

On Fri, Aug 14, 2026 at 06:04:48PM -0400, Shuangpeng Bai wrote:
> disk_register_independent_access_ranges() clears disk->ia_ranges when
> creating the top-level kobject fails. However, if adding one of the range
> kobjects fails, the cleanup drops the final reference to iars and frees it
> while disk->ia_ranges still points at it.
> 
> A concurrent disk revalidation can wait for q->sysfs_lock and then call
> disk_unregister_independent_access_ranges(), which dereferences the stale
> pointer after registration releases the mutex.
> 
> Clear disk->ia_ranges before dropping the kobject references on the child
> registration error path, matching the top-level error handling.
> 
> Fixes: a2247f19ee1c ("block: Add independent access ranges support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
> ---
>  block/blk-ia-ranges.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/block/blk-ia-ranges.c b/block/blk-ia-ranges.c
> index 7be8b58893c9..2430e475a8e7 100644
> --- a/block/blk-ia-ranges.c
> +++ b/block/blk-ia-ranges.c
> @@ -135,6 +135,7 @@ int disk_register_independent_access_ranges(struct gendisk *disk)
>  					   &blk_ia_range_ktype, &iars->kobj,
>  					   "%d", i);
>  		if (ret) {
> +			disk->ia_ranges = NULL;
>  			while (--i >= 0)
>  				kobject_del(&iars->ia_range[i].kobj);
>  			kobject_del(&iars->kobj);
> -- 
> 2.43.0
> 
> 
---end quoted text---

      reply	other threads:[~2026-08-17  7:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 22:04 Shuangpeng Bai
2026-08-17  7:46 ` Christoph Hellwig [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=aoK8STazvF366Qwo@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuangpeng.kernel@gmail.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

all inboxes | Powered by JetHome®