From: Bart Van Assche <bvanassche@acm.org>
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, "Darrick J. Wong" <djwong@kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH V2] Documentation: Document the kernel flag bdev_allow_write_mounted
Date: Fri, 23 Aug 2024 09:11:22 -0700 [thread overview]
Message-ID: <35febff2-e7cc-4b57-9ba5-798271fe0e3b@acm.org> (raw)
In-Reply-To: <20240823142840.63234-1-gpiccoli@igalia.com>
On 8/23/24 7:26 AM, Guilherme G. Piccoli wrote:
> + bdev_allow_write_mounted=
> + Format: <bool>
> + Control the ability of directly writing to mounted block
> + devices' page cache, i.e., allow / disallow writes that
> + bypasses the 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.
> +
Does this flag also affect direct I/O? If so, does this mean that the
reference to the page cache should be left out?
Thanks,
Bart.
next prev parent reply other threads:[~2024-08-23 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 14:26 [PATCH V2] Documentation: Document the kernel flag bdev_allow_write_mounted Guilherme G. Piccoli
2024-08-23 16:11 ` Bart Van Assche [this message]
2024-08-23 17:05 ` Darrick J. Wong
2024-08-23 18:02 ` 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=35febff2-e7cc-4b57-9ba5-798271fe0e3b@acm.org \
--to=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