From: Steve Magnani <steve.magnani@digidescorp.com>
To: jack@suse.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] udf: Fix corrupt on-disk integrity descriptor following sync()
Date: Fri, 8 Feb 2019 11:34:53 -0600 [thread overview]
Message-ID: <20190208173455.20151-1-steve@digidescorp.com> (raw)
In cases where the next unique ID or file/directory count of the
in-core Logical Volume Integrity Descriptor have been updated,
a sync() causes a (corrupt) LVID with a stale CRC to be written to disk.
Ordinarily, this is corrected by an update of the on-disk LVID that occurs
when the filesystem is unmounted. However, if power is lost or the
filesystem resides on a device that is surprise-removed, the corrupt LVID
remains and can complicate later remounting or fsck/chkdsk.
next reply other threads:[~2019-02-08 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 17:34 Steve Magnani [this message]
2019-02-08 17:34 ` [PATCH 1/2] udf: factor out LVID finalization for reuse Steve Magnani
2019-02-08 17:34 ` [PATCH 2/2] udf: finalize integrity descriptor before writeback Steve Magnani
2019-02-09 4:06 ` [PATCH 0/2] udf: Fix corrupt on-disk integrity descriptor following sync() Steve Magnani
2019-02-11 8:42 ` Jan Kara
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=20190208173455.20151-1-steve@digidescorp.com \
--to=steve.magnani@digidescorp.com \
--cc=jack@suse.com \
--cc=linux-kernel@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