From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] JFFS2: bug fix for summary support.
Date: Wed, 13 Apr 2011 16:17:15 +0200 [thread overview]
Message-ID: <m2mxju8cd0.fsf@ohwell.denx.de> (raw)
In-Reply-To: <BANLkTimbGpFWO4Kk3UvEcSB2rwQJEp7j-Q@mail.gmail.com> (Baidu Liu's message of "Wed, 13 Apr 2011 21:19:35 +0800")
Hi Baidu,
> Hi, Detlev:
>
> 2011/4/13 Detlev Zundel <dzu@denx.de>:
>> Hi Leo,
>>
>>> This patch fixes some issues with JFFS2 summary support in U-Boot.
>>> 1/ Bug fix for summary support: we need to get the latest DIRENT.
>>
>> Can you give an exmaple how this bug showed?
>>
> For example, if you create a file in linux jffs2 which config summary
> support, then you delete the file , you will not see the file in
> linux jffs2. But you can also see this file in uboot after you reset
> the system.
> That is because all the nodes in jffs2 which config summary support
> will not be marked as obsolete. The delete file's DIRENT node will be
> seen in uboot. So what we need to do is to get the latest DIRENT whose
> ino in DIRENT is 0. So we will not see this file in uboot which is
> what we want.
Ok, I see. Please include this in the commit message in the next round.
Cheers
Detlev
--
Actually, to be honest, i see no shame in missing things. All those
neutrinos don't seem to mind, despite their direction and energy...
-- Thien-Thi Nguyen, <87r5gqop65.fsf@ambire.localdomain>
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
prev parent reply other threads:[~2011-04-13 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 13:34 [U-Boot] [PATCH] JFFS2: bug fix for summary support Leo Liu
2011-04-13 11:23 ` Detlev Zundel
2011-04-13 13:19 ` Baidu Liu
2011-04-13 14:17 ` Detlev Zundel [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=m2mxju8cd0.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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