Re: [PATCH v2] MIPS: Reduce _NSIG from 128 to 127 to avoid BUG_ON

2013-09-03 Thread Rich Felker
On Fri, Jun 28, 2013 at 11:03:33PM +0100, James Hogan wrote: > On 28 June 2013 20:28, Denys Vlasenko wrote: > > On Monday 17 June 2013 12:36, James Hogan wrote: > >> On 14/06/13 17:03, James Hogan wrote: > >> > MIPS has 128 signals, the highest of which has the number 128 (they > >> > start from 1

Re: [microblaze-linux] [RESEND PATCH v2] microblaze: Fix clone syscall

2013-07-28 Thread Rich Felker
On Mon, Jul 29, 2013 at 08:22:56AM +0200, Michal Simek wrote: > Microblaze was assign to CLONE_BACKWARDS type where > parent tid was passed via 3rd argument. > Microblaze glibc is using 4th argument for it. > > Create new CLONE_BACKWARDS3 type where stack_size is passed > via 3rd argument, parent

Re: RFC: named anonymous vmas

2013-08-01 Thread Rich Felker
On Thu, Aug 01, 2013 at 01:29:51AM -0700, Christoph Hellwig wrote: > Btw, FreeBSD has an extension to shm_open to create unnamed but fd > passable segments. From their man page: > > As a FreeBSD extension, the constant SHM_ANON may be used for the path > argument to shm_open(). In this c

Request for comments: reserving a value for O_SEARCH and O_EXEC

2013-08-02 Thread Rich Felker
Hi, At present, one of the few interface-level conformance issues for Linux against POSIX 2008 is lack of O_SEARCH and O_EXEC. I am trying to get full, conforming support for them both into musl libc (for which I am the maintainer) and glibc (see the libc-alpha post[1]). At this point, I believe i

Re: [microblaze-linux] [RESEND PATCH] microblaze: Fix clone syscall

2013-07-23 Thread Rich Felker
On Wed, Jul 24, 2013 at 07:34:07AM +0200, Michal Simek wrote: > Microblaze was assign to CLONE_BACKWARDS type where > parent tid was passed via 3rd argument. > Microblaze glibc is using 4th argument for it. > > Create new CLONE_BACKWARDS3 type where stack_size is passed > via 3rd argument, parent

Re: [microblaze-linux] [RESEND PATCH] microblaze: Fix clone syscall

2013-07-24 Thread Rich Felker
On Wed, Jul 24, 2013 at 08:48:27AM +0200, Michal Simek wrote: > >> Create new CLONE_BACKWARDS3 type where stack_size is passed > >> via 3rd argument, parent thread id pointer via 4th, > >> child thread id pointer via 5th and tls value as 6th > >> argument > > > > I believe this also affects us in

Re: [microblaze-linux] [RESEND PATCH] microblaze: Fix clone syscall

2013-07-24 Thread Rich Felker
On Wed, Jul 24, 2013 at 09:16:03AM +0200, Michal Simek wrote: > BTW: Where to get musl package Source is available from http://www.musl-libc.org/. We also have cross compilers and binaries for a number of archs here: https://bitbucket.org/GregorR/musl-cross However, microblaze was not included

Re: Request for comments: reserving a value for O_SEARCH and O_EXEC

2013-08-12 Thread Rich Felker
On Mon, Aug 12, 2013 at 10:42:03AM -0700, Andy Lutomirski wrote: > You'll have the same problem that O_TMPFILE had: the kernel currently > ignores unrecognized flags. I wonder if it's time to add a new syscall > (or syscalls) with more sensible semantics. That's not a problem here. In fact, in th

Re: [PATCH] sh-DWARF: Delete unnecessary checks before the function call "mempool_destroy"

2016-07-22 Thread Rich Felker
On Tue, Jul 19, 2016 at 11:08:24PM +0200, SF Markus Elfring wrote: > > From: Markus Elfring > > Date: Mon, 16 Nov 2015 08:20:36 +0100 > > > > The mempool_destroy() function tests whether its argument is NULL > > and then returns immediately. Thus the test around the calls is not needed. > > > >

Adding linux-sh (arch/sh) to linux-next

2016-07-22 Thread Rich Felker
Hi Stephen, Can you please add the linux-sh tree's for-next branch to be pulled for linux-next? git://git.libc.org/linux-sh for-next Let me know if anything's wrong with how it's set up. I'm new to linux-next (and still fairly new to arch maintainership) so apologies if I missed anything

[PATCH v7 1/2] of: add J-Core timer bindings

2016-09-23 Thread Rich Felker
Signed-off-by: Rich Felker Acked-by: Rob Herring --- .../devicetree/bindings/timer/jcore,pit.txt| 24 ++ 1 file changed, 24 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt diff --git a/Documentation/devicetree/bindings/timer

[PATCH v7 0/2] J-Core timer support

2016-09-23 Thread Rich Felker
This version has been updated to include specific changes requested in the last round of review, and to work around a problem discussed with Paul McKenney (See thread "rcu_sched stalls in idle task introduced in pre-4.8?" for details). Rich Felker (2): of: add J-Core time

[PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

2016-09-23 Thread Rich Felker
to a full-range 32-bit nanoseconds count. Signed-off-by: Rich Felker --- drivers/clocksource/Kconfig | 10 ++ drivers/clocksource/Makefile| 1 + drivers/clocksource/jcore-pit.c | 240 include/linux/cpuhotplug.h | 1 + 4 files changed, 252

Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

2016-09-26 Thread Rich Felker
Ping. Is there anything that still needs to be changed for this driver to be acceptable? On Mon, Sep 17, 2001 at 04:00:00AM +, Rich Felker wrote: > At the hardware level, the J-Core PIT is integrated with the interrupt > controller, but it is represented as its own device and

Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

2016-09-26 Thread Rich Felker
On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > On 26/09/2016 23:07, Rich Felker wrote: > > Ping. Is there anything that still needs to be changed for this driver > > to be acceptable? > > It is on my radar. I'm reviewing it. > > Can you elabo

Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

2016-09-26 Thread Rich Felker
On Mon, Sep 26, 2016 at 07:55:13PM -0400, Thomas Gleixner wrote: > On Mon, 26 Sep 2016, Rich Felker wrote: > > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > > Based on use of ftrace, I was able to see situations where a second > > timer hardirq happened

Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver

2016-09-27 Thread Rich Felker
On Mon, Sep 26, 2016 at 08:42:58PM -0400, Rich Felker wrote: > On Mon, Sep 26, 2016 at 07:55:13PM -0400, Thomas Gleixner wrote: > > On Mon, 26 Sep 2016, Rich Felker wrote: > > > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > > > Based on use o

Re: [PATCH v4 2/2] irqchip: add J-Core AIC driver

2016-07-27 Thread Rich Felker
On Wed, Jul 27, 2016 at 11:15:38AM +0100, Mark Rutland wrote: > On Wed, Jul 27, 2016 at 05:35:09AM +0000, Rich Felker wrote: > > For simplicity, there is no aic1-specific logic in the driver beyond > > setting the priority register, which is necessary for interrupts to > > wo

Re: [PATCH v4 2/2] irqchip: add J-Core AIC driver

2016-07-27 Thread Rich Felker
On Wed, Jul 27, 2016 at 02:22:52PM +0100, Mark Rutland wrote: > On Wed, Jul 27, 2016 at 09:06:06AM -0400, Rich Felker wrote: > > On Wed, Jul 27, 2016 at 11:12:36AM +0100, Mark Rutland wrote: > > > On Wed, Jul 27, 2016 at 05:35:09AM +, Rich Felker wrote: > > > &g

Re: [PATCH v4 2/2] irqchip: add J-Core AIC driver

2016-07-27 Thread Rich Felker
On Wed, Jul 27, 2016 at 02:27:54PM +0100, Mark Rutland wrote: > On Wed, Jul 27, 2016 at 09:08:21AM -0400, Rich Felker wrote: > > On Wed, Jul 27, 2016 at 11:15:38AM +0100, Mark Rutland wrote: > > > On Wed, Jul 27, 2016 at 05:35:09AM +, Rich Felker wrote: > > > > Fo

Re: [PATCH v4 2/2] irqchip: add J-Core AIC driver

2016-07-27 Thread Rich Felker
On Wed, Jul 27, 2016 at 06:31:52PM +0100, Mark Rutland wrote: > > > > It's looping over possible cpus (per the kernel configuration for max > > > > cpus) so it's expected that a system with fewer cpus will also have > > > > fewer reg ranges for the aic. This is not an error. If you think > > > > th

[PATCH v4 2/2] spi: add driver for J-Core SPI controller

2016-07-27 Thread Rich Felker
ll be extended to support future versions of the J-Core SPI controller with DMA transfers when they become available. Signed-off-by: Rich Felker --- drivers/spi/Kconfig | 4 + drivers/spi/Makefile| 1 + drivers/spi/spi-jcore.c | 220 +

[PATCH v4 0/2] J-Core SPI controller support

2016-07-27 Thread Rich Felker
ges I failed to make before), plus significant cleanup (removal of unused macros and other cruft) and refactoring to eliminate duplicate code. Rich Rich Felker (2): of: add J-Core SPI master bindings spi: add driver for J-Core SPI controller .../devicetree/bindings/spi/jcore,sp

[PATCH v4 1/2] of: add J-Core SPI master bindings

2016-07-27 Thread Rich Felker
Signed-off-by: Rich Felker --- .../devicetree/bindings/spi/jcore,spi.txt | 30 ++ 1 file changed, 30 insertions(+) create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt diff --git a/Documentation/devicetree/bindings/spi/jcore,spi.txt b

[PATCH v5 2/2] irqchip: add J-Core AIC driver

2016-07-28 Thread Rich Felker
x27;s currently in use in deployments and all released bitstream binaries. Signed-off-by: Rich Felker --- drivers/irqchip/Kconfig | 6 +++ drivers/irqchip/Makefile| 1 + drivers/irqchip/irq-jcore-aic.c | 86 + 3 files changed, 93 inser

[PATCH v5 0/2] J-Core interrupt controller support

2016-07-28 Thread Rich Felker
Updated based on feedback from Mark Rutland. Rich Felker (2): of: add J-Core interrupt controller bindings irqchip: add J-Core AIC driver .../bindings/interrupt-controller/jcore,aic.txt| 26 +++ drivers/irqchip/Kconfig| 6 ++ drivers/irqchip/Makefile

[PATCH v5 0/2] J-Core timer support

2016-07-28 Thread Rich Felker
The only difference since v4 should be merging of Arnd Bergmann's patch that addresses the API change whereby init functions can return an error. Rich Rich Felker (2): of: add J-Core timer bindings clocksource: add J-Core timer/clocksource driver .../devicetree/bindings/timer/

[PATCH v5 2/2] clocksource: add J-Core timer/clocksource driver

2016-07-28 Thread Rich Felker
provided using the J-Core "RTC" registers, which give a 64-bit seconds count and 32-bit nanoseconds. The driver converts these to a 64-bit nanoseconds count. Signed-off-by: Rich Felker --- drivers/clocksource/Kconfig | 8 ++ drivers/clocksource/Makefile| 1 + drivers/clockso

[PATCH v5 1/2] of: add J-Core interrupt controller bindings

2016-07-28 Thread Rich Felker
Signed-off-by: Rich Felker --- .../bindings/interrupt-controller/jcore,aic.txt| 26 ++ 1 file changed, 26 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt diff --git a/Documentation/devicetree/bindings/interrupt

[PATCH v5 1/2] of: add J-Core timer bindings

2016-07-28 Thread Rich Felker
Signed-off-by: Rich Felker --- .../devicetree/bindings/timer/jcore,pit.txt| 25 ++ 1 file changed, 25 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt diff --git a/Documentation/devicetree/bindings/timer/jcore,pit.txt b

Re: [PATCH] clocksource: j-core: type fix init function return code

2016-07-28 Thread Rich Felker
On Wed, Jul 27, 2016 at 10:00:50AM +0200, Arnd Bergmann wrote: > On Wednesday, July 27, 2016 1:25:33 AM CEST Rich Felker wrote: > > On Tue, Jul 26, 2016 at 02:31:29PM +0200, Arnd Bergmann wrote: > > > The CLOCKSOURCE_OF_DECLARE now takes a function that returns an '

Re: [PATCH v5 2/2] irqchip: add J-Core AIC driver

2016-07-28 Thread Rich Felker
On Thu, Jul 28, 2016 at 03:15:09PM +0200, Thomas Gleixner wrote: > On Thu, 17 Mar 2016, Rich Felker wrote: > > @@ -0,0 +1,86 @@ > > +/* > > + * J-Core SoC AIC driver > > + * > > + * Copyright (C) 2015-2016 Smart Energy Instruments, Inc. > > + * > &

Re: [PATCH v5 2/2] clocksource: add J-Core timer/clocksource driver

2016-07-28 Thread Rich Felker
On Thu, Jul 28, 2016 at 04:44:05PM +0200, Thomas Gleixner wrote: > > + > > +#define PIT_IRQ_SHIFT 12 > > +#define PIT_PRIO_SHIFT 20 > > +#define PIT_ENABLE_SHIFT 26 > > +#define PIT_IRQ_MASK 0x3f > > +#define PIT_PRIO_MASK 0xf > > Can you please align the numbers as nicely as you did below and ple

Re: [PATCH v5 2/2] clocksource: add J-Core timer/clocksource driver

2016-07-28 Thread Rich Felker
On Thu, Jul 28, 2016 at 06:44:15PM +0200, Thomas Gleixner wrote: > On Thu, 28 Jul 2016, Rich Felker wrote: > > On Thu, Jul 28, 2016 at 04:44:05PM +0200, Thomas Gleixner wrote: > > > > + return ((u64)sechi << 32 | seclo) * NSEC_PER_SEC + nsec; > > > > &

Re: [PATCH v4 2/2] spi: add driver for J-Core SPI controller

2016-07-28 Thread Rich Felker
On Thu, Jul 28, 2016 at 08:11:53PM +0100, Mark Brown wrote: > On Sun, Apr 03, 2016 at 05:12:45AM +0000, Rich Felker wrote: > > > +config SPI_JCORE > > + tristate "J-Core SPI Master" > > + depends on OF > > + > > An architecture or SoC depende

Re: [PATCH v5 2/2] clocksource: add J-Core timer/clocksource driver

2016-07-28 Thread Rich Felker
On Thu, Jul 28, 2016 at 04:44:05PM +0200, Thomas Gleixner wrote: > > +static int jcore_pit_cpu_notify(struct notifier_block *self, > > + unsigned long action, void *hcpu) > > +{ > > + struct jcore_pit_nb *nb = container_of(self, struct jcore_pit_nb, nb); > > + switch (action &

Re: [PATCH v5 2/2] clocksource: add J-Core timer/clocksource driver

2016-07-28 Thread Rich Felker
On Thu, Jul 28, 2016 at 04:00:47PM -0400, Rich Felker wrote: > On Thu, Jul 28, 2016 at 04:44:05PM +0200, Thomas Gleixner wrote: > > > +static int jcore_pit_cpu_notify(struct notifier_block *self, > > > + unsigned long action, void *hcpu) > > > +{ &

Re: [PATCH v4 2/2] spi: add driver for J-Core SPI controller

2016-07-29 Thread Rich Felker
On Thu, Jul 28, 2016 at 08:51:25PM +0100, Mark Brown wrote: > On Thu, Jul 28, 2016 at 03:40:45PM -0400, Rich Felker wrote: > > On Thu, Jul 28, 2016 at 08:11:53PM +0100, Mark Brown wrote: > > > > An architecture or SoC dependency with || COMPILE_TEST would be useful > >

Re: [PATCH v5 2/2] clocksource: add J-Core timer/clocksource driver

2016-07-31 Thread Rich Felker
On Thu, Jul 28, 2016 at 04:18:44PM -0400, Rich Felker wrote: > On Thu, Jul 28, 2016 at 04:00:47PM -0400, Rich Felker wrote: > > On Thu, Jul 28, 2016 at 04:44:05PM +0200, Thomas Gleixner wrote: > > > > +static int jcore_pit_cpu_notify(struct

Re: rcu_sched stalls in idle task introduced in pre-4.8?

2016-09-08 Thread Rich Felker
On Wed, Aug 03, 2016 at 09:16:31AM -0700, Paul E. McKenney wrote: > On Tue, Aug 02, 2016 at 01:45:04PM -0700, Paul E. McKenney wrote: > > On Tue, Aug 02, 2016 at 04:32:17PM -0400, Rich Felker wrote: > > > On Tue, Aug 02, 2016 at 12:48:02PM -0700, Paul

Re: [PATCH v6 2/2] irqchip: add J-Core AIC driver

2016-08-04 Thread Rich Felker
On Thu, Aug 04, 2016 at 04:32:57PM +0200, Geert Uytterhoeven wrote: > Hi Rich, > > On Thu, Aug 4, 2016 at 6:30 AM, Rich Felker wrote: > > --- /dev/null > > +++ b/drivers/irqchip/irq-jcore-aic.c > > > +int __init aic_irq_of_init(struct device_node *node, s

Re: [PATCH v4 2/2] spi: add driver for J-Core SPI controller

2016-08-04 Thread Rich Felker
On Thu, Aug 04, 2016 at 03:05:16PM +0200, Geert Uytterhoeven wrote: > Hi Rich, > > On Sat, Jul 30, 2016 at 5:34 AM, Rich Felker wrote: > > On Thu, Jul 28, 2016 at 08:51:25PM +0100, Mark Brown wrote: > >> On Thu, Jul 28, 2016 at 03:40:45PM -0400, Rich Felker wrote: > &

Re: Build error in -next due to 'sh: add working futex atomic ops on userspace addresses for smp'

2016-08-04 Thread Rich Felker
On Wed, Aug 03, 2016 at 09:44:51PM -0700, Guenter Roeck wrote: > Hi, > > I see the following build error in -next when building sh:shx3_defconfig. > > {standard input}: Assembler messages: > {standard input}:177: Error: unknown opcode > {standard input}:7760: Error: unknown opcode > > {standard

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-04 Thread Rich Felker
On Thu, Aug 04, 2016 at 02:24:51PM +0600, Alexnader Kuleshov wrote: > Hello Rich, > > On 08-04-16, Rich Felker wrote: > > At the hardware level, the J-Core PIT is integrated with the interrupt > > controller, but it is represented as its own device and has an > > indepe

Re: [PATCH v3 01/12] of: add vendor prefix for J-Core

2016-08-04 Thread Rich Felker
On Wed, Jul 27, 2016 at 01:31:12AM -0400, Rich Felker wrote: > On Wed, May 25, 2016 at 08:18:06AM -0500, Rob Herring wrote: > > On Wed, May 25, 2016 at 12:43 AM, Rich Felker wrote: > > > The J-Core project (j-core.org) produces open source cpu and SoC > > > peripheral

[GIT PULL] arch/sh updates for 4.8

2016-08-06 Thread Rich Felker
ake time.c explicitly non-modular sh: make mm/asids-debugfs explicitly non-modular sh: make board-secureedge5410 explicitly non-modular sh: make heartbeat driver explicitly non-modular Rich Felker (16): sh: add support for linking a builtin device tree blob in the kernel

Re: Build regressions/improvements in v4.8-rc1

2016-08-08 Thread Rich Felker
On Mon, Aug 08, 2016 at 10:38:07AM +0200, Geert Uytterhoeven wrote: > On Mon, Aug 8, 2016 at 10:32 AM, Geert Uytterhoeven > wrote: > > Below is the list of build error/warning regressions/improvements in > > v4.8-rc1[1] compared to v4.7[2]. > > > > Summarized: > > - build errors: +8/-12 > > >

Re: Build regressions/improvements in v4.8-rc1

2016-08-08 Thread Rich Felker
On Mon, Aug 08, 2016 at 05:46:33PM +0200, Geert Uytterhoeven wrote: > Hi Rich, > > On Mon, Aug 8, 2016 at 4:31 PM, Rich Felker wrote: > > On Mon, Aug 08, 2016 at 10:38:07AM +0200, Geert Uytterhoeven wrote: > >> On Mon, Aug 8, 2016 at 10:32 AM, Geert Uytterhoeven > >

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-24 Thread Rich Felker
On Wed, Aug 24, 2016 at 06:42:05PM +0200, Daniel Lezcano wrote: > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig > > index 5677886..3210ca5 100644 > > --- a/drivers/clocksource/Kconfig > > +++ b/drivers/clocksource/Kconfig > > @@ -407,6 +407,15 @@ config SYS_SUPPORTS_SH_TM

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-24 Thread Rich Felker
On Wed, Aug 24, 2016 at 08:01:52PM +0100, Marc Zyngier wrote: > On Wed, 24 Aug 2016 13:40:01 -0400 > Rich Felker wrote: > > [...] > > > > IIUC, there is a problem with the interrupt controller where > the per irq > > > line are not working correctly. Is tha

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-24 Thread Rich Felker
On Wed, Aug 24, 2016 at 10:01:08PM +0200, Arnd Bergmann wrote: > On Wednesday, August 24, 2016 1:40:01 PM CEST Rich Felker wrote: > > On Wed, Aug 24, 2016 at 06:42:05PM +0200, Daniel Lezcano wrote: > > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-24 Thread Rich Felker
On Wed, Aug 24, 2016 at 10:22:13PM +0100, Mark Rutland wrote: > On Wed, Aug 24, 2016 at 04:52:26PM -0400, Rich Felker wrote: > > On Wed, Aug 24, 2016 at 10:01:08PM +0200, Arnd Bergmann wrote: > > > On Wednesday, August 24, 2016 1:40:01 PM CEST Rich Felker wrote: > > >

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-25 Thread Rich Felker
On Thu, Aug 25, 2016 at 10:07:08AM +0200, Thomas Gleixner wrote: > Rich, > > On Wed, 24 Aug 2016, Rich Felker wrote: > > I don't think that's a correct characterization. Rather the percpu > > infrastructure just means something completely different from what you

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-25 Thread Rich Felker
On Thu, Aug 25, 2016 at 05:41:29PM +0200, Thomas Gleixner wrote: > On Thu, 25 Aug 2016, Rich Felker wrote: > > assumption that is was just a bug. Now that Mark Rutland has explained > > it well (and with your additional explanation below in your email), I > > see what the

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-25 Thread Rich Felker
On Thu, Aug 25, 2016 at 05:38:06PM +0100, Mark Rutland wrote: > On Thu, Aug 25, 2016 at 10:56:50AM -0400, Rich Felker wrote: > > On Thu, Aug 25, 2016 at 10:07:08AM +0200, Thomas Gleixner wrote: > > > On Wed, 24 Aug 2016, Rich Felker wrote: > > As for this topic, what hap

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

2016-08-25 Thread Rich Felker
On Thu, Aug 25, 2016 at 07:21:13PM +0100, Mark Rutland wrote: > On Thu, Aug 25, 2016 at 01:51:35PM -0400, Rich Felker wrote: > > On Thu, Aug 25, 2016 at 05:38:06PM +0100, Mark Rutland wrote: > > > On Thu, Aug 25, 2016 at 10:56:50AM -0400, Rich Felker wrote: > > > >

Re: [PATCH] fs/binfmt_elf_fdpic.c: provide NOMMU loader for regular ELF binaries

2015-10-06 Thread Rich Felker
Ping. On Tue, Sep 29, 2015 at 07:16:49PM -0400, Rich Felker wrote: > From: Rich Felker > > The ELF binary loader in binfmt_elf.c requires an MMU, making it > impossible to use regular ELF binaries on NOMMU archs. However, the > FDPIC ELF loader in binfmt_elf_fdpic.c is fully capa

Re: [PATCH v2] fs/binfmt_elf_fdpic.c: provide NOMMU loader for regular ELF binaries

2015-10-13 Thread Rich Felker
On Tue, Oct 13, 2015 at 10:55:45PM +1000, Greg Ungerer wrote: > Hi Rich, > > On 09/10/15 02:38, Rich Felker wrote: > >From: Rich Felker > > > >The ELF binary loader in binfmt_elf.c requires an MMU, making it > >impossible to use regular ELF binaries on NOMMU

Re: [musl] RFC: adding Linux vsyscall-disable and similar backwards-incompatibility flags to ELF headers?

2015-09-01 Thread Rich Felker
On Tue, Sep 01, 2015 at 05:51:44PM -0700, Andy Lutomirski wrote: > Hi all- > > Linux has a handful of weird features that are only supported for > backwards compatibility. The big one is the x86_64 vsyscall page, but > uselib probably belongs on the list, too, and we might end up with > more at s

Re: [musl] RFC: adding Linux vsyscall-disable and similar backwards-incompatibility flags to ELF headers?

2015-09-01 Thread Rich Felker
On Tue, Sep 01, 2015 at 08:39:27PM -0700, Andy Lutomirski wrote: > On Tue, Sep 1, 2015 at 7:54 PM, Rich Felker wrote: > > On Tue, Sep 01, 2015 at 05:51:44PM -0700, Andy Lutomirski wrote: > >> Hi all- > >> > >> Linux has a handful of weird features that a

Re: [musl] RFC: adding Linux vsyscall-disable and similar backwards-incompatibility flags to ELF headers?

2015-09-01 Thread Rich Felker
On Tue, Sep 01, 2015 at 09:32:22PM -0700, Andy Lutomirski wrote: > On Tue, Sep 1, 2015 at 9:18 PM, Rich Felker wrote: > > On Tue, Sep 01, 2015 at 08:39:27PM -0700, Andy Lutomirski wrote: > >> On Tue, Sep 1, 2015 at 7:54 PM, Rich Felker wrote: > >> > On Tue, Sep 01,

Re: [musl] RFC: adding Linux vsyscall-disable and similar backwards-incompatibility flags to ELF headers?

2015-09-01 Thread Rich Felker
On Tue, Sep 01, 2015 at 10:03:27PM -0700, Andy Lutomirski wrote: > On Tue, Sep 1, 2015 at 9:55 PM, Rich Felker wrote: > > On Tue, Sep 01, 2015 at 09:32:22PM -0700, Andy Lutomirski wrote: > >> On Tue, Sep 1, 2015 at 9:18 PM, Rich Felker wrote: > >> > On Tue, Sep 01,

Re: [PATCH v2] arch/sh: provide unified syscall trap compatible with all SH models

2015-10-01 Thread Rich Felker
Ping. On Tue, Sep 15, 2015 at 12:11:24AM -0400, Rich Felker wrote: > Ping? > > On Tue, Aug 25, 2015 at 05:23:11PM -0400, Rich Felker wrote: > > From: Rich Felker > > > > Historically SH-2 Linux (and originally uClinux) used a syscall > > calling convention inc

futex_cmpxchg_enabled breakage

2018-08-29 Thread Rich Felker
I just spent a number of hours helping someone track down a bug that looks like it's some kind of futex_cmpxchg_enabled detection error on powerpc64 (still not sure of the root cause; set_robust_list producing -ENOSYS), and a while back I hit the same problem on sh2 due to lack of EFAULT on nommu,

Re: futex_cmpxchg_enabled breakage

2018-08-30 Thread Rich Felker
On Thu, Aug 30, 2018 at 11:19:58AM +0200, Thomas Gleixner wrote: > On Wed, 29 Aug 2018, Rich Felker wrote: > > > I just spent a number of hours helping someone track down a bug that > > looks like it's some kind of futex_cmpxchg_enabled detection error on > > powerpc6

Re: cpu_no_speculation omissions?

2018-07-26 Thread Rich Felker
On Thu, Jul 26, 2018 at 04:18:42PM +0200, Joerg Roedel wrote: > On Thu, Jul 26, 2018 at 03:29:53PM +0200, Jiri Kosina wrote: > > On Mon, 16 Jul 2018, Alan Cox wrote: > > > The pre Silvermont atom cores are in order. When I did the original > > > list I didn't bother with all the 32bit cores as we d

Re: [J-core] [PATCH v5 00/22] sh: LANDISK and R2Dplus convert to device tree

2018-01-05 Thread Rich Felker
On Fri, Nov 17, 2017 at 08:54:47PM +0100, John Paul Adrian Glaubitz wrote: > On 11/17/2017 08:17 PM, Rich Felker wrote: > > There were significant problems that I don't think were ever > > addressed, including incompatible changes in how boot command line was > > hand

Re: [J-core] [PATCH v5 00/22] sh: LANDISK and R2Dplus convert to device tree

2018-01-05 Thread Rich Felker
On Fri, Jan 05, 2018 at 10:47:34PM +0100, John Paul Adrian Glaubitz wrote: > On 01/05/2018 10:28 PM, Rich Felker wrote: > > I'm trying to reproduce this but can't find any documentation for > > cross-LILO in [2], much less any code except possibly the binary > > &q

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

2018-03-23 Thread Rich Felker
On Fri, Mar 23, 2018 at 05:48:06AM -0700, Matthew Wilcox wrote: > On Thu, Mar 22, 2018 at 07:36:36PM +0300, Ilya Smith wrote: > > Current implementation doesn't randomize address returned by mmap. > > All the entropy ends with choosing mmap_base_addr at the process > > creation. After that mmap bui

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

2018-03-23 Thread Rich Felker
On Fri, Mar 23, 2018 at 12:06:18PM -0700, Matthew Wilcox wrote: > On Fri, Mar 23, 2018 at 02:00:24PM -0400, Rich Felker wrote: > > On Fri, Mar 23, 2018 at 05:48:06AM -0700, Matthew Wilcox wrote: > > > On Thu, Mar 22, 2018 at 07:36:36PM +0300, Ilya Smith wrote: > > &g

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

2018-03-23 Thread Rich Felker
On Fri, Mar 23, 2018 at 12:29:52PM -0700, Matthew Wilcox wrote: > On Fri, Mar 23, 2018 at 03:16:21PM -0400, Rich Felker wrote: > > > Huh, I thought libc was aware of this. Also, I'd expect a libc-based > > > implementation to restrict itself to, eg, only loading librari

Re: Regression with arm in next with stack protector

2018-03-27 Thread Rich Felker
On Tue, Mar 27, 2018 at 10:04:10AM +0100, Russell King - ARM Linux wrote: > On Fri, Mar 23, 2018 at 11:14:53AM -0700, Tony Lindgren wrote: > > Hi, > > > > Looks like commit 5638790dadae ("zboot: fix stack protector in > > compressed boot phase") breaks booting on arm. > > > > This is all I get fr

Re: Regression with arm in next with stack protector

2018-03-27 Thread Rich Felker
On Tue, Mar 27, 2018 at 12:34:53PM +0100, Russell King - ARM Linux wrote: > On Tue, Mar 27, 2018 at 10:04:10AM +0100, Russell King - ARM Linux wrote: > > On Fri, Mar 23, 2018 at 11:14:53AM -0700, Tony Lindgren wrote: > > > Hi, > > > > > > Looks like commit 5638790dadae ("zboot: fix stack protector

[GIT PULL] arch/sh updates for 4.17

2018-04-13 Thread Rich Felker
bugs in futex, device tree, and userspace breakpoint traps, and for PCI issues on SH7786. Aurelien Jarno (1): sh: fix futex FUTEX_OP_SET op on userspace addresses Rich Felker (2): sh: fix memory corruption of unflattened

Re: [RFC v2 2/2] base: dma-mapping: Postpone page_to_pfn() on mmap()

2018-04-09 Thread Rich Felker
On Mon, Apr 09, 2018 at 04:06:15PM +0300, Laurent Pinchart wrote: > Hello, > > On Monday, 9 April 2018 14:11:22 EEST Robin Murphy wrote: > > On 09/04/18 08:25, jacopo mondi wrote: > > > Hi Robin, Laurent, > > > > > > a long time passed, sorry about this. > > > > > > On Wed, Nov 15, 2017 at

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-22 Thread Rich Felker
On Thu, Nov 22, 2018 at 05:59:44PM +0100, Florian Weimer wrote: > * Mathieu Desnoyers: > > > - On Nov 22, 2018, at 11:28 AM, Florian Weimer fwei...@redhat.com wrote: > > > >> * Mathieu Desnoyers: > >> > >>> Here is one scenario: we have 2 early adopter libraries using rseq which > >>> are dep

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-22 Thread Rich Felker
On Thu, Nov 22, 2018 at 01:35:44PM -0500, Mathieu Desnoyers wrote: > - On Nov 22, 2018, at 11:24 AM, Szabolcs Nagy szabolcs.n...@arm.com wrote: > > > On 22/11/18 15:33, Mathieu Desnoyers wrote: > >> - On Nov 22, 2018, at 10:21 AM, Florian Weimer fwei...@redhat.com > >> wrote: > >>> Right,

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-23 Thread Rich Felker
On Fri, Nov 23, 2018 at 02:10:14PM +0100, Florian Weimer wrote: > * Rich Felker: > > >> I'm not entirely sure because the glibc terminology is confusing, but I > >> think it places intial-exec TLS into the static TLS area (so that it has > >> a fixed offset

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-23 Thread Rich Felker
On Fri, Nov 23, 2018 at 12:05:20PM -0500, Mathieu Desnoyers wrote: > - On Nov 23, 2018, at 9:28 AM, Rich Felker dal...@libc.org wrote: > [...] > > > > Absolutely. As long as it's in libc, implicit destruction will happen. > > Actually I think the glibc code shou

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-23 Thread Rich Felker
On Fri, Nov 23, 2018 at 06:39:04PM +0100, Florian Weimer wrote: > * Rich Felker: > > > On Fri, Nov 23, 2018 at 12:05:20PM -0500, Mathieu Desnoyers wrote: > >> There has been presumptions about signals being blocked when the thread > >> exits throughout this email

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-23 Thread Rich Felker
On Fri, Nov 23, 2018 at 12:52:21PM -0500, Mathieu Desnoyers wrote: > - On Nov 23, 2018, at 12:30 PM, Rich Felker dal...@libc.org wrote: > > > On Fri, Nov 23, 2018 at 12:05:20PM -0500, Mathieu Desnoyers wrote: > >> - On Nov 23, 2018, at 9:28 AM, Rich Felker

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-26 Thread Rich Felker
On Mon, Nov 26, 2018 at 11:30:51AM -0500, Mathieu Desnoyers wrote: > - On Nov 26, 2018, at 10:51 AM, Mathieu Desnoyers > mathieu.desnoy...@efficios.com wrote: > > > - On Nov 26, 2018, at 3:28 AM, Florian Weimer fwei...@redhat.com wrote: > > > >> * Mathieu Desnoyers: > >> > >>> Using a "

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-26 Thread Rich Felker
On Mon, Nov 26, 2018 at 05:03:02PM +0100, Florian Weimer wrote: > * Mathieu Desnoyers: > > > So let's make __rseq_abi and __rseq_refcount strong symbols then ? > > Yes, please. (But I'm still not sure we need the reference counter.) The reference counter is needed for out-of-libc implementation

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-22 Thread Rich Felker
On Wed, Nov 21, 2018 at 01:39:32PM -0500, Mathieu Desnoyers wrote: > Register rseq(2) TLS for each thread (including main), and unregister > for each thread (excluding main). "rseq" stands for Restartable > Sequences. Maybe I'm missing something obvious, but "unregister" does not seem to be a mean

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-22 Thread Rich Felker
On Thu, Nov 22, 2018 at 10:04:16AM -0500, Mathieu Desnoyers wrote: > - On Nov 22, 2018, at 9:36 AM, Rich Felker dal...@libc.org wrote: > > > On Wed, Nov 21, 2018 at 01:39:32PM -0500, Mathieu Desnoyers wrote: > >> Register rseq(2) TLS for each thread (including main), an

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-22 Thread Rich Felker
On Thu, Nov 22, 2018 at 04:11:45PM +0100, Florian Weimer wrote: > * Mathieu Desnoyers: > > > Thoughts ? > > > > /* Unregister rseq TLS from kernel. */ > > if (has_rseq && __rseq_unregister_current_thread ()) > > abort(); > > > > advise_stack_range (pd->stackblock, pd->stackblock_size, (u

Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation

2018-11-22 Thread Rich Felker
On Thu, Nov 22, 2018 at 10:33:19AM -0500, Mathieu Desnoyers wrote: > - On Nov 22, 2018, at 10:21 AM, Florian Weimer fwei...@redhat.com wrote: > > > * Rich Felker: > > > >> On Thu, Nov 22, 2018 at 04:11:45PM +0100, Florian Weimer wrote: > >>> * Mat

Re: [PATCH] sh: switch to NO_BOOTMEM

2018-05-11 Thread Rich Felker
pens before > bootmem is initialized. Swapping the order of bootmem init and > unflattening could also fix this, but removing bootmem is desired. So > enable NO_BOOTMEM on SH like other architectures have done. > > Fixes: 0fa1c579349f ("of/fdt: use memblock_virt_alloc for early alloc&q

Re: [PATCH] sh: switch to NO_BOOTMEM

2018-05-11 Thread Rich Felker
On Fri, May 11, 2018 at 10:37:42AM -0500, Rob Herring wrote: > On Fri, May 11, 2018 at 10:02 AM, Rich Felker wrote: > > On Fri, May 11, 2018 at 08:45:59AM -0500, Rob Herring wrote: > >> Commit 0fa1c579349f ("of/fdt: use memblock_virt_alloc for early alloc") > &

[GIT PULL] arch/sh regression fixes for 4.17

2018-05-11 Thread Rich Felker
and a build failure. Jacopo Mondi (1): sh: mm: Fix unprotected access to struct device Rich Felker (1): sh: fix build failure for J2 cpu with SMP disabled Rob Herring (1): sh: switch to NO_BOOTMEM arch/sh/Kconfig

Re: Can we drop upstream Linux x32 support?

2018-12-12 Thread Rich Felker
On Wed, Dec 12, 2018 at 09:12:34AM +, Steven Newbury wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > First off I'd like to request: Please don't break my userspace! > > I have a number of systems running with x32-abi as native. They work > well, I've no want or desire to upgra

Re: Can we drop upstream Linux x32 support?

2018-12-12 Thread Rich Felker
On Wed, Dec 12, 2018 at 02:46:00PM +, Steven Newbury wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, 2018-12-12 at 09:01 -0500, Rich Felker wrote: > > On Wed, Dec 12, 2018 at 09:12:34AM +, Steven Newbury wrote: > > > -BEGIN PGP SIG

Re: Can we drop upstream Linux x32 support?

2018-12-12 Thread Rich Felker
On Wed, Dec 12, 2018 at 08:39:53AM -0800, Andy Lutomirski wrote: > > On Dec 11, 2018, at 6:33 PM, Thorsten Glaser wrote: > > > > Andy Lutomirski dixit: > > > > > > >> IMO the real right solution would be to push the whole problem to > >> userspace: get an ILP32 system working with almost or entir

Re: Can we drop upstream Linux x32 support?

2018-12-13 Thread Rich Felker
On Thu, Dec 13, 2018 at 12:40:25PM +, Catalin Marinas wrote: > On Wed, Dec 12, 2018 at 10:03:30AM -0800, Andy Lutomirski wrote: > > On Wed, Dec 12, 2018 at 8:52 AM Rich Felker wrote: > > > On Wed, Dec 12, 2018 at 08:39:53AM -0800, Andy Lutomirski wrote: > > &

Re: Can we drop upstream Linux x32 support?

2018-12-13 Thread Rich Felker
On Tue, Dec 11, 2018 at 11:29:14AM +0100, John Paul Adrian Glaubitz wrote: > I can't say anything about the syscall interface. However, what I do know > is that the weird combination of a 32-bit userland with a 64-bit kernel > interface is sometimes causing issues. For example, application code usu

Re: Can we drop upstream Linux x32 support?

2018-12-13 Thread Rich Felker
On Thu, Dec 13, 2018 at 05:04:59PM +0100, Florian Weimer wrote: > * Rich Felker: > > >> If the compiler can handle the zeroing, that would be great, though not > >> sure how (some __attribute__((zero)) which generates a type constructor > >> for such structure; i

Re: Can we drop upstream Linux x32 support?

2018-12-14 Thread Rich Felker
On Fri, Dec 14, 2018 at 12:42:34PM +0100, Florian Weimer wrote: > * Rich Felker: > > > On Thu, Dec 13, 2018 at 05:04:59PM +0100, Florian Weimer wrote: > >> * Rich Felker: > >> > >> >> If the compiler can handle the zeroing, that would be great, th

Re: Can we drop upstream Linux x32 support?

2018-12-14 Thread Rich Felker
On Fri, Dec 14, 2018 at 03:13:10PM +0100, Bernd Petrovitsch wrote: > On 13/12/2018 17:02, Rich Felker wrote: > > On Tue, Dec 11, 2018 at 11:29:14AM +0100, John Paul Adrian Glaubitz wrote: > >> I can't say anything about the syscall interface. However, what I do know

Re: Can we drop upstream Linux x32 support?

2018-12-14 Thread Rich Felker
On Fri, Dec 14, 2018 at 05:38:33PM +0100, Florian Weimer wrote: > * Rich Felker: > > > This is all useless (and wrong since tv_nsec is required to have type > > long as part of C and POSIX, regardless of ILP32-vs-LP64; that's a bug > > in glibc's x32). > &g

Re: Fixing MIPS delay slot emulation weakness?

2018-12-15 Thread Rich Felker
On Sat, Dec 15, 2018 at 11:19:37AM -0800, Andy Lutomirski wrote: > Hi all- > > Some security researchers pointed out that writing to the delay slot > emulation page is a great exploit technique on MIPS. It was > introduced in: > > commit 432c6bacbd0c16ec210c43da411ccc3855c4c010 > Author: Paul Bu

  1   2   3   4   5   6   >