From: Ming Lei <ming.lei@redhat.com>
To: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mingfangsen <mingfangsen@huawei.com>, Guiyao <guiyao@huawei.com>,
zhangsaisai <zhangsaisai@huawei.com>,
"wubo (T)" <wubo40@huawei.com>
Subject: Re: [PATCH V3] brd: check and limit max_part par
Date: Wed, 15 Jan 2020 10:27:25 +0800 [thread overview]
Message-ID: <20200115022725.GA14585@ming.t460p> (raw)
In-Reply-To: <c8236e55-f64f-ef40-b394-8b7e86ce50df@huawei.com>
On Tue, Jan 14, 2020 at 07:56:07PM +0800, Zhiqiang Liu wrote:
>
> In brd_init func, rd_nr num of brd_device are firstly allocated
> and add in brd_devices, then brd_devices are traversed to add each
> brd_device by calling add_disk func. When allocating brd_device,
> the disk->first_minor is set to i * max_part, if rd_nr * max_part
> is larger than MINORMASK, two different brd_device may have the same
> devt, then only one of them can be successfully added.
> when rmmod brd.ko, it will cause oops when calling brd_exit.
>
> Follow those steps:
> # modprobe brd rd_nr=3 rd_size=102400 max_part=1048576
> # rmmod brd
> then, the oops will appear.
>
> Oops log:
> [ 726.613722] Call trace:
> [ 726.614175] kernfs_find_ns+0x24/0x130
> [ 726.614852] kernfs_find_and_get_ns+0x44/0x68
> [ 726.615749] sysfs_remove_group+0x38/0xb0
> [ 726.616520] blk_trace_remove_sysfs+0x1c/0x28
> [ 726.617320] blk_unregister_queue+0x98/0x100
> [ 726.618105] del_gendisk+0x144/0x2b8
> [ 726.618759] brd_exit+0x68/0x560 [brd]
> [ 726.619501] __arm64_sys_delete_module+0x19c/0x2a0
> [ 726.620384] el0_svc_common+0x78/0x130
> [ 726.621057] el0_svc_handler+0x38/0x78
> [ 726.621738] el0_svc+0x8/0xc
> [ 726.622259] Code: aa0203f6 aa0103f7 aa1e03e0 d503201f (7940e260)
>
> Here, we add brd_check_and_reset_par func to check and limit max_part par.
>
> --
> V2->V3: (suggested by Ming Lei)
> - clear .minors when running out of consecutive minor space in brd_alloc
> - remove limit of rd_nr
>
> V1->V2: add more checks in brd_check_par_valid as suggested by Ming Lei.
>
> Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
> ---
> drivers/block/brd.c | 35 ++++++++++++++++++++++++++++-------
> 1 file changed, 28 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/block/brd.c b/drivers/block/brd.c
> index df8103dd40ac..2295a0bafb5e 100644
> --- a/drivers/block/brd.c
> +++ b/drivers/block/brd.c
> @@ -330,16 +330,16 @@ static const struct block_device_operations brd_fops = {
> /*
> * And now the modules code and kernel interface.
> */
> -static int rd_nr = CONFIG_BLK_DEV_RAM_COUNT;
> -module_param(rd_nr, int, 0444);
> +static unsigned int rd_nr = CONFIG_BLK_DEV_RAM_COUNT;
> +module_param(rd_nr, uint, 0444);
The above change isn't needed.
> MODULE_PARM_DESC(rd_nr, "Maximum number of brd devices");
>
> unsigned long rd_size = CONFIG_BLK_DEV_RAM_SIZE;
> module_param(rd_size, ulong, 0444);
> MODULE_PARM_DESC(rd_size, "Size of each RAM disk in kbytes.");
>
> -static int max_part = 1;
> -module_param(max_part, int, 0444);
> +static unsigned int max_part = 1;
> +module_param(max_part, uint, 0444);
The above change isn't needed.
> MODULE_PARM_DESC(max_part, "Num Minors to reserve between devices");
>
> MODULE_LICENSE("GPL");
> @@ -393,7 +393,14 @@ static struct brd_device *brd_alloc(int i)
> if (!disk)
> goto out_free_queue;
> disk->major = RAMDISK_MAJOR;
> - disk->first_minor = i * max_part;
> + /*
> + * Clear .minors when running out of consecutive minor space since
> + * GENHD_FL_EXT_DEVT is set, and we can allocate from extended devt.
> + */
> + if ((i * disk->minors) & ~MINORMASK)
> + disk->minors = 0;
> + else
> + disk->first_minor = i * disk->minors;
The above looks a bit ugly, one nice way could be to change in
brd_alloc():
disk = brd->brd_disk = alloc_disk(((i * max_part) & ~MINORMASK) ?
0 : max_part);
> disk->fops = &brd_fops;
> disk->private_data = brd;
> disk->queue = brd->brd_queue;
> @@ -468,6 +475,21 @@ static struct kobject *brd_probe(dev_t dev, int *part, void *data)
> return kobj;
> }
>
> +static inline void brd_check_and_reset_par(void)
> +{
> + if (unlikely(!rd_nr))
> + rd_nr = 1;
zero rd_nr should work as expected, given user can create dev file via
mknod, and brd_probe() will be called for populate brd disk/queue when
the disk file is opened.
> +static inline void brd_check_and_reset_par(void)
> +{
> + if (unlikely(!rd_nr))
> + rd_nr = 1;
> +
> + if (unlikely(!max_part))
> + max_part = 1;
Another limit is that 'max_part' needs to be divided exactly by (1U <<
MINORBITS), something like:
max_part = 1UL << fls(max_part);
Thanks,
Ming
next prev parent reply other threads:[~2020-01-15 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 11:56 [PATCH V3] brd: check and limit max_part par Zhiqiang Liu
2020-01-15 2:27 ` Ming Lei [this message]
2020-01-20 13:14 ` Zhiqiang Liu
2020-01-20 22:58 ` Ming Lei
2020-01-21 1:44 ` Zhiqiang Liu
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=20200115022725.GA14585@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=guiyao@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=mingfangsen@huawei.com \
--cc=wubo40@huawei.com \
--cc=zhangsaisai@huawei.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