[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YV2h/iA79JhMJt07@redhat.com>
Date: Wed, 6 Oct 2021 09:17:50 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: axboe@...nel.dk, martin.petersen@...cle.com, jejb@...ux.ibm.com,
sagi@...mberg.me, adrian.hunter@...el.com, beanhuo@...ron.com,
ulf.hansson@...aro.org, avri.altman@....com, swboyd@...omium.org,
agk@...hat.com, josef@...icpanda.com
Cc: hch@...radead.org, hare@...e.de, bvanassche@....org,
ming.lei@...hat.com, linux-scsi@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-mmc@...r.kernel.org,
dm-devel@...hat.com, nbd@...er.debian.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 4/6] dm: add add_disk() error handling
On Mon, Sep 27 2021 at 5:59P -0400,
Luis Chamberlain <mcgrof@...nel.org> wrote:
> We never checked for errors on add_disk() as this function
> returned void. Now that this is fixed, use the shiny new
> error handling.
>
> There are two calls to dm_setup_md_queue() which can fail then,
> one on dm_early_create() and we can easily see that the error path
> there calls dm_destroy in the error path. The other use case is on
> the ioctl table_load case. If that fails userspace needs to call
> the DM_DEV_REMOVE_CMD to cleanup the state - similar to any other
> failure.
>
> Reviewed-by: Hannes Reinecke <hare@...e.de>
> Signed-off-by: Luis Chamberlain <mcgrof@...nel.org>
Reviewed-by: Mike Snitzer <snitzer@...hat.com>
Powered by blists - more mailing lists