search for: __openat

...> + > +int open(const char *pathname, int flags, mode_t mode) > +{ > + return openat(AT_FDCWD, pathname, flags, mode); > +} > + > +#endif This applies equally to a 32-bit platform that doesn't define __NR_open, except there we need to add O_LARGEFILE to the flags and call __openat in order to not have to pull in openat.c as well. I suggest merging this into open.c and making it look something like: #ifndef __NR_open # if __BITSIZE == 32 extern int __openat(int, const char *, int, mode_t); int open(const char *pathname, int flags, mode_t mode) { return __openat(AT_FDCWD...

I think it's time to issue an official call for anything missing in klibc 2.0... testing would also be appreciated. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

...;h=cd5927c02749b7c9d58b5144586505c85b903c27 Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Mon, 21 May 2012 10:21:21 -0700 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 21 May 2012 10:24:45 -0700 [klibc] SYSCALLS.def: add openat() on 64-bit platforms We had __openat() as a system call on 32 bits, wrappered in openat.c; however, the unwrappered system call used on 64-bit platforms was missing from SYSCALLS.def. Reported-by: Maximilan Attems <max at stro.at> Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- usr/klibc/SYSCALLS.def | 1 + 1 fi...

Hi, number three, where I first thought it was a GCC bug but is apparently bad code in klibc. Submitted with permission: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47533#c6 Patch attached again (sorry) not just because that is easier with my mail system but also to keep original author intact. bye, //mirabilos -- > emacs als auch vi zum Kotzen finde (joe rules) und pine f?r den einzig >

.../klibc/SYSCALLS.def index 41cfa17..e62a9e8 100644 --- a/usr/klibc/SYSCALLS.def +++ b/usr/klibc/SYSCALLS.def @@ -157,15 +157,17 @@ int getcwd::__getcwd(char *, size_t); /* * I/O operations */ -<!i386,m68k,64> int open::__open(const char *, int, mode_t); -<?!i386,m68k,64> int openat::__openat(int, const char *, int, mode_t); -<?64> int open(const char *, int, mode_t); -<64> int openat(int, const char *, int, mode_t); +<!i386,m68k,64,x32> int open::__open(const char *, int, mode_t); +<?!i386,m68k,64,x32> int openat::__openat(int, const char *, int, mode_t); +<?...

...t;?> int inotify_init(); <?> int inotify_add_watch(int, const char *, __u32); <?> int inotify_rm_watch(int, __u32); @@ -158,7 +159,7 @@ int getcwd::__getcwd(char *, size_t); */ <!i386,m68k,64> int open::__open(const char *, int, mode_t); <?!i386,m68k,64> int openat::__openat(int, const char *, int, mode_t); -<64> int open(const char *, int, mode_t); +<?64> int open(const char *, int, mode_t); <64> int openat(int, const char *, int, mode_t); ssize_t read(int, void *, size_t); ssize_t write(int, const void *, size_t); @@ -166,14 +167,14 @@ int close(...

Hi, after a year, I decided to hack on klibc again. I?ve reworked both the patch to add mkstemp(), discussing to use AT_RANDOM as cheap entropy source on IRC (if there will ever be another entropy consumer, I can quickly write a minimal arc4random() seeded from it, as it has only 16 octets), capable of making a working mksh (static and shared) on amd64/xen, and the m68k support code, leading to

...nat.c index 2975112..e2ce67b 100644 --- a/klibc/openat.c +++ b/klibc/openat.c @@ -10,7 +10,7 @@ #include <fcntl.h> #include <bitsize.h> -#if _BITSIZE == 32 && !defined(__i386__) && defined(__NR_openat) +#if _BITSIZE == 32 && defined(__NR_openat) extern int __openat(int, const char *, int, mode_t);

Hi, I?ve gone through the mailing list archives and hereby want to resubmit my pending patches. Most are independent of each other, except the m68k patch which will only be complete if sigsuspend is also fixed. (It can be applied before that, though.) http://www.zytor.com/pipermail/klibc/2012-January/003173.html [PATCH] fix m68k support Resubmitted here as 0005. While there was a question from

Hello, This series introduces arm64 support to klibc. I've rebased the work from Neil Williams and Anil Singhar into the following three patches. Most of the code changes are due to new syscall implementations being needed for arm64 as a only a minimal set of syscalls are defined in the arm64 kernel. This series is to be applied against the latest klibc, just after 25a66fa README.klibc:

Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64

...t;?> int inotify_init(); <?> int inotify_add_watch(int, const char *, __u32); <?> int inotify_rm_watch(int, __u32); @@ -158,7 +159,7 @@ int getcwd::__getcwd(char *, size_t); */ <!i386,m68k,64> int open::__open(const char *, int, mode_t); <?!i386,m68k,64> int openat::__openat(int, const char *, int, mode_t); -<64> int open(const char *, int, mode_t); +<?64> int open(const char *, int, mode_t); <64> int openat(int, const char *, int, mode_t); ssize_t read(int, void *, size_t); ssize_t write(int, const void *, size_t); @@ -166,14 +167,14 @@ int close(...

...de -I/root/gen/trunk/knl/linux/usr//arch/powerpc/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=32 -fno-stack-protector -fwrapv -m32 -Os -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/syscalls/__open.o usr/klibc/syscalls/__open.S ppc-linux-gcc -Wp,-MD,usr/klibc/syscalls/.__openat.o.d -D__ASSEMBLY__ -nostdinc -iwithprefix include -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include/arch/ppc -Iusr/include/arch/ppc -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include/bits32 -Iusr/include/bits32 -I/root/ofs/trunk/packages/klibc-2.0.2/usr/klibc/../include -Iusr/klibc/../include...

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux