Re: [PATCH v9] Input: synaptics-rmi4 - add support for F34 V7 bootloader

Hi NIck, On Sun, Dec 11, 2016 at 12:18:26AM +, Nick Dyer wrote: > +static void rmi_f34v7_parse_img_header_10_bl_container(struct f34_data *f34, > +const u8 *image) > +{ > + int i; > + int num_of_containers; > + unsigned int addr;

Re: [PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

Yes, It will not fixes any defect. But we are going to free allocate memory then why we need devm api. In this case Devm will first add this entry to list and immediately it will remove from list. -Arvind On Saturday 10 December 2016 02:49 PM, Robert Jarzmik wrote: Arvind Yadav

Re: [GIT PULL] readlink cleanup

On Sun, Dec 11, 2016 at 3:39 AM, Al Viro wrote: > On Sun, Dec 11, 2016 at 02:36:20AM +, Al Viro wrote: > >> I'm still not sure what does "vfs: convert ->readlink to same signature as >> ->get_link" buy us. If anything, the result appears to be more complex - >> you

Re: Misalignment, MIPS, and ip_hdr(skb)->version

Willy Tarreau writes: > Hi Jason, > > On Thu, Dec 08, 2016 at 11:20:04PM +0100, Jason A. Donenfeld wrote: >> Hi David, >> >> On Thu, Dec 8, 2016 at 1:37 AM, David Miller wrote: >> > You really have to land the IP header on a proper 4 byte boundary. >> > >> > I

drivers/auxdisplay/img-ascii-lcd.c:384: undefined reference to `devm_ioremap_resource'

Hi Paul, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 045169816b31b10faed984b01c390db1b32ee4c1 commit: 0cad855fbd083ee5fd0584a47c2aaa7dca936fd4 auxdisplay: img-ascii-lcd: driver for simple ASCII LCD displays

Re: [PATCH] kbuild/mkspec: avoid using brace expansion

On Tue, Oct 25, 2016 at 06:00:44PM +0900, Anton Tikhomirov wrote: > Brace expansion might not work properly if _buildshell RPM macro > points to a shell other than bash. Particularly, with _bulidshell > defined to /bin/dash it leads to broken build and source symlinks. > > Signed-off-by: Anton

collect2: error: ld returned 1 exit status

Hi Linus, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 045169816b31b10faed984b01c390db1b32ee4c1 commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 4 months ago config:

Re: [PATCH 0/7] Move dell-led to drivers/platform/x86

On Thursday 08 December 2016 15:26:37 Jacek Anaszewski wrote: > Hi Michał, > > Thanks for the patch set. > > On 12/08/2016 01:36 PM, Michał Kępień wrote: > > This patch series moves the dell-led driver from the LED subsystem > > to the x86 platform driver subsystem. I decided to also CC the > >

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On 12/10/16 at 05:28pm, Borislav Petkov wrote: > On Sat, Dec 10, 2016 at 09:41:56PM +0800, Baoquan He wrote: > > 1) Fedora 25 defaults to enable CONFIG_RANDOMIZE_BASE. And this worries > > maintainers of several Fedora component. People ever asked me how to > > judge whether it's a kaslr kernel. I

Re: [PATCH v4 0/3] Coccinelle: misc: Improve the script for more accurate results

On Wed, Nov 23, 2016 at 02:12:58PM +0530, Vaishali Thakkar wrote: > Few changes to improve the results given by the irqf_oneshot.cocci: > > - Change in the matching rules to eliminate false postives in the > patch mode > - Change in the context mode to eliminate false postives in the >

[PATCH 0/2] mm/memblock.c: fix potential bug and code refine

Here are two patch of mm/memblock.c. [1]. A trivial code refine in memblock_is_region_memory(), which removes an unnecessary check on base address. [2]. The original code forgets to check the return value of memblock_reserve(), which may lead to potential problem. The patch fix this. Wei Yang

[PATCH] firmware: simplify defining and handling FW_OPT_FALLBACK

From: Rafał Miłecki I found handling of FW_OPT_FALLBACK a bit complex. It was defined using another option and their values were dependent on kernel config. It was also non-trivial to follow the code. Some callers were using FW_OPT_FALLBACK which was confusing since the

Re: Misalignment, MIPS, and ip_hdr(skb)->version

Hi Jason, On Thu, Dec 08, 2016 at 11:20:04PM +0100, Jason A. Donenfeld wrote: > Hi David, > > On Thu, Dec 8, 2016 at 1:37 AM, David Miller wrote: > > You really have to land the IP header on a proper 4 byte boundary. > > > > I would suggest pushing 3 dummy garbage bytes of

Re: kvm: use-after-free in process_srcu

On Sun, Dec 11, 2016 at 9:40 AM, Vegard Nossum wrote: > On 11 December 2016 at 07:46, Dmitry Vyukov wrote: >> Hello, >> >> I am getting the following use-after-free reports while running >> syzkaller fuzzer. >> On commit

[PATCH] media: platform: xilinx: xilinx-tpg: constify v4l2_subdev_* structures

v4l2_subdev_{core/pad/video}_ops structures are stored in the fields of the v4l2_subdev_ops structure which are of type const. Also, v4l2_subdev_ops structure is passed to a function having its argument of type const. As these structures are never modified, so declare them as const. Done using

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On Sun, Dec 11, 2016 at 06:58:29PM +0800, Baoquan He wrote: > For arguing and defending myself, I couldn't be very objective. Yeah, it is mind-boggling the amount of bullshit you would come up with instead of simply saying, "no, I don't have a good reason and use case for my patch". It made me

Re: ILP32 for ARM64 - testing with lmbench

On Mon, Dec 05, 2016 at 02:13:12PM +, Catalin Marinas wrote: > On Mon, Dec 05, 2016 at 06:16:09PM +0800, Zhangjian (Bamvor) wrote: > > Do you have suggestion of next move of upstreaming ILP32? > > I mentioned the steps a few time before. I'm pasting them again here: > > 1. Complete the

[PATCH 1/2] mm/memblock.c: trivial code refine in memblock_is_region_memory()

The base address is already guaranteed to be in the region by memblock_search(). This patch removes the check on base, also a little refine in a macro. Signed-off-by: Wei Yang --- include/linux/memblock.h |5 ++--- mm/memblock.c|2 +- 2 files

[PATCH 2/2] mm/memblock.c: check return value of memblock_reserve() in memblock_virt_alloc_internal()

memblock_reserve() may fail in case there is not enough regions. This patch checks the return value. Signed-off-by: Wei Yang --- mm/memblock.c |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/mm/memblock.c b/mm/memblock.c index

[PATCH RFC 2/2] ARM: nommu: remap exception base address to RAM

Remap exception base address to start of RAM in Kernel in !MMU mode. Based on existing Kconfig help, Kernel was expecting it to be configured by external support. Also earlier it was not possible to copy the exception table to start of RAM due to Kconfig dependency, which has been fixed by a

Re: [PATCH 3/3] mm: make pagoff_t type 64-bit

/mm-move-argument-checkers-of-mmap_pgoff-to-separated-routine/20161211-211314 config: i386-randconfig-x003-201650 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings (new ones

[PATCH] drivers: media: i2c: mt9t001: constify v4l2_subdev_* structures

v4l2_subdev_{core/pad/video}_ops structures are stored in the fields of the v4l2_subdev_ops structure which are of type const. Also, v4l2_subdev_ops structure is passed to a function having its argument of type const. As these structures are never modified, so declare them as const. Done using

Re: [PATCH 2/2] mm, oom: do not enfore OOM killer for __GFP_NOFAIL automatically

Michal Hocko wrote: > On Thu 08-12-16 21:53:44, Tetsuo Handa wrote: > > If we could agree > > with calling __alloc_pages_nowmark() before out_of_memory() if __GFP_NOFAIL > > is given, we can avoid locking up while minimizing possibility of invoking > > the OOM killer... > > I do not understand. We

[PATCH 3/3] mm: make pagoff_t type 64-bit

Also fix related interfaces Signed-off-by: Yury Norov --- fs/btrfs/extent_io.c | 2 +- fs/ext2/dir.c | 4 ++-- include/linux/mm.h | 9 + include/linux/radix-tree.h | 8 include/linux/types.h | 2 +- lib/radix-tree.c

Re: [Question] New mmap64 syscall?

This is the draft of sys_mmap64() support in the kernel. For 64-bit kernels everything is simple. For 32-bit kernels we have a problem. pgoff_t is declared as unsigned long, and should be turned to unsigned long long. It affects the number of structures and interfaces. Last patch does the change.

[PATCH 2/3] sys_mmap64()

Signed-off-by: Yury Norov --- include/linux/syscalls.h | 3 +++ include/uapi/asm-generic/unistd.h | 4 +++- mm/mmap.c | 25 + 3 files changed, 31 insertions(+), 1 deletion(-) diff --git

[PATCH 1/3] mm: move argument checkers of mmap_pgoff() to separated routine

Signed-off-by: Yury Norov --- mm/mmap.c | 34 +- 1 file changed, 25 insertions(+), 9 deletions(-) diff --git a/mm/mmap.c b/mm/mmap.c index 1af87c1..fc1c943 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -1455,12 +1455,12 @@ unsigned long

[PATCH 1/2] ARM: nommu: allow enabling REMAP_VECTORS_TO_RAM

REMAP_VECTORS_TO_RAM depends on DRAM_BASE, but since DRAM_BASE is a hex, REMAP_VECTORS_TO_RAM could never get enabled. Also depending on DRAM_BASE is redundant as whenever REMAP_VECTORS_TO_RAM makes itself available to Kconfig, DRAM_BASE also is available as the Kconfig gets sourced on !MMU.

Re: [PATCH 3/3] mm: make pagoff_t type 64-bit

/mm-move-argument-checkers-of-mmap_pgoff-to-separated-routine/20161211-211314 config: i386-tinyconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings (new ones prefixed

Re: [GIT PULL] overlayfs update for 4.10

On Sun, Dec 11, 2016 at 3:12 AM, Al Viro wrote: > On Sat, Dec 10, 2016 at 09:49:26PM +0100, Miklos Szeredi wrote: >> Hi Al, >> >> I usually send overlayfs pulls directly to Linus, but it it suits you, please >> feel free to pull from: >> >>

kvm: assorted bugs after OOMs

Hello, When I run the following program on a VM with 2GB of memory: https://gist.githubusercontent.com/dvyukov/8ccb55ae7da35ac780d55efc07a058a6/raw/cd5cadc1226a132b8d2731eaf8b03ac4d52e2763/gistfile1.txt it starts causing OOM kills as each process allocates ~1GB, and eventually if kills the VM.

Re: kvm: use-after-free in process_srcu

On 11 December 2016 at 07:46, Dmitry Vyukov wrote: > Hello, > > I am getting the following use-after-free reports while running > syzkaller fuzzer. > On commit 318c8932ddec5c1c26a4af0f3c053784841c598e (Dec 7). > Unfortunately it is not reproducible, but all reports look sane

Re: [PATCH 2/2] kcov: make kcov work properly with KASLR enabled

On Sun, Dec 11, 2016 at 1:50 AM, Alexander Popov wrote: > Subtract KASLR offset from the kernel addresses reported by kcov. > Tested on x86_64 and AArch64 (Hikey LeMaker). > > Signed-off-by: Alexander Popov > --- > kernel/kcov.c | 8 +++- > 1 file

Re: [PATCH 3/7] ALSA: hda - use dell_micmute_led_set() instead of dell_app_wmi_led_set()

On Thursday 08 December 2016 13:36:14 Michał Kępień wrote: > --- a/sound/pci/hda/dell_wmi_helper.c > +++ b/sound/pci/hda/dell_wmi_helper.c > @@ -6,7 +6,7 @@ > #include > > static int dell_led_value; > -static int (*dell_led_set_func)(int, int); > +static int (*dell_led_set_func)(int);

Re: [PATCH 4/7] dell-led: remove dell_app_wmi_led_set()

On Thursday 08 December 2016 13:36:15 Michał Kępień wrote: > All calls to dell_app_wmi_led_set() have been replaced with direct > calls to dell_micmute_led_set(), so the former can be safely removed > along with its related enum. > > Signed-off-by: Michał Kępień I would

Re: [PATCH] kbuild: cmd_export_list: tighten the sed script

On Wed, Nov 16, 2016 at 07:28:39PM -0500, Nicolas Pitre wrote: > > When LTO is used, some ___ksymtab_string sections are seen by this sed > script, creating lines containing a single ) such as: > > EXPORT(foo) > ) > ) > EXPORT(bar) > > Let's make it so the + character is also required for any

Re: [PATCH] staging/android: remove Sync Framework tasks from TODO

Hi Gustavo, On 6 December 2016 at 23:55, Gustavo Padovan wrote: > From: Gustavo Padovan > > The destaging work is now fully complete. > Thanks for the patch, and your awesome work here :). > Cc: Arve Hjønnevåg > Cc: Riley

Re: net: deadlock on genl_mutex

On Fri, Dec 9, 2016 at 6:08 AM, Cong Wang wrote: > On Thu, Dec 8, 2016 at 4:32 PM, Cong Wang wrote: >> On Thu, Dec 8, 2016 at 9:16 AM, Dmitry Vyukov wrote: >>> Chain exists of: >>> Possible unsafe locking scenario: >>> >>>

Re: [PATCH] scripts/kallsyms: remove last remnants of --page-offset option

On Fri, Nov 25, 2016 at 08:43:55AM +, Ard Biesheuvel wrote: > On 28 October 2016 at 18:09, Ard Biesheuvel wrote: > > The implementation of the --page-offset kallsyms command line option has > > been removed, so remove it from the usage string as well. > > > >

Documenting the ioctl interfaces to discover relationships between namespaces

[was: [PATCH 0/4 v3] Add an interface to discover relationships between namespaces] Hello Andrei See below for my attempt to document the following. On 6 September 2016 at 09:47, Andrei Vagin wrote: > From: Andrey Vagin > > Each namespace has an owning

[PATCH 0/2] ARM: v7-A !MMU fixes for fun ()

Hi, ARM core fixes required to bring up !MMU Kernel on v7 Cortex-A. This was done on top of Vladimir Murzin's !MMU multiplatform series[1]. Platform used was Cortex-A9, AM437x IDK. Kernel reached the stage of invoking user space init & panicked, though it could not reach till prompt for want

Re: [PATCH 2/2] mm, oom: do not enfore OOM killer for __GFP_NOFAIL automatically

Tetsuo Handa wrote: > Michal Hocko wrote: > > On Thu 08-12-16 21:53:44, Tetsuo Handa wrote: > > > If we could agree > > > with calling __alloc_pages_nowmark() before out_of_memory() if > > > __GFP_NOFAIL > > > is given, we can avoid locking up while minimizing possibility of invoking > > > the

RE: [PATCH V4 00/11] megaraid_sas: Updates for scsi-next

Hi Chris, I will be rebasing to include " pci_alloc_irq_vectors conversion from Hannes" in the next version of the patch Thanks sasi -Original Message- From: Christoph Hellwig [mailto:h...@infradead.org] Sent: Wednesday, December 07, 2016 2:31 AM To: Sasikumar Chandrasekaran Cc:

linux-next: manual merge of the staging tree with the vfs tree

Hi Greg, Today's linux-next merge of the staging tree got a conflict in: drivers/staging/lustre/lustre/llite/statahead.c between commit: 7126bc2e8d60 ("lustre: switch to use of ->d_init()") from the vfs tree and commit: 3c8fb1b105cd ("staging: lustre: statahead: set sai_index_wait with

Re: [PATCH v2] siphash: add cryptographically secure hashtable function

Hey Linus, On Mon, Dec 12, 2016 at 5:01 AM, Linus Torvalds wrote: > The above is extremely inefficient. Considering that most kernel data > would be expected to be smallish, that matters (ie the usual benchmark > would not be about hashing megabytes of data, but

Re: [PATCH 2/2] kcov: make kcov work properly with KASLR enabled

On Sun, Dec 11, 2016 at 10:37 PM, Alexander Popov wrote: > On 11.12.2016 12:32, Dmitry Vyukov wrote: >> On Sun, Dec 11, 2016 at 1:50 AM, Alexander Popov >> wrote: >>> Subtract KASLR offset from the kernel addresses reported by kcov. >>> Tested on

[PATCH] serial: mxs-auart: support CMSPAR termios cflag

If CMSPAR is set in the c_cflag of termios, "stick" parity is enabled. Tested on an i.MX28 system Signed-off-by: Wolfgang Ocker --- v2: require PARENB to be also set in termios' c_cflag for CMSPAR --- drivers/tty/serial/mxs-auart.c | 3 +++ 1 file changed, 3 insertions(+)

Re: [media] bt8xx: One function call less in bttv_input_init() after error detection

>> I would prefer a safer coding style for the corresponding >> exception handling. > > Can you please point out what is wrong in the current code Is it useful to reconsider the software situation that another memory allocation is attempted when it could be determined that a previous one failed

linux-next: manual merge of the devicetree tree with the drm-panel tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: Documentation/devicetree/bindings/vendor-prefixes.txt between commit: 05ec0e4501f7 ("drm/panel: simple: Add NVD9128 as a simple panel") from the drm-panel tree and commit: 1a85ff590440 ("devicetree: add vendor

[lkp-developer] [scsi] 8eea81e090: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 8eea81e0903fcde1c28044ea66acc4c5c578f553 ("scsi: enable IO scheduling for scsi-mq") https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git blk-mq-legacy-sched.1 in testcase: boot on test machine: qemu-system-i386 -enable-kvm -cpu

[lkp-developer] [kernel/fork] cc639db4ac: BUG:using_smp_processor_id()in_preemptible

FYI, we noticed the following commit: commit: cc639db4acfeb459f3dcec080c6cfe11e36266e0 ("kernel/fork: use vfree_atomic() to free thread stack") https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master in testcase: iperf with following parameters: runtime: 300s

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On 12/11/16 at 01:06pm, Borislav Petkov wrote: > On Sun, Dec 11, 2016 at 06:58:29PM +0800, Baoquan He wrote: > > For arguing and defending myself, I couldn't be very objective. > > Yeah, it is mind-boggling the amount of bullshit you would come up with > instead of simply saying, "no, I don't

Re: [PATCH] Fix multiple definition error under lto

On Sat, 2016-11-26 at 17:25 -0500, Peter Foley wrote: > drivers/thermal/built-in.o: In function `type_show.lto_priv.33': > (.text+0x3d80): multiple definition of `type_show.lto_priv.33' > drivers/base/built-in.o:(.text+0x2a40): first defined here > can you illustrate how to reproduce this

Re: [PATCH v8 3/3] iio: adc: add support for Allwinner SoCs ADC

Hi Maxime, On 10/12/2016 10:44, Maxime Ripard wrote: > Hi, > > Just some minor comments. > > On Fri, Dec 09, 2016 at 11:22:36AM +0100, Quentin Schulz wrote: >> +/* >> + * Since the thermal sensor needs the IP to be in touchscreen mode and >> + * there is no register to know if the

Re: [PATCH v2 1/1] lockd: Change nsm_use_hostnames from bool to u32

Hi Xinhui Thanks, it really works. Will send out V3 soon afterwards B.R. Jia On 12/12/16 1:43 AM, Pan Xinhui wrote: hi, jia nice catch! However I think we should fix it totally. This is because do_proc_dointvec_conv() try to get a int value from a bool *. something like below might

Re: [PATCH] arm64: mm: Fix NOMAP page initialization

hi Robert, On 2016/12/10 2:10, Robert Richter wrote: > On ThunderX systems with certain memory configurations we see the > following BUG_ON(): > > kernel BUG at mm/page_alloc.c:1848! > > This happens for some configs with 64k page size enabled. The BUG_ON() > checks if start and end page of a

[PATCH v2] siphash: add cryptographically secure hashtable function

SipHash is a 64-bit keyed hash function that is actually a cryptographically secure PRF, like HMAC. Except SipHash is super fast, and is meant to be used as a hashtable keyed lookup function. SipHash isn't just some new trendy hash function. It's been around for a while, and there really isn't

[tip:sched/core] sched/core: Fix find_idlest_group() for fork

Commit-ID: f519a3f1c6b7a990e5aed37a8f853c6ecfdee945 Gitweb: http://git.kernel.org/tip/f519a3f1c6b7a990e5aed37a8f853c6ecfdee945 Author: Vincent Guittot AuthorDate: Thu, 8 Dec 2016 17:56:53 +0100 Committer: Ingo Molnar CommitDate: Sun, 11 Dec

[tip:perf/core] perf/x86: Fix exclusion of BTS and LBR for Goldmont

Commit-ID: b0c1ef52959582144bbea9a2b37db7f4c9e399f7 Gitweb: http://git.kernel.org/tip/b0c1ef52959582144bbea9a2b37db7f4c9e399f7 Author: Andi Kleen AuthorDate: Thu, 8 Dec 2016 16:14:17 -0800 Committer: Ingo Molnar CommitDate: Sun, 11 Dec 2016

Re: [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support

On 2016/12/9 23:07, Marty Plummer wrote: > On 12/04/2016 08:03 PM, Jiancheng Xue wrote: >> Hi Arnd, >> >> On 2016/10/17 21:48, Arnd Bergmann wrote: >>> On Monday, October 17, 2016 8:07:03 PM CEST Pan Wen wrote: Add support for some HiSilicon SoCs which depend on ARCH_MULTI_V5.

[GIT PULL] RCU changes for v4.10

Linus, Please pull the latest core-rcu-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus # HEAD: af91a81131aee3e233a977632a23b839857a327b Merge branch 'for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into

[PATCH] drivers: media: i2c: constify v4l2_subdev_* structures

v4l2_subdev_{core/pad/video}_ops structures are stored in the fields of the v4l2_subdev_ops structure which are of type const. Also, v4l2_subdev_ops structure is passed to a function having its argument of type const. As these structures are never modified, so declare them as const. Done using

Re: [PATCH v6 2/8] MFD: add STM32 Timers driver

On Fri, 09 Dec 2016, Benjamin Gaignard wrote: > This hardware block could at used at same time for PWM generation > and IIO timers. > PWM and IIO timer configuration are mixed in the same registers > so we need a multi fonction driver to be able to share those registers. > > version 6: > -

Re: [PATCH v6 0/8] Add PWM and IIO timer drivers for STM32

On Fri, 09 Dec 2016, Benjamin Gaignard wrote: > version 6: > - rename stm32-gptimer in stm32-timers. > - change "st,stm32-gptimer" compatible to "st,stm32-timers". > - modify "st,breakinput" parameter in pwm part. > - split DT patch in 2 > > version 5: > - fix comments done on version 4 > -

Re: [PATCH v6 1/8] MFD: add bindings for STM32 Timers driver

On Fri, 09 Dec 2016, Benjamin Gaignard wrote: > Add bindings information for STM32 Timers > > version 6: > - rename stm32-gtimer to stm32-timers > - change compatible > - add description about the IPs > > version 2: > - rename stm32-mfd-timer to stm32-gptimer > - only keep one compatible string

Re: [V2] mtd: devices: docg3:- Handle return value of devm_ioremap.

On 12/12/2016 04:00 AM, Arvind Yadav wrote: > Here, If devm_ioremap will fail. It will return NULL. > Kernel can run into a NULL-pointer dereference. > > Signed-off-by: Arvind Yadav > --- > drivers/mtd/devices/docg3.c | 7 ++- > 1 file changed, 6 insertions(+), 1

Re: Documenting the ioctl interfaces to discover relationships between namespaces

[Fixing Serge's address in my original CC] On 12/11/2016 11:30 PM, Eric W. Biederman wrote: > "Michael Kerrisk (man-pages)" writes: > >> [was: [PATCH 0/4 v3] Add an interface to discover relationships >> between namespaces] > > One small comment below. > >> >>

[PATCH] Input: elantech - force a module ignore ABS mode

One Elan sample which sample version is 0x74 and hw_version is 0x04 has a bug in abs mode, so let it run in default mode Signed-off-by: KT Liao --- drivers/input/mouse/elantech.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/input/mouse/elantech.c

[PATCH RFC] clk: wm831x: fix usleep_range with bad range

The delay here is not in atomic context and does not seem critical with respect to precision, but usleep_range(min,max) with min==max results in giving the timer subsystem no room to optimize uncritical delays. Fix this by setting the range to 2000,3000 us. Fixes: commit f05259a6ffa4 ("clk:

Re: [PATCH v3] sparc64: Multi-page size support

From: David Miller Date: Sun, 11 Dec 2016 21:06:30 -0500 (EST) > Applied. Actually, I'm reverting. Just doing a simply "make -s -j128" kernel build on a T4-2 I'm getting kernel log warnings: [2024810.925975] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

linux-next: manual merge of the tip tree with the net-next tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/net/ethernet/ti/Kconfig between commit: 6246168b4a38 ("net: ethernet: ti: netcp: add support of cpts") from the net-next tree and commit: d1cbfd771ce8 ("ptp_clock: Allow for it to be optional") from the tip

[PATCH RFC 0/1] mm, page_alloc: fix incorrect zone_statistics data

In commit b9f00e147f27 ("mm, page_alloc: reduce branches in zone_statistics"), it reconstructed the code to reduce the branch miss rate. Compared with the original logic, it assumed if !(flag & __GFP_OTHER_NODE) z->node would not be equal to preferred_zone->node. That seems to be incorrect.

[PATCH] ACPI: small formatting fixes

A quick cleanup that passes scripts/checkpatch.pl -f . Signed-off-by: Nick Desaulniers --- arch/x86/kernel/acpi/cstate.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/x86/kernel/acpi/cstate.c

Re: linux-next: build failure after merge of the spi tree

Hi Mark, On Fri, 9 Dec 2016 13:32:56 +1100 Stephen Rothwell wrote: > > After merging the spi tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/spi/spi-orion.c: In function 'orion_spi_baudrate_set': > drivers/spi/spi-orion.c:192:8:

Re: [PATCH v2] siphash: add cryptographically secure hashtable function

On Sun, Dec 11, 2016 at 7:48 PM, Jason A. Donenfeld wrote: > + switch (left) { > + case 7: b |= ((u64)data[6]) << 48; > + case 6: b |= ((u64)data[5]) << 40; > + case 5: b |= ((u64)data[4]) << 32; > + case 4: b |=

Re: usb:xhci: support disable usb2 LPM Remote Wakeup

On Sat, Dec 10, 2016 at 4:36 AM, Rob Herring wrote: > On Sun, Dec 04, 2016 at 07:42:01PM +0700, Thang Q. Nguyen wrote: >> From: Thang Nguyen >> >> As per USB 2.0 link power management addendum ECN, table 1-2, page 4, >> device or host initiated via resume

Re: [PATCH] trace: extend trace_clock to support arch_arm clock counter

On 12/06/2016 05:43 PM, Will Deacon wrote: On Sun, Dec 04, 2016 at 02:06:23PM +0530, Srinivas Ramana wrote: On 12/02/2016 04:38 PM, Will Deacon wrote: On Fri, Dec 02, 2016 at 01:44:55PM +0530, Srinivas Ramana wrote: Extend the trace_clock to support the arch timer cycle counter so that we can

Re: Tearing down DMA transfer setup after DMA client has finished

On Fri, Dec 09, 2016 at 07:23:17PM +0100, Mason wrote: > [ Dropping Mans to preserve his peace-of-mind ] > > On 09/12/2016 18:56, Vinod Koul wrote: > > On Fri, Dec 09, 2016 at 06:34:15PM +0100, Mason wrote: > >> On 09/12/2016 18:17, Vinod Koul wrote: > >> > >>> On Fri, Dec 09, 2016 at 11:25:57AM

Re: [PATCH v2] siphash: add cryptographically secure hashtable function

On Mon, Dec 12, 2016 at 04:48:17AM +0100, Jason A. Donenfeld wrote: > > diff --git a/lib/Makefile b/lib/Makefile > index 50144a3aeebd..71d398b04a74 100644 > --- a/lib/Makefile > +++ b/lib/Makefile > @@ -22,7 +22,8 @@ lib-y := ctype.o string.o vsprintf.o cmdline.o \ >sha1.o chacha20.o md5.o

linux-next: manual merge of the akpm tree with the vfs tree

Hi all, Al let me know that he had put a newer version of the autofs patches into his vfs tree, so I have dropped the following patches from the akpm tree today: vfs: change d_manage() to take a struct path vfs: add path_is_mountpoint() helper vfs: fix boolreturn.cocci warnings vfs: add

RE: [PATCH v6 2/2] crypto: add virtio-crypto driver

Hi, Michael & Herbert Because the virtio-crypto device emulation had been in QEMU 2.8, would you please merge the virtio-crypto driver for 4.10 if no other comments? If so, Miachel pls ack and/or review the patch, then Herbert will take it (I asked him last week). Thank you! Ps: Note on 4.10

Re: [media] bt8xx: One function call less in bttv_input_init() after error detection

On 12/12/16 00:33, SF Markus Elfring wrote: >>> I would prefer a safer coding style for the corresponding >>> exception handling. >> >> Can you please point out what is wrong in the current code > > Is it useful to reconsider the software situation that another memory > allocation is attempted

[GIT PULL] SMP bootup printout changes for v4.10

Linus, Please pull the latest core-smp-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-smp-for-linus # HEAD: 5dce2509506d16efd321939895ff7ffe1dc2 kernel/smp: Tell the user we're bringing up secondary CPUs Three changes to unify/standardize

Re: [PATCH v8 2/4] vcodec: mediatek: Add Mediatek JPEG Decoder Driver

Hi Rick, On Wed, Nov 30, 2016 at 11:08 AM, Rick Chang wrote: > Add v4l2 driver for Mediatek JPEG Decoder > > Signed-off-by: Rick Chang > Signed-off-by: Minghsiu Tsai > +static bool

[PATCH RFC 1/1] mm, page_alloc: fix incorrect zone_statistics data

In commit b9f00e147f27 ("mm, page_alloc: reduce branches in zone_statistics"), it reconstructed codes to reduce the branch miss rate. Compared with the original logic, it assumed if !(flag & __GFP_OTHER_NODE) z->node would not be equal to preferred_zone->node. That seems to be incorrect. Fixes:

[tip:sched/core] sched/core: Use load_avg for selecting idlest group

Commit-ID: 6b94780e45c17b83e3e75f8aaca5a328db583c74 Gitweb: http://git.kernel.org/tip/6b94780e45c17b83e3e75f8aaca5a328db583c74 Author: Vincent Guittot AuthorDate: Thu, 8 Dec 2016 17:56:54 +0100 Committer: Ingo Molnar CommitDate: Sun, 11 Dec

[tip:locking/core] x86/paravirt: Fix bool return type for PVOP_CALL()

Commit-ID: 11f254dbb3a2e3f0d8552d0dd37f4faa432b6b16 Gitweb: http://git.kernel.org/tip/11f254dbb3a2e3f0d8552d0dd37f4faa432b6b16 Author: Peter Zijlstra AuthorDate: Thu, 8 Dec 2016 16:42:15 +0100 Committer: Ingo Molnar CommitDate: Sun, 11 Dec 2016

[tip:locking/core] x86/paravirt: Fix native_patch()

Commit-ID: 45dbea5f55c05980cbb4c30047c71a820cd3f282 Gitweb: http://git.kernel.org/tip/45dbea5f55c05980cbb4c30047c71a820cd3f282 Author: Peter Zijlstra AuthorDate: Thu, 8 Dec 2016 16:42:14 +0100 Committer: Ingo Molnar CommitDate: Sun, 11 Dec 2016

Re: [PATCH v6 0/3] spi-nor: Add support for Intel SPI serial flash controller

On Fri, 09 Dec 2016, Marek Vasut wrote: > On 12/09/2016 01:25 PM, Mika Westerberg wrote: > > On Fri, Dec 09, 2016 at 08:57:53AM +, Lee Jones wrote: > >> On Wed, 07 Dec 2016, Marek Vasut wrote: > >> > >>> On 12/07/2016 09:53 AM, Mika Westerberg wrote: > On Tue, Dec 06, 2016 at 09:45:25AM

Re: [PATCH] ocfs2: fix crash caused by stale lvb with fsdlm plugin

Hi Eric, Looks good for me. Just one suggestion, please monitor if the LVB sharing mechanism in the cluster still works well in the normal scenario, to avoid any performance decrease regression problem. Reviewed-by: Gang He Thanks Gang >>> > The crash happens rather often

Re: [V1] mtd: devices: docg3:- Handle return value of devm_ioremap.

Yes, We are returning -ENOMEM, ret is initialized to -ENOMEM. As per your concern, I have added dev_err failure message. Thanks -Arvind On Monday 12 December 2016 12:45 AM, Marek Vasut wrote: On 12/11/2016 07:01 PM, Arvind Yadav wrote: Here, If devm_ioremap will fail. It will return NULL.

[V2] mtd: devices: docg3:- Handle return value of devm_ioremap.

Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer dereference. Signed-off-by: Arvind Yadav --- drivers/mtd/devices/docg3.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/devices/docg3.c

Re: [Ocfs2-devel] [PATCH] ocfs2: fix crash caused by stale lvb with fsdlm plugin

Hi Gang, On 12/12/2016 10:56 AM, Gang He wrote: Hi Eric, Looks good for me. Just one suggestion, please monitor if the LVB sharing mechanism in the cluster still works well in the normal scenario, to avoid any performance decrease regression problem. Thanks for your review. I have done the

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Sat, 10 Dec 2016 13:41:03 +0100 Greg Kroah-Hartman wrote: > On Fri, Dec 09, 2016 at 11:46:54PM +0100, Dodji Seketeli wrote: > > Hello, > > > > Nicholas Piggin a écrit: > > > > [...] > > > > > That said, a dwarf based checker tool should be

Re: [PATCH v7 1/2] usb: xhci: plat: Enable runtime PM

Hi Robert, On 2 December 2016 at 05:46, Robert Foss wrote: > Enable runtime PM for the xhci-plat device so that the parent device > may implement runtime PM. > > Signed-off-by: Robert Foss > > Tested-by: Robert Foss

linux-next: manual merge of the akpm tree with Linus' tree

Hi Andrew, Today's linux-next merge of the akpm tree got a conflict in: lib/radix-tree.c between commit: 2b41226b39b6 ("Revert "radix tree test suite: fix compilation"") from Linus' tree and patch: "reimplement IDR and IDA using the radix tree" from the akpm tree. I fixed it up (I

linux-next: Tree for Dec 12

Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. Changes since 20161209: The vfs tree gained conflicts against the overlayfs and xfs trees. The vfs-miklos tree gained a cofnlict against the vfs tree. The hid tree

Re: [PATCH RFC 2/2] ARM: nommu: remap exception base address to RAM

Hi, On Sun, Dec 11, 2016 at 06:42:55PM +0530, Afzal Mohammed wrote: > Kernel text start at an offset of at least 32K to account for page > tables in MMU case. Proper way to put it might have been "32K (to account for 16K initial page tables & the old atags)", unless i missed something. Regards

Re: [PATCH] iio: adc: max1027: allocate DMA-safe buffer

On 10/12/16 20:53, Marcus Folkesson wrote: > On Sat, Dec 10, 2016 at 05:36:34PM +, Jonathan Cameron wrote: >> On 09/12/16 10:24, Marcus Folkesson wrote: >>> The buffer needs to be DMA-safe when used with spi_read() >>> >>> Signed-off-by: Marcus Folkesson >> Please

Re: Misalignment, MIPS, and ip_hdr(skb)->version

On Sun, Dec 11, 2016 at 03:50:31PM +0100, Jason A. Donenfeld wrote: > 3. Add 3 bytes of padding, set to zero, to the encrypted section just > before the IP header, marked for future use. > Pros: satisfies IETF mantras, can use those extra bits in the future > for interesting protocol extensions

  1   2   3   4   >