From: Luis Chamberlain <mcgrof@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-raid@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, axboe@kernel.dk, hch@lst.de,
efremov@linux.com, song@kernel.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, viro@zeniv.linux.org.uk,
hare@suse.de, jack@suse.cz, ming.lei@redhat.com, tj@kernel.org
Subject: Re: [PATCH v2 1/2] block: make __register_blkdev() return an error
Date: Fri, 15 Oct 2021 11:34:07 -0700 [thread overview]
Message-ID: <YWnJnyysQQ86i5e/@bombadil.infradead.org> (raw)
In-Reply-To: <11a884b0-53f2-5174-fcb2-6247cece7104@i-love.sakura.ne.jp>
On Tue, Sep 28, 2021 at 09:19:47AM +0900, Tetsuo Handa wrote:
> On 2021/09/28 7:03, Luis Chamberlain wrote:
> > diff --git a/drivers/block/ataflop.c b/drivers/block/ataflop.c
> > index 5dc9b3d32415..be0627345b21 100644
> > --- a/drivers/block/ataflop.c
> > +++ b/drivers/block/ataflop.c
> > @@ -1989,24 +1989,34 @@ static int ataflop_alloc_disk(unsigned int drive, unsigned int type)
> >
> > static DEFINE_MUTEX(ataflop_probe_lock);
> >
> > -static void ataflop_probe(dev_t dev)
> > +static int ataflop_probe(dev_t dev)
> > {
> > int drive = MINOR(dev) & 3;
> > int type = MINOR(dev) >> 2;
> > + int err = 0;
> >
> > if (type)
> > type--;
> >
> > - if (drive >= FD_MAX_UNITS || type >= NUM_DISK_MINORS)
> > - return;
> > + if (drive >= FD_MAX_UNITS || type >= NUM_DISK_MINORS) {
> > + err = -EINVAL;
> > + goto out;
> > + }
> > +
> > mutex_lock(&ataflop_probe_lock);
> > if (!unit[drive].disk[type]) {
> > - if (ataflop_alloc_disk(drive, type) == 0) {
> > - add_disk(unit[drive].disk[type]);
> > + err = ataflop_alloc_disk(drive, type);
> > + if (err == 0) {
> > + err = add_disk(unit[drive].disk[type]);
> > + if (err)
> > + blk_cleanup_disk(unit[drive].disk[type]);
> > unit[drive].registered[type] = true;
>
> Why setting registered to true despite add_disk() failed?
> del_gendisk() without successful add_disk() sounds wrong.
That was a mistake, fixed.
> Don't we need to undo ataflop_alloc_disk() because it sets
> unit[drive].disk[type] to non-NULL ?
ataflop_alloc_disk() just calls blk_mq_alloc_disk() for its
allocation, and so blk_cleanup_disk() does that for us. Please
let me know if I missed anything.
> > diff --git a/drivers/block/brd.c b/drivers/block/brd.c
> > index c2bf4946f4e3..82a93044de95 100644
> > --- a/drivers/block/brd.c
> > +++ b/drivers/block/brd.c
> > @@ -426,10 +426,11 @@ static int brd_alloc(int i)
> > return err;
> > }
> >
> > -static void brd_probe(dev_t dev)
> > +static int brd_probe(dev_t dev)
> > {
> > int i = MINOR(dev) / max_part;
> > struct brd_device *brd;
> > + int err = 0;
> >
> > mutex_lock(&brd_devices_mutex);
> > list_for_each_entry(brd, &brd_devices, brd_list) {
> > @@ -437,9 +438,11 @@ static void brd_probe(dev_t dev)
> > goto out_unlock;
> > }
> >
> > - brd_alloc(i);
> > + err = brd_alloc(i);
> > out_unlock:
> > mutex_unlock(&brd_devices_mutex);
> > +
> > + return err;
> > }
> >
> > static void brd_del_one(struct brd_device *brd)
>
> https://lkml.kernel.org/r/e205f13d-18ff-a49c-0988-7de6ea5ff823@i-love.sakura.ne.jp
> will require this part to be updated.
Indeed, rebased, thanks for the heads up!
> > diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c
> > index 0434f28742e7..95a1c8ef62f7 100644
> > --- a/drivers/block/floppy.c
> > +++ b/drivers/block/floppy.c
> > @@ -4517,21 +4517,27 @@ static int floppy_alloc_disk(unsigned int drive, unsigned int type)
> >
> > static DEFINE_MUTEX(floppy_probe_lock);
> >
> > -static void floppy_probe(dev_t dev)
> > +static int floppy_probe(dev_t dev)
> > {
> > unsigned int drive = (MINOR(dev) & 3) | ((MINOR(dev) & 0x80) >> 5);
> > unsigned int type = (MINOR(dev) >> 2) & 0x1f;
> > + int err = 0;
> >
> > if (drive >= N_DRIVE || !floppy_available(drive) ||
> > type >= ARRAY_SIZE(floppy_type))
> > - return;
> > + return -EINVAL;
> >
> > mutex_lock(&floppy_probe_lock);
> > if (!disks[drive][type]) {
> > - if (floppy_alloc_disk(drive, type) == 0)
> > - add_disk(disks[drive][type]);
> > + if (floppy_alloc_disk(drive, type) == 0) {
> > + err = add_disk(disks[drive][type]);
> > + if (err)
> > + blk_cleanup_disk(disks[drive][type]);
>
> This makes future floppy_probe() no-op once add_disk() failed (or maybe a bad
> thing happens somewhere else), for disks[drive][type] was set to non-NULL by
> floppy_alloc_disk() but blk_cleanup_disk() does not reset it to NULL.
Thanks!
I think just setting disks[drive][type] = NULL after the
blk_cleanup_disk() fixes that issue.
> According to floppy_module_exit() which tries to cleanup it, implementing
> undo might be complicated...
I can't see what would be missing from just setting disks[drive][type] = NULL.
Can you clarify?
Luis
next prev parent reply other threads:[~2021-10-15 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 22:03 [PATCH v2 0/2] block: 7th -- last batch of add_disk() error handling conversions Luis Chamberlain
2021-09-27 22:03 ` [PATCH v2 1/2] block: make __register_blkdev() return an error Luis Chamberlain
2021-09-28 0:19 ` Tetsuo Handa
2021-10-15 18:34 ` Luis Chamberlain [this message]
2021-09-28 0:57 ` Finn Thain
2021-10-15 18:43 ` Luis Chamberlain
2021-09-27 22:03 ` [PATCH v2 2/2] block: add __must_check for *add_disk*() callers Luis Chamberlain
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=YWnJnyysQQ86i5e/@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).