From: Jens Axboe <axboe@kernel.dk>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>, linux-doc@vger.kernel.org
Cc: corbet@lwn.net, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, kernel-dev@igalia.com,
kernel@gpiccoli.net, Bart Van Assche <bvanassche@acm.org>,
"Darrick J. Wong" <djwong@kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH V3] Documentation: Document the kernel flag bdev_allow_write_mounted
Date: Fri, 23 Aug 2024 12:17:54 -0600 [thread overview]
Message-ID: <6f303c9f-7180-45ef-961e-6f235ed57553@kernel.dk> (raw)
In-Reply-To: <20240823180635.86163-1-gpiccoli@igalia.com>
On 8/23/24 12:05 PM, Guilherme G. Piccoli wrote:
> Commit ed5cc702d311 ("block: Add config option to not allow writing to mounted
> devices") added a Kconfig option along with a kernel command-line tuning to
> control writes to mounted block devices, as a means to deal with fuzzers like
> Syzkaller, that provokes kernel crashes by directly writing on block devices
> bypassing the filesystem (so the FS has no awareness and cannot cope with that).
>
> The patch just missed adding such kernel command-line option to the kernel
> documentation, so let's fix that.
>
> Cc: Bart Van Assche <bvanassche@acm.org>
> Cc: Darrick J. Wong <djwong@kernel.org>
> Cc: Jan Kara <jack@suse.cz>
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
> ---
>
> V3: Dropped reference to page cache (thanks Bart!).
>
> V2 link: https://lore.kernel.org/r/20240823142840.63234-1-gpiccoli@igalia.com
>
>
> Documentation/admin-guide/kernel-parameters.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 09126bb8cc9f..58b9455baf4a 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -517,6 +517,18 @@
> Format: <io>,<irq>,<mode>
> See header of drivers/net/hamradio/baycom_ser_hdx.c.
>
> + bdev_allow_write_mounted=
> + Format: <bool>
> + Control the ability of directly writing to mounted block
Since we're nit picking...
Control the ability to directly write [...]
The directly may be a bit confusing ("does it mean O_DIRECT?"), so maybe
just
Control the ability to write [...]
would be better and more clear.
> + devices, i.e., allow / disallow writes that bypasses the
Since we're nit picking, s/bypasses/bypass
> + FS. This was implemented as a means to prevent fuzzers
> + from crashing the kernel by overwriting the metadata
> + underneath a mounted FS without its awareness. This
> + also prevents destructive formatting of mounted
> + filesystems by naive storage tooling that don't use
> + O_EXCL. Default is Y and can be changed through the
> + Kconfig option CONFIG_BLK_DEV_WRITE_MOUNTED.
> +
> bert_disable [ACPI]
> Disable BERT OS support on buggy BIOSes.
--
Jens Axboe
next prev parent reply other threads:[~2024-08-23 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 18:05 [PATCH V3] Documentation: Document the kernel flag bdev_allow_write_mounted Guilherme G. Piccoli
2024-08-23 18:17 ` Jens Axboe [this message]
2024-08-23 18:42 ` Darrick J. Wong
2024-08-26 0:17 ` Guilherme G. Piccoli
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=6f303c9f-7180-45ef-961e-6f235ed57553@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=jack@suse.cz \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@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