From: "Pali Rohár" <pali.rohar@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] udf: Do not mark possibly inconsistent filesystems as closed
Date: Thu, 1 Mar 2018 18:26:09 +0100 [thread overview]
Message-ID: <20180301172609.icjmg476j7t3db3f@pali> (raw)
In-Reply-To: <20180301123308.arm2t6bvdllaus3t@quack2.suse.cz>
On Thursday 01 March 2018 13:33:08 Jan Kara wrote:
> On Wed 28-02-18 22:58:38, Pali Rohár wrote:
> > On Wednesday 28 February 2018 12:22:55 Jan Kara wrote:
> > > If logical volume integrity descriptor contains non-closed integrity
> > > type when mounting the volume, there are high chances that the volume is
> > > not consistent (device was detached before the filesystem was
> > > unmounted). Warn when mounting such volume and don't touch integrity
> >
> > Need to edit commit message as there is no warning in patch...
>
> Good point. Fixed and pushed to my tree. Can I add your Reviewed-by tag?
Yes!
--
Pali Rohár
pali.rohar@gmail.com
prev parent reply other threads:[~2018-03-01 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 11:22 [PATCH] udf: Do not mark possibly inconsistent filesystems as closed Jan Kara
2018-02-28 21:58 ` Pali Rohár
2018-03-01 12:33 ` Jan Kara
2018-03-01 17:26 ` Pali Rohár [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=20180301172609.icjmg476j7t3db3f@pali \
--to=pali.rohar@gmail.com \
--cc=jack@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).