All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Bug & Question] ubifs does not understand ".." in file path ?
Date: Fri, 13 Jul 2018 12:18:33 +0200	[thread overview]
Message-ID: <4938782.XPOmnulII3@blindfold> (raw)
In-Reply-To: <3b661caf-e582-f833-b6c9-afa59c999aae@denx.de>

Marek,

Am Freitag, 13. Juli 2018, 10:53:48 CEST schrieb Marek Vasut:
> On 07/13/2018 10:15 AM, Richard Weinberger wrote:
> > Am Freitag, 13. Juli 2018, 10:00:23 CEST schrieb Marek Vasut:
> >> CCing Richard, btw ubifs in U-Boot is completely broken.
> > 
> > BTW: Can you please define "completely broken"?
> > 
> > Last week it used to work here. ;)
> 
> Did you fix it ? Last time we discussed this, about a month ago, you
> mentioned the ubifs code is completely broken and I had massive problems
> with it myself.

Well, this is not what I said on IRC.
The u-boot "bindings" are not nice but functional.
We saw over the last time a few ubifs_assert() triggering, these triggered since
ever but nobody noticed. The loglevel rework just exposed them.

So yes, there are things that need improving but calling the whole thing as broken
is false.
For the ".." issue, here someone has to sit down and either make sure that all filesystems
in u-boot get this handled in a generic way or hack it directly into the ubifs code.
I prefer the former...

Thanks,
//richard

      reply	other threads:[~2018-07-13 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  4:44 [U-Boot] [Bug & Question] ubifs does not understand ".." in file path ? Masahiro Yamada
2018-07-13  7:44 ` Heiko Schocher
2018-07-13  8:00   ` Marek Vasut
2018-07-13  8:08     ` Richard Weinberger
2018-07-13  8:15     ` Richard Weinberger
2018-07-13  8:53       ` Marek Vasut
2018-07-13 10:18         ` Richard Weinberger [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=4938782.XPOmnulII3@blindfold \
    --to=richard@nod.at \
    --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 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.