From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B293AC4332F for ; Mon, 6 Nov 2023 14:48:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231493AbjKFOsE (ORCPT ); Mon, 6 Nov 2023 09:48:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55072 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229705AbjKFOsD (ORCPT ); Mon, 6 Nov 2023 09:48:03 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 64270B6; Mon, 6 Nov 2023 06:48:00 -0800 (PST) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9D32DC433C8; Mon, 6 Nov 2023 14:47:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1699282080; bh=NbG9LobHKx4M+DgwpqcL4EQ1C+67EgVNxWBQ5IyC8Hs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oSDNx7PrJ6RAX3b2chmxrEWpWHyFxUov+iA7LLvQzfDHsO3OgyrgRdnHpOU2+FIAi SaIqI+X//CZpPaOrE2Y/3oHMyyAM2GtJpWB+rfc+zjq5K1f3ZsnYh8/eqlTEdCrmlW XJ9p4wddF43aAUrr4RfZqUO+wvBe0+5CxzSA7l1tBT3JZkvciiRbWVBdRCGHA1LK0e TKnpW7ihvkg1VofShx6zeEFHnxd5F3KzUodrg2ss3vI96DHDiLLGOQ+mHThxt5jM8/ lA8CXqWDC+HGdl16t9rQ1c+IMV4iBT0EgR6LPsrCbfoyoQCb7uu5H41GFV/emJXqNA Dkmvx+qBH4XlQ== Date: Mon, 6 Nov 2023 15:47:54 +0100 From: Christian Brauner To: Jan Kara Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, Jens Axboe , Christoph Hellwig , Kees Cook , syzkaller , Alexander Popov , linux-xfs@vger.kernel.org, Dmitry Vyukov Subject: Re: [PATCH 3/7] block: Add config option to not allow writing to mounted devices Message-ID: <20231106-einladen-macht-30a9ad957294@brauner> References: <20231101173542.23597-1-jack@suse.cz> <20231101174325.10596-3-jack@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20231101174325.10596-3-jack@suse.cz> Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Wed, Nov 01, 2023 at 06:43:08PM +0100, Jan Kara wrote: > Writing to mounted devices is dangerous and can lead to filesystem > corruption as well as crashes. Furthermore syzbot comes with more and > more involved examples how to corrupt block device under a mounted > filesystem leading to kernel crashes and reports we can do nothing > about. Add tracking of writers to each block device and a kernel cmdline > argument which controls whether other writeable opens to block devices > open with BLK_OPEN_RESTRICT_WRITES flag are allowed. We will make > filesystems use this flag for used devices. > > Note that this effectively only prevents modification of the particular > block device's page cache by other writers. The actual device content > can still be modified by other means - e.g. by issuing direct scsi > commands, by doing writes through devices lower in the storage stack > (e.g. in case loop devices, DM, or MD are involved) etc. But blocking > direct modifications of the block device page cache is enough to give > filesystems a chance to perform data validation when loading data from > the underlying storage and thus prevent kernel crashes. > > Syzbot can use this cmdline argument option to avoid uninteresting > crashes. Also users whose userspace setup does not need writing to > mounted block devices can set this option for hardening. > > Link: https://lore.kernel.org/all/60788e5d-5c7c-1142-e554-c21d709acfd9@linaro.org > Signed-off-by: Jan Kara > --- A few minor tweaks I would do in-tree. Please see below. I know it's mostly stylistic that's why I would do it so there's no resend dance for non-technical reasons. > block/Kconfig | 20 +++++++++++++ > block/bdev.c | 62 ++++++++++++++++++++++++++++++++++++++- > include/linux/blk_types.h | 1 + > include/linux/blkdev.h | 2 ++ > 4 files changed, 84 insertions(+), 1 deletion(-) > > diff --git a/block/Kconfig b/block/Kconfig > index f1364d1c0d93..ca04b657e058 100644 > --- a/block/Kconfig > +++ b/block/Kconfig > @@ -78,6 +78,26 @@ config BLK_DEV_INTEGRITY_T10 > select CRC_T10DIF > select CRC64_ROCKSOFT > > +config BLK_DEV_WRITE_MOUNTED > + bool "Allow writing to mounted block devices" > + default y Let's hope that this can become the default one day. > +static void bdev_unblock_writes(struct block_device *bdev) > +{ > + bdev->bd_writers = 0; > +} > + > +static bool blkdev_open_compatible(struct block_device *bdev, blk_mode_t mode) I would like to mirror our may_{open,create}() routines here and call this: bdev_may_open() This is a well-known vfs pattern and also easy to understand for block devs as well. > @@ -800,12 +834,21 @@ struct bdev_handle *bdev_open_by_dev(dev_t dev, blk_mode_t mode, void *holder, > goto abort_claiming; > if (!try_module_get(disk->fops->owner)) > goto abort_claiming; > + ret = -EBUSY; > + if (!blkdev_open_compatible(bdev, mode)) > + goto abort_claiming; > if (bdev_is_partition(bdev)) > ret = blkdev_get_part(bdev, mode); > else > ret = blkdev_get_whole(bdev, mode); > if (ret) > goto put_module; > + if (!bdev_allow_write_mounted) { > + if (mode & BLK_OPEN_RESTRICT_WRITES) > + bdev_block_writes(bdev); > + else if (mode & BLK_OPEN_WRITE) > + bdev->bd_writers++; > + } I would like to move this to a tiny helper for clarity: static void bdev_claim_write_access(struct block_device *bdev) { if (!bdev_allow_write_mounted) return; /* Claim exclusive or shared write access to the block device. */ if (mode & BLK_OPEN_RESTRICT_WRITES) bdev_block_writes(bdev); else if (mode & BLK_OPEN_WRITE) bdev->bd_writers++; } > if (holder) { > bd_finish_claiming(bdev, holder, hops); > > @@ -901,6 +944,14 @@ void bdev_release(struct bdev_handle *handle) > sync_blockdev(bdev); > > mutex_lock(&disk->open_mutex); > + if (!bdev_allow_write_mounted) { > + /* The exclusive opener was blocking writes? Unblock them. */ > + if (handle->mode & BLK_OPEN_RESTRICT_WRITES) > + bdev_unblock_writes(bdev); > + else if (handle->mode & BLK_OPEN_WRITE) > + bdev->bd_writers--; > + } static void bdev_yield_write_access(struct block_device *bdev) { if (!bdev_allow_write_mounted) return; /* Yield exclusive or shared write access. */ if (handle->mode & BLK_OPEN_RESTRICT_WRITES) bdev_unblock_writes(bdev); else if (handle->mode & BLK_OPEN_WRITE) bdev->bd_writers--; }