| Age | Commit message (Collapse) | Author |
|---|
|
|
|
(cherry picked from commit b55ec98c6490b944593243c7da54dda1796e3f84)
|
|
(cherry picked from commit 0f622686af3ae5a8f03dae886b08c260b38bda16)
|
|
The pt_chown program is completely transparently called. It might
not be able to live with the various file descriptors the program
has open at the time of the call (e.g., under SELinux). Close all
but the needed descriptor and connect stdin, stdout, and stderr
with /dev/null. pt_chown shouldn't print anything when called to
do real work.
(cherry picked from commit 139ee080b6b428240bf49f3e6361f3ac729f891a)
|
|
Before the change they crash on startup. Perform IREL relocations
earlier to prevent this.
(cherry picked from commit 1c3c269b55c84c29ec1e2c70f122c5e33fef4257)
|
|
(cherry picked from commit ee5a5ba6725ee949483f043cd0cf2a1579b6b509)
|
|
(cherry picked from commit 49c7f27194d16976a6bb9c5b7be186662ec7a6e6)
|
|
(cherry picked from commit 6503cfe2de2105e83456fb04fdeb5d4e2323e9b4)
|
|
Programs forking and using RPC in the forks would use the same XIDs.
(cherry picked from commit c5a8b997e2de005697a992d8db5c54995bd361a8)
|
|
(cherry picked from commit 66221417957963c1d2df8d79f43573e328df2275)
|
|
I've noticed that sync_file_range is a stub on ppc/ppc64.
The kernel on these arches provides sync_file_range2 syscall with swapped
parameters.
The following completely untested patch ought to fix this.
(cherry picked from commit 8ad81b316bc158746aee18aa7d7df44d3eb61871)
|
|
(cherry picked from commit df1934daa7788ca5f19d82efb02cdf9b9c495b1a)
|
|
(cherry picked from commit 03ebadd9eaa4663f58bd3fa6fe8283f255925632)
|
|
(cherry picked from commit 3933378fd3cbe49c1e0ca42844f959eb12f05f60)
|
|
(cherry picked from commit 3a00b16da491d5c869795251e1ad4f43b3ba1469)
|
|
This is another bug in computing the fastmap. It was reported by a user
of sed because it usually does not happen with !_LIBC. However, it is
there in that case too.
The bug is that whenever we have a range at the beginning of the regex,
the regex must be tested on any possible multibyte character. The reason
why _LIBC masks it, is that in general there is a collation symbol for
each possible multibyte-character lead byte, so all the lead bytes are
in general already part of the fastmap.
The tests use cyrillic characters as an example. With _LIBC, they pass
without the patch too, but you can make them fail by removing collation
symbols handling.
(cherry picked from commit 815d8147a3418334ffa91e2384c6e159f0809d65)
|
|
(cherry picked from commit 7443244740724babd575943ee33c45da326afbe7)
|
|
(cherry picked from commit 4fb9241e4edbe238de8ba251f4448e31e8b1baf4)
|
|
(cherry picked from commit 2866eeb1b70c989591293d37ae292e71def16775)
|
|
(cherry picked from commit fabe43aba8fb46614eb2a74b2916bfbbf8fec10e)
|
|
Fix building on x86 when older linux headers lack __NR_fallocate define.
(cherry picked from commit f9a7bd536e0b1693db32e1330bbd96108ca63c42)
|
|
(cherry picked from commit 5ec794b4b537bc507010af28d2d93bb76d0972ac)
|
|
(cherry picked from commit 8964681064db9f13ee4ec7f46c53f04d66a04b99)
|
|
With big DNS answers like the one you get for goodtimesdot.com you can
get a truncated address list if IPv6 mapping is enabled. Instead tell
the caller to resize the buffer.
|
|
|
|
|
|
|
|
|
|
do_sym should use DL_FIXUP_VALUE_XXX macros to call IFUNC function.
Otherwise, it won't compile on ia64. This patch fixes it and adds
a test.
|
|
Due to alignment of 64bit parameters there is a dummy second argument.
But other than that the syscall arguments are directly mapped to the
function arguments.
|
|
I've just committed STT_GNU_IFUNC ppc/ppc64 support into prelink,
and this patch is needed on the glibc side. Without it ld.so segfaults,
as in dl-conflict.c sym_map is always NULL. While dl-machine.h could use
RESOLVE_CONFLICT_FIND_MAP macro to compute it, it doesn't make sense,
because with prelink we know it is already properly relocated (all relative
relocations are applied by prelink).
|
|
As reported in http://bugzilla.redhat.com/533063 , preadv/pwritev prototypes
are wrong on 32-bit arches with -D_FILE_OFFSET_BITS=64 and as I've just
found, fallocate is wrong too.
The problem is that only off_t is remapped to the 64-bit type transparently,
__off_t is not.
|
|
|
|
This code is only used when MALLOC_CHECK_ is used. Then some bogus
crashes and/or assert could result from the locking changes. The code
ain't fast.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
