From: Sascha Hauer <s.hauer@pengutronix.de>
To: Wjatscheslaw Stoljarski <wjatscheslaw.stoljarski@kiwigrid.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Bug?
Date: Thu, 7 Jul 2016 12:07:30 +0200 [thread overview]
Message-ID: <20160707100730.GL20657@pengutronix.de> (raw)
In-Reply-To: <20160707093738.GA24951@gmail.com>
On Thu, Jul 07, 2016 at 11:37:38AM +0200, Wjatscheslaw Stoljarski wrote:
> Hi Sascha,
>
> I can reproduce this on barebox 2016.06.0 for example with:
> cp /env/data/ansi-colors /env/data/
> But "memcpy -s /env/data/ansi-colors -d /env/data/ansi-colors 0 0" works without problem.
>
> I try this with next barebox version (2016.07.0). Maybe it's already fixed.
Nope, it isn't.
So the problem comes when you copy a file over itself. This indeed
crashes here aswell. This points to a bug in the ramfs implementation
which should be fixed. Also there's another bug in 'cp': copy_file
should recognize when source and destination are the same file and
report an error in this case.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-07-07 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 14:02 Bug? Wjatscheslaw Stoljarski
2016-07-07 6:55 ` Bug? Sascha Hauer
2016-07-07 9:37 ` Bug? Wjatscheslaw Stoljarski
2016-07-07 10:07 ` Sascha Hauer [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=20160707100730.GL20657@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=wjatscheslaw.stoljarski@kiwigrid.com \
/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