linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 v4] UBIFS: compute KSA size and store in superblock
Date: Thu, 07 Jun 2012 12:10:40 +0300	[thread overview]
Message-ID: <1339060240.6875.90.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206062052140.31834@eristoteles.iwoars.net>

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

On Wed, 2012-06-06 at 20:52 +0200, Joel Reardon wrote:
> This patch makes the super block reserve space for the KSA. It computes the
> number of KSA LEBs and adds the ksa_lebs to on-medium superblock. The value is
> read off the media. The decision to use a KSA is controlled by use_ubifsec
> switch, added as a flag to the superblock, ubifs_info, and is controlled as a mount
> option. Validate superblock also checks these values.
> 
> This is tested by creating a drive and checking the mount debug output. The
> number of LEBS assigned during create_default_filesystem was changed to ensure
> that remounting does infact read the old value. When the use_ubifsec option
> was not enabled, no LEBs were assigned. Integck was run and the drive was
> filled to capacity. The LEBs in the KSA were not used when filled. Invalid
> value for ksa_lebs were used and then rejected by validate superblock.
> 
> Signed-off-by: Joel Reardon <reardonj@inf.ethz.ch>

Thank Joel, but this patch has several major issues with the KSA size
calculation, I believe. I've pushed it anyway to the 'joel' branch, then
on top of it I've added several clean-ups and little improvements, and
then on top of it I've added a patch which adds several TODO comments
for you. Please, take a look. I've also sent the patches to you
separately.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2012-06-07  9:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 13:10 [PATCH] UBIFS: compute KSA size and store in superblock Joel Reardon
2012-05-25 13:24 ` Artem Bityutskiy
2012-05-26 11:21   ` Joel Reardon
2012-05-26 13:31     ` Artem Bityutskiy
2012-05-30 13:32   ` [PATCH v2] " Joel Reardon
2012-05-30 15:18     ` Artem Bityutskiy
2012-05-31 10:12       ` Joel Reardon
2012-05-31 10:19         ` Artem Bityutskiy
2012-05-31 10:36           ` Artem Bityutskiy
2012-06-06 10:03             ` [PATCH v3] " Joel Reardon
2012-06-06 14:30               ` Artem Bityutskiy
2012-06-06 18:52               ` [PATCH v4] " Joel Reardon
2012-06-07  9:06                 ` [PATCH 1/4] UBIFS: correction to Joels' patch Artem Bityutskiy
2012-06-07  9:06                   ` [PATCH 2/4] UBIFS: another correction to joel's patch Artem Bityutskiy
2012-06-07  9:06                   ` [PATCH 3/4] UBIFS: improvement to Joel's patch Artem Bityutskiy
2012-06-07  9:06                   ` [PATCH 4/4] UBIFS: add TOTOs for Joel Artem Bityutskiy
2012-06-07  9:10                 ` 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=1339060240.6875.90.camel@sauron.fi.intel.com \
    --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).