Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Broken pread() on ARM
Date: Fri, 07 Feb 2014 10:56:59 +0100	[thread overview]
Message-ID: <87txcb6yac.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAKgsxVTJ+eYtOPxqe0CfxY+zfB8jNvCkJE8qD-tvQ42+VUZ=0Q@mail.gmail.com> (Justin Maggard's message of "Thu, 6 Feb 2014 17:54:18 -0800")

>>>>> "Justin" == Justin Maggard <jmaggard10@gmail.com> writes:

Hi,

 > Thanks for your answer.  A workable backport doesn't look all that
 > difficult -- just a bit ugly.  I submitted a kinda-sort backport at
 > http://lists.uclibc.org/pipermail/uclibc/2014-February/048220.html .

Yes, I saw. With all the uClibc mess (especially as we also support
external uClibc based toolchains) I really prefer to not add any more
patches if possible.

 > But I can't argue with just reverting those patches in the next
 > busybox.  I never had a problem with the old pread/pwrite emulation in
 > the first place.

No, it only triggers in rare cases. Afaik the issue is about locking
between the lseek and read/write, so it should only be an issue if you
have an application doing pread/pwrite from multiple threads with the
same file descriptor.

git gc was apparently such a case.


 > Hopefully uClibc 0.9.33.3 doesn't get released with this problem
 > though.

Lets hope not.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-07  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 22:26 [Buildroot] Broken pread() on ARM Justin Maggard
2014-02-05  0:21 ` Justin Maggard
2014-02-05  7:49   ` Peter Korsgaard
2014-02-07  1:54     ` Justin Maggard
2014-02-07  9:56       ` Peter Korsgaard [this message]
2014-02-05  7:47 ` Peter Korsgaard

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=87txcb6yac.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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