litmus-rt-budgetable-locks.git/.git/arch/x86_64/ia32/ia32entry.S, branch update_litmus_2019

x86_64: move ia32

2007-10-11T09:17:21+00:00

Signed-off-by: Thomas Gleixner 
Signed-off-by: Ingo Molnar

x86_64: Zero extend all registers after ptrace in 32bit entry path.

2007-09-21T16:52:07+00:00

Strictly it's only needed for eax.

It actually does a little more than strictly needed -- the other registers
are already zero extended.

Also remove the now unnecessary and non functional compat task check
in ptrace.

This is CVE-2007-4573

Found by Wojciech Purczynski

Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

x86_64: ia32entry adjustments

2007-07-22T01:37:09+00:00

Consolidate the three 32-bit system call entry points so that they all
treat registers in similar ways.

Signed-off-by: Jan Beulich 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

sys_fallocate() implementation on i386, x86_64 and powerpc

2007-07-18T01:42:44+00:00

fallocate() is a new system call being proposed here which will allow
applications to preallocate space to any file(s) in a file system.
Each file system implementation that wants to use this feature will need
to support an inode operation called ->fallocate().
Applications can use this feature to avoid fragmentation to certain
level and thus get faster access speed. With preallocation, applications
also get a guarantee of space for particular file(s) - even if later the
the system becomes full.

Currently, glibc provides an interface called posix_fallocate() which
can be used for similar cause. Though this has the advantage of working
on all file systems, but it is quite slow (since it writes zeroes to
each block that has to be preallocated). Without a doubt, file systems
can do this more efficiently within the kernel, by implementing
the proposed fallocate() system call. It is expected that
posix_fallocate() will be modified to call this new system call first
and incase the kernel/filesystem does not implement it, it should fall
back to the current implementation of writing zeroes to the new blocks.
ToDos:
1. Implementation on other architectures (other than i386, x86_64,
   and ppc). Patches for s390(x) and ia64 are already available from
   previous posts, but it was decided that they should be added later
   once fallocate is in the mainline. Hence not including those patches
   in this take.
2. Changes to glibc,
   a) to support fallocate() system call
   b) to make posix_fallocate() and posix_fallocate64() call fallocate()

Signed-off-by: Amit Arora

diskquota: 32bit quota tools on 64bit architectures

2007-07-16T16:05:48+00:00

OpenVZ Linux kernel team has discovered the problem with 32bit quota tools
working on 64bit architectures.  In 2.6.10 kernel sys32_quotactl() function
was replaced by sys_quotactl() with the comment "sys_quotactl seems to be
32/64bit clean, enable it for 32bit" However this isn't right.  Look at
if_dqblk structure:

struct if_dqblk {
        __u64 dqb_bhardlimit;
        __u64 dqb_bsoftlimit;
        __u64 dqb_curspace;
        __u64 dqb_ihardlimit;
        __u64 dqb_isoftlimit;
        __u64 dqb_curinodes;
        __u64 dqb_btime;
        __u64 dqb_itime;
        __u32 dqb_valid;
};

For 32 bit quota tools sizeof(if_dqblk) == 0x44.
But for 64 bit kernel its size is 0x48, 'cause of alignment!
Thus we got a problem. Attached patch reintroduce sys32_quotactl() function,
that handles this and related situations.

[michal.k.k.piotrowski@gmail.com: build fix]
[akpm@linux-foundation.org: Make it link with CONFIG_QUOTA=n]
Signed-off-by: Vasily Tarasov 
Cc: Andi Kleen 
Cc: "Luck, Tony" 
Cc: Jan Kara 
Cc: 
Signed-off-by: Michal Piotrowski 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

x86_64: Fix readahead/sync_file_range/fadvise64 compat calls

2007-06-20T21:27:25+00:00

Correctly convert the u64 arguments from 32bit to 64bit.

Pointed out by Heiko Carstens.

I guess this proves Linus' theory that nobody uses the more exotic Linux
specific syscalls.  It wasn't discovered by a user.

Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

x86_64: use signalfd and timerfd compat syscalls

2007-05-12T16:47:15+00:00

Looks like these two are wired up in a wrong way.

Cc: Davide Libenzi 
Cc: Andi Kleen 
Signed-off-by: Heiko Carstens 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

signal/timer/event: eventfd wire up x86 arches

2007-05-11T15:29:37+00:00

This patch wires the eventfd system call to the x86 architectures.

Signed-off-by: Davide Libenzi 
Cc: Michael Kerrisk 
Cc: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

signal/timer/event: timerfd wire up x86 arches

2007-05-11T15:29:36+00:00

This patch wires the timerfd system call to the x86 architectures.

Signed-off-by: Davide Libenzi 
Cc: Andi Kleen 
Cc: Michael Kerrisk 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

signal/timer/event: signalfd wire up x86 arches

2007-05-11T15:29:36+00:00

This patch wires the signalfd system call to the x86 architectures.

Signed-off-by: Davide Libenzi 
Cc: Michael Kerrisk 
Cc: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds