Re: [tip:efi/core] x86/mm/pat: Use _PAGE_GLOBAL bit for EFI page table mappings

On Tue, Feb 23, 2016 at 4:50 PM, Sai Praneeth Prakhya wrote: > On Tue, 2016-02-23 at 09:47 -0800, Andy Lutomirski wrote: >> On Feb 23, 2016 1:09 AM, <"tip-bot for Sai Praneeth >> "@zytor.com> wrote: >> >> Something's wrong with tip-bot. This should say: >> >> >> commit 397630150

Re: 4.4-final: 28 bioset threads on small notebook

On Tue, Feb 23, 2016 at 10:54 PM, Mike Snitzer wrote: > On Mon, Feb 22 2016 at 9:55pm -0500, > Ming Lei wrote: > >> On Tue, Feb 23, 2016 at 6:58 AM, Kent Overstreet >> wrote: >> > On Sun, Feb 21, 2016 at 05:40:59PM +0800, Ming Lei wrote: >> >> On Sun, Feb 21, 2016 at 2:43 PM, Ming Lin-SSI >>

Re: [PATCH 3.2 00/67] 3.2.78-rc1 review

On 02/23/2016 01:42 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.2.78 release. There are 67 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 b

Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info

On Tue, Feb 23, 2016 at 04:31:35PM +0300, Dan Carpenter wrote: > Blergh... You want it machine readable and I want it human readable. I Yeah. It's kind of tasting which may differ among people. I'll leave the judgments to Junio and others, and only add necessary comments to your points. > don't

Re: fs: NULL deref in atime_needs_update

On Wed, 2016-02-17 at 00:40 +0100, Mickaël Salaün wrote: > Hi, > > Actually I found the same bug (without fuzzing) and I can reproduce it > in a deterministic way (e.g. by creating a LSM that return 1 for the > security_file_open hook). At least, from v4.2.8 I can easily trigger > traces like this

Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info

On Tue, Feb 23, 2016 at 11:51:31AM -0800, Junio C Hamano wrote: > Fengguang Wu writes: > > >> >> I have a mixed feeling about this one, primarily because this was > >> >> already tried quite early in the life of "format-patch" command. > >> >> > >> >> > >> >> http://thread.gmane.org/gmane.c

Re: [PATCH 0/4] serial: omap: robustify for high speed transfers

On 02/23/2016 01:59 AM, Sekhar Nori wrote: > On Monday 22 February 2016 09:00 PM, John Ogness wrote: >> Hi Tony, >> >> On 2016-02-11, Tony Lindgren wrote: At these speeds, nearly every DMA interrupt is accompanied by a spurious UART interrupt. So, sadly, the interrupts are doubled.

[PATCHv3] net: fix bridge multicast packet checksum validation

We need to update the skb->csum after pulling the skb, otherwise an unnecessary checksum (re)computation can ocure for IGMP/MLD packets in the bridge code. Additionally this fixes the following splats for network devices / bridge ports with support for and enabled RX checksum offloading: [...] [

Re: 4.4-final: 28 bioset threads on small notebook

On Wed, Feb 24, 2016 at 10:48:10AM +0800, Ming Lei wrote: > On Tue, Feb 23, 2016 at 10:54 PM, Mike Snitzer wrote: > > On Mon, Feb 22 2016 at 9:55pm -0500, > > Ming Lei wrote: > > > >> On Tue, Feb 23, 2016 at 6:58 AM, Kent Overstreet > >> wrote: > >> > On Sun, Feb 21, 2016 at 05:40:59PM +0800, M

Re: [alsa-devel] [PATCH] ASoC: rt5640: add master clock handling for rt5640

On Wed, Feb 24, 2016 at 12:08:31AM +0100, Heiko Stuebner wrote: > Am Dienstag, 23. Februar 2016, 08:50:04 schrieb Pierre-Louis Bossart: > > This patch assumes that the information on mclk comes from DeviceTree. > > The mclk may also be enabled/disabled in the machine driver with an > > explicit tr

Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info

On Tue, Feb 23, 2016 at 12:35:12PM -0800, Junio C Hamano wrote: > ebied...@xmission.com (Eric W. Biederman) writes: > > > Junio C Hamano writes: > > > >> It is valuable for a testing organization to say "We tested this > >> series on top of version X. We know it works, we have tested on a > >> l

Re: [PATCH] ASoC: rockchip: i2s: add default values for registers

On Tue, Feb 23, 2016 at 09:19:22AM +0800, Sugar Zhang wrote: > this patch add default values for registers according description from TRM. This patch has already been applied, please send incremental changes if any are required. signature.asc Description: PGP signature

Re: [PATCH] ASoC: rt5640: add master clock handling for rt5640

On Tue, Feb 23, 2016 at 09:26:22AM +0800, Sugar Zhang wrote: > enable/disable master clock when codec is active or not. This patch has already been applied, please send incremental patches if any changes are required. signature.asc Description: PGP signature

[PATCH v2 2/2] usb: dwc2: Move host-specific core functions into hcd.c

Move host core initialization and host channel routines into hcd.c. This allows these functions to only be compiled in host-enabled driver configurations (DRD or host-only). Tested-by: Douglas Anderson Reviewed-by: Douglas Anderson Signed-off-by: John Youn --- drivers/usb/dwc2/core.c | 1776 --

[PATCH v2 1/2] usb: dwc2: Move register save and restore functions

Move the register save and restore functions into the host and gadget specific files. Tested-by: Douglas Anderson Reviewed-by: Douglas Anderson Signed-off-by: John Youn --- drivers/usb/dwc2/core.c | 183 -- drivers/usb/dwc2/core.h | 13 dri

[PATCH v2 0/2] usb: dwc2: Remove host and gadget only code from core

This series moves the host/gadget-specific code from core.c to hcd.c and gadget.c so that they will be compiled only when their respective configurations are selected, or in DRD. This is mostly just a straight move of the code. I have also added some comments to group related functions together.

[PATCH] dmaengine: pl330: fix to support the brust mode

This patch fixes the brust mode that will break DMA uart on SoCFPGA. In some cases, some SoCS didn't support the multi-brust even if the devices who use the pl330 claim support the maxbrust. Fixes: commit 848e977 "dmaengine: pl330: support burst mode for dev-to-mem and mem-to-dev transmit" Repor

[PATCH 3.10 48/54] radix-tree: fix race in gang lookup

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Matthew Wilcox commit 46437f9a554fbe3e110580ca08ab703b59f2f95a upstream. If the indirect_ptr bit is set on a slot, that indicates we need to redo the lookup. Introduce a new function radix_tr

[PATCH 3.10 22/54] scsi_dh_rdac: always retry MODE SELECT on command lock violation

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit d2d06d4fe0f2cc2df9b17fefec96e6e1a1271d91 upstream. If MODE SELECT returns with sense '05/91/36' (command lock violation) it should always be retried without counting the

[PATCH 3.10 52/54] futex: Drop refcount if requeue_pi() acquired the rtmutex

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit fb75a4282d0d9a3c7c44d940582c2d226cf3acfb upstream. If the proxy lock in the requeue loop acquires the rtmutex for a waiter then it acquired also refcount on the pi_state

[PATCH 3.10 35/54] ARM: 8517/1: ICST: avoid arithmetic overflow in icst_hz()

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 5070fb14a0154f075c8b418e5bc58a620ae85a45 upstream. When trying to set the ICST 307 clock to 25174000 Hz I ran into this arithmetic error: the icst_hz_to_vco() correctly fi

[PATCH 3.10 50/54] intel_scu_ipcutil: underflow in scu_reg_access()

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit b1d353ad3d5835b16724653b33c05124e1b5acf1 upstream. "count" is controlled by the user and it can be negative. Let's prevent that by making it unsigned. You have to have C

[PATCH 3.10 03/54] staging/speakup: Use tty_ldisc_ref() for paste kworker

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Hurley commit f4f9edcf9b5289ed96113e79fa65a7bf27ecb096 upstream. As the function documentation for tty_ldisc_ref_wait() notes, it is only callable from a tty file_operations routine; oth

[PATCH 3.10 29/54] cifs: fix erroneous return value

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Anton Protopopov commit 4b550af519854421dfec9f7732cdddeb057134b2 upstream. The setup_ntlmv2_rsp() function may return positive value ENOMEM instead of -ENOMEM in case of kmalloc failure. Sign

[PATCH 3.10 51/54] x86/asm/irq: Stop relying on magic JMP behavior for early_idt_handlers

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 425be5679fd292a3c36cb1fe423086708a99f11a upstream. The early_idt_handlers asm code generates an array of entry points spaced nine bytes apart. It's not really clear fro

[PATCH 3.10 47/54] memcg: only free spare array when readers are done

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Martijn Coenen commit 6611d8d76132f86faa501de9451a89bf23fb2371 upstream. A spare array holding mem cgroup threshold events is kept around to make sure we can always safely deregister an event

[PATCH 3.10 49/54] radix-tree: fix oops after radix_tree_iter_retry

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 732042821cfa106b3c20b9780e4c60fee9d68900 upstream. Helper radix_tree_iter_retry() resets next_index to the current index. In following radix_tree_next_slot current

[PATCH 3.10 46/54] scripts/bloat-o-meter: fix python3 syntax error

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Sergey Senozhatsky commit 72214a24a7677d4c7501eecc9517ed681b5f2db2 upstream. In Python3+ print is a function so the old syntax is not correct anymore: $ ./scripts/bloat-o-meter vmlinux.o vm

[PATCH 3.10 44/54] m32r: fix m32104ut_defconfig build fail

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit 601f1db653217f205ffa5fb33514b4e1711e56d1 upstream. The build of m32104ut_defconfig for m32r arch was failing for long long time with the error: ERROR: "memory_start"

[PATCH 3.10 45/54] dma-debug: switch check from _text to _stext

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit ea535e418c01837d07b6c94e817540f50bfdadb0 upstream. In include/asm-generic/sections.h: /* * Usage guidelines: * _text, _data: architecture specific, don't use them

[PATCH 3.10 43/54] xhci: Fix list corruption in urb dequeue at host removal

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 5c82171167adb8e4ac77b91a42cd49fb211a81a0 upstream. xhci driver frees data for all devices, both usb2 and and usb3 the first time usb_remove_hcd() is called, including td_l

[PATCH 3.10 34/54] ARM: 8519/1: ICST: try other dividends than 1

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit e972c37459c813190461dabfeaac228e00aae259 upstream. Since the dawn of time the ICST code has only supported divide by one or hang in an eternal loop. Luckily we were always

[PATCH 3.10 06/54] AIO: properly check iovec sizes

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman In Linus's tree, the iovec code has been reworked massively, but in older kernels the AIO layer should be checking this before passing the request on to other layers. Many t

[PATCH 3.10 08/54] Btrfs: fix hang on extent buffer lock caused by the inode_paths ioctl

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 0c0fe3b0fa45082cd752553fdb3a4b42503a118e upstream. While doing some tests I ran into an hang on an extent buffer's rwlock that produced the following trace: [39389.800012

[PATCH 3.10 28/54] iio: dac: mcp4725: set iio name property in sysfs

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Yong Li commit 97a249e98a72d6b79fb7350a8dd56b147e9d5bdb upstream. Without this change, the name entity for mcp4725 is missing in /sys/bus/iio/devices/iio\:device*/name With this change, name

[PATCH 3.10 00/54] 3.10.98-stable review

This is the start of the stable review cycle for the 3.10.98 release. There are 54 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 Fri Feb 26 03:33:35 UTC 2016. Anything receiv

[PATCH 3.10 07/54] ext4: fix potential integer overflow

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Insu Yun commit 46901760b46064964b41015d00c140c83aa05bcf upstream. Since sizeof(ext_new_group_data) > sizeof(ext_new_flex_group_data), integer overflow could be happened. Therefore, need to fi

[PATCH 3.10 05/54] pty: make sure super_block is still valid in final /dev/tty close

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Herton R. Krzesinski commit 1f55c718c290616889c04946864a13ef30f64929 upstream. Considering current pty code and multiple devpts instances, it's possible to umount a devpts file system while a

[PATCH 3.10 04/54] pty: fix possible use after free of tty->driver_data

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Herton R. Krzesinski commit 2831c89f42dcde440cfdccb9fee9f42d54bbc1ef upstream. This change fixes a bug for a corner case where we have the the last release from a pty master/slave coming from

Re: [PATCH] usb: dwc2: Use kmem_cache_free()

On 2/22/2016 12:11 AM, Amitoj Kaur Chawla wrote: > Here, free memory is allocated using kmem_cache_zalloc. So, use > kmem_cache_free instead of kfree. > > This is done using Coccinelle and semantic patch used > is as follows: > > // > @@ > expression x,E,c; > @@ > x = > \(kmem_cache_alloc\|kmem

[PATCH 3.10 30/54] nfs: Fix race in __update_open_stateid()

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Elble commit 361cad3c89070aeb37560860ea8bfc092d545adc upstream. We've seen this in a packet capture - I've intermixed what I think was going on. The fix here is to grab the so_lock soon

[PATCH 3.10 31/54] udf: limit the maximum number of indirect extents in a row

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Vegard Nossum commit b0918d9f476a8434b055e362b83fa4fd1d462c3f upstream. udf_next_aext() just follows extent pointers while extents are marked as indirect. This can loop forever for corrupted f

[PATCH 3.10 21/54] drivers/scsi/sg.c: mark VMA as VM_IO to prevent migration

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 461c7fa126794157484dca48e88effa4963e3af3 upstream. Reduced testcase: #include #include #include #include #define SIZE 0x2000 int main()

[PATCH 3.10 32/54] udf: Prevent buffer overrun with multi-byte characters

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Gabbasov commit ad402b265ecf6fa22d04043b41444cdfcdf4f52d upstream. udf_CS0toUTF8 function stops the conversion when the output buffer length reaches UDF_NAME_LEN-2, which is correct max

Re: [PATCH v3 1/3] lib/percpu-list: Per-cpu list with associated per-cpu locks

On 02/23/2016 09:00 PM, Boqun Feng wrote: Hi Waiman, On Tue, Feb 23, 2016 at 02:04:30PM -0500, Waiman Long wrote: } + +/* + * List selection is based on the CPU being used when the pcpu_list_add() + * function is called. However, deletion may be done by a different CPU. + * So we still need to

[PATCH 3.10 24/54] iio:ad7793: Fix ad7785 product ID

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 785171fd6cd7dcd7ada5a733b6a2d44ec566c3a0 upstream. While the datasheet for the AD7785 lists 0xXB as the product ID the actual product ID is 0xX3. Fix the product ID

[PATCH 3.10 26/54] iio:ad5064: Make sure ad5064_i2c_write() returns 0 on success

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Michael Hennerich commit 03fe472ef33b7f31fbd11d300dbb3fdab9c00fd4 upstream. i2c_master_send() returns the number of bytes transferred on success while the ad5064 driver expects that the write(

[PATCH 3.10 25/54] iio: lpc32xx_adc: fix warnings caused by enabling unprepared clock

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit 01bb70ae0b98d266fa3e860482c7ce22fa482a6e upstream. If common clock framework is configured, the driver generates a warning, which is fixed by this change: root@d

[PATCH 3.10 27/54] iio: adis_buffer: Fix out-of-bounds memory access

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit d590faf9e8f8509a0a0aa79c38e87fcc6b913248 upstream. The SPI tx and rx buffers are both supposed to be scan_bytes amount of bytes large and a common allocation is used

[PATCH 3.10 12/54] tracing: Fix freak link error caused by branch tracer

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit b33c8ff4431a343561e2319f17c14286f2aa52e2 upstream. In my randconfig tests, I came across a bug that involves several components: * gcc-4.9 through at least 5.3 * CONFIG_G

[PATCH 4.4 012/137] staging/speakup: Use tty_ldisc_ref() for paste kworker

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Hurley commit f4f9edcf9b5289ed96113e79fa65a7bf27ecb096 upstream. As the function documentation for tty_ldisc_ref_wait() notes, it is only callable from a tty file_operations routine; othe

[PATCH 3.14 11/70] ext4: fix potential integer overflow

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Insu Yun commit 46901760b46064964b41015d00c140c83aa05bcf upstream. Since sizeof(ext_new_group_data) > sizeof(ext_new_flex_group_data), integer overflow could be happened. Therefore, need to fi

[PATCH 4.4 005/137] x86/mm: Fix vmalloc_fault() to handle large pages properly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Toshi Kani commit f4eafd8bcd5229e998aa252627703b8462c3b90f upstream. A kernel page fault oops with the callstack below was observed when a read syscall was made to a pmem device after a huge am

[PATCH 3.10 23/54] scsi: fix soft lockup in scsi_remove_target() on module removal

3.10-stable review patch. If anyone has any objections, please let me know. -- From: James Bottomley commit 90a88d6ef88edcfc4f644dddc7eef4ea41bccf8b upstream. This softlockup is currently happening: [ 444.088002] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworke

[PATCH 3.10 19/54] iscsi-target: Fix potential dead-lock during node acl delete

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit 26a99c19f810b2593410899a5b304b21b47428a6 upstream. This patch is a iscsi-target specific bug-fix for a dead-lock that can occur during explicit struct se_node_acl->ac

[PATCH 4.4 001/137] x86/mm: Fix types used in pgprot cacheability flags translations

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 3625c2c234ef66acf21a72d47a5ffa94f6c5ebf2 upstream. For PAE kernels "unsigned long" is not suitable to hold page protection flags, since _PAGE_NX doesn't fit there. This is th

[PATCH 4.4 027/137] Btrfs: fix hang on extent buffer lock caused by the inode_paths ioctl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 0c0fe3b0fa45082cd752553fdb3a4b42503a118e upstream. While doing some tests I ran into an hang on an extent buffer's rwlock that produced the following trace: [39389.800012]

[PATCH 3.14 45/70] ARM: dts: Kirkwood: Fix QNAP TS219 power-off

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Helmut Klein commit 5442f0eadf2885453d5b2ed8c8592f32a3744f8e upstream. The "reg" entry in the "poweroff" section of "kirkwood-ts219.dtsi" addressed the wrong uart (0 = console). This patch cha

[PATCH 4.4 028/137] Btrfs: fix direct IO requests not reporting IO error to user space

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 1636d1d77ef4e01e57f706a4cae3371463896136 upstream. If a bio for a direct IO request fails, we were not setting the error in the parent bio (the main DIO bio), making us not

[PATCH 4.4 026/137] Btrfs: fix page reading in extent_same ioctl leading to csum errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 313140023026ae542ad76e7e268c56a1eaa2c28e upstream. In the extent_same ioctl, we were grabbing the pages (locked) and attempting to read them without bothering about any con

[PATCH 4.4 029/137] ptrace: use fsuid, fsgid, effective creds for fs access checks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit caaee6234d05a58c5b4d05e7bf766131b810a657 upstream. By checking the effective credentials instead of the real UID / permitted capabilities, ensure that the calling process actua

[PATCH 4.4 023/137] Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Sterba commit 80ad623edd2d0ccb47d85357ee31c97e6c684e82 upstream. This reverts commit 696249132158014d594896df3a81390616069c5c. The cleaner thread can block freezing when there's a snapsho

[PATCH 4.4 025/137] Btrfs: fix invalid page accesses in extent_same (dedup) ioctl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit e0bd70c67bf996b360f706b6c643000f2e384681 upstream. In the extent_same ioctl we are getting the pages for the source and target ranges and unlocking them immediately after,

[PATCH 3.14 54/70] Input: elantech - mark protocols v2 and v3 as semi-mt

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 6544a1df11c48c8413071aac3316792e4678fbfb upstream. When using a protocol v2 or v3 hardware, elantech uses the function elantech_report_semi_mt_data() to report data.

[PATCH 4.4 022/137] Btrfs: fix fitrim discarding device area reserved for boot loaders use

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 8cdc7c5b00d945a3c823fc4277af304abb9cb43d upstream. As of the 4.3 kernel release, the fitrim ioctl can now discard any region of a disk that is not allocated to any chunk/bl

Re: [PATCH] ASoC: arizona: Make logging of FLL calculations clearer

On Tue, Feb 23, 2016 at 02:16:32PM +, Richard Fitzgerald wrote: > The debug logging of FLL calculations was confusing. Values were > printed in hex without indicating this by a leading 0x, and > despite these normally being required in decimal. Also where the > register value isn't the actual v

[PATCH 4.4 021/137] btrfs: handle invalid num_stripes in sys_array

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Sterba commit f5cdedd73fa71b74dcc42f2a11a5735d89ce7c4f upstream. We can handle the special case of num_stripes == 0 directly inside btrfs_read_sys_array. The BUG_ON in btrfs_chunk_item_si

[PATCH 4.4 000/137] 4.4.3-stable review

This is the start of the stable review cycle for the 4.4.3 release. There are 137 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 Fri Feb 26 03:33:58 UTC 2016. Anything receive

[PATCH 4.4 020/137] ext4: dont read blocks from disk after extents being swapped

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eryu Guan commit bcff24887d00bce102e0857d7b0a8c44a40f53d1 upstream. I notice ext4/307 fails occasionally on ppc64 host, reporting md5 checksum mismatch after moving data from original file to d

Re: [PATCH 10/48] perf tools: Introduce bpf-output event

On 2016/2/24 10:04, Wangnan (F) wrote: On 2016/2/24 9:58, Wangnan (F) wrote: On 2016/2/24 1:45, Arnaldo Carvalho de Melo wrote: Em Mon, Feb 22, 2016 at 09:10:37AM +, Wang Nan escreveu: Commit a43eec304259a6c637f4014a6d4767159b6a3aa3 (bpf: introduce bpf_perf_event_output() helper) add

Re: [PATCH v4 0/5] getcpu_cache system call for 4.6

- On Feb 23, 2016, at 8:36 PM, H. Peter Anvin h...@zytor.com wrote: > On 02/23/2016 03:28 PM, Mathieu Desnoyers wrote: >> Hi, >> >> Here is a patchset implementing a cache for the CPU number of the >> currently running thread in user-space. >> >> Benchmarks comparing this approach to a getcp

Re: [PATCH v4] spi: master driver to enable RTC on ICPDAS LP-8841

On Tue, Feb 23, 2016 at 01:44:28PM +0300, Sergei Ianovich wrote: > CC: Mark Brown > CC: Rob Herring > >v3..v4 >fix Mark Brown review comments >* fix dependencies in Kconfig > --- As covered in SubmittingPatches please put inter-version changelogs after the --- so they get stripped

[PATCH 3.14 51/70] mm: soft-offline: check return value in second __get_any_page() call

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Naoya Horiguchi commit d96b339f453997f2f08c52da3f41423be48c978f upstream. I saw the following BUG_ON triggered in a testcase where a process calls madvise(MADV_SOFT_OFFLINE) on thps, along wit

[PATCH 4.4 011/137] phy: twl4030-usb: Fix unbalanced pm_runtime_enable on module reload

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 58a66dba1beac2121d931cda4682ae4d40816af5 upstream. If we reload phy-twl4030-usb, we get a warning about unbalanced pm_runtime_enable. Let's fix the issue and also fix idlin

[PATCH 3.14 68/70] futex: Drop refcount if requeue_pi() acquired the rtmutex

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit fb75a4282d0d9a3c7c44d940582c2d226cf3acfb upstream. If the proxy lock in the requeue loop acquires the rtmutex for a waiter then it acquired also refcount on the pi_state

[PATCH 4.4 007/137] ALSA: pcm: Fix rwsem deadlock for non-atomic PCM stream

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 67ec1072b053c15564e6090ab30127895dc77a89 upstream. A non-atomic PCM stream may take snd_pcm_link_rwsem rw semaphore twice in the same code path, e.g. one in snd_pcm_action_n

[PATCH 4.4 008/137] ALSA: seq: Fix leak of pool buffer at concurrent writes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit d99a36f4728fcbcc501b78447f625bdcce15b842 upstream. When multiple concurrent writes happen on the ALSA sequencer device right after the open, it may try to allocate vmalloc b

[RFC][PATCH] thermal: add sysfs_notify on some attributes

Add a sysfs_notify on thermal_zone*/temp and cooling_device*/ cur_state whenever a passive or critical trip is triggered. This change allows usermode apps to register itself to get notified, when certain thermal conditions occur and reduce their workload. This workload throttling can reduce\preven

[PATCH 4.4 009/137] ALSA: seq: Fix double port list deletion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 13d5e5d4725c64ec06040d636832e78453f477b7 upstream. The commit [7f0973e973cd: ALSA: seq: Fix lockdep warnings due to double mutex locks] split the management of two linked li

[PATCH 4.4 004/137] x86/uaccess/64: Handle the caching of 4-byte nocache copies properly in __copy_user_nocache()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Toshi Kani commit a82eee7424525e34e98d821dd059ce14560a1e35 upstream. Data corruption issues were observed in tests which initiated a system crash/reset while accessing BTT devices. This proble

[PATCH 3.14 60/70] dma-debug: Fix dma_debug_entry offset calculation

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit 0354aec19ce3d355c6213b0434064efc25c9b22c upstream. dma-debug uses struct dma_debug_entry to keep track of dma coherent memory allocation requests. The virtual address is co

[PATCH 4.4 003/137] x86/uaccess/64: Make the __copy_user_nocache() assembly code more readable

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Toshi Kani commit ee9737c924706aaa72c2ead93e3ad5644681dc1c upstream. Add comments to __copy_user_nocache() to clarify its procedures and alignment requirements. Also change numeric branch targ

[PATCH 3.14 53/70] Input: elantech - add Fujitsu Lifebook U745 to force crc_enabled

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 60603950f836ef4e88daddf61a273b91e671db2d upstream. Another Lifebook machine that needs the same quirk as other similar models to make the driver working. Bugzilla: https:/

[PATCH 4.4 006/137] ALSA: hda - Cancel probe work instead of flush at remove

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 0b8c82190c12e530eb6003720dac103bf63e146e upstream. The commit [991f86d7ae4e: ALSA: hda - Flush the pending probe work at remove] introduced the sync of async probe work at r

[PATCH 3.14 52/70] mm: fix mlock accouting

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 7162a1e87b3e380133dadc7909081bb70d0a7041 upstream. Tetsuo Handa reported underflow of NR_MLOCK on munlock. Testcase: #include #include #include

[PATCH 3.14 56/70] iommu/vt-d: Fix 64-bit accesses to 32-bit DMAR_GSTS_REG

3.14-stable review patch. If anyone has any objections, please let me know. -- From: CQ Tang commit fda3bec12d0979aae3f02ee645913d66fbc8a26e upstream. This is a 32-bit register. Apparently harmless on real hardware, but causing justified warnings in simulation. Signed-off-by:

[PATCH 4.4 033/137] tracepoints: Do not trace when cpu is offline

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (Red Hat) commit f37755490fe9bf76f6ba1d8c6591745d3574a6a6 upstream. The tracepoint infrastructure uses RCU sched protection to enable and disable tracepoints safely. There are so

[PATCH 4.4 032/137] tracing: Fix freak link error caused by branch tracer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit b33c8ff4431a343561e2319f17c14286f2aa52e2 upstream. In my randconfig tests, I came across a bug that involves several components: * gcc-4.9 through at least 5.3 * CONFIG_GC

[PATCH 4.4 095/137] mm: fix regression in remap_file_pages() emulation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 48f7df329474b49d83d0dffec1b6186647f11976 upstream. Grazvydas Ignotas has reported a regression in remap_file_pages() emulation. Testcase: #define _GNU_SOURCE

[PATCH 4.4 127/137] ovl: setattr: check permissions before copy-up

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit cf9a6784f7c1b5ee2b9159a1246e327c331c5697 upstream. Without this copy-up of a file can be forced, even without actually being allowed to do anything on the file. [Arnd Ber

[PATCH 4.4 128/137] libxfs: pack the agfl header structure so XFS_AGFL_SIZE is correct

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 96f859d52bcb1c6ea6f3388d39862bf7143e2f30 upstream. Because struct xfs_agfl is 36 bytes long and has a 64-bit integer inside it, gcc will quietly round the structure size

[PATCH 4.4 109/137] scripts/bloat-o-meter: fix python3 syntax error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sergey Senozhatsky commit 72214a24a7677d4c7501eecc9517ed681b5f2db2 upstream. In Python3+ print is a function so the old syntax is not correct anymore: $ ./scripts/bloat-o-meter vmlinux.o vml

[PATCH 4.4 124/137] ovl: use a minimal buffer in ovl_copy_xattr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vito Caputo commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe upstream. Rather than always allocating the high-order XATTR_SIZE_MAX buffer which is costly and prone to failure, only allocate what

[PATCH 4.4 126/137] ovl: root: copy attr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit ed06e069775ad9236087594a1c1667367e983fb5 upstream. We copy i_uid and i_gid of underlying inode into overlayfs inode. Except for the root inode. Fix this omission. Signe

[PATCH 4.4 121/137] devm_memremap_release(): fix memremapd addr handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Toshi Kani commit 9273a8bbf58a15051e53a777389a502420ddc60e upstream. The pmem driver calls devm_memremap() to map a persistent memory range. When the pmem driver is unloaded, this memremap'd ra

[PATCH 4.4 125/137] ovl: check dentry positiveness in ovl_cleanup_whiteouts()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 84889d49335627bc770b32787c1ef9ebad1da232 upstream. This patch fixes kernel crash at removing directory which contains whiteouts from lower layers. Cache of directo

[PATCH 4.4 120/137] ipc/shm: handle removed segments gracefully in shm_mmap()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 1ac0b6dec656f3f78d1c3dd216fad84cb4d0a01e upstream. remap_file_pages(2) emulation can reach file which represents removed IPC ID as long as a memory segment is mapped.

[PATCH 4.4 129/137] xfs: inode recovery readahead can race with inode buffer creation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit b79f4a1c68bb99152d0785ee4ea3ab4396cdacc6 upstream. When we do inode readahead in log recovery, we do can do the readahead before we've replayed the icreate transaction that

[PATCH 4.4 068/137] powerpc/ioda: Set "read" permission when "write" is set

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy commit 6ecad912a0073c768db1491c27ca55ad2d0ee68f upstream. Quite often drivers set only "write" permission assuming that this includes "read" permission as well and this wor

[PATCH 4.4 123/137] ovl: allow zero size xattr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 97daf8b97ad6f913a34c82515be64dc9ac08d63e upstream. When ovl_copy_xattr() encountered a zero size xattr no more xattrs were copied and the function returned success. This

<    5   6   7   8   9   10   11   12   13   >