From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4 v2] UBIFS: Change ubifsload to not read beyond the requested size
Date: Thu, 2 Dec 2010 16:18:39 +0100 [thread overview]
Message-ID: <201012021618.39668.sr@denx.de> (raw)
In-Reply-To: <20101101190500.27F5D4C7@gemini.denx.de>
Hi Wolfgang,
sorry for the late reply. I just "stumbled" again over this mail.
On Monday 01 November 2010 20:05:00 Wolfgang Denk wrote:
> I still wonder what's the logic behind this code. When will
> read_block() return -ENOENT (aka "No such file or directory") ?
> What are the other possible error conditions, and why would it make
> sense to continue reading after these other errors?
As it seems, ENOENT is used to mark "a hole" in the file system. Meaning space
that will be filled with zeros but does not occupy space (other than in the
index). So we should keep the existing logic intact.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2010-12-02 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 16:28 [U-Boot] [PATCH 3/4 v2] UBIFS: Change ubifsload to not read beyond the requested size Stefan Roese
2010-11-01 19:05 ` Wolfgang Denk
2010-12-02 15:18 ` Stefan Roese [this message]
2010-12-03 15:52 ` Stefan Roese
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=201012021618.39668.sr@denx.de \
--to=sr@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