public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
	Deepanshu Kartikey <kartikey406@gmail.com>,
	axboe@kernel.dk, dvyukov@google.com, adilger.kernel@dilger.ca,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+fb32afec111a7d61b939@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] loop: block changing lo_offset/lo_sizelimit on mounted device
Date: Tue, 31 Mar 2026 08:02:40 -0700	[thread overview]
Message-ID: <acviEBik3OrtfiRV@infradead.org> (raw)
In-Reply-To: <20260331122408.GB74409@macsyma-wired.lan>

On Tue, Mar 31, 2026 at 08:24:08AM -0400, Theodore Tso wrote:
> Do we expect people to seriously be running with
> !CONFIG_BLK_DEV_WRITE_MOUNTED? 

Yes, it's the only sane option.

> I view this as a syzkaller noise
> suppression only.  As I mentioned earlier this option will very likely
> break grub.

Yes, the horrible things grub does won't work with this.  But I thought
with EFI-based systems people had mostly stopped using the access
to the root file system misfeature in grub.  And a lot of specialized
distros seem to stop using grub entirely.


      reply	other threads:[~2026-03-31 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  5:46 [PATCH v2] loop: block changing lo_offset/lo_sizelimit on mounted device Deepanshu Kartikey
2026-03-31  7:22 ` Christoph Hellwig
2026-03-31 12:24   ` Theodore Tso
2026-03-31 15:02     ` Christoph Hellwig [this message]

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=acviEBik3OrtfiRV@infradead.org \
    --to=hch@infradead.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=axboe@kernel.dk \
    --cc=dvyukov@google.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+fb32afec111a7d61b939@syzkaller.appspotmail.com \
    --cc=tytso@mit.edu \
    /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