[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1334160265.13842.23.camel@sauron.fi.intel.com>
Date: Wed, 11 Apr 2012 19:04:25 +0300
From: Artem Bityutskiy <dedekind1@...il.com>
To: Joel Reardon <joel@...mbassador.com>
Cc: "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] UBI: allow atomic updates to sychronously erase old PEB
On Wed, 2012-04-11 at 15:14 +0200, Joel Reardon wrote:
> This is a proposal for adding an immediate mode for atomic updates of LEBs in
> UBI. The idea is that, if the erase parameter is non-zero, then the old PEB
> will be erase after the new PEB is written, but before the function returns. It
> will not go into a work queue. This is for security-relevant situations where,
> for instance, the user needs assurance that sensitive information on an
> eraseblock is actually gone after the update.
Amended the commit message, and actually squashed 2 patches to preserve
bisectability.
I've pushed this to the master branch.
I've also re-based your 'joel' branch on top of the master branch.
Your old branch is saved in 'joel_old'.
I did this because there were minor a minor conflict with other UBIFS
changes, so I thought it makes sense to rebase now.
Some tips.
1. save all your changes.
2. checkout the 'joel' branch
3. git fetch -f
4. git reset --hard origin/joel
This will let you update to the latest joel.
git checkout -b jeol_old origin/joel_old
will give you your old stuff.
Yes, sorry, I told you I won't rebase but then I noticed small conflicts
and decided that it is better if you are up-to-date. If you are unhappy
- let me know and I'll return you to the old stuff and will apply this
patch there.
Thanks!
--
Best Regards,
Artem Bityutskiy
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists