arch/mips/sni/time.c includes asm-generic/rtc.h for no apparent reason,
and it works fine without that header, so lets remove the inclusion
in preparation of deleting the file.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/mips/sni/time.c | 1 -
1 file changed, 1 deletion(-)
diff
: linuxppc-...@lists.ozlabs.org
Cc: linux...@vger.kernel.org
Cc: linux-m...@lists.linux-m68k.org
Cc: rtc-li...@googlegroups.com
Cc: linux-a...@vger.kernel.org
Arnd Bergmann (16):
rtc: cmos: remove empty asm/mc146818rtc.h files
rtc: cmos: move mc146818rtc code out of asm-generic/rtc.h
char/g
asm/rtc.h are now changed so
they include the headers that were used implicitly through
asm/rtc.h.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/m68k/amiga/config.c| 1 -
arch/m68k/apollo/config.c | 1 -
arch/m68k/bvme6000/config.c | 1 -
arch/m68k/hp300/config.c| 2 +-
, skipping one of the abstraction
levels.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/sh/include/asm/rtc.h | 11 ---
arch/sh/kernel/time.c | 33 -
drivers/rtc/rtc-generic.c | 2 +-
3 files changed, 21 insertions(+), 25 deletions(-)
diff
All architectures using this driver are now converted to
provide their own operations, so this one can be turned
into a trivial stub driver relying on its platform data.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/rtc/rtc-generic.c | 35 +--
I've had these patches in my tree for a while, after the first one
had a few issues that are fixed in this new version. The old-style
PC RTC driver is now also disabled on m68k (as pointed out by
Geert), ppc (it was also blacklisted), and m32r (I showed that
it did not build).
For the genrtc
The asm-generic/rtc.h header can now be included by
architectures that provide their own set_rtc_time/get_rtc_time
macros, letting us remove most of the common contents in
the powerpc implementation.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/parisc/include/asm/rtc.
MOS driver.
This removes x86 from the list for genrtc, and changes all references
to the asm/rtc.h header to instead point to the interfaces
from linux/mc146818rtc.h.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/x86/include/asm/rtc.h | 1 -
arch/x86/kernel/hpet.c | 3 +--
by one.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/powerpc/kernel/time.c | 29 -
drivers/rtc/rtc-generic.c | 2 +-
2 files changed, 29 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
index 3ed9a5
This architecture selects RTC_CLASS unconditionally, so the GEN_RTC
has not worked here for a long time.
Now we can remove both the asm/rtc.h header and the Kconfig dependency
for CONFIG_GEN_RTC.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/parisc/include/asm/rtc.h
, using the normal helper functions,
which makes this y2038 safe (on 32-bit) and simplifies
the implementation.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/parisc/kernel/time.c | 36 +++-
drivers/rtc/rtc-generic.c | 3 +--
2 files changed, 36 insertions
asm/rtc.h are now changed so
they include the headers that were used implicitly through
asm/rtc.h.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/m68k/amiga/config.c| 1 -
arch/m68k/apollo/config.c | 1 -
arch/m68k/bvme6000/config.c | 1 -
arch/m68k/hp300/config.c| 2 +-
No architecture uses the genrtc driver any more, so let's kill it off
for good. This now also includes asm-generic/rtc.h, which is otherwise
completely unused.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/char/Kconfig | 26 ---
drivers/char/Makefile | 1 -
driver
, skipping one of the abstraction
levels.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/sh/include/asm/rtc.h | 11 ---
arch/sh/kernel/time.c | 32 +++-
drivers/rtc/rtc-generic.c | 2 +-
3 files changed, 20 insertions(+), 25 deletions(-)
diff
.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/m68k/kernel/time.c | 24 ++--
drivers/rtc/rtc-generic.c | 2 +-
2 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/arch/m68k/kernel/time.c b/arch/m68k/kernel/time.c
index 3857737e3958..80e024a10115
point it was used to abstract a quirk for the "Marvel" platform,
but it does not do this any more after the code was moved into yet
another driver in arch/alpha/kernel/rtc.c.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/alpha/include/asm/rtc.h| 1 -
arch/alpha/kernel/c
instead, for the only reason of not breaking
existing defconfig and .config files that users may have.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/powerpc/include/asm/rtc.h| 78 ---
arch/powerpc/platforms/Kconfig| 11 ++
arch/p
All architectures using this driver are now converted to
provide their own operations, so this one can be turned
into a trivial stub driver relying on its platform data.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/rtc/rtc-generic.c | 35 +--
-by: Arnd Bergmann <a...@arndb.de>
---
arch/mn10300/include/asm/rtc.h | 2 --
arch/mn10300/kernel/rtc.c | 2 +-
drivers/char/Kconfig | 2 +-
3 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/mn10300/include/asm/rtc.h b/arch/mn10300/include/asm/rtc.h
On Thursday 28 April 2016 00:34:23 Arnd Bergmann wrote:
> return -ENODEV;
>
> - pdev = platform_device_register_simple("rtc-generic", -1, NULL, 0);
> + /* or just call devm_rtc_device_register instead? */
Oops, I was planning to remove the com
y small changes in there that
I still need to pick up, so hopefully that will be the last version.
It would be nice if you could take it through your tree then.
Arnd
> On 28/04/2016 at 00:34:14 +0200, Arnd Bergmann wrote :
> > I ended up stuffing the two patch series into one, as they ar
OCGPTPEER ioctl")
> Signed-off-by: Gleb Fotengauer-Malinovskiy <gle...@altlinux.org>
Acked-by: Arnd Bergmann <a...@arndb.de>
--
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jun 26, 2017 at 6:26 PM, Logan Gunthorpe wrote:
> Hi Jyri,
>
> Thanks for the ack. However, I'm reworking this patch set to use the
> include/linux/io-64-nonatomic* headers which will explicitly devolve
> into two 32-bit transfers. It's not clear whether this is
> +u64 ioread64(void __iomem *addr)
> +{
> + u64 low, high;
> +
> + low = ioread32(addr);
> + high = ioread32(addr + sizeof(u32));
> + return low | (high << 32);
> +}
> +u64 ioread64be(void __iomem *addr)
> +{
> + u64 low, high;
> +
> + low = ioread32be(addr +
On Fri, Jun 2, 2017 at 10:48 AM, Aleksa Sarai wrote:
> When opening the slave end of a PTY, it is not possible for userspace to
> safely ensure that /dev/pts/$num is actually a slave (in cases where the
> mount namespace in which devpts was mounted is controlled by an
> untrusted
On Sat, Jun 3, 2017 at 3:51 PM, Aleksa Sarai wrote:
> In order to avoid future diversions between fs/compat_ioctl.c and
> drivers/tty/pty.c, define .compat_ioctl callbacks for the relevant
> tty_operations structs. Since both pty_unix98_ioctl() and
> pty_bsd_ioctl() are compatible
On Tue, Jun 6, 2017 at 1:05 PM, Aleksa Sarai wrote:
>>> diff --git a/drivers/tty/pty.c b/drivers/tty/pty.c
>>> index 65799575c666..2a6bd9ae3f8b 100644
>>> --- a/drivers/tty/pty.c
>>> +++ b/drivers/tty/pty.c
>>> @@ -481,6 +481,16 @@ static int pty_bsd_ioctl(struct tty_struct *tty,
l() are compatible between 32-bit and 64-bit userspace no
> special translation is required.
>
> Signed-off-by: Aleksa Sarai <asa...@suse.de>
Looks good,
Reviewed-by: Arnd Bergmann <a...@arndb.de>
--
To unsubscribe from this list: send the line "unsubscribe lin
On Mon, Nov 27, 2017 at 9:41 PM, Arnd Bergmann <a...@arndb.de> wrote:
>
> One argument for using c) plus the emulation in glibc is that glibc
> has to do emulation anyway, to allow running user space with 64-bit
> time_t on older kernels that don't have the new getrusage system
&
, but it has the risk of introducing compile-time
incompatibilities with user space sources that rely on the type
of ru_utime and ru_stime.
I'm picking approch c) for its simplicity, but I'd like to hear from
others whether they would prefer a different approach.
Signed-off-by: Arnd Bergmann
On Mon, Nov 27, 2017 at 7:49 PM, Eric W. Biederman
<ebied...@xmission.com> wrote:
> Paul Eggert <egg...@cs.ucla.edu> writes:
>
>> On 11/27/2017 09:00 AM, Arnd Bergmann wrote:
>>> b) Extend the approach taken by the x32 ABI, and use the 64-bit
>>>
() helper for those.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
v2: fix ktime_get_real_ts64()/ktime_get_ts64() typo
---
arch/alpha/kernel/osf_sys.c | 68 ++---
1 file changed, 34 insertions(+), 34 deletions(-)
diff --git a/arch/alpha/kernel/osf_s
: 1cc6c4635e9f ("osf_sys.c: switch handling of timeval32/itimerval32 to
copy_{to,from}_user()")
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
v2: fix incorrect changelog description
---
arch/alpha/kernel/osf_sys.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
On Tue, Nov 7, 2017 at 4:52 PM, Al Viro <v...@zeniv.linux.org.uk> wrote:
> On Tue, Nov 07, 2017 at 03:09:24PM +0100, Arnd Bergmann wrote:
>> There was a typo in the new version of put_tv32() that caused
>> uninitialized stack data to be written back to user space, rather
>&
On Sat, Aug 18, 2018 at 12:05 AM Maciej W. Rozycki wrote:
>
> On Fri, 17 Aug 2018, Arnd Bergmann wrote:
>
> > - For outb()/outw()/outl(), we ought to provide stronger barriers than for
> > writeb()/writew()/writel(), as PCI drivers should expect the store to have
> &
On Mon, Aug 20, 2018 at 11:42 PM Mikulas Patocka wrote:
> On Mon, 20 Aug 2018, Arnd Bergmann wrote:
>
> > On Mon, Aug 20, 2018 at 4:17 PM Mikulas Patocka wrote:
> > > On Sun, 19 Aug 2018, ok...@codeaurora.org wrote:
> > >
> > > > +my new email
> >
On Tue, Aug 21, 2018 at 3:40 PM Mikulas Patocka wrote:
> On Tue, 21 Aug 2018, Arnd Bergmann wrote:
> > On Mon, Aug 20, 2018 at 11:42 PM Mikulas Patocka
> > wrote:
> > > On Mon, 20 Aug 2018, Arnd Bergmann wrote:
> > > > On Mon, Aug 20, 2018 at 4:1
On Mon, Aug 20, 2018 at 4:17 PM Mikulas Patocka wrote:
> On Sun, 19 Aug 2018, ok...@codeaurora.org wrote:
>
> > +my new email
> >
> > On 2018-08-18 19:03, Arnd Bergmann wrote:
> > > On Sat, Aug 18, 2018 at 12:05 AM Maciej W. Rozycki
> > I think we need
On Sun, Aug 19, 2018 at 5:12 PM wrote:
> On 2018-08-18 19:03, Arnd Bergmann wrote:
> > On Sat, Aug 18, 2018 at 12:05 AM Maciej W. Rozycki
> >
> >> A while ago I proposed a set of different MMIO barriers, that some
> >> systems may require, corresponding
On Sun, Aug 19, 2018 at 5:28 PM Sinan Kaya wrote:
>
> On 8/19/2018 11:21 AM, Arnd Bergmann wrote:
> >> This matches my understanding of mmiowb. In fact, mmiowb is a powerpc
> >> thing. All other architectures stub out.
> > There are a few architectures that de
On Fri, Aug 17, 2018 at 9:10 PM Mikulas Patocka wrote:
>
> Hi
>
> The commit 9ce8654323d69273b4977f76f11c9e2d345ab130 breaks the Alpha
> Avanti platform. There is temporary 40-second hang during boot when
> detecting serial ports (although the hang eventually resolves and the
> machine boots) and
On Wed, Aug 22, 2018 at 5:50 PM Mikulas Patocka wrote:
> On Wed, 22 Aug 2018, Maciej W. Rozycki wrote:
> > On Wed, 22 Aug 2018, Sinan Kaya wrote:
>
> According to the Alpha handbook, non-overlapping accesses may be
> reordered.
>
> So if someone does
> writel(REG1);
> readl(REG2);
>
> readl may
On Wed, Apr 11, 2018 at 11:54 AM, James Hogan <jho...@kernel.org> wrote:
> On Wed, Apr 11, 2018 at 09:30:56AM +0200, Arnd Bergmann wrote:
>> On Wed, Apr 11, 2018 at 12:48 AM, James Hogan <jho...@kernel.org> wrote:
>> > Before I forward port those patches to ad
focus instead on the question whether we want it at all or not.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/alpha/kernel/osf_sys.c | 2 +-
include/linux/compat.h| 26 -
include/linux/resource.h | 4 +-
include/linux/sched/task.h| 4 +-
include
to the getrusage() system call interface
but that will be different from one defined in sys/resource.h for the
getrusage library interface.
Link: https://patchwork.kernel.org/patch/10077527/
Cc: Paul Eggert <egg...@cs.ucla.edu>
Cc: Eric W. Biederman <ebied...@xmission.com>
Signed-off-by: A
On Tue, Jan 15, 2019 at 12:52 PM Russell King - ARM Linux admin
wrote:
>
> On Thu, Jan 10, 2019 at 05:24:35PM +0100, Arnd Bergmann wrote:
> > Most architectures define system call numbers for the rseq and pkey system
> > calls, even when they don't support the features,
The io_pgetevents system call was added in linux-4.18 but has
no entry for alpha:
warning: #warning syscall io_pgetevents not implemented [-Wcpp]
Assign a the next system call number here.
Cc: sta...@vger.kernel.org
Signed-off-by: Arnd Bergmann
---
arch/alpha/kernel/syscalls/syscall.tbl | 1
the number of differences
between architectures. If we want to implement kexec_file_load on ARM
in the future, the number assignment means that kexec tools can already
be built with the now current set of kernel headers.
Signed-off-by: Arnd Bergmann
---
arch/arm/tools/syscall.tbl| 1 +
arch
-bit counterpart yet,
but these can all be safely implemented in the C library by wrapping
around the existing system calls because the 32-bit time_t they
pass only counts elapsed time, not time since the epoch. They
will be dealt with later.
Signed-off-by: Arnd Bergmann
---
The one point
be removed as
a side-effect.
Signed-off-by: Arnd Bergmann
---
arch/ia64/include/asm/unistd.h| 14 --
arch/ia64/include/uapi/asm/unistd.h | 2 ++
arch/ia64/kernel/syscalls/syscall.tbl | 2 +-
3 files changed, 3 insertions(+), 15 deletions(-)
diff --git a/arch/ia64/include
statx is available on almost all other architectures but
got missed on sh, so add it now.
Signed-off-by: Arnd Bergmann
---
arch/sh/kernel/syscalls/syscall.tbl | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/sh/kernel/syscalls/syscall.tbl
b/arch/sh/kernel/syscalls/syscall.tbl
index
On Fri, Jan 18, 2019 at 5:57 PM Dennis Clarke wrote:
>
> On 1/18/19 11:18 AM, Arnd Bergmann wrote:
> > This is a minor update of the patches I posted last week, I
> > would like to add this into linux-next now, but would still do
> > changes if there are concerns about
__kernel_timespec and timespec are currently the same type, but once
they are different, the type cast has to be changed here.
Signed-off-by: Arnd Bergmann
---
arch/sparc/kernel/sys_sparc_64.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/sparc/kernel/sys_sparc_64.c b
rintuitive.
This is only a cleanup patch and it should not change any behavior.
Signed-off-by: Arnd Bergmann
---
arch/arm/include/asm/unistd.h | 4 ++--
arch/arm/tools/syscall.tbl | 10 +-
arch/m68k/include/asm/unistd.h | 4 ++--
arch/m68k/kerne
-off-by: Arnd Bergmann
---
include/linux/syscalls.h | 6 +++---
kernel/time/posix-timers.c | 2 +-
kernel/time/time.c | 4 +++-
3 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
index baa4b70b02d3..09330d5bda0c 100644
sparc32.
Signed-off-by: Arnd Bergmann
---
arch/sparc/kernel/sys_sparc_64.c | 59 +-
arch/sparc/kernel/syscalls/syscall.tbl | 6 ++-
include/linux/timex.h | 2 +
kernel/time/posix-timers.c | 24 +--
4 files changed, 76 insertions
-ENOSYS.
Signed-off-by: Arnd Bergmann
---
arch/ia64/kernel/syscalls/syscall.tbl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/ia64/kernel/syscalls/syscall.tbl
b/arch/ia64/kernel/syscalls/syscall.tbl
index 52585281205b..2e93dbdcdb80 100644
--- a/arch/ia64/kernel/syscalls/syscall.tbl
+++ b
All architectures should implement these two, so assign numbers
and hook them up on ia64.
Signed-off-by: Arnd Bergmann
---
arch/ia64/kernel/syscalls/syscall.tbl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/ia64/kernel/syscalls/syscall.tbl
b/arch/ia64/kernel/syscalls/syscall.tbl
on 64-bit kernels as well
as providing a more consistent set of syscalls across architectures.
Signed-off-by: Arnd Bergmann
---
arch/arm/include/asm/unistd.h | 1 -
arch/arm/tools/syscall.tbl| 1 +
arch/arm64/include/asm/unistd.h | 2 +-
arch/arm64/include/asm/unistd32.h | 2 +
From: Deepa Dinamani
struct timex uses struct timeval internally.
struct timeval is not y2038 safe.
Introduce a new UAPI type struct __kernel_timex
that is y2038 safe.
struct __kernel_timex uses a timeval type that is
similar to struct __kernel_timespec which preserves the
same structure size
,
corresponding to the timespec/timeval structures, and make it controlled
by CONFIG_COMPAT_32BIT_TIME, which 32-bit architectures will then select.
Signed-off-by: Arnd Bergmann
---
include/linux/compat.h | 35 ++-
include/linux/time32.h | 32 -
kernel/compat.c
These are all for ignoring the lack of obsolete system calls,
which have been marked the same way in scripts/checksyscall.sh,
so these can be removed.
Signed-off-by: Arnd Bergmann
---
arch/mips/include/asm/unistd.h | 16
arch/parisc/include/asm/unistd.h | 3 ---
arch/s390
. They only add a few bytes of bloat, so it seems
better to keep them compared to adding yet another Kconfig symbol.
I considered adding new syscall numbers for the IPC_64 variants for
consistency, but decided against that for now.
Signed-off-by: Arnd Bergmann
---
arch/alpha/kernel/syscalls
and __kernel_timex can get removed with this.
It would be easy to split this commit by architecture, but with the new
generated system call tables, it's easy enough to do it all at once,
which makes it a little easier to check that the changes are the same
in each table.
Signed-off-by: Arnd Bergmann
---
arch
From: Deepa Dinamani
struct timex is not y2038 safe.
Replace all uses of timex with y2038 safe __kernel_timex.
Note that struct __kernel_timex is an ABI interface definition.
We could define a new structure based on __kernel_timex that
is only available internally instead. Right now, there
] https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git
y2038-5.0-rc1
Arnd Bergmann (26):
ia64: add __NR_umount2 definition
ia64: add statx and io_pgetevents syscalls
ia64: assign syscall numbers for perf and seccomp
alpha: wire up io_pgetevents system call
alpha: update syscall
A small typo has crept into the y2038 conversion of the timer_settime
system call. So far this was completely harmless, but once we start
using the new version, this has to be fixed.
Fixes: 6ff847350702 ("time: Change types to new y2038 safe __kernel_itimerspec")
Signed-off-by: Arn
calls that have different names and calling conventions on alpha,
which would further help unify the syscall ABI, but for now
I decided against that.
Signed-off-by: Arnd Bergmann
---
arch/alpha/include/asm/unistd.h| 6 --
arch/alpha/include/uapi/asm/unistd.h | 5 +
arch/alpha
x32 has always followed the time64 calling conventions of these
syscalls, which required a special hack in compat_get_timespec
aka get_old_timespec32 to continue working.
Since we now have the time64 syscalls, use those explicitly.
Signed-off-by: Arnd Bergmann
---
arch/x86/entry/syscalls
Most architectures have assigned a numbers for the seccomp syscall
even when they do not implement it.
m68k is an exception here, so for consistency lets add the number.
Unless CONFIG_SECCOMP is implemented, the system call just
returns -ENOSYS.
Signed-off-by: Arnd Bergmann
---
arch/m68k
call numbers won't get out of sync then.
Signed-off-by: Arnd Bergmann
---
arch/alpha/include/asm/unistd.h | 4
arch/alpha/kernel/syscalls/syscall.tbl | 4
arch/ia64/kernel/syscalls/syscall.tbl | 4
arch/m68k/kernel/syscalls/syscall.tbl | 4
arch/parisc/include/asm
not adding the new semtimedop() or semop() on 32-bit architectures,
those will get implemented using the new semtimedop_time64() version
that gets added along with the other time64 calls.
Three 64-bit architectures (powerpc, s390 and sparc) get semtimedop().
Signed-off-by: Arnd Bergmann
---
One
to user space.
Signed-off-by: Arnd Bergmann
---
arch/alpha/kernel/syscalls/syscall.tbl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/alpha/kernel/syscalls/syscall.tbl
b/arch/alpha/kernel/syscalls/syscall.tbl
index 25b4a7e76943..0ebd59fdcb8b 100644
--- a/arch/alpha/kernel/syscalls
When I merged this patch, the file was accidentally left intact
instead of being removed, which means any changes to syscall.tbl
have no effect.
Fixes: 2b3c5a99d5f3 ("sh: generate uapi header and syscall table header files")
Signed-off-by: Arnd Bergmann
---
arch/sh/include/uapi/asm/u
5 files changed, 1 insertion(+), 4 deletions(-)
For asm-generic:
Acked-by: Arnd Bergmann
On Fri, Jan 18, 2019 at 8:53 PM Andy Lutomirski wrote:
> I think we have two issues if we reuse those numbers for new syscalls.
> First, I'd really like to see new syscalls be numbered consistently
> everywhere, or at least on all x86 variants, and we can't on x32
> because they mean something
On Fri, Jan 18, 2019 at 7:50 PM Andy Lutomirski wrote:
> On Fri, Jan 18, 2019 at 8:25 AM Arnd Bergmann wrote:
> > - Once we get to 512, we clash with the x32 numbers (unless
> > we remove x32 support first), and probably have to skip
> > a few more. I also considered usi
On Fri, Jan 18, 2019 at 6:20 PM Gabriel Paubert wrote:
>
> On Fri, Jan 18, 2019 at 05:18:19PM +0100, Arnd Bergmann wrote:
> > The IPC system call handling is highly inconsistent across architectures,
> > some use sys_ipc, some use separate calls, and some use both. We
On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman wrote:
> Arnd Bergmann writes:
> > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
> > arch/mips/kernel/syscalls/syscall_o32.tbl | 11 +++
> > arch/powerpc/kernel/syscalls/syscall.tbl | 12
&g
On Tue, Jan 15, 2019 at 5:36 PM Geert Uytterhoeven wrote:
> On Tue, Jan 15, 2019 at 4:19 PM Arnd Bergmann wrote:
> > On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
> > > On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman
> > > wrote:
> > > > Arnd
On Fri, Jan 18, 2019 at 5:25 PM Arnd Bergmann wrote:
>
> This adds 21 new system calls on each ABI that has 32-bit time_t
> today. All of these have the exact same semantics as their existing
> counterparts, and the new ones all have macro names that end in 'time64'
> fo
On Mon, Jan 21, 2019 at 9:19 AM Geert Uytterhoeven wrote:
> On Sat, Jan 19, 2019 at 3:29 PM Russell King - ARM Linux admin
> wrote:
> > On Fri, Jan 18, 2019 at 11:53:25AM -0800, Andy Lutomirski wrote:
> > > On Fri, Jan 18, 2019 at 11:33 AM Arnd Bergmann wrote:
> > &g
On Mon, Jan 21, 2019 at 6:08 PM Arnd Bergmann wrote:
> On Mon, Jan 21, 2019 at 9:19 AM Geert Uytterhoeven
> wrote:
> > Regardless, I'm wondering what to do with the holes marked "room for
> > arch specific calls".
> > When is a syscall really
On Mon, Jan 21, 2019 at 9:56 AM Geert Uytterhoeven wrote:
>
> Note that all architectures that already define pkey syscalls, list
> pkey_mprotect first.
It's easy enough to change, so I've reordered them for consistency now.
> Regardless, for m68k:
> Acked-by: Geert Uytterhoeven
Thanks,
On Fri, Jan 18, 2019 at 7:50 PM Andy Lutomirski wrote:
> On Fri, Jan 18, 2019 at 8:25 AM Arnd Bergmann wrote:
>
> I have a patch that I'll send soon to make x32 use its own table. As
> far as I'm concerned, 547 is *it*. 548 is just a normal number and is
> not special. B
On Tue, Jan 15, 2019 at 4:01 PM Arnd Bergmann wrote:
>
> On Mon, Jan 14, 2019 at 4:59 AM Michael Ellerman wrote:
> > Arnd Bergmann writes:
> > > arch/m68k/kernel/syscalls/syscall.tbl | 11 +++
> > > arch/mips/kernel/syscalls/syscall_o32.tbl | 11 +
On Wed, Dec 12, 2018 at 4:25 PM Willem de Bruijn
wrote:
> On Tue, Dec 11, 2018 at 3:30 PM Deepa Dinamani wrote:
> > @@ -851,39 +890,7 @@ int sock_setsockopt(struct socket *sock, int level,
> > int optname,
> > break;
> >
> > case SO_TIMESTAMPING_OLD:
> > -
On Sat, Dec 15, 2018 at 7:52 PM Willem de Bruijn
wrote:
>
> > 3 reasons for not doing this:
> >
> > 1. We do not want to break userspace. If we move this to
> > linux/socket.h all the userspace programs now have to include
> > linux/socket.h or get this definition through a new libc.
> > 2. All
On Thu, Jun 21, 2018 at 5:49 PM, Ingo Molnar wrote:
> * Arnd Bergmann wrote:
>
>> +int put_compat_rusage_time64(const struct __kernel_rusage *r,
>> + struct compat_rusage_time64 __user *ru)
>> +{
>> + struct compat_rusage_time64 r32;
&
On Thu, Jun 21, 2018 at 6:11 PM, Ingo Molnar wrote:
>
> * Arnd Bergmann wrote:
>
>> Sure, no problem. Do you have an opinion on the question I raised in the
>> first patch [1], i.e. whether we actually want this to be done this way in
>> the
>> kernel, or one of
On Fri, Jun 22, 2018 at 7:45 PM, Eric W. Biederman
wrote:
> Ingo Molnar writes:
>
> So I suspect the simplest thing to do would be to set a flag in the
> idtype member of waitid that says give me rusage64 and then we would
> be done.
It would have to be a flag in both the 'idtype' field of
not provided
by ia64 but are provided by the generic header for historic reasons.
Signed-off-by: Arnd Bergmann
---
arch/ia64/include/asm/io.h | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/arch/ia64/include/asm/io.h b/arch/ia64/include/asm/io.h
index fb0651961e2c
the existing helpers and add macros to define them
to the same implementation.
Signed-off-by: Arnd Bergmann
---
arch/sparc/include/asm/io_64.h | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/arch/sparc/include/asm/io_64.h b/arch/sparc/include/asm/io_64.h
On Mon, Jul 16, 2018 at 12:23 PM, Firoz Khan wrote:
> The goal of this patch series is to easily add/modify/delete a
> system call by changing entry in syscall.tbl file. No need
> to manually edit many files.
>
> The another goal of this patch series is to to unify the system
> call
port and use asm/compiler.h instead of
> asm/compiler-gcc.h]
> Signed-off-by: James Hogan
> Reviewed-by: Paul Burton
> Cc: Arnd Bergmann
> Cc: Ralf Baechle
> Cc: linux-a...@vger.kernel.org
> Cc: linux-m...@linux-mips.org
> Cc: linux...@lists.infradead.org
Reviewed-by: Ar
On Thu, Aug 9, 2018 at 7:45 PM Paul Burton wrote:
> +/*
> + * With GCC v4.5 onwards can use __builtin_unreachable to indicate to the
> + * compiler that a particular code path will never be hit. This allows it to
> be
> + * optimised out of the generated binary.
> + *
> + * Unfortunately GCC
On Sat, Aug 11, 2018 at 10:59 PM Michael Cree wrote:
>
> On Sat, Aug 11, 2018 at 08:28:04PM +0100, Al Viro wrote:
> > On Mon, Jul 16, 2018 at 03:53:53PM +0530, Firoz Khan wrote:
> > > It is correct to keep __IGNORE* entry in non uapi header
> > > asm/unistd.h while uapi/asm/unistd.h must hold
interprets the new command codes as always
referring to the 64-bit structure on all architectures, while the old
architecture specific command code still refers to the old architecture
specific layout. The new command number is only used when they are
actually different.
Signed-off-by: Arnd Bergmann
On Sun, Nov 25, 2018 at 3:33 PM Willem de Bruijn
wrote:
> On Sun, Nov 25, 2018 at 12:28 AM Deepa Dinamani
> wrote:
> > So failing here means adding a bunch of ifdef's to verify it is not
> > executing on 64 bit arch or something like x32.
>
> The code as is adds branches on platforms that do
space can now use old_timeval32 on both 32-bit
and 64-bit machines, while 64-bit code can use
__old_kernel_timeval.
Signed-off-by: Arnd Bergmann
---
net/compat.c| 66 +
net/core/sock.c | 65 +++-
2 files
1 - 100 of 170 matches
Mail list logo