All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Weidemann <kwe-lnx@postn.eu>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: udf: Prevent write-unsupported filesystem to be remounted read-write
Date: Wed, 23 Jan 2019 21:29:42 +0100	[thread overview]
Message-ID: <3aaf70fd-39de-be64-c9b3-e821167f9e99@postn.eu> (raw)
In-Reply-To: <20190122132228.GF13149@quack2.suse.cz>

Hello,

On Wednesday 22 January 2019 14:22 Jan Kara wrote
> The kernel is 5.0-rc3. What kernel were you testing with?

I don't remember exactly, but it was probably in the 4.20 line, as far
as I can tell.
The test case was a Veracrypt-compatible container file mounted with
cryptsetup using |the --readonly flag.|||
||

|--||
Kevin Weidemann|
||


      reply	other threads:[~2019-01-23 20:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <124cc6ea-ca79-20f2-651e-c2f909729ac0@gmx.de>
2019-01-14  0:33 ` udf: Prevent write-unsupported filesystem to be remounted read-write Kevin Weidemann
2019-01-14 10:30   ` Jan Kara
2019-01-14 12:00     ` Pali Rohár
2019-01-14 12:30       ` Jan Kara
2019-01-15  3:07         ` Michael Sabolish
2019-01-15  8:31           ` Pali Rohár
2019-01-15  8:41             ` Jan Kara
2019-01-15  8:48               ` Pali Rohár
2019-01-15  9:45                 ` Jan Kara
2019-01-15 10:50                   ` Pali Rohár
2019-01-15 11:15                     ` Jan Kara
2019-01-14 15:12     ` Pali Rohár
2019-01-14 16:26       ` Kevin Weidemann
2019-01-22 13:22     ` Jan Kara
2019-01-23 20:29       ` Kevin Weidemann [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=3aaf70fd-39de-be64-c9b3-e821167f9e99@postn.eu \
    --to=kwe-lnx@postn.eu \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.