[PATCH 4.4 04/60] powerpc/powernv: Fix opal_exit tracepoint opcode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit a7e0fb6c2029a780444d09560f739e020d54fe4d upstream. Currently the opal_exit tracepoint usually shows the opcode as 0: -0 [047] d.h. 635.654292: opal_entry: opcod

Re: [PATCH 07/14] Implement fsopen() to prepare for a mount

On Thu, 2017-05-11 at 15:30 +0100, David Howells wrote: > Sargun Dhillon wrote: > > > Instead of string based configuration, does it perhaps make sense to > > pass in structured mount data? Something like: > > I don't think it helps particularly. > > > enum mount_command_id { > > MOUNT_OPTI

[PATCH 4.4 05/60] power: supply: bq24190_charger: Fix irq trigger to IRQF_TRIGGER_FALLING

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 767eee362fd72bb2ca44cc80419ca4b38c6d8369 upstream. The interrupt signal is TRIGGER_FALLING. This is is specified in the data sheet PIN FUNCTIONS: "The INT pin sends active low

Re: [v3 0/9] parallelized "struct page" zeroing

From: Michal Hocko Date: Thu, 11 May 2017 10:05:38 +0200 > Anyway, do you agree that doing the struct page initialization along > with other writes to it shouldn't add a measurable overhead comparing > to pre-zeroing of larger block of struct pages? We already have an > exclusive cache line and

[PATCH 4.4 07/60] power: supply: bq24190_charger: Install irq_handler_thread() at end of probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit d62acc5ef0621463446091ebd7a345e06e9ab80c upstream. The device specific data is not fully initialized on request_threaded_irq(). This may cause a crash when the IRQ handler tri

Re: [PATCH] sched/deadline: Zero out positive runtime after throttling constrained tasks

On 05/10/2017 03:03 PM, Xunlei Pang wrote: > When a contrained task is throttled by dl_check_constrained_dl(), > it may carry the remaining positive runtime, as a result when > dl_task_timer() fires and calls replenish_dl_entity(), it will > not be replenished correctly due to the positive dl_se->r

[PATCH 4.4 08/60] power: supply: bq24190_charger: Call power_supply_changed() for relevant component

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 2d9fee6a42ea170e4378b3363a7ad385d0e67281 upstream. We wrongly get uevents for bq24190-charger and bq24190-battery on every register change. Fix by checking the association wi

[PATCH 4.4 09/60] power: supply: bq24190_charger: Dont read fault register outside irq_handle_thread()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 68abfb8015832ddf728b911769659468efaf8bd9 upstream. Caching the fault register after a single I2C read may not keep an accurate value. Fix by doing two reads in irq_handle_thr

[PATCH 4.4 03/60] cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 4cca0457686e4ee1677d69469e4ddfd94d389a80 upstream. The switch that conditionally sets CPUPOWER_CAP_HAS_TURBO_RATIO and CPUPOWER_CAP_IS_SNB flags is missing a break, so all

[PATCH 4.4 25/60] usb: host: ohci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 68bd6fc3cfa98ef253e17307ccafd8ef907b5556 upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount. Error paths lacked it s

[PATCH 4.9 075/103] MIPS: R2-on-R6 MULTU/MADDU/MSUBU emulation bugfix

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leonid Yegoshin commit d65e5677ad5b3a49c43f60ec07644dc1f87bbd2e upstream. MIPS instructions MULTU, MADDU and MSUBU emulation requires registers HI/LO to be converted to signed 32bits before 64b

[PATCH 4.4 02/60] ARM: 8452/3: PJ4: make coprocessor access sequences buildable in Thumb2 mode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 5008efc83bf85b647aa1cbc44718b1675bbb7444 upstream. The PJ4 inline asm sequence to write to cp15 cannot be built in Thumb-2 mode, due to the way it performs arithmetic on t

[PATCH 4.4 19/60] kprobes/x86: Fix kernel panic when certain exception-handling addresses are probed

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 75013fb16f8484898eaa8d0b08fed942d790f029 upstream. Fix to the exception table entry check by using probed address instead of the address of copied instruction. This bug

RE: [PATCH] qed: fix uninitialized data in aRFS intrastructure

> > For the most part - I'm almost all in favor of this change. > > But just to make it clear - the actual fix could have been a one-liner, > > right? > > The rest are style changes. > Correct. Having the correct length in the memset is a sufficient fix for the > warning, > but it felt wrong to

[PATCH 4.4 12/60] ARM: OMAP5 / DRA7: Fix HYP mode boot for thumb2 build

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matthijs van Duin commit 448c077eeb02240c430db2a2c3bf5285a4c65d66 upstream. 'adr' yields a data-pointer, not a function-pointer. Fixes: 999f934de195 ("ARM: omap5/dra7xx: Enable booting seconda

[PATCH 4.4 18/60] clk: Make x86/ conditional on CONFIG_COMMON_CLK

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Pierre-Louis Bossart commit f35b6542c3ac3f28056d298348a81f7d56d3a041 upstream. Fix Makefile for x86 support, dependency on CONFIG_COMMON_CLK was not explicit Fixes: 701190fd7419 ('clk: x86: ad

[PATCH 4.9 078/103] staging/lustre/llite: move root_squash from sysfs to debugfs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Oleg Drokin commit 4c13990e35b9f053857d4ad83bf0f58e612ec414 upstream. root_squash control got accidentally moved to sysfs instead of debugfs, and the write side of it was also broken expecting

[PATCH 4.4 16/60] x86/ioapic: Restore IO-APIC irq_chip retrigger callback

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ruslan Ruslichenko commit a9b4f08770b415f30f2fb0f8329a370c8f554aa3 upstream. commit d32932d02e18 removed the irq_retrigger callback from the IO-APIC chip and did not add it to the new IO-APIC-I

[PATCH 4.4 10/60] power: supply: bq24190_charger: Handle fault before status on interrupt

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit ba52e75718784fda1b683ee0bfded72a0b83b047 upstream. Reading both fault and status registers and logging any fault should take priority over handling status register update. Fi

[PATCH 4.4 13/60] mwifiex: debugfs: Fix (sometimes) off-by-1 SSID print

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6183468a23fc6b6903f8597982017ad2c7fdefcf upstream. Similar to commit fcd2042e8d36 ("mwifiex: printk() overflow with 32-byte SSIDs"), we failed to account for the existence o

[PATCH 4.9 074/103] scsi: smartpqi: fix time handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ed10858eadd4988260c6bc7d75fc25176342b5a7 upstream. When we have turned off RTC support, the smartpqi driver fails to build: ERROR: "rtc_time64_to_tm" [drivers/scsi/smartpq

[PATCH 4.4 11/60] leds: ktd2692: avoid harmless maybe-uninitialized warning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit cbe99c538d1776009e8710755bb6e726f7fffa9b upstream. gcc gets confused about the control flow in ktd2692_parse_dt(), causing it to warn about what seems like a potential bug:

[PATCH 4.4 15/60] mwifiex: Avoid skipping WEP key deletion for AP

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ganapathi Bhat commit a5b60de6972decc6b50a39abb376077c3c3621c8 upstream. This patch fixes the issue specific to AP. AP is started with WEP security and external station is connected to it. Data

[PATCH 4.9 076/103] brcmfmac: Ensure pointer correctly set if skb data location changes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 455a1eb4654c24560eb9dfc634f29cba3d87601e upstream. The incoming skb header may be resized if header space is insufficient, which might change the data adddress in the skb. E

[PATCH 4.4 14/60] mwifiex: remove redundant dma padding in AMSDU

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xinming Hu commit 5f0a221f59ad6b72202ef9c6e232086de8c336f2 upstream. We already ensure 64 bytes alignment and add padding if required during skb_aggr allocation. Alignment and padding in mwifi

[PATCH 4.9 099/103] xen: Revert commits da72ff5bfcb0 and 72a9b186292d

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 84d582d236dc1f9085e741affc72e9ba061a67c2 upstream. Recent discussion (http://marc.info/?l=xen-devel&m=149192184523741) established that commit 72a9b186292d ("xen: Remove

[PATCH 4.9 070/103] serial: 8250_omap: Fix probe and remove for PM runtime

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 4e0f5cc65098ea32a1e77baae74215b9bd5276b1 upstream. Otherwise the interconnect related code implementing PM runtime will produce these errors on a failed probe: omap_uart 4

[PATCH 4.9 077/103] brcmfmac: Make skb header writable before use

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 9cc4b7cb86cbcc6330a3faa8cd65268cd2d3c227 upstream. The driver was making changes to the skb_header without ensuring it was writable (i.e. uncloned). This patch also removes

[PATCH 4.4 01/60] 9p: fix a potential acl leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang commit b5c66bab72a6a65edb15beb60b90d3cb84c5763b upstream. posix_acl_update_mode() could possibly clear 'acl', if so we leak the memory pointed by 'acl'. Save this pointer before call

[PATCH 4.9 100/103] wlcore: Pass win_size taken from ieee80211_sta to FW

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maxim Altshul commit 42c7372a111630dab200c2f959424f5ec3bf79a4 upstream. When starting a new BA session, we must pass the win_size to the FW. To do this we take max_rx_aggregation_subframes (BA

Re: [PATCH v2 04/10] pinctrl: sunxi: switch A20's pinctrl driver to use the A10 version

On Thu, May 4, 2017 at 3:50 PM, Icenowy Zheng wrote: > As we added A20 support to A10 pinctrl driver, now we can delete the > dedicated A20 pinctrl driver, and enable A10 driver for A20. > > Signed-off-by: Icenowy Zheng Looks all right to me but I'm waiting for Maxime's review on these patches.

[PATCH 4.9 101/103] wlcore: Add RX_BA_WIN_SIZE_CHANGE_EVENT event

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maxim Altshul commit e7ee74b56f23ba447d3124f2eccc32033cca501d upstream. This event is used by the Firmware to limit the RX BA win size for a specific link. The event handler updates the new si

[PATCH 4.9 103/103] block: get rid of blk_integrity_revalidate()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 19b7ccf8651df09d274671b53039c672a52ad84d upstream. Commit 25520d55cdb6 ("block: Inline blk_integrity in struct gendisk") introduced blk_integrity_revalidate(), which seems t

[PATCH 4.9 073/103] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b upstream. We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC handler")

[PATCH 4.9 096/103] bpf: dont let ldimm64 leak map addresses on unprivileged

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 0d0e57697f162da4aa218b5feafe614fb666db07 ] The patch fixes two things at once: 1) It checks the env->allow_ptr_leaks and only prints the map address to th

[PATCH 4.9 098/103] f2fs: sanity check segment count

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jin Qian commit b9dd46188edc2f0d1f37328637860bb65a771124 upstream. F2FS uses 4 bytes to represent block address. As a result, supported size of disk is 16 TB and it equals to 16 * 1024 * 1024 /

[PATCH] metag-TCM: Delete an error message for a failed memory allocation in tcm_add_region()

From: Markus Elfring Date: Thu, 11 May 2017 16:16:32 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf Sign

Re: [PATCH] ARM: remove duplicate 'const' annotations'

* Alexandre Belloni [170511 05:02]: > On 11/05/2017 at 13:50:16 +0200, Arnd Bergmann wrote: > > gcc-7 warns about some declarations that are more 'const' than necessary: > > > > arch/arm/mach-at91/pm.c:338:34: error: duplicate 'const' declaration > > specifier [-Werror=duplicate-decl-specifier]

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

On Thursday, May 11, 2017 03:52:11 PM Michał Kępień wrote: > > On Tuesday, May 09, 2017 09:47:34 AM Darren Hart wrote: > > > On Tue, May 09, 2017 at 11:35:24AM +0200, Michał Kępień wrote: > > > > > On Sat, May 06, 2017 at 02:45:16PM +0200, Michał Kępień wrote: > > > > > > > Just to make sure we are

Re: [PATCH v3 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU

2017-04-19 16:20 GMT+02:00 Vladimir Murzin : > On 19/04/17 12:56, Joerg Roedel wrote: >> On Tue, Apr 18, 2017 at 01:51:35PM +0100, Vladimir Murzin wrote: >>> FYI, nothing has changed since last "ping" - András and Alexandre are still >>> dependant on this series to safely enable DMA on their platfo

Re: [PATCH 1/2] of: remove extraneous 'const' in typedef

On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: > One change that was meant to address a sparse warning turned out > to cause hundreds of new gcc-7 warnings: I guess you are the only one on gcc-7. > include/linux/of_irq.h:11:13: error: type qualifiers ignored on function > return type [-W

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

Hello, On Thu, May 11, 2017 at 03:20:58PM +0100, Andre Przywara wrote: > > Tejun, do I read your comments on the patch as an ACK? > > Tejun and I were wondering why we need this "create an array with the > indices" in the first place. If we can just call radix_tree_delete() > directly from the ra

Re: [v5 1/4] ACPICA: IORT: Add Cavium ThunderX2 SMMUv3 model definition.

On Thursday, May 11, 2017 09:45:25 AM Will Deacon wrote: > On Thu, May 11, 2017 at 02:26:02AM +0200, Rafael J. Wysocki wrote: > > On Wednesday, May 10, 2017 05:01:55 PM Geetha sowjanya wrote: > > > From: Linu Cherian > > > > > > Add SMMUv3 model definition for ThunderX2. > > > > > > Signed-off-b

Re: [PATCH 2/2] of: reserved_mem: fix 'const' annotation

On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: > It's the pointer that is supposed to be const, not the return > type of the function. > > drivers/of/of_reserved_mem.c: In function '__reserved_mem_init_node': > drivers/of/of_reserved_mem.c:200:7: error: type qualifiers ignored on > functio

Re: [PATCH] ata: avoid gcc-7 warning in ata_timing_quantize

Hello, Arnd. On Thu, May 11, 2017 at 02:51:25PM +0200, Arnd Bergmann wrote: > gcc-7 warns about the result of a constant multiplication used as > a boolean: > > drivers/ata/libata-core.c: In function 'ata_timing_quantize': > drivers/ata/libata-core.c:3164:30: warning: '*' in boolean context, sugg

Re: [PATCH 2/3] livepatch/rcu: Warn when system consistency is broken in RCU code

On Thu, May 11, 2017 at 03:52:46PM +0200, Petr Mladek wrote: > On Mon 2017-05-08 15:13:22, Steven Rostedt wrote: > > On Mon, 8 May 2017 11:51:08 -0500 > > Josh Poimboeuf wrote: > > > > > Another idea would be to figure out a way to stop using RCU in > > > klp_ftrace_handler() altogether. > > > >

FROM AISHA GADDAFI

Dr. Aisha Gaddafi, the daughter of late Libyan president, I need a partner or an investor that will help me in investing the sum of $87.5 million USD in his or her country, the funds is deposited here in Burkina Faso where I am staying for the moment with my family, I would like to know your m

RE: [RFC 00/11] ima: namespace support for IMA policy

I would like to replace part of the email below which briefly presents each one of the patches in this series. This is the right summary: -- Patches 1, 2 and 3 qualify the file pathname considering multiple namespaces. Patch 4 adds the namespace securityfs file which is the interface to define IM

Re: [PATCH] xfs: avoid harmless gcc-7 warnings

On Thu, May 11, 2017 at 4:02 PM, Christoph Hellwig wrote: > On Thu, May 11, 2017 at 02:49:21PM +0200, Arnd Bergmann wrote: >> gcc-7 flags the use of integer math inside of a condition >> as a potential bug: >> >> fs/xfs/xfs_bmap_util.c: In function 'xfs_swap_extents_check_format': >> fs/xfs/xfs_bm

Re: [PATCH] ACPI / GED: use late init to allow other drivers init

On Thursday, May 11, 2017 09:43:14 AM Sinan Kaya wrote: > Hi Rafael, > > On 5/10/2017 8:46 PM, Rafael J. Wysocki wrote: > >> My proposal was to require platform AML code to indicate the dependencies > >> between GED and drivers on the right side of the picture via _DEP as this > >> cannot be done

Re: [PATCH 2/2] of: reserved_mem: fix 'const' annotation

On Thu, May 11, 2017 at 4:50 PM, Rob Herring wrote: > On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: >> It's the pointer that is supposed to be const, not the return >> type of the function. >> >> drivers/of/of_reserved_mem.c: In function '__reserved_mem_init_node': >> drivers/of/of_reserv

[PATCH 4.9 090/103] tcp: do not inherit fastopen_req from parent

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 8b485ce69876c65db12ed390e7f9c0d2a64eff2c ] Under fuzzer stress, it is possible that a child gets a non NULL fastopen_req pointer from its parent at accept() time

Re: [PATCH] qed: fix uninitialized data in aRFS intrastructure

On Thu, May 11, 2017 at 4:37 PM, Mintz, Yuval wrote: >> > For the most part - I'm almost all in favor of this change. >> > But just to make it clear - the actual fix could have been a one-liner, >> > right? >> > The rest are style changes. > >> Correct. Having the correct length in the memset is

[PATCHv2] arm64/cpufeature: don't use mutex in bringup path

Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which must take the jump_label mutex. We call cpus_set_cap() in the secondary bringup path, from the idle thread where interrupts are disabled. Taking a mutex in this path "is a NONO" regardless of whether it's contended, and somet

Re: [PATCH 0/3] SATA: Fine-tuning for two function implementations

Hi, On Friday, April 28, 2017 05:53:34 PM Tejun Heo wrote: > Hello, > > On Tue, Apr 18, 2017 at 10:00:37PM +0200, SF Markus Elfring wrote: > > From: Markus Elfring > > Date: Tue, 18 Apr 2017 21:54:32 +0200 > > > > A few update suggestions were taken into account > > from static source code ana

[PATCH 4.9 072/103] scsi: mac_scsi: Fix MAC_SCSI=m option when SCSI=m

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 2559a1ef688f933835912c731bed2254146a9b04 upstream. The mac_scsi driver still gets disabled when SCSI=m. This should have been fixed back when I enabled the tristate but I didn

[PATCH 4.9 085/103] bpf: enhance verifier to understand stack pointer arithmetic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ Upstream commit 332270fdc8b6fba07d059a9ad44df9e1a2ad4529 ] llvm 4.0 and above generates the code like below: 440: (b7) r1 = 15 441: (05) goto pc+73 515: (79) r6 = *(u64 *)

Re: [RFC] adding of TGID to ftrace output

On Wed, 10 May 2017 20:10:06 -0700 Joel Fernandes wrote: > Hi Steven, > Thanks for your quick reply. > > On Wed, May 10, 2017 at 6:28 PM, Steven Rostedt wrote: > > On Wed, 10 May 2017 16:04:55 -0700 > > Joel Fernandes wrote: > > > >> Hi Steven, > >> > >> Can we add TGID information along wit

[PATCH 4.9 084/103] tcp: do not underestimate skb->truesize in tcp_trim_head()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7162fb242cb8322beb558828fd26b33c3e9fc805 ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using syzkaller and a filter attache

Re: [PATCH] bluetooth: hci_ll: add proper SERDEV dependency

On Thu, May 11, 2017 at 6:41 AM, Arnd Bergmann wrote: > When SERDEV is a loadable module, and the HCI code is built-in, we > get a link error: > > drivers/bluetooth/built-in.o: In function `ll_close': > hci_ll.c:(.text+0x278d): undefined reference to `serdev_device_close' > drivers/bluetooth/built

Re: [PATCH 2/3] livepatch/rcu: Warn when system consistency is broken in RCU code

On Thu, May 11, 2017 at 02:40:42PM +0200, Miroslav Benes wrote: > I'm still not sure if we know for 100 percent what we're doing :) At least we know that we don't know! -- Josh

Re: [PATCH 1/2] of: remove extraneous 'const' in typedef

On Thu, May 11, 2017 at 4:44 PM, Rob Herring wrote: > On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: >> One change that was meant to address a sparse warning turned out >> to cause hundreds of new gcc-7 warnings: > > I guess you are the only one on gcc-7. It was just released last week or

[PATCH 4.9 082/103] sparc64: fix fault handling in NGbzero.S and GENbzero.S

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Aldridge commit 3c7f62212018b904ae17f5636ead18a4dca3a88f upstream. When any of the functions contained in NGbzero.S and GENbzero.S vector through *bzero_from_clear_user, we may end up taki

[PATCH 4.9 080/103] staging: emxx_udc: remove incorrect __init annotations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4f3445067d5f78fb8d1970b02610f85c2f377ea4 upstream. The probe function is not marked __init, but some other functions are. This leads to a warning on older compilers (e.g. g

[PATCH 4.9 032/103] iwlwifi: mvm: overwrite skb info later

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit bd05a5bd6b11d7fd26a668de83c5cb996de05f8f upstream. We don't really need clear the skb's status area nor store the dev_cmd into it until we really commit to the frame by han

[PATCH v2] xfs: avoid harmless gcc-7 warnings

gcc-7 flags the use of integer math inside of a condition as a potential bug: fs/xfs/xfs_bmap_util.c: In function 'xfs_swap_extents_check_format': fs/xfs/xfs_bmap_util.c:1619:8: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context] fs/xfs/xfs_bmap_util.c:1629:8: error:

[PATCH 4.9 041/103] iwlwifi: mvm: synchronize firmware DMA paging memory

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 4b70f07686d75d1eb5d956812cc810944e0b29b2 upstream. When driver needs to access the contents of a streaming DMA buffer without unmapping it it should call dma_sync_single_for_

[PATCH 4.9 040/103] iwlwifi: mvm: fix references to first_agg_queue in DQA mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit c56108b58ab870892277940a1def0d6b153f3e26 upstream. In DQA mode, first_agg_queue is initialized to IWL_MVM_DQA_MIN_DATA_QUEUE. This causes two bugs in the tx response flow: 1

[PATCH 4.9 039/103] iwlwifi: mvm: fix pending frame counter calculation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 94c3e614df2117626fccfac8f821c66e30556384 upstream. In DQA mode the check whether to decrement the pending frames counter relies on the tid status and not on the txq id. This

[PATCH 4.9 068/103] clk: rockchip: add "," to mux_pll_src_apll_dpll_gpll_usb480m_p on rk3036

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Stuebner commit 9b1b23f03abdd25ffde8bbfe5824b89bc0448c28 upstream. The mux_pll_src_apll_dpll_gpll_usb480m_p parent list was missing a "," between the 3rd and 4th parent names, making them

Re: [PATCH v2] xfs: avoid harmless gcc-7 warnings

Yes, this looks much better: Reviewed-by: Christoph Hellwig

[PATCH 4.9 037/103] iwlwifi: mvm: Use aux queue for offchannel frames in dqa

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Beni Lev commit 6574dc943fc32a2fce69fab14891abca7eecb67c upstream. Since offchannel activity doesn't always require a BSS, e.g. ANQP sessions, offchannel frames should not use the BSS queue, be

[PATCH 4.9 069/103] phy: qcom-usb-hs: Add depends on EXTCON

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 1a09b6a7c10e22c489a8b212dd6862b1fd9674ad upstream. We get the following compile errors if EXTCON is enabled as a module but this driver is builtin: drivers/built-in.o: In f

[PATCH 4.9 063/103] USB: serial: ftdi_sio: fix latency-timer error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit e3e574ad85a208cb179f33720bb5f12b453de33c upstream. Make sure to detect short responses when reading the latency timer to avoid using stale buffer data. Note that no heap da

[PATCH 4.9 067/103] USB: serial: sierra: fix bogus alternate-setting assumption

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 16620b483eaf7750413bae472f4363b6b959fcaa upstream. Interface numbers do not change when enabling alternate settings as comment and code in this driver suggested. Remove the

[PATCH 4.9 065/103] USB: serial: mct_u232: fix modem-status error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 36356a669eddb32917fc4b5c2b9b8bf80ede69de upstream. Make sure to detect short control-message transfers so that errors are logged when reading the modem status at open. Note

Re: [PATCH] ARM: remove duplicate 'const' annotations'

On Thu, 11 May 2017, Arnd Bergmann wrote: > gcc-7 warns about some declarations that are more 'const' than necessary: > > arch/arm/mach-at91/pm.c:338:34: error: duplicate 'const' declaration > specifier [-Werror=duplicate-decl-specifier] > static const struct of_device_id const ramc_ids[] __ini

[PATCH 4.9 064/103] USB: serial: quatech2: fix control-message error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 8c34cb8ddfe808d557b51da983ff10c02793beb2 upstream. Make sure to detect short control-message transfers when fetching modem and line state in open and when retrieving registe

[PATCH 4.9 057/103] USB: serial: keyspan_pda: fix receive sanity checks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c528fcb116e61afc379a2e0a0f70906b937f1e2c upstream. Make sure to check for short transfers before parsing the receive buffer to avoid acting on stale data. Fixes: 1da177e4c3

[PATCH 4.9 035/103] iwlwifi: pcie: fix the set of DMA memory mask

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 2c6262b754f3c3338cb40b23880a3ac1f4693b25 upstream. Our 9000 device supports 64 bit DMA address for RX only, and not for TX. Setting DMA mask to 64 for the whole device is err

[PATCH 4.9 058/103] USB: serial: digi_acceleport: fix incomplete rx sanity check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1b0aed2b1600f6e5c7b9acfbd610a4e351ef5232 upstream. Make sure the received data has the required headers before parsing it. Also drop the redundant urb-status check, which h

[PATCH 4.9 061/103] USB: serial: ti_usb_3410_5052: fix control-message error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 39712e8bfa8d3aa6ce1e60fc9d62c9b076c17a30 upstream. Make sure to detect and return an error on zero-length control-message transfers when reading from the device. This addre

[PATCH 4.9 059/103] USB: serial: ssu100: fix control-message error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1eac5c244f705182d1552a53e2f74e2775ed95d6 upstream. Make sure to detect short control-message transfers rather than continue with zero-initialised data when retrieving modem

[PATCH 4.9 053/103] usb: host: ehci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 3f6026b1dcb3c8ee71198c485a72ac674c6890dd upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount. Error paths lacked it s

[PATCH 4.9 048/103] x86/platform/intel-mid: Correct MSI IRQ line for watchdog device

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 80354c29025833acd72ddac1ffa21c6cb50128cd upstream. The interrupt line used for the watchdog is 12, according to the official Intel Edison BSP code. And indeed after fixi

[PATCH 4.9 052/103] usb: dwc2: host: use msleep() for long delay

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire commit d3fe81d2ccc41b355e494413115c0c7c18426fa1 upstream. ulseep_range() uses hrtimers and provides no advantage over msleep() for larger delays. Fix up the 100ms delays here

[PATCH 4.9 054/103] usb: host: ohci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 68bd6fc3cfa98ef253e17307ccafd8ef907b5556 upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount. Error paths lacked it s

[PATCH 4.9 045/103] x86/mpx: Re-add MPX to selftests Makefile

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit e64d5fbe56259c94df504af8ce804cfc6a022adb upstream. Ingo pointed out that the MPX tests were no longer in the selftests Makefile. It appears that I shot myself in the foot on

[PATCH 4.9 042/103] iwlwifi: mvm: writing zero bytes to debugfs causes a crash

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 251fe09f13bfb54c1ede66ee8bf8ddd0061c4f7c upstream. This is a static analysis fix. The warning is: drivers/net/wireless/intel/iwlwifi/mvm/fw-dbg.c:912 iwl_mvm_fw_

[PATCH 4.9 043/103] x86/ioapic: Restore IO-APIC irq_chip retrigger callback

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ruslan Ruslichenko commit a9b4f08770b415f30f2fb0f8329a370c8f554aa3 upstream. commit d32932d02e18 removed the irq_retrigger callback from the IO-APIC chip and did not add it to the new IO-APIC-I

[PATCH 4.9 000/103] 4.9.28-stable review

This is the start of the stable review cycle for the 4.9.28 release. There are 103 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat May 13 14:11:46 UTC 2017. Anything receiv

[PATCH 4.9 008/103] cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 4cca0457686e4ee1677d69469e4ddfd94d389a80 upstream. The switch that conditionally sets CPUPOWER_CAP_HAS_TURBO_RATIO and CPUPOWER_CAP_IS_SNB flags is missing a break, so all

[PATCH 4.9 009/103] powerpc/mm: Fixup wrong LPCR_VRMASD value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Aneesh Kumar K.V commit 4ab2537c4204b976e4ca350bbdc193b4649cad28 upstream. In commit a4b349540a26af ("powerpc/mm: Cleanup LPCR defines") we updated LPCR_VRMASD wrongly as below. -#define LPC

[PATCH 4.9 029/103] mwifiex: Avoid skipping WEP key deletion for AP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ganapathi Bhat commit a5b60de6972decc6b50a39abb376077c3c3621c8 upstream. This patch fixes the issue specific to AP. AP is started with WEP security and external station is connected to it. Data

[PATCH 4.9 004/103] tpm: fix RC value check in tpm2_seal_trusted

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 7d761119a914ec0ac05ec2a5378d1f86e680967d upstream. The error code handling is broken as any error code that has the same bits set as TPM_RC_HASH passes. Implemented tpm2_

[PATCH] crypto-testmgr: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Thu, 11 May 2017 17:05:17 +0200 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf Si

Re: [PATCH 1/2] of: remove extraneous 'const' in typedef

On Thu, May 11, 2017 at 10:03 AM, Arnd Bergmann wrote: > On Thu, May 11, 2017 at 4:44 PM, Rob Herring wrote: >> On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: >>> One change that was meant to address a sparse warning turned out >>> to cause hundreds of new gcc-7 warnings: >> >> I guess yo

[PATCH 4.9 027/103] mwifiex: debugfs: Fix (sometimes) off-by-1 SSID print

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6183468a23fc6b6903f8597982017ad2c7fdefcf upstream. Similar to commit fcd2042e8d36 ("mwifiex: printk() overflow with 32-byte SSIDs"), we failed to account for the existence o

[PATCH 4.9 025/103] ARM: OMAP5 / DRA7: Fix HYP mode boot for thumb2 build

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Matthijs van Duin commit 448c077eeb02240c430db2a2c3bf5285a4c65d66 upstream. 'adr' yields a data-pointer, not a function-pointer. Fixes: 999f934de195 ("ARM: omap5/dra7xx: Enable booting seconda

[PATCH 4.9 021/103] arm: dts: qcom: Fix ipq board clock rates

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 06dbf468a2c42bf6c327a8eaf11ecb3ea96196f9 upstream. The ipq board has these rates as 25MHz, and not 19.2 and 27. I copy/pasted from other boards that have those rates but for

<    1   2   3   4   5   6   7   8   9   10   >