Re: [linus:master] BUILD REGRESSION f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051

On Sat, Dec 16, 2017 at 10:46:05PM -0500, Nicolas Pitre wrote: > Date: Fri, 10 Nov 2017 15:57:21 +0100 > From: Arnd Bergmann > Subject: [PATCH] cramfs: fix MTD dependency > > With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure: > > fs/cramfs/inode.o: In function

Re: [linus:master] BUILD REGRESSION f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051

On Sat, Dec 16, 2017 at 10:46:05PM -0500, Nicolas Pitre wrote: > Date: Fri, 10 Nov 2017 15:57:21 +0100 > From: Arnd Bergmann > Subject: [PATCH] cramfs: fix MTD dependency > > With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure: > > fs/cramfs/inode.o: In function `cramfs_mount': >

[RFC GIT PULL] Page Table Isolation (PTI), x86 syscall entry code changes

Linus, Please pull the latest WIP.x86-pti.entry-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.entry-for-linus # HEAD: 6cbd2171e89b13377261d15e64384df60ecb530e x86/cpufeatures: Make CPU bugs sticky The main changes here are Andy

[RFC GIT PULL] Page Table Isolation (PTI), x86 syscall entry code changes

Linus, Please pull the latest WIP.x86-pti.entry-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.entry-for-linus # HEAD: 6cbd2171e89b13377261d15e64384df60ecb530e x86/cpufeatures: Make CPU bugs sticky The main changes here are Andy

Re: [PATCH v19 3/7] xbitmap: add more operations

Wang, Wei W wrote: > > Wei Wang wrote: > > > > But passing GFP_NOWAIT means that we can handle allocation failure. > > > > There is no need to use preload approach when we can handle allocation > > > > failure. > > > > > > I think the reason we need xb_preload is because radix tree insertion > >

Re: [PATCH v19 3/7] xbitmap: add more operations

Wang, Wei W wrote: > > Wei Wang wrote: > > > > But passing GFP_NOWAIT means that we can handle allocation failure. > > > > There is no need to use preload approach when we can handle allocation > > > > failure. > > > > > > I think the reason we need xb_preload is because radix tree insertion > >

[GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

Linus, Please pull the latest WIP.x86-pti.base-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.base-for-linus # HEAD: 2aeb07365bcd489620f71390a7d2031cd4dfb83e x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow Note, this tree

[GIT PULL] Page Table Isolation (PTI) v4.14 backporting base tree

Linus, Please pull the latest WIP.x86-pti.base-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.base-for-linus # HEAD: 2aeb07365bcd489620f71390a7d2031cd4dfb83e x86/mm/kasan: Don't use vmemmap_populate() to initialize shadow Note, this tree

Re: [GIT PULL] x86 fixes

On Sun, Dec 17, 2017 at 12:41:42PM +0100, Thomas Gleixner wrote: > > X86_BUG_CPU_SECURE_MODE_PTI should be added to DISABLED_FEATURES or > > DISABLED_BUGS or whatever if it's not configured in, which will reduce > > bloat. Borislav, that's kind of up your alley, since I don't think > > the

Re: [GIT PULL] x86 fixes

On Sun, Dec 17, 2017 at 12:41:42PM +0100, Thomas Gleixner wrote: > > X86_BUG_CPU_SECURE_MODE_PTI should be added to DISABLED_FEATURES or > > DISABLED_BUGS or whatever if it's not configured in, which will reduce > > bloat. Borislav, that's kind of up your alley, since I don't think > > the

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, Dec 17, 2017 at 04:00:43PM +0100, Willy Tarreau wrote: > > > Any idea why this issue is on v4.14, but not observed on v4.4? > > > > I have absolutely no idea. > > Warning, the 4.4 in openwrt very likely is heavily patched! That's also > why I'm moving to mainline instead (to know what

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, Dec 17, 2017 at 04:00:43PM +0100, Willy Tarreau wrote: > > > Any idea why this issue is on v4.14, but not observed on v4.4? > > > > I have absolutely no idea. > > Warning, the 4.4 in openwrt very likely is heavily patched! That's also > why I'm moving to mainline instead (to know what

[GIT pull] timer fix for 4.15

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus A single bugfix which prevents arbitrary sigev_notify values in posix-timers. Thanks, tglx --> Thomas Gleixner

[GIT pull] timer fix for 4.15

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus A single bugfix which prevents arbitrary sigev_notify values in posix-timers. Thanks, tglx --> Thomas Gleixner

[RFC GIT PULL] Page Table Isolation (PTI) preparatory tree

Linus, Please pull the latest WIP.x86-pti.base.prep-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.base.prep-for-linus # HEAD: 1784f9144b143a1e8b19fe94083b040aa559182b drivers/misc/intel/pti: Rename the header file to free up the namespace

[RFC GIT PULL] Page Table Isolation (PTI) preparatory tree

Linus, Please pull the latest WIP.x86-pti.base.prep-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86-pti.base.prep-for-linus # HEAD: 1784f9144b143a1e8b19fe94083b040aa559182b drivers/misc/intel/pti: Rename the header file to free up the namespace

Re: [RFC GIT PULL] x86 Page Table Isolation (PTI) syscall entry code preparatory patches

* Ingo Molnar wrote: > > was supposed to be a synchronization point, but if you do > > > > git diff 9a818d1a3235..9a818d1a3235^ > > > > it isn't actually synchronized. It's *almost* synchronized, but not > > quite. How did those cherry-picks that were already upstream

Re: [RFC GIT PULL] x86 Page Table Isolation (PTI) syscall entry code preparatory patches

* Ingo Molnar wrote: > > was supposed to be a synchronization point, but if you do > > > > git diff 9a818d1a3235..9a818d1a3235^ > > > > it isn't actually synchronized. It's *almost* synchronized, but not > > quite. How did those cherry-picks that were already upstream end up > > causing

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, Dec 17, 2017 at 03:53:05PM +0100, Boris Brezillon wrote: > On Sun, 17 Dec 2017 11:27:51 -0300 > Ezequiel Garcia wrote: > > > On 17 December 2017 at 09:05, Willy Tarreau wrote: > > > Hello, > > > > > > I recently bought a Linksys WRT1900ACS

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, Dec 17, 2017 at 03:53:05PM +0100, Boris Brezillon wrote: > On Sun, 17 Dec 2017 11:27:51 -0300 > Ezequiel Garcia wrote: > > > On 17 December 2017 at 09:05, Willy Tarreau wrote: > > > Hello, > > > > > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > > > NAND

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, 17 Dec 2017 11:27:51 -0300 Ezequiel Garcia wrote: > On 17 December 2017 at 09:05, Willy Tarreau wrote: > > Hello, > > > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > > NAND flash. While I could get OpenWRT to work

Re: pxa3xx_nand times out in 4.14 with JFFS2

On Sun, 17 Dec 2017 11:27:51 -0300 Ezequiel Garcia wrote: > On 17 December 2017 at 09:05, Willy Tarreau wrote: > > Hello, > > > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > > NAND flash. While I could get OpenWRT to work flawlessly on it using > > kernel 4.4,

[tip:WIP.x86/pti.entry 10/39] include/linux/compiler.h:344:2: error: implicit declaration of function 'smp_read_barrier_depends'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/pti.entry head: 6891282dd3ab7fead975ed52d0f7f8da37ab96a5 commit: c2bc66082e1048c7573d72e62f597bdc5ce13fea [10/39] locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE() config:

[tip:WIP.x86/pti.entry 10/39] include/linux/compiler.h:344:2: error: implicit declaration of function 'smp_read_barrier_depends'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/pti.entry head: 6891282dd3ab7fead975ed52d0f7f8da37ab96a5 commit: c2bc66082e1048c7573d72e62f597bdc5ce13fea [10/39] locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE() config:

Re: pxa3xx_nand times out in 4.14 with JFFS2

On 17 December 2017 at 09:05, Willy Tarreau wrote: > Hello, > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > NAND flash. While I could get OpenWRT to work flawlessly on it using > kernel 4.4, mainline 4.14.6 fails with a lot of such messages : > >

Re: pxa3xx_nand times out in 4.14 with JFFS2

On 17 December 2017 at 09:05, Willy Tarreau wrote: > Hello, > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > NAND flash. While I could get OpenWRT to work flawlessly on it using > kernel 4.4, mainline 4.14.6 fails with a lot of such messages : > > pxa3xx-nand

Re: pxa3xx_nand times out in 4.14 with JFFS2

On 17 December 2017 at 10:17, Willy Tarreau wrote: > Hi Boris! > > On Sun, Dec 17, 2017 at 01:33:55PM +0100, Boris Brezillon wrote: >> You should have a look at this thread [1], and in case you don't want >> to read everything, > > I've read it entirely, it was very instructive! > >>

Re: pxa3xx_nand times out in 4.14 with JFFS2

On 17 December 2017 at 10:17, Willy Tarreau wrote: > Hi Boris! > > On Sun, Dec 17, 2017 at 01:33:55PM +0100, Boris Brezillon wrote: >> You should have a look at this thread [1], and in case you don't want >> to read everything, > > I've read it entirely, it was very instructive! > >> you can just

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

Hello, On Sat, Dec 16, 2017 at 6:51 PM, Stephen Hemminger wrote: > It makes sense to organize the config if you dont break old configs. > It would be more logical to group and treat all para-virtualized guest > support in same way. Hyper-V should be next to KVM and

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

Hello, On Sat, Dec 16, 2017 at 6:51 PM, Stephen Hemminger wrote: > It makes sense to organize the config if you dont break old configs. > It would be more logical to group and treat all para-virtualized guest > support in same way. Hyper-V should be next to KVM and Xen. I agree, I can try to

RE: [PATCH v19 3/7] xbitmap: add more operations

On Saturday, December 16, 2017 3:22 AM, Matthew Wilcox wrote: > On Fri, Dec 15, 2017 at 10:49:15AM -0800, Matthew Wilcox wrote: > > Here's the API I'm looking at right now. The user need take no lock; > > the locking (spinlock) is handled internally to the implementation. Another place I saw

RE: [PATCH v19 3/7] xbitmap: add more operations

On Saturday, December 16, 2017 3:22 AM, Matthew Wilcox wrote: > On Fri, Dec 15, 2017 at 10:49:15AM -0800, Matthew Wilcox wrote: > > Here's the API I'm looking at right now. The user need take no lock; > > the locking (spinlock) is handled internally to the implementation. Another place I saw

Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register")

2017-12-17 0:32 GMT+08:00 Bruno Wolff III : > On Fri, Dec 15, 2017 at 13:51:22 -0600, > Bruno Wolff III wrote: >> >> >> I do not know what is different. Do you have any ideas? Most likely I >> won't be able to test any more kernels until Monday (unless I can use

Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register")

2017-12-17 0:32 GMT+08:00 Bruno Wolff III : > On Fri, Dec 15, 2017 at 13:51:22 -0600, > Bruno Wolff III wrote: >> >> >> I do not know what is different. Do you have any ideas? Most likely I >> won't be able to test any more kernels until Monday (unless I can use most >> of my most recent build

Re: PROBLEM: NULL pointer dereference in kernel 4.14.6

This has happend again, and hopefully the report is not as mangled as the previous one. I was also trying to start "systemctl status", only once this time. The kernel build is different because I've just disabled RCU tracing/debugging options. One more thing, this kernel was built with gcc 7.2.1

Re: PROBLEM: NULL pointer dereference in kernel 4.14.6

This has happend again, and hopefully the report is not as mangled as the previous one. I was also trying to start "systemctl status", only once this time. The kernel build is different because I've just disabled RCU tracing/debugging options. One more thing, this kernel was built with gcc 7.2.1

Re: pxa3xx_nand times out in 4.14 with JFFS2

Hi Boris! On Sun, Dec 17, 2017 at 01:33:55PM +0100, Boris Brezillon wrote: > You should have a look at this thread [1], and in case you don't want > to read everything, I've read it entirely, it was very instructive! > you can just test the solution proposed here [2]. > >

Re: pxa3xx_nand times out in 4.14 with JFFS2

Hi Boris! On Sun, Dec 17, 2017 at 01:33:55PM +0100, Boris Brezillon wrote: > You should have a look at this thread [1], and in case you don't want > to read everything, I've read it entirely, it was very instructive! > you can just test the solution proposed here [2]. > >

Re: [PATCH 01/19] fs: new API for handling inode->i_version

On Sat, 2017-12-16 at 15:17 +1100, NeilBrown wrote: > On Wed, Dec 13 2017, Jeff Layton wrote: > > > On Thu, 2017-12-14 at 09:04 +1100, NeilBrown wrote: > > > On Wed, Dec 13 2017, Jeff Layton wrote: > > > > > > > +/* > > > > + * The change attribute (i_version) is mandated by NFSv4 and is mostly

Re: [PATCH 01/19] fs: new API for handling inode->i_version

On Sat, 2017-12-16 at 15:17 +1100, NeilBrown wrote: > On Wed, Dec 13 2017, Jeff Layton wrote: > > > On Thu, 2017-12-14 at 09:04 +1100, NeilBrown wrote: > > > On Wed, Dec 13 2017, Jeff Layton wrote: > > > > > > > +/* > > > > + * The change attribute (i_version) is mandated by NFSv4 and is mostly

Re: [PATCH/RFC] DT: leds: Fix 'label' property description and add 'colour' property

cc devicet...@vger.kernel.org On 12/14/2017 10:35 PM, Jacek Anaszewski wrote: > On 12/11/2017 05:27 PM, Rob Herring wrote: >> On Mon, Dec 4, 2017 at 4:43 AM, Pavel Machek wrote: >>> Hi! >>> Label property was imposed a uniqueness requirement, which was erroneous, since

Re: [PATCH/RFC] DT: leds: Fix 'label' property description and add 'colour' property

cc devicet...@vger.kernel.org On 12/14/2017 10:35 PM, Jacek Anaszewski wrote: > On 12/11/2017 05:27 PM, Rob Herring wrote: >> On Mon, Dec 4, 2017 at 4:43 AM, Pavel Machek wrote: >>> Hi! >>> Label property was imposed a uniqueness requirement, which was erroneous, since ePAPR defines it

Re: [PATCH v3] iio: adc: ina2xx: Make calibration register value fixed

On Fri, 15 Dec 2017 08:59:23 +0100 Maciej Purski wrote: > Calibration register is used for calculating current register in > hardware according to datasheet: > current = shunt_volt * calib_register / 2048 (ina 226) > current = shunt_volt * calib_register / 4096 (ina 219) >

Re: [PATCH v3] iio: adc: ina2xx: Make calibration register value fixed

On Fri, 15 Dec 2017 08:59:23 +0100 Maciej Purski wrote: > Calibration register is used for calculating current register in > hardware according to datasheet: > current = shunt_volt * calib_register / 2048 (ina 226) > current = shunt_volt * calib_register / 4096 (ina 219) > > Fix calib_register

Re: [PATCH v4 1/2] iio: hx711: add triggered buffer support

On Wed, 13 Dec 2017 18:10:11 +0100 Andreas Klinger wrote: > Add buffer to device data struct and add trigger function > > Data format is quite simple: > voltage - channel 0 32 Bit > voltage - channel 1 32 Bit > timestamp 64 Bit > > Using

Re: [PATCH v4 1/2] iio: hx711: add triggered buffer support

On Wed, 13 Dec 2017 18:10:11 +0100 Andreas Klinger wrote: > Add buffer to device data struct and add trigger function > > Data format is quite simple: > voltage - channel 0 32 Bit > voltage - channel 1 32 Bit > timestamp 64 Bit > > Using both channels at the

Re: [PATCH v4 2/2] iio: hx711: fix bug in reset functionality

On Wed, 13 Dec 2017 18:10:34 +0100 Andreas Klinger wrote: > Return value in hx711_reset() should indicate status of dout otherwise the > calling function is reporting an error as false positive > > If there are two reads too close to each other, then the second one will >

Re: [PATCH v4 2/2] iio: hx711: fix bug in reset functionality

On Wed, 13 Dec 2017 18:10:34 +0100 Andreas Klinger wrote: > Return value in hx711_reset() should indicate status of dout otherwise the > calling function is reporting an error as false positive > > If there are two reads too close to each other, then the second one will > never succeed. This

Re: [PATCH v5 1/3] lib: Add strongly typed 64bit int_sqrt

On Wed, 13 Dec 2017 15:00:39 +0100 Crt Mori wrote: > There is no option to perform 64bit integer sqrt on 32bit platform. > Added stronger typed int_sqrt64 enables the 64bit calculations to > be performed on 32bit platforms. Although int_sqrt() is a rough > approximation, the

Re: [PATCH v5 1/3] lib: Add strongly typed 64bit int_sqrt

On Wed, 13 Dec 2017 15:00:39 +0100 Crt Mori wrote: > There is no option to perform 64bit integer sqrt on 32bit platform. > Added stronger typed int_sqrt64 enables the 64bit calculations to > be performed on 32bit platforms. Although int_sqrt() is a rough > approximation, the same algorithm is

Re: pxa3xx_nand times out in 4.14 with JFFS2

Hi Willy, On Sun, 17 Dec 2017 13:05:03 +0100 Willy Tarreau wrote: > Hello, > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > NAND flash. While I could get OpenWRT to work flawlessly on it using > kernel 4.4, mainline 4.14.6 fails with a lot of such

Re: pxa3xx_nand times out in 4.14 with JFFS2

Hi Willy, On Sun, 17 Dec 2017 13:05:03 +0100 Willy Tarreau wrote: > Hello, > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a > NAND flash. While I could get OpenWRT to work flawlessly on it using > kernel 4.4, mainline 4.14.6 fails with a lot of such messages : > >

PROBLEM: NULL pointer dereference in kernel 4.14.6

Hello I noticed my system is less stable after upgrade from kernel 4.13 to 4.14.6 yesterday. There was a soft CPU lockup, hard CPU lockup and one kernel panic while shutting down the system, all on the same day. There was little diagnostic information collected at the time, but since then I've

PROBLEM: NULL pointer dereference in kernel 4.14.6

Hello I noticed my system is less stable after upgrade from kernel 4.13 to 4.14.6 yesterday. There was a soft CPU lockup, hard CPU lockup and one kernel panic while shutting down the system, all on the same day. There was little diagnostic information collected at the time, but since then I've

pxa3xx_nand times out in 4.14 with JFFS2

Hello, I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a NAND flash. While I could get OpenWRT to work flawlessly on it using kernel 4.4, mainline 4.14.6 fails with a lot of such messages : pxa3xx-nand f10d.flash: Wait time out!!! Looking a bit closer, I found that

pxa3xx_nand times out in 4.14 with JFFS2

Hello, I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a NAND flash. While I could get OpenWRT to work flawlessly on it using kernel 4.4, mainline 4.14.6 fails with a lot of such messages : pxa3xx-nand f10d.flash: Wait time out!!! Looking a bit closer, I found that

Re: [PATCH v1 5/7] iio: adc: ina2xx: Use a monotonic clock for delay calculation

On Tue, 12 Dec 2017 20:21:14 + Jonathan Cameron wrote: > On Sun, 10 Dec 2017 21:47:37 +0100 > Stefan Brüns wrote: > > > On Sunday, December 10, 2017 6:31:57 PM CET Jonathan Cameron wrote: > > > On Fri, 8 Dec 2017 18:41:50 +0100 > > > > > >

Re: [PATCH v1 5/7] iio: adc: ina2xx: Use a monotonic clock for delay calculation

On Tue, 12 Dec 2017 20:21:14 + Jonathan Cameron wrote: > On Sun, 10 Dec 2017 21:47:37 +0100 > Stefan Brüns wrote: > > > On Sunday, December 10, 2017 6:31:57 PM CET Jonathan Cameron wrote: > > > On Fri, 8 Dec 2017 18:41:50 +0100 > > > > > > Stefan Brüns wrote: > > > > The iio

Re: [PATCH v1 4/7] iio: adc: ina2xx: Do not udelay for several seconds

On Fri, 8 Dec 2017 18:41:49 +0100 Stefan Brüns wrote: > The conversion time can be up to 16 seconds (8 ms per channel, 2 channels, > 1024 times averaging). > > Signed-off-by: Stefan Brüns Applied > --- > >

Re: [PATCH v1 4/7] iio: adc: ina2xx: Do not udelay for several seconds

On Fri, 8 Dec 2017 18:41:49 +0100 Stefan Brüns wrote: > The conversion time can be up to 16 seconds (8 ms per channel, 2 channels, > 1024 times averaging). > > Signed-off-by: Stefan Brüns Applied > --- > > drivers/iio/adc/ina2xx-adc.c | 8 +--- > 1 file changed, 5 insertions(+), 3

RE: [PATCH v19 3/7] xbitmap: add more operations

> -Original Message- > From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > Sent: Sunday, December 17, 2017 6:22 PM > To: Wang, Wei W ; wi...@infradead.org > Cc: virtio-...@lists.oasis-open.org; linux-kernel@vger.kernel.org; qemu- > de...@nongnu.org;

RE: [PATCH v19 3/7] xbitmap: add more operations

> -Original Message- > From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > Sent: Sunday, December 17, 2017 6:22 PM > To: Wang, Wei W ; wi...@infradead.org > Cc: virtio-...@lists.oasis-open.org; linux-kernel@vger.kernel.org; qemu- > de...@nongnu.org;

Re: [GIT PULL] x86 fixes

On Sat, 16 Dec 2017, Andy Lutomirski wrote: > On Fri, Dec 15, 2017 at 8:07 AM, Ingo Molnar wrote: > I few things I noticed in the PTI tree: > > "x86/mm/pti: Map ESPFIX into user space" has a leftover pr_err(). > Sorry, my bad, I've spent *way* too long looking at this crap to >

Re: [GIT PULL] x86 fixes

On Sat, 16 Dec 2017, Andy Lutomirski wrote: > On Fri, Dec 15, 2017 at 8:07 AM, Ingo Molnar wrote: > I few things I noticed in the PTI tree: > > "x86/mm/pti: Map ESPFIX into user space" has a leftover pr_err(). > Sorry, my bad, I've spent *way* too long looking at this crap to > retain my sanity.

[PATCH 3/3] lib: cleanup dead code from lib/percpu_test.c

lib/percpu_test.c code allows to compile either as a loadable modules or builtin into the kernel. Current code returns -EAGAIN on successful termination from module_init. Such a fail will directly unload the module and hence there is no scope to execute percpu_test_exit on module_exit.

[PATCH 3/3] lib: cleanup dead code from lib/percpu_test.c

lib/percpu_test.c code allows to compile either as a loadable modules or builtin into the kernel. Current code returns -EAGAIN on successful termination from module_init. Such a fail will directly unload the module and hence there is no scope to execute percpu_test_exit on module_exit.

Re: [patch V149 38/50] x86/pti: Put the LDT in its own PGD if PTI is on

On Sat, Dec 16, 2017 at 10:24:32PM +0100, Thomas Gleixner wrote: > From: Andy Lutomirski > > With PTI enabled, the LDT must be mapped in the usermode tables somewhere. > The LDT is per process, i.e. per mm. > > An earlier approach mapped the LDT on context switch into a fixmap

Re: [patch V149 38/50] x86/pti: Put the LDT in its own PGD if PTI is on

On Sat, Dec 16, 2017 at 10:24:32PM +0100, Thomas Gleixner wrote: > From: Andy Lutomirski > > With PTI enabled, the LDT must be mapped in the usermode tables somewhere. > The LDT is per process, i.e. per mm. > > An earlier approach mapped the LDT on context switch into a fixmap area, > but

Re: [patch V149 37/50] x86/mm/64: Make a full PGD-entry size hole in the memory map

On Sat, Dec 16, 2017 at 10:24:31PM +0100, Thomas Gleixner wrote: > From: Andy Lutomirski > > Shrink vmalloc space from 16384TiB to 12800TiB to enlarge the hole starting > at 0xff90 to be a full PGD entry. > > A subsequent patch will use this hole for the pagetable

Re: [patch V149 37/50] x86/mm/64: Make a full PGD-entry size hole in the memory map

On Sat, Dec 16, 2017 at 10:24:31PM +0100, Thomas Gleixner wrote: > From: Andy Lutomirski > > Shrink vmalloc space from 16384TiB to 12800TiB to enlarge the hole starting > at 0xff90 to be a full PGD entry. > > A subsequent patch will use this hole for the pagetable isolation LDT >

[GIT PULL REQUEST] watchdog - v4.15 Fixes

Hi Linus, here are 4 fixes for the watchdog device drivers. Please pull. Kind regards, Wim. The following changes since commit f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051: Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2017-12-16 13:43:08 -0800) are

[GIT PULL REQUEST] watchdog - v4.15 Fixes

Hi Linus, here are 4 fixes for the watchdog device drivers. Please pull. Kind regards, Wim. The following changes since commit f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051: Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2017-12-16 13:43:08 -0800) are

Re: BUG: unable to handle kernel NULL pointer dereference in irq_bypass_register_consumer

2017-12-17 17:56 GMT+08:00 syzbot : > Hello, > > syzkaller hit the following crash on > 41d8c16909ebda40f7b4982a7f5e2ad102705ade > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC)

Re: BUG: unable to handle kernel NULL pointer dereference in irq_bypass_register_consumer

2017-12-17 17:56 GMT+08:00 syzbot : > Hello, > > syzkaller hit the following crash on > 41d8c16909ebda40f7b4982a7f5e2ad102705ade > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. >

[PATCH 2/2] lib: cleanup dead code from rbtree_test.c

lib/rbtree_test.c code allows to compile either as a loadable modules or builtin into the kernel. Current code returns -EAGAIN on successful termination from module_init. Such a fail will directly unload the module and hence there is no scope to execute rbtree_test_exit on module_exit. This

[PATCH 2/2] lib: cleanup dead code from rbtree_test.c

lib/rbtree_test.c code allows to compile either as a loadable modules or builtin into the kernel. Current code returns -EAGAIN on successful termination from module_init. Such a fail will directly unload the module and hence there is no scope to execute rbtree_test_exit on module_exit. This

Re: [PATCH v19 3/7] xbitmap: add more operations

Wei Wang wrote: > > But passing GFP_NOWAIT means that we can handle allocation failure. There is > > no need to use preload approach when we can handle allocation failure. > > I think the reason we need xb_preload is because radix tree insertion > needs the memory being preallocated already (it

Re: [PATCH v19 3/7] xbitmap: add more operations

Wei Wang wrote: > > But passing GFP_NOWAIT means that we can handle allocation failure. There is > > no need to use preload approach when we can handle allocation failure. > > I think the reason we need xb_preload is because radix tree insertion > needs the memory being preallocated already (it

Re: [PATCH v1 3/7] iio: adc: ina2xx: Remove unneeded dummy read to clear CNVR flag

On Wed, 13 Dec 2017 00:48:40 +0100 Stefan Brüns wrote: > On Tuesday, December 12, 2017 9:15:30 PM CET Jonathan Cameron wrote: > > On Sun, 10 Dec 2017 21:53:42 +0100 > > > > Stefan Brüns wrote: > > > On Sunday, December 10, 2017

Re: [PATCH v1 3/7] iio: adc: ina2xx: Remove unneeded dummy read to clear CNVR flag

On Wed, 13 Dec 2017 00:48:40 +0100 Stefan Brüns wrote: > On Tuesday, December 12, 2017 9:15:30 PM CET Jonathan Cameron wrote: > > On Sun, 10 Dec 2017 21:53:42 +0100 > > > > Stefan Brüns wrote: > > > On Sunday, December 10, 2017 6:27:33 PM CET Jonathan Cameron wrote: > > > > On Fri, 8 Dec

drivers/input//touchscreen/hideep.c:670:3: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'?

Hi Anthony, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051 commit: 842ff286166e8512450573f6b6eb5e04e626a07f Input: add support for HiDeep touchscreen date: 5 weeks ago

drivers/input//touchscreen/hideep.c:670:3: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'?

Hi Anthony, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051 commit: 842ff286166e8512450573f6b6eb5e04e626a07f Input: add support for HiDeep touchscreen date: 5 weeks ago

Re: [PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x

On Sun, 2017-12-17 at 01:45 -0800, Joe Perches wrote: > On Sun, 2017-12-17 at 15:07 +0530, Shreeya Patel wrote: > > > > Replace true and false keywords with "x" and "!x" > > respectively to follow the kernel coding style. > [] > > > > diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c > >

Re: [PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x

On Sun, 2017-12-17 at 01:45 -0800, Joe Perches wrote: > On Sun, 2017-12-17 at 15:07 +0530, Shreeya Patel wrote: > > > > Replace true and false keywords with "x" and "!x" > > respectively to follow the kernel coding style. > [] > > > > diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c > >

[PATCH] lib: add module unload support to sort tests

test_sort.c perform array-based and linked list sort test. Code allows to compile either as a loadable modules or builtin into the kernel. Current code is not allow to unload the test_sort.ko module after successful completion. This patch add support to unload the "test_sort.ko" module.

[PATCH] lib: add module unload support to sort tests

test_sort.c perform array-based and linked list sort test. Code allows to compile either as a loadable modules or builtin into the kernel. Current code is not allow to unload the test_sort.ko module after successful completion. This patch add support to unload the "test_sort.ko" module.

Re: [PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x

On Sun, 2017-12-17 at 15:07 +0530, Shreeya Patel wrote: > Replace true and false keywords with "x" and "!x" > respectively to follow the kernel coding style. [] > diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c > b/drivers/staging/rtl8723bs/hal/sdio_ops.c [] > @@ -191,8 +191,8 @@ static u32

Re: [PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x

On Sun, 2017-12-17 at 15:07 +0530, Shreeya Patel wrote: > Replace true and false keywords with "x" and "!x" > respectively to follow the kernel coding style. [] > diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c > b/drivers/staging/rtl8723bs/hal/sdio_ops.c [] > @@ -191,8 +191,8 @@ static u32

Re: [PATCH v1 2/7] iio: adc: ina2xx: Clarify size requirement for data buffer

On Fri, 8 Dec 2017 18:41:47 +0100 Stefan Brüns wrote: > The timestamp is inserted into the buffer after the sample data by > iio_push_to_buffers_with_timestamp, document the space requirement for > the timestamp. > > Signed-off-by: Stefan Brüns

Re: [PATCH v1 2/7] iio: adc: ina2xx: Clarify size requirement for data buffer

On Fri, 8 Dec 2017 18:41:47 +0100 Stefan Brüns wrote: > The timestamp is inserted into the buffer after the sample data by > iio_push_to_buffers_with_timestamp, document the space requirement for > the timestamp. > > Signed-off-by: Stefan Brüns Applied and pushed out as testing for the

Re: [PATCH v1 1/7] iio: adc: ina2xx: Remove bogus cast for data argument

On Fri, 8 Dec 2017 18:41:46 +0100 Stefan Brüns wrote: > iio_push_to_buffers_with_timestamp expects a void pointer, so the cast > is both unnecessary and misleading. > > Signed-off-by: Stefan Brüns Applied to the togreg branch of

Re: [PATCH v1 1/7] iio: adc: ina2xx: Remove bogus cast for data argument

On Fri, 8 Dec 2017 18:41:46 +0100 Stefan Brüns wrote: > iio_push_to_buffers_with_timestamp expects a void pointer, so the cast > is both unnecessary and misleading. > > Signed-off-by: Stefan Brüns Applied to the togreg branch of iio.git and pushed out as testing for the autobuilders to play

[PATCH 4/4] Staging: rtl8723bs: Use !x instead of NULL comparison

If "x" is compared to NULL, use "!x" instead of it, so as to follow the kernel coding style. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git

[PATCH 4/4] Staging: rtl8723bs: Use !x instead of NULL comparison

If "x" is compared to NULL, use "!x" instead of it, so as to follow the kernel coding style. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c

[PATCH 3/4] Staging: rtl8723bs: Change condition to assignment

Change the conditional operator to assignment as it is not a conditional statement. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/4] Staging: rtl8723bs: Change condition to assignment

Change the conditional operator to assignment as it is not a conditional statement. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c

[PATCH 2/4] Staging: rtl8723bs: Change names to conform to the kernel code

Change names of some variables and functions to conform to the kernel coding style. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 714 +++ 1 file changed, 357 insertions(+), 357 deletions(-) diff --git

[PATCH 2/4] Staging: rtl8723bs: Change names to conform to the kernel code

Change names of some variables and functions to conform to the kernel coding style. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 714 +++ 1 file changed, 357 insertions(+), 357 deletions(-) diff --git

[PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x

Replace true and false keywords with "x" and "!x" respectively to follow the kernel coding style. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 30 ++ 1 file changed, 14 insertions(+), 16 deletions(-) diff

[PATCH 1/4] Staging: rtl8723bs: Replace true with x and false with !x

Replace true and false keywords with "x" and "!x" respectively to follow the kernel coding style. Signed-off-by: Shreeya Patel --- drivers/staging/rtl8723bs/hal/sdio_ops.c | 30 ++ 1 file changed, 14 insertions(+), 16 deletions(-) diff --git

<    3   4   5   6   7   8   9   >