From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joel Reardon <joel@clambassador.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UBIFS: add ksa_pos to replay buds, read when replaying
Date: Sun, 20 May 2012 21:40:15 +0300 [thread overview]
Message-ID: <1337539215.1745.11.camel@koala> (raw)
In-Reply-To: <alpine.DEB.2.00.1205201418170.27583@eristoteles.iwoars.net>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On Sun, 2012-05-20 at 14:28 +0200, Joel Reardon wrote:
> This patch read the ksa_pos from data nodes to the replay buds when performing
> a replay after unclean commit. This is critical for the correctness of the key
> state map, because the keys that are assigned to uncommited data nodes will be
> considered "unused" after mounting but will be considered "used" after
> replaying. The ksa_pos values stored in the replay bud are passed to the TNC
> using ubifs_tnc_add.
>
> This was tested by assigning distinct ksa_pos values and disabling commiting.
> Data was written and then the drive was remounted. The ksa_pos values were
> read from the journal and outputted while replaying. When the file was later
> read, it was confirmed that the ksa_pos values were already loaded into the
> TNC.
>
> Signed-off-by: Joel Reardon <reardonj@inf.ethz.ch>
Pushed to the "joel" branch as well.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-20 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 12:28 [PATCH] UBIFS: add ksa_pos to replay buds, read when replaying Joel Reardon
2012-05-20 18:40 ` Artem Bityutskiy [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=1337539215.1745.11.camel@koala \
--to=dedekind1@gmail.com \
--cc=joel@clambassador.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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).