linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Michael Hudson-Doyle <michael.hudson@ubuntu.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] resize2fs: open device read-only when -P is passed
Date: Fri, 12 Aug 2022 21:11:17 -0400	[thread overview]
Message-ID: <Yvb6NT31OUb1y2kt@mit.edu> (raw)
In-Reply-To: <20220526010828.1462397-1-michael.hudson@ubuntu.com>

On Thu, May 26, 2022 at 01:08:28PM +1200, Michael Hudson-Doyle wrote:
> We ran into this because we noticed that resize2fs -P $device was
> triggering udev events.
> 
> I added a very simple test that just checks resize2fs -P on a file
> lacking the w bit succeeds.
> 
> Signed-off-by: Michael Hudson-Doyle <michael.hudson@ubuntu.com>

Applied, thanks!

						- Ted

  reply	other threads:[~2022-08-13  1:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  1:08 [PATCH] resize2fs: open device read-only when -P is passed Michael Hudson-Doyle
2022-08-13  1:11 ` Theodore Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-26  0:33 Michael Hudson-Doyle

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=Yvb6NT31OUb1y2kt@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=michael.hudson@ubuntu.com \
    /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;
as well as URLs for NNTP newsgroup(s).