From: Estelle HAMMACHE <estelle.hammache@st.com>
To: Joe Barnett <joseph.barnett@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: symlink corruption in jffs2
Date: Thu, 10 Mar 2005 14:22:19 +0100 [thread overview]
Message-ID: <42304A0B.434C1858@st.com> (raw)
In-Reply-To: 52249cdc0503091355364639dc@mail.gmail.com
Forwarded to the list.
Congratulations !
Joe Barnett wrote:
>
> Found it, map driver was broken in the copy_to/copy_from routines.
> Seems that the odd reads where broken
>
> On Fri, 18 Feb 2005 10:13:06 -0500, Joe Barnett
> <joseph.barnett@gmail.com> wrote:
> > Thank you all for your input, I will try your suggestions and post any
> > results I find back to the list.
> >
> > Kind regards,
> > Joseph
> >
> >
> > On Fri, 18 Feb 2005 15:06:32 +0100, Estelle wrote :
> > > Notice how even-length names are ok and odd-length names are KO.
> > > There was a thread about a similar problem, with a suggested
> > > approach for finding the bug.
> > > http://lists.infradead.org/pipermail/linux-mtd/2004-May/009735.html
> > >
> > > > lrwxrwxrwx 1 root root 11 Feb 17 2005 ld.so.1 -> ld-2.3.2.so?10
> > > > lrwxrwxrwx 1 root root 24 Feb 17 2005 libBrokenLocale.so.1 ->
> > > > libBrokenLocale-2.3.2.so
> > > > lrwxrwxrwx 1 root root 15 Feb 17 2005 libacl.so.1 -> libacl.so.1.1.0?.3
> > > > lrwxrwxrwx 1 root root 15 Feb 17 2005 libanl.so.1 ->
> > > > libanl-2.3.2.so?.so?so
> > > > lrwxrwxrwx 1 root root 16 Feb 17 2005 libattr.so.1 -> libattr.so.1.1.0
> > > > lrwxrwxrwx 1 root root 15 Feb 17 2005 libblkid.so.1 -> libblkid.so.1.0?3?
> > >
> > > bye
> > > Estelle
> > >
> >
prev parent reply other threads:[~2005-03-10 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 20:25 symlink corruption in jffs2 Joe Barnett
2005-02-18 8:05 ` Artem B. Bityuckiy
2005-02-18 14:06 ` Estelle HAMMACHE
[not found] ` <52249cdc05021807135f0ff90f@mail.gmail.com>
[not found] ` <52249cdc0503091355364639dc@mail.gmail.com>
2005-03-10 13:22 ` Estelle HAMMACHE [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=42304A0B.434C1858@st.com \
--to=estelle.hammache@st.com \
--cc=joseph.barnett@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.