[PATCH 3.16 139/192] l2tp: avoid use-after-free caused by l2tp_ip_backlog_recv

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Paul Hüber commit 51fb60eb162ab84c5edf2ae9c63cf0b878e5547e upstream. l2tp_ip_backlog_recv may not return -1 if the packet gets dropped. The return value is passed up to ip_local_deliver_finish

[PATCH 3.16 168/192] perf/x86: Fix undefined shift on 32-bit kernels

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 6d6f2833bfbf296101f9f085e10488aef2601ba5 upstream. Jim reported: UBSAN: Undefined behaviour in arch/x86/events/intel/core.c:3708:12 shift exponent 35 is

[PATCH 3.16 167/192] perf/x86: Honor the architectural performance monitoring version

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: "Palik, Imre" commit 2c33645d366d13b969d936b68b9f4875b1fdddea upstream. Architectural performance monitoring, version 1, doesn't support fixed counters. Currently, even if a hypervisor advert

[PATCH 3.16 190/192] sched: add macros to define bitops for task atomic flags

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Zefan Li commit e0e5070b20e01f0321f97db4e4e174f3f6b49e50 upstream. This will simplify code when we add new flags. v3: - Kees pointed out that no_new_privs should never be cleared, so we shoul

[PATCH 3.16 002/192] sched/topology: Refactor function build_overlap_sched_groups()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Lauro Ramos Venancio commit 8c0334697dc37eb3d6d7632304d3a3662248daac upstream. Create functions build_group_from_child_sched_domain() and init_overlap_sched_group(). No functional change. Sig

[PATCH 3.16 005/192] sched/topology: Fix overlapping sched_group_mask

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 73bb059f9b8a00c5e1bf2f7ca83138c05d05e600 upstream. The point of sched_group_mask is to select those CPUs from sched_group_cpus that can actually arrive at this balance do

[PATCH 3.16 154/192] net sched filters: fix notification of filter delete with proper handle

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Jamal Hadi Salim [ Upstream commit 9ee7837449b3d6f0fcf9132c6b5e5aaa58cc67d4 ] Daniel says: While trying out [1][2], I noticed that tc monitor doesn't show the correct handle on delete: $ tc

[PATCH 3.16 014/192] tools/lib/lockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain/: Depth

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 98dcea0cfd04e083ac74137ceb9a632604740e2d upstream. liblockdep has been broken since commit 75dd602a5198 ("lockdep: Fix lock_chain::base size"), as that adds a check that M

[PATCH 3.16 181/192] netvsc: fix incorrect receive checksum offloading

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit e52fed7177f74382f742c27de2cc5314790aebb6 upstream. The Hyper-V netvsc driver was looking at the incorrect status bits in the checksum info. It was setting the receive

[PATCH 3.16 173/192] s390/seccomp: fix error return for filtered system calls

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Willeke commit dc295880c6752076f8b94ba3885d0bfff09e3e82 upstream. The syscall_set_return_value function of s390 negates the error argument before storing the value to the return register g

[PATCH 3.16 164/192] serial: samsung: Reorder the sequence of clock control when call s3c24xx_serial_set_termios()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Chanwoo Choi commit b8995f527aac143e83d3900ff39357651ea4e0f6 upstream. This patch fixes the broken serial log when changing the clock source of uart device. Before disabling the original clock

[PATCH 3.16 140/192] net/route: enforce hoplimit max value

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 626abd59e51d4d8c6367e03aae252a8aa759ac78 ] Currently, when creating or updating a route, no check is performed in both ipv4 and ipv6 code to the hoplimit value.

[PATCH 3.16 003/192] sched/fair, cpumask: Export for_each_cpu_wrap()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit c743f0a5c50f2fcbc628526279cfa24f3dabe182 upstream. More users for for_each_cpu_wrap() have appeared. Promote the construct to generic cpumask interface. The implementati

[PATCH 3.16 001/192] sched: Rename a misleading variable in build_overlap_sched_groups()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Zhihui Zhang commit aaecac4ad46b35ad308245384d019633fb9bc21b upstream. The child variable in build_overlap_sched_groups() actually refers to the peer or sibling domain of the given CPU. Rename

Re: [PATCH] perf tests attr: Make hw events optional

Em Mon, Oct 09, 2017 at 03:07:12PM +0200, Jiri Olsa escreveu: > Otherwise we fail on virtual machines with no support > for specific HW events. Thanks, applied. - Arnaldo

[PATCH 3.16 189/192] sched: fix confusing PFA_NO_NEW_PRIVS constant

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Zefan Li commit a2b86f772227bcaf962c8b134f8d187046ac5f0e upstream. Commit 1d4457f99928 ("sched: move no_new_privs into new atomic flags") defined PFA_NO_NEW_PRIVS as hexadecimal value, but it

[PATCH 3.16 162/192] ARM: OMAP3: Fix booting with thumb2 kernel

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit d8a50941c91a68da202aaa96a3dacd471ea9c693 upstream. We get a NULL pointer dereference on omap3 for thumb2 compiled kernels: Internal error: Oops: 8005 [#1] SMP THUMB2

[PATCH 3.16 161/192] Input: ads7846 - correct the value got from SPI

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Andrey Gelman commit 879f2fea8a5a748bcbf98d2cdce9139c045505d3 upstream. According to the touch controller spec, SPI return a 16 bit value, only 12 bits are valid, they are bit[14-3]. The valu

[PATCH 3.16 158/192] usb: musb: cppi41: correct the macro name EP_MODE_AUTOREG_*

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit 0149b07a9e28b0d8bd2fc1c238ffe7d530c2673f upstream. The macro EP_MODE_AUTOREG_* should be called EP_MODE_AUTOREQ_*, as they are used for register AUTOREQ. Signed-off-by: Bin Liu

[PATCH 3.16 174/192] mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Andrea Arcangeli commit ad33bb04b2a6cee6c1f99fabb15cddbf93ff0433 upstream. pmd_trans_unstable()/pmd_none_or_trans_huge_or_clear_bad() were introduced to locklessy (but atomically) detect when

[PATCH 3.16 159/192] usb: musb: cppi41: improve rx channel abort routine

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit cb83df77f3ec151d68a1b6be957207e6fc7b7f50 upstream. 1. set AUTOREQ to NONE at the beginning of teardown; 2. add delay for dma pipeline to drain; 3. Do not set USB_TDOWN bit for

Re: [PATCH 1/1] driver:garmin gps: use setup_timer

On Thu, Sep 21, 2017 at 04:54:24PM +0530, Allen Pais wrote: > Use setup_timer function instead of initializing timer with the > function and data fields. Why the odd indentation here? > Signed-off-by: Allen Pais > --- > drivers/usb/serial/garmin_gps.c | 5 ++--- > 1 file changed, 2 inse

[PATCH 3.16 004/192] sched/topology: Fix building of overlapping sched-groups

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 0372dd2736e02672ac6e189c31f7d8c02ad543cd upstream. When building the overlapping groups, we very obviously should start with the previous domain of _this_ @cpu, not CPU-0

[PATCH 3.16 165/192] misc: ad525x_dpot: Fix the enabling of the "otpXen" attributes

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Bogdan Nechita commit 1bb850a1b7f68b66361e658e334f9fdf8231f17d upstream. Currently writing the attributes with "echo" will result in comparing: "enabled\n" with "enabled\0" and attribute i

[PATCH 3.16 175/192] PCI: Support PCIe devices with short cfg_size

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: "Jason S. McMullan" commit c20aecf6963d1273d8f6d61c042b4845441ca592 upstream. If a device quirk modifies the pci_dev->cfg_size to be less than PCI_CFG_SPACE_EXP_SIZE (4096), but greater than P

[PATCH 3.16 177/192] PCI: Limit config space size for Netronome NFP6000 family

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: "Jason S. McMullan" commit 9f33a2ae59f24452c1076749deb615bccd435ca9 upstream. The NFP6000 has an erratum where reading/writing to PCI config space addresses above 0x600 can cause the NFP to ge

[PATCH 3.16 013/192] Fix serial console on SNI RM400 machines

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Thomas Bogendoerfer commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d upstream. sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK is disabled. Correct usage of clk API

[PATCH 3.16 176/192] PCI: Add Netronome vendor and device IDs

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: "Jason S. McMullan" commit a755e169031dac9ebaed03302c4921687c271d62 upstream. Device IDs for the Netronome NFP3200, NFP3240, NFP6000, and NFP6000 SR-IOV devices. Signed-off-by: Jason S. McMul

[PATCH 3.16 171/192] arm64: Rework valid_user_regs

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Rutland commit dbd4d7ca563fd0a8949718d35ce197e5642d5d9d upstream. We validate pstate using PSR_MODE32_BIT, which is part of the user-provided pstate (and cannot be trusted). Also, we conf

[PATCH 3.16 179/192] PCI: Limit config space size for Netronome NFP4000

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Simon Horman commit c2e771b02792d222cbcd9617fe71482a64f52647 upstream. Like the NFP6000, the NFP4000 as an erratum where reading/writing to PCI config space addresses above 0x600 can cause the

[PATCH 3.16 182/192] fs/cifs: make share unaccessible at root level mountable

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Aurelien Aptel commit a6b5058fafdf508904bbf16c29b24042cef3c496 upstream. if, when mounting //HOST/share/sub/dir/foo we can query /sub/dir/foo but not any of the path components above: - store

[PATCH 3.16 178/192] PCI: Add Netronome NFP4000 PF device ID

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Simon Horman commit 69874ec233871a62e1bc8c89e643993af93a8630 upstream. Add the device ID for the PF of the NFP4000. The device ID for the VF, 0x6003, is already present as PCI_DEVICE_ID_NETRO

Re: [PATCH 4.9 086/104] arm64: kasan: avoid bad virt_to_pfn()

On Mon, Oct 09, 2017 at 01:42:26PM +0200, Greg Kroah-Hartman wrote: >On Mon, Oct 09, 2017 at 11:06:53AM +0100, Will Deacon wrote: >> On Mon, Oct 09, 2017 at 10:14:50AM +0100, Mark Brown wrote: >> > On Sat, Oct 07, 2017 at 03:10:06AM +, Levin, Alexander (Sasha Levin) >> > wrote: >> > >> > > We

[PATCH 3.16 180/192] ALSA: oxygen: Fix logical-not-parentheses warning

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Tomer Barletz commit 8ec7cfce3762299ae289c384e281b2f4010ae231 upstream. This fixes the following warning, that is seen with gcc 5.1: warning: logical not is only applied to the left hand side

[PATCH 3.16 183/192] Fix memory leaks in cifs_do_mount()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit 4214ebf4654798309364d0c678b799e402f38288 upstream. Fix memory leaks introduced by the patch fs/cifs: make share unaccessible at root level mountable Also move allocation

[PATCH 3.16 187/192] Fix match_prepath()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit cd8c42968ee651b69e00f8661caff32b0086e82d upstream. Incorrect return value for shares not using the prefix path means that we will never match superblocks for these shares.

[PATCH 3.16 184/192] Compare prepaths when comparing superblocks

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit c1d8b24d18192764fe82067ec6aa8d4c3bf094e0 upstream. The patch fs/cifs: make share unaccessible at root level mountable makes use of prepaths when any component of the under

[PATCH 3.16 008/192] pinctrl: imx: fix debug message for SHARE_MUX_CONF_REG case

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Dong Aisheng commit 66b54e3a5a64925d9819eae86b8f36e90e60037f upstream. The original implemented debug message does not work for SHARE_MUX_CONF_REG case. This patch fixes it. Fixes: bf5a530971

[PATCH 3.16 012/192] arm64: Preventing READ_IMPLIES_EXEC propagation

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Dong Bo commit 48f99c8ec0b25756d0283ab058826ae07d14fad7 upstream. Like arch/arm/, we inherit the READ_IMPLIES_EXEC personality flag across fork(). This is undesirable for a number of reasons:

[PATCH 3.16 185/192] Move check for prefix path to within cifs_get_root()

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit 348c1bfa84dfc47da1f1234b7f2bf09fa798edea upstream. Signed-off-by: Sachin Prabhu Tested-by: Aurelien Aptel Signed-off-by: Steve French Signed-off-by: Ben Hutchings ---

[PATCH 3.16 017/192] [media] mceusb: fix memory leaks in error path

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 2d5a6ce71c72d98d4f7948672842e3e8c265a8b7 upstream. Fix urb and transfer-buffer leaks in an urb-submission error path which may be hit when a device is disconnected. Fixes:

[PATCH 3.16 186/192] Fix regression which breaks DFS mounting

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit d171356ff11ab1825e456dfb979755e01b3c54a1 upstream. Patch a6b5058 results in -EREMOTE returned by is_path_accessible() in cifs_mount() to be ignored which breaks DFS mounti

[PATCH 3.16 000/192] 3.16.49-rc1 review

This is the start of the stable review cycle for the 3.16.49 release. There are 192 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Oct 11 20:00:00 UTC 2017. Anything rece

[PATCH 3.16 188/192] sched: move no_new_privs into new atomic flags

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 1d4457f99928a968767f6405b4a1f50845aa15fd upstream. Since seccomp transitions between threads requires updates to the no_new_privs flag to be atomic, the flag must be part of a

[PATCH 3.16 011/192] wlcore: fix 64K page support

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4a4274bf2dbbd1c7a45be0c89a1687c9d2eef4a0 upstream. In the stable linux-3.16 branch, I ran into a warning in the wlcore driver: drivers/net/wireless/ti/wlcore/spi.c: In fu

[PATCH 3.16 015/192] Documentation: DMA API: fix a typo in a function name

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit 6a08d83e4324fcb23994dfd481acedf49e37cc06 upstream. Correct the typo, the wrongly typed function does not exist. Fixes: 6c9c6d6301287e ("dma-debug: New interfaces to debug

[PATCH 3.16 192/192] dm: flush queued bios when process blocks to avoid deadlock

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit d67a5f4b5947aba4bfe9a80a2b86079c215ca755 upstream. Commit df2cb6daa4 ("block: Avoid deadlocks with bio allocation by stacking drivers") created a workqueue for every bio

[PATCH 3.16 009/192] f2fs: load inode's flag from disk

3.16.49-rc1 review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 93607124c5450148e592c3d18ac533b4e5f25b8b upstream. This patch fixes missing inode flag loaded from disk, reported by Tom. [tom@localhost ~]$ sudo mount /dev/loop0 /mnt/ [to

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

On Mon, Oct 09, 2017 at 03:41:51PM +0200, Jiri Olsa wrote: > On Wed, Oct 04, 2017 at 09:27:11AM -0700, Andi Kleen wrote: > > On Wed, Oct 04, 2017 at 12:30:52PM +0200, Jiri Olsa wrote: > > > On Tue, Oct 03, 2017 at 01:06:05PM -0300, Arnaldo Carvalho de Melo wrote: > > > > Em Tue, Sep 12, 2017 at 12:

Re: [PATCH v2 3/3] arm64: dts: uniphier: add efuse node for LD20

2017-10-06 14:03 GMT+09:00 Keiji Hayashibara : > Add efuse node for UniPhier LD20 SoC. > This efuse node is included in soc-glue. > > Signed-off-by: Keiji Hayashibara Applied to linux-uniphier. Thanks. -- Best Regards Masahiro Yamada

Re: [Drbd-dev] [PATCH] block/drbd: Fix a sleep-in-atomic bug in drbd_bcast_event

On Wed, Oct 04, 2017 at 09:33:18AM +0800, Jia-Ju Bai wrote: > The driver may sleep under a RCU lock, and the function call path is: > drbd_sync_handshake (acquire the RCU lock) > drbd_asb_recover_1p > drbd_khelper > drbd_bcast_event > genlmsg_new(GFP_NOIO) --> may sleep > > To

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

Em Mon, Oct 09, 2017 at 03:41:51PM +0200, Jiri Olsa escreveu: > On Wed, Oct 04, 2017 at 09:27:11AM -0700, Andi Kleen wrote: > > On Wed, Oct 04, 2017 at 12:30:52PM +0200, Jiri Olsa wrote: > > > right, it looks like we allow whole path (including / char) > > > for BPF file, which messes up with out p

Re: [PATCH 4.9 086/104] arm64: kasan: avoid bad virt_to_pfn()

On Mon, Oct 09, 2017 at 01:42:26PM +0200, Greg Kroah-Hartman wrote: > On Mon, Oct 09, 2017 at 11:06:53AM +0100, Will Deacon wrote: > > On the flip side, it means that the default response (silence) stops the > > patches getting into stable, which isn't ideal for Greg. Thoughts? > Yeah, default "d

Re: usb/sound/line6: trying to register non-static key in podhd_disconnect

On Mon, Oct 9, 2017 at 2:59 PM, Takashi Iwai wrote: > On Mon, 09 Oct 2017 14:39:44 +0200, > Andrey Konovalov wrote: >> >> On Mon, Oct 9, 2017 at 2:31 PM, Takashi Iwai wrote: >> > On Mon, 09 Oct 2017 12:58:59 +0200, >> > Andrey Konovalov wrote: >> >> >> >> On Tue, Oct 3, 2017 at 9:41 AM, Takashi I

[PATCH v3 0/7] Fix i.MX7D OCOTP write support

V3: - Fix compile bug caused by a rebase typo - kbuild test robot V2: - Added Reviewed-by and Acked-by as indicated by Philipp - octp_params -> ocotp_params Philipp Zabel - Added whitespace to aggregate initaliser - Philipp Zabel - Dropped (void*) cast to data - Philipp Zabel - Made use of of_devi

[PATCH v3 6/7] nvmem: imx-ocotp: Enable i.MX7D OTP write support

After applying patches for both banked access and write timings we can re-enable the OTP write interface on i.MX7D processors. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 2 -- 1 file changed, 2 deletions(-) diff -

[PATCH v3 5/7] nvmem: imx-ocotp: Add i.MX7D timing write clock setup support

This patch adds logic to correctly setup the write timing parameters when blowing an OTP fuse for the i.MX7S/D. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 63 ++- 1 file

[PATCH v3 7/7] nvmem: imx-ocotp: Update module description

This imx-ocotp driver encapsulates support for a subset of both i.MX6 and i.MX7 processors. Update the module description to reflect. Fixes: 711d45477931 ("nvmem: octop: Add i.MX7D support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v3 4/7] nvmem: imx-ocotp: Move i.MX6 write clock setup to dedicated function

The i.MX7S/D has a different set of timing requirements, as a pre-cursor to adding the i.MX7 timing parameters, move the i.MX6 stuff to a dedicated function. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue Reviewed-by: Philipp Zabel --- drivers/nvmem

[PATCH v3 2/7] nvmem: imx-ocotp: Pass parameters via a struct

It will be useful in later patches to know the register access mode and bit-shift to apply to a given input offset. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support") Signed-off-by: Bryan O'Donoghue --- drivers/nvmem/imx-ocotp.c | 32 ++-- 1 file changed, 22

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

Em Mon, Oct 09, 2017 at 07:07:29AM -0700, Andi Kleen escreveu: > On Mon, Oct 09, 2017 at 03:41:51PM +0200, Jiri Olsa wrote: > > On Wed, Oct 04, 2017 at 09:27:11AM -0700, Andi Kleen wrote: > > > On Wed, Oct 04, 2017 at 12:30:52PM +0200, Jiri Olsa wrote: > > > > On Tue, Oct 03, 2017 at 01:06:05PM -03

[PATCH v3 3/7] nvmem: imx-ocotp: Add support for banked OTP addressing

The i.MX7S/D takes the bank address in the CTRLn.ADDR field and the data value in one of the DATAx {0, 1, 2, 3} register fields. The current write routine is based on writing the CTRLn.ADDR field and writing a single DATA register only. Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support")

[PATCH v3 1/7] nvmem: imx-ocotp: Restrict OTP write to IMX6 processors

i.MX7S/D have a different scheme for addressing the OTP registers inside the OCOTP block. Currently it's possible to address the wrong OTP registers given the disparity between IMX6 and IMX7 OTP addressing. Since OTP programming is one-time destructive its important we restrict this interface ASAP

Re: [PATCH v7 5/6] lib/dlock-list: Enable faster lookup with hashing

On 10/09/2017 09:08 AM, Davidlohr Bueso wrote: > On Thu, 05 Oct 2017, Waiman Long wrote: > >> Insertion and deletion is relatively cheap and mostly contention >> free for dlock-list. Lookup, on the other hand, can be rather costly >> because all the lists in a dlock-list will have to be iterated. >

Re: [PATCHv2 1/1] [tools]: android/ion: userspace test utility for ion buffer sharing

On Fri, Oct 6, 2017 at 7:58 PM, Pintu Kumar wrote: >>> + >>> + heap_type = ion_info->heap_type; >>> + heap_size = ion_info->heap_size; >>> + flag_type = ion_info->flag_type; >>> + alloc_data.len = heap_size; >>> + alloc_data.heap_id_mask = heap_type; >> >> The heap type and hea

Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2

On Mon, Oct 09, 2017 at 08:26:05AM -0500, Josh Poimboeuf wrote: On Mon, Oct 09, 2017 at 08:55:04PM +0800, Fengguang Wu wrote: On Mon, Oct 09, 2017 at 08:21:13PM +0800, Fengguang Wu wrote: > On Mon, Oct 09, 2017 at 12:50:55PM +0200, Peter Zijlstra wrote: > > > Fengguang, if you're still listening

Re: [PATCH workqueue/for-4.14-fixes] workqueue: replace pool->manager_arb mutex with a flag

On Mon, Oct 09, 2017 at 01:21:04PM +, Tejun Heo wrote: > Josef reported a HARDIRQ-safe -> HARDIRQ-unsafe lock order detected by > lockdep: > > [ 1270.472259] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected > [ 1270.472783] 4.14.0-rc1-xfstests-12888-g76833e8 #110 Not tainted > [

Re: [PATCH] regulator: lp873x: Update the enable mask for LDOs and BUCKs

On Wed, Sep 27, 2017 at 05:55:40PM +0530, Keerthy wrote: > The reset value of the EN_PIN_CTRL bit fields of LDOs and BUCKs > need not be set correctly. Hence update the enable mask to include > the EN_PIN_CTRL bit. While enabling this should be set to 1 so > that all the regulators are tied to EN p

Re: [PATCH v2] Update MIPS email addresses

Thanks Paul. Acked-by: Dengcheng Zhu Dengcheng --- *From:* Paul Burton *Sent:* Sunday, October 08, 2017 5:24PM *To:* Linux-kernel , Trivial

Re: [PATCH] usb: musb: sunxi: Explicitly release USB PHY on exit

Hi, On Tue, Sep 26, 2017 at 09:39:23PM +1000, Jonathan Liu wrote: > This fixes a kernel oops when unloading the driver due to usb_put_phy > being called after usb_phy_generic_unregister when the device is > detached. Calling usb_phy_generic_unregister causes x->dev->driver to > be NULL in usb_put_

Re: [PATCH 1/2] ARM: cpuidle: refine failure handling in init flow

Hi Daniel, On Mon, Oct 09, 2017 at 02:04:40PM +0200, Daniel Lezcano wrote: > On 04/09/2017 08:52, Leo Yan wrote: > > After applied Stefan Wahren patch ("ARM: cpuidle: Avoid memleak if init > > fail") there have no memleak issue, but the code is not consistent to > > handle initialization failure b

Re: [PATCH] xfs: Fix bool initialization/comparison

On Sat, Oct 07, 2017 at 04:02:21PM +0200, Thomas Meyer wrote: > Bool initializations should use true and false. Bool tests don't need > comparisons. > > Signed-off-by: Thomas Meyer > --- Reviewed-by: Brian Foster > > diff -u -p a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c > --- a/fs/

[GIT PULL] at91: fixes for 4.14 #2

Arnd, Olof, A second batch of fixes for AT91, all about DT modifications. We discovered the Ethernet phy issue lately and the ADC fixes are patches that we forgot while converting sama5d2 ADC to use hardware triggers. The 2 ADC patches are needed so that the driver can probe corectly again: https:

Re: [PATCH] hexagon: get rid of #include

2017-10-03 10:26 GMT+09:00 Masahiro Yamada : > Hi Richard, > > 2017-09-28 8:24 GMT+09:00 Richard Kuo : >> On Thu, Sep 21, 2017 at 12:17:50AM +0900, Masahiro Yamada wrote: >>> is created (or updated) when Kbuild descends >>> into the init/ directory. In parallel building from a pristine >>> source

[PATCH v2 0/1] block,bfq: Disable writeback throttling

This is the v2 of the previous patch[1]. There are no functional changes. The only difference from v1 to v2 is the fix of the wbt_disable_default's comment, thanks to Lee Tibbert who pointed me out that mistake. [1]:https://www.mail-archive.com/linux-block@vger.kernel.org/msg12806.html Luca Micci

[PATCH V2 1/1] block,bfq: Disable writeback throttling

Similarly to CFQ, BFQ has its write-throttling heuristics, and it is better not to combine them with further write-throttling heuristics of a different nature. So this commit disables write-back throttling for a device if BFQ is used as I/O scheduler for that device. Signed-off-by: Luca Miccio Si

Re: [PATCH v2 0/1] block,bfq: Disable writeback throttling

On 10/09/2017 08:27 AM, Luca Miccio wrote: > This is the v2 of the previous patch[1]. There are > no functional changes. The only difference from v1 to > v2 is the fix of the wbt_disable_default's comment, > thanks to Lee Tibbert who pointed me out that mistake. Applied, thanks. -- Jens Axboe

Re: [PATCH] skd: Use kmem_cache_free

On 10/08/2017 03:30 PM, Himanshu Jha wrote: > Use kmem_cache_free instead of kfree for freeing the memory previously > allocated with kmem_cache_zalloc/kmem_cache_alloc/kmem_cache_node. Good catch, I wonder how long that's been there... Applied for 4.14. -- Jens Axboe

Re: [PATCH] scsi: libiscsi: fix shifting of DID_REQUEUE host byte

On Mon, Oct 09, 2017 at 02:35:06PM +0200, Steffen Maier wrote: > Use wrapper functions to advertize their use in an attempt to avoid wrong > shifting in the future? After a second thought and a bit of coccinelle magic I converted all drivers under drivers/scsi to use set_host_byte(), msg and drive

[PATCH] MAINTAINERS: Add Paul Mackerras as maintainer for KVM/powerpc

Paul is handling almost all of the powerpc related KVM patches nowadays, so he should be mentioned in the MAINTAINERS file accordingly. Signed-off-by: Thomas Huth --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 2d3d750..177ffde 100644 --- a/MAI

Re: [PATCH] bitfield: Use __ffs64(x) to fix missing __ffsdi2()

On Mon, 9 Oct 2017 10:40:49 +0200, Geert Uytterhoeven wrote: > On most architectures[*], gcc turns __builtin_ffsll() into a call to > __ffsdi2(), which is not provided by any architecture, leading to > failures like: > > rcar-gen3-cpg.c:(.text+0x289): undefined reference to `__ffsdi2' > > To

[PATCH 2/3] hexagon: add KBUILD_ prefix to CFLAGS_MODULE, LDFLAGS_MODULE

{CFLAGS,LDFLAGS}_MODULE are supposed to be set by users, not by in-kernel makefiles. Documentation/kbuild/makefiles.txt clearly explains the difference: KBUILD_CFLAGS_MODULE Options for $(CC) when building modules $(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that

[PATCH 3/3] c6x: add KBUILD_ prefix to CFLAGS_MODULE

CFLAGS_MODULE is supposed to be set by users, not by in-kernel makefiles. Documentation/kbuild/makefiles.txt clearly explains the difference: KBUILD_CFLAGS_MODULE Options for $(CC) when building modules $(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that are used fo

[PATCH 1/3] ARM: add KBUILD_ prefix to CFLAGS_MODULE, LDFLAGS_MODULE

{CFLAGS,LDFLAGS}_MODULE are supposed to be set by users, not by in-kernel makefiles. Documentation/kbuild/makefiles.txt clearly explains the difference: KBUILD_CFLAGS_MODULE Options for $(CC) when building modules $(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that

[PATCH 0/3] ARM, hexagon, c6x: build: fix usage of CFLAGS_MODULE, LDFLAGS_MODULE

CFLAGS_MODULE, AFLAGS_MODULE, and LDFLAGS_MODULE are supposed to be set by users. In-kernel Makefile must use KBUILD_ prefixed variables. This is explained in Documentation/kbuild/{kbuild.txt, makefiles.txt} Most of architectures follow the rule, but I found violations in ARM, hexagone, and c6x.

Re: [PATCH tip/core/rcu 1/9] rcu: Provide GP ordering in face of migrations and delays

On Mon, Oct 09, 2017 at 10:16:37AM +0200, Peter Zijlstra wrote: > On Sat, Oct 07, 2017 at 11:28:57AM -0700, Paul E. McKenney wrote: > > But if you are saying that it would be good to have wait_for_completion() > > and complete() directly modeled at some point, no argument. In addition, > > I hope

Re: [PATCH] MAINTAINERS: Add Paul Mackerras as maintainer for KVM/powerpc

On 09.10.17 16:34, Thomas Huth wrote: > Paul is handling almost all of the powerpc related KVM patches nowadays, > so he should be mentioned in the MAINTAINERS file accordingly. > > Signed-off-by: Thomas Huth Feel free to replace me too. Reviewed-by: Alexander Graf Alex

Re: [PATCH v3 03/22] dt-bindings: arm: scmi: add ARM MHU specific mailbox client bindings

On 09/10/17 14:52, Rob Herring wrote: > On Fri, Oct 6, 2017 at 9:26 PM, Jassi Brar wrote: >> On Fri, Oct 6, 2017 at 9:24 PM, Rob Herring wrote: >>> On Fri, Oct 6, 2017 at 6:01 AM, Jassi Brar wrote: On Fri, Oct 6, 2017 at 4:50 AM, Rob Herring wrote: > On Thu, Sep 28, 2017 at 02:11:27P

Re: [BUG] fs/dlm: A possible sleep-in-atomic bug in dlm_master_lookup

On Sat, Oct 07, 2017 at 03:26:11AM +0100, Al Viro wrote: > On Sat, Oct 07, 2017 at 09:59:41AM +0800, Jia-Ju Bai wrote: > > According to fs/dlm/lock.c, the kernel may sleep under a spinlock, > > and the function call path is: > > dlm_master_lookup (acquire the spinlock) > > dlm_send_rcom_lookup_du

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

On Mon, Oct 09, 2017 at 11:12:58AM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 09, 2017 at 07:07:29AM -0700, Andi Kleen escreveu: > > On Mon, Oct 09, 2017 at 03:41:51PM +0200, Jiri Olsa wrote: > > > On Wed, Oct 04, 2017 at 09:27:11AM -0700, Andi Kleen wrote: > > > > On Wed, Oct 04, 2017 at

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

On Mon, Oct 09, 2017 at 11:09:44AM -0300, Arnaldo Carvalho de Melo wrote: SNIP > [root@jouet bpf]# cat sys_read.c > #define SEC(NAME) __attribute__((section(NAME), used)) > SEC("func=sys_read") > int bpf_func__sys_read(void *ctx) > { > return 1; > } > char _license[] SEC("license") = "GPL"

Re: [ANNOUNCE] fsperf: a simple fs/block performance testing framework

On Fri, Oct 06, 2017 at 05:09:57PM -0400, Josef Bacik wrote: > One thing that comes up a lot every LSF is the fact that we have no general > way > that we do performance testing. Every fs developer has a set of scripts or > things that they run with varying degrees of consistency, but nothing cen

Re: [PATCH] MAINTAINERS: Add Paul Mackerras as maintainer for KVM/powerpc

On 09/10/2017 16:34, Thomas Huth wrote: > Paul is handling almost all of the powerpc related KVM patches nowadays, > so he should be mentioned in the MAINTAINERS file accordingly. > > Signed-off-by: Thomas Huth > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAI

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

On Mon, Oct 09, 2017 at 07:07:29AM -0700, Andi Kleen wrote: SNIP > > > > > The only real fix would be probably to add some unique > > > prefix for BPF, but that would break all existing users. > > > > > > yea, there was no response from bpf folks, but it's probably not an optio > > > > how

Re: [PATCH] MAINTAINERS: Add Paul Mackerras as maintainer for KVM/powerpc

On 09.10.17 16:42, Paolo Bonzini wrote: > On 09/10/2017 16:34, Thomas Huth wrote: >> Paul is handling almost all of the powerpc related KVM patches nowadays, >> so he should be mentioned in the MAINTAINERS file accordingly. >> >> Signed-off-by: Thomas Huth >> --- >> MAINTAINERS | 1 + >> 1 file

Re: [PATCH v3 03/22] dt-bindings: arm: scmi: add ARM MHU specific mailbox client bindings

On Mon, Oct 9, 2017 at 7:22 PM, Rob Herring wrote: > On Fri, Oct 6, 2017 at 9:26 PM, Jassi Brar wrote: >> On Fri, Oct 6, 2017 at 9:24 PM, Rob Herring wrote: >>> On Fri, Oct 6, 2017 at 6:01 AM, Jassi Brar wrote: On Fri, Oct 6, 2017 at 4:50 AM, Rob Herring wrote: > On Thu, Sep 28, 2017

Re: [PATCH workqueue/for-4.14-fixes] workqueue: replace pool->manager_arb mutex with a flag

Hello, Boqun. On Mon, Oct 09, 2017 at 10:21:17PM +0800, Boqun Feng wrote: > > +static DECLARE_WAIT_QUEUE_HEAD(wq_manager_wait); /* wait for manager to go > > away */ > > I think this wait_queue_head better be a per-pool one rather than shared > among pools? It should be fine either way. All th

Re: [PATCH v2] livepatch: unpatch all klp_objects if klp_module_coming fails

On Mon, 2 Oct 2017, Joe Lawrence wrote: > When an incoming module is considered for livepatching by > klp_module_coming(), it iterates over multiple patches and multiple > kernel objects in this order: > > list_for_each_entry(patch, &klp_patches, list) { > klp_for_each_object(

Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case

Em Mon, Oct 09, 2017 at 04:39:53PM +0200, Jiri Olsa escreveu: > On Mon, Oct 09, 2017 at 11:12:58AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Mon, Oct 09, 2017 at 07:07:29AM -0700, Andi Kleen escreveu: > > > On Mon, Oct 09, 2017 at 03:41:51PM +0200, Jiri Olsa wrote: > > > > On Wed, Oct 04, 2017

Re: [PATCH v2] ALSA: seq: resize buffer for overflow

On 10/07/2017 02:39 AM, Takashi Iwai wrote: I doubt it came from snd_midi_event_encode_byte(). Judging from the call trace below, the event originated from the OSS sequencer write, i.e. it received an OSS event packet, and it was delivered again to another OSS sequencer port back via dummy client

<    4   5   6   7   8   9   10   11   12   13   >