Re: [PATCH 1/6] x86/efi: PFN_ALIGN() _text and _end when calculating number of pages

* Matt Fleming wrote: > While _text is currently aligned to PAGE_SIZE in the vmlinux linker > script because it's based on CONFIG_PHYSICAL_ALIGN, it's always better > to be explicit about these things to be sure no alignment bugs are > lurking. There's no analogous enforcement for _end. > > Dav

Re: [PATCH 1/6] x86/efi: PFN_ALIGN() _text and _end when calculating number of pages

On Tue, 24 Nov, at 09:23:23AM, Ingo Molnar wrote: > > Didn't we want to do the _end alignment linker script fix instead? I think we should do both. This patch is tagged for stable because it fixes a bug in the existing code. It's obvious and it's explicit and it's much easier to know when someon

[PATCH] PCI: Fix NUMA bounds check

Suggested here: http://marc.info/?l=linux-pci&m=144706760307247&w=2 P. -8<- The fix for 1266963 ("PCI: Prevent out of bounds access in numa_node override") should allow for the setting of all valid NUMA states including NUMA_NO_NODE, which is also interpreted as "any node". This change s

Re: [Intel-gfx] [PATCH v4] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping

On Sat, Nov 21, 2015 at 02:01:55AM +0800, kbuild test robot wrote: > Hi Chris, > > [auto build test WARNING on drm-intel/for-linux-next] > [cannot apply to v4.4-rc1 next-20151120] > > url: > https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Pin-the-ifbdev-for-the-info-system_base

[PATCH] TTY: n_gsm, fix false positive WARN_ON

Dmitry reported, that the current cleanup code in n_gsm can trigger a warning: WARNING: CPU: 2 PID: 24238 at drivers/tty/n_gsm.c:2048 gsm_cleanup_mux+0x166/0x6b0() ... Call Trace: ... [] warn_slowpath_null+0x29/0x30 kernel/panic.c:490 [] gsm_cleanup_mux+0x166/0x6b0 drivers/tty/n_gsm.c:2048 [] g

[PULL 3/8] arm64: KVM: Add workaround for Cortex-A57 erratum 834220

From: Marc Zyngier Cortex-A57 parts up to r1p2 can misreport Stage 2 translation faults when a Stage 1 permission fault or device alignment fault should have been reported. This patch implements the workaround (which is to validate that the Stage-1 translation actually succeeds) by using code pa

[PULL 2/8] arm64: KVM: Fix AArch32 to AArch64 register mapping

From: Marc Zyngier When running a 32bit guest under a 64bit hypervisor, the ARMv8 architecture defines a mapping of the 32bit registers in the 64bit space. This includes banked registers that are being demultiplexed over the 64bit ones. On exceptions caused by an operation involving a 32bit regi

[PULL 1/8] ARM/arm64: KVM: test properly for a PTE's uncachedness

From: Ard Biesheuvel The open coded tests for checking whether a PTE maps a page as uncached use a flawed '(pte_val(xxx) & CONST) != CONST' pattern, which is not guaranteed to work since the type of a mapping is not a set of mutually exclusive bits For HYP mappings, the type is an index into the

[Resend PATCH] RDS: fix race condition when sending a message on unbound socket

From: Quentin Casasnovas Sasha's found a NULL pointer dereference in the RDS connection code when sending a message to an apparently unbound socket. The problem is caused by the code checking if the socket is bound in rds_sendmsg(), which checks the rs_bound_addr field without taking a lock on t

Re: [Intel-gfx] [PATCH v4] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping

Hi Chris, On Fri, Nov 20, 2015 at 04:29:52PM +, Chris Wilson wrote: > A long time ago (before 3.14) we relied on a permanent pinning of the > ifbdev to lock the fb in place inside the GGTT. However, the > introduction of stealing the BIOS framebuffer and reusing its address in > the GGTT for t

Re: [Resend PATCH] RDS: fix race condition when sending a message on unbound socket

From: Santosh Shilimkar Date: Tue, 24 Nov 2015 17:13:21 -0500 > From: Quentin Casasnovas > > Sasha's found a NULL pointer dereference in the RDS connection code when > sending a message to an apparently unbound socket. The problem is caused > by the code checking if the socket is bound in rds_

[PATCH 3.2 13/52] ARM: pxa: remove incorrect __init annotation on pxa27x_set_pwrmode

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 54c09889bff6d99c8733eed4a26c9391b177c88b upstream. The z2 machine calls pxa27x_set_pwrmode() in order to power off the machine, but this function gets discarded early at bo

[PATCH 3.2 47/52] fs: if a coredump already exists, unlink and recreate with O_EXCL

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit fbb1816942c04429e85dbf4c1a080accc534299e upstream. It was possible for an attacking user to trick root (or another user) into writing his coredumps into an attacker-readable, p

[PATCH 3.2 17/52] Bluetooth: ath3k: Add new AR3012 0930:021c id

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Dmitry Tunin commit cd355ff071cd37e7197eccf9216770b2b29369f7 upstream. This adapter works with the existing linux-firmware. T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D:

[PATCH 3.2 32/52] scsi: restart list search after unlock in scsi_remove_target

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 40998193560dab6c3ce8d25f4fa58a23e252ef38 upstream. When dropping a lock while iterating a list we must restart the search as other threads could have manipulated the li

[PATCH 3.2 21/52] MIPS: atomic: Fix comment describing atomic64_add_unless's return value.

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Ralf Baechle commit f25319d2cb439249a6859f53ad42ffa332b0acba upstream. Signed-off-by: Ralf Baechle Fixes: f24219b4e90cf70ec4a211b17fbabc725a0ddf3c (cherry picked from commit f0a232cde7be18a207

[PATCH 3.2 48/52] irda: precedence bug in irlmp_seq_hb_idx()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 50010c20597d14667eff0fdb628309986f195230 ] This is decrementing the pointer, instead of the value stored in the pointer. KASan detects it as an out of bounds re

[PATCH 3.2 20/52] ACPI: Use correct IRQ when uninstalling ACPI interrupt handler

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Chen Yu commit 49e4b84333f338d4f183f28f1f3c1131b9fb2b5a upstream. Currently when the system is trying to uninstall the ACPI interrupt handler, it uses acpi_gbl_FADT.sci_interrupt as the IRQ num

[PATCH 3.2 15/52] Btrfs: fix truncation of compressed and inlined extents

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 0305cd5f7fca85dae392b9ba85b116896eb7c1c7 upstream. When truncating a file to a smaller size which consists of an inline extent that is compressed, we did not discard (or ma

[PATCH 3.2 29/52] ipv6: fix tunnel error handling

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Michal Kubeček commit ebac62fe3d24c0ce22dd83afa7b07d1a2aaef44d upstream. Both tunnel6_protocol and tunnel46_protocol share the same error handler, tunnel6_err(), which traverses through tunnel6

[PATCH 3.2 11/52] Btrfs: fix file corruption and data loss after cloning inline extents

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 8039d87d9e473aeb740d4fdbd59b9d2f89b2ced9 upstream. Currently the clone ioctl allows to clone an inline extent from one file to another that already has other (non-inlined)

[PATCH 3.2 49/52] RDS-TCP: Recover correctly from pskb_pull()/pksb_trim() failure in rds_tcp_data_recv

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Sowmini Varadhan [ Upstream commit 8ce675ff39b9958d1c10f86cf58e357efaafc856 ] Either of pskb_pull() or pskb_trim() may fail under low memory conditions. If rds_tcp_data_recv() ignores such fail

[PATCH 3.2 45/52] binfmt_elf: Don't clobber passed executable's file header

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: "Maciej W. Rozycki" commit b582ef5c53040c5feef4c96a8f9585b6831e2441 upstream. Do not clobber the buffer space passed from `search_binary_handler' and originally preloaded by `prepare_binprm' wi

[PATCH 3.2 30/52] ALSA: hda - Apply pin fixup for HP ProBook 6550b

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit c932b98c1e47312822d911c1bb76e81ef50e389c upstream. HP ProBook 6550b needs the same pin fixup applied to other HP B-series laptops with docks for making its headphone and doc

[PATCH 3.2 34/52] Btrfs: fix race leading to incorrect item deletion when dropping extents

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit aeafbf8486c9e2bd53f5cc3c10c0b7fd7149d69c upstream. While running a stress test I got the following warning triggered: [191627.672810] [ cut here ]---

[PATCH 3.2 37/52] scsi_sysfs: Fix queue_ramp_up_period return code

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Oberparleiter commit 863e02d0e173bb9d8cea6861be22820b25c076cc upstream. Writing a number to /sys/bus/scsi/devices//queue_ramp_up_period returns the value of that number instead of the num

[PATCH 3.2 44/52] FS-Cache: Handle a write to the page immediately beyond the EOF marker

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: David Howells commit 102f4d900c9c8f5ed89ae4746d493fe3ebd7ba64 upstream. Handle a write being requested to the page immediately beyond the EOF marker on a cache object. Currently this gets an a

[PATCH 3.2 46/52] fs: make dumpable=2 require fully qualified path

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 9520628e8ceb69fa9a4aee6b57f22675d9e1b709 upstream. When the suid_dumpable sysctl is set to "2", and there is no core dump pipe defined in the core_pattern sysctl, a local user

[PATCH 3.2 22/52] ALSA: hda - Disable 64bit address for Creative HDA controllers

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit cadd16ea33a938d49aee99edd4758cc76048b399 upstream. We've had many reports that some Creative sound cards with CA0132 don't work well. Some reported that it starts working a

[PATCH 3.2 24/52] can: Use correct type in sizeof() in nla_put()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Marek Vasut commit 562b103a21974c2f9cd67514d110f918bb3e1796 upstream. The sizeof() is invoked on an incorrect variable, likely due to some copy-paste error, and this might result in memory corr

[PATCH 3.2 26/52] crypto: algif_hash - Only export and import on sockets with data

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 4afa5f9617927453ac04b24b584f6c718dfb4f45 upstream. The hash_accept call fails to work on sockets that have not received any data. For some algorithm implementations it may ca

[PATCH 3.2 31/52] firewire: ohci: fix JMicron JMB38x IT context discovery

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Stefan Richter commit 100ceb66d5c40cc0c7018e06a9474302470be73c upstream. Reported by Clifford and Craig for JMicron OHCI-1394 + SDHCI combo controllers: Often or even most of the time, the con

[PATCH 3.2 50/52] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context.

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Ani Sinha [ Upstream commit 44f49dd8b5a606870a1f21101522a0f9c4414784 ] Fixes the following kernel BUG : BUG: using __this_cpu_add() in preemptible [] code: bash/2758 caller is __this_c

[PATCH 3.2 25/52] mtd: blkdevs: fix potential deadlock + lockdep warnings

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit f3c63795e90f0c6238306883b6c72f14d5355721 upstream. Commit 073db4a51ee4 ("mtd: fix: avoid race condition when accessing mtd->usecount") fixed a race condition but due to poor

[PATCH 3.2 33/52] x86/cpu: Call verify_cpu() after having entered long mode too

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 04633df0c43d710e5f696b06539c100898678235 upstream. When we get loaded by a 64-bit bootloader, kernel entry point is startup_64 in head_64.S. We don't trust any and all bo

[PATCH 3.2 39/52] scsi: Fix a bdi reregistration race

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit bf2cf3baa20b0a6cd2d08707ef05dc0e992a8aa0 upstream. Unregister and reregister BDI devices in the proper order. This patch avoids that the following kernel warning can get

[PATCH 3.2 38/52] Btrfs: fix race when listing an inode's xattrs

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit f1cd1f0b7d1b5d4aaa5711e8f4e4898b0045cb6d upstream. When listing a inode's xattrs we have a time window where we race against a concurrent operation for adding a new hard li

[PATCH 3.2 41/52] KVM: svm: unconditionally intercept #DB

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit cbdb967af3d54993f5814f1cee0ed311a055377d upstream. This is needed to avoid the possibility that the guest triggers an infinite stream of #DB exceptions (CVE-2015-8104). VM

[PATCH 3.2 40/52] net: fix a race in dst_release()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit d69bbf88c8d0b367cf3e3a052f6daadf630ee566 upstream. Only cpu seeing dst refcount going to 0 can safely dereference dst->flags. Otherwise an other cpu might already have free

[PATCH 3.2 42/52] FS-Cache: Increase reference of parent after registering, netfs success

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Kinglong Mee commit 86108c2e34a26e4bec3c6ddb23390bf8cedcf391 upstream. If netfs exist, fscache should not increase the reference of parent's usage and n_children, otherwise, never be decreased.

[PATCH 3.2 04/52] HID: core: Avoid uninitialized buffer access

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Richard Purdie commit 79b568b9d0c7c5d81932f4486d50b38efdd6da6d upstream. hid_connect adds various strings to the buffer but they're all conditional. You can find circumstances where nothing wou

[PATCH 3.2 23/52] megaraid_sas: Do not use PAGE_SIZE for max_sectors

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: "sumit.sax...@avagotech.com" commit 357ae967ad66e357f78b5cfb5ab6ca07fb4a7758 upstream. Do not use PAGE_SIZE marco to calculate max_sectors per I/O request. Driver code assumes PAGE_SIZE will be

[PATCH 3.2 27/52] megaraid_sas : SMAP restriction--do not access user memory from IOCTL code

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: "sumit.sax...@avagotech.com" commit 323c4a02c631d00851d8edc4213c4d184ef83647 upstream. This is an issue on SMAP enabled CPUs and 32 bit apps running on 64 bit OS. Do not access user memory from

[PATCH 3.2 36/52] perf: Fix inherited events vs. tracepoint filters

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b71b437eedaed985062492565d9d421d975ae845 upstream. Arnaldo reported that tracepoint filters seem to misbehave (ie. not apply) on inherited events. The fix is obvious; fil

[PATCH 3.2 19/52] staging: rtl8712: Add device ID for Sitecom WLA2100

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit 1e6e63283691a2a9048a35d9c6c59cf0abd342e4 upstream. This adds the USB ID for the Sitecom WLA2100. The Windows 10 inf file was checked to verify that the addition is correct.

[PATCH 3.2 28/52] recordmcount: Fix endianness handling bug for nop_mcount

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: libin commit c84da8b9ad3761eef43811181c7e896e9834b26b upstream. In nop_mcount, shdr->sh_offset and welp->r_offset should handle endianness properly, otherwise it will trigger Segmentation fault

[PATCH 3.2 51/52] net: avoid NULL deref in inet_ctl_sock_destroy()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 8fa677d2706d325d71dab91bf6e6512c05214e37 ] Under low memory conditions, tcp_sk_init() and icmp_sk_init() can both iterate on all possible cpus and call inet_ctl_s

[PATCH 3.2 18/52] Bluetooth: ath3k: Add support of AR3012 0cf3:817b device

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Dmitry Tunin commit 18e0afab8ce3f1230ce3fef52b2e73374fd9c0e7 upstream. T: Bus=04 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1

[PATCH 3.2 52/52] splice: sendfile() at once fails for big files

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit 0ff28d9f4674d781e492bcff6f32f0fe48cf0fed upstream. Using sendfile with below small program to get MD5 sums of some files, it appear that big files (over 64kbytes with 4k

[PATCH 3.2 10/52] Btrfs: added helper btrfs_next_item()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Schmidt commit c7d22a3c3cdb73d8a0151e2ccc8cf4a48c48310b upstream. btrfs_next_item() makes the btrfs path point to the next item, crossing leaf boundaries if needed. Signed-off-by: Arne Jan

[PATCH 3.2 00/52] 3.2.74-rc1 review

This is the start of the stable review cycle for the 3.2.74 release. There are 52 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 Fri Nov 27 00:00:00 UTC 2015. Anything receiv

[PATCH 3.2 02/52] PCI: Use function 0 VPD for identical functions, regular VPD for others

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Williamson commit da2d03ea27f6ed9d2005a67b20dd021ddacf1e4d upstream. 932c435caba8 ("PCI: Add dev_flags bit to access VPD through function 0") added PCI_DEV_FLAGS_VPD_REF_F0. Previously, w

[PATCH 3.2 09/52] packet: fix match_fanout_group()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 161642e24fee40fba2c5bc2ceacc00d118a22d65 upstream. Recent TCP listener patches exposed a prior af_packet bug : match_fanout_group() blindly assumes it is always safe to cast

[PATCH 3.2 12/52] iommu/vt-d: Fix ATSR handling for Root-Complex integrated endpoints

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit d14053b3c714178525f22660e6aaf41263d00056 upstream. The VT-d specification says that "Software must enable ATS on endpoint devices behind a Root Port only if the Root Port

[PATCH 3.2 03/52] mac80211: fix driver RSSI event calculations

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 8ec6d97871f37e4743678ea4a455bd59580aa0f4 upstream. The ifmgd->ave_beacon_signal value cannot be taken as is for comparisons, it must be divided by since it's represented li

[PATCH 3.2 16/52] ext4, jbd2: ensure entering into panic after recording an error in superblock

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Daeho Jeong commit 4327ba52afd03fc4b5afa0ee1d774c9c5b0e85c5 upstream. If a EXT4 filesystem utilizes JBD2 journaling and an error occurs, the journaling will be aborted first and the error numbe

[PATCH 3.2 07/52] mtd: mtdpart: fix add_mtd_partitions error path

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Boris BREZILLON commit e5bae86797141e4a95e42d825f737cb36d7b8c37 upstream. If we fail to allocate a partition structure in the middle of the partition creation process, the already allocated par

[PATCH 3.2 06/52] mwifiex: fix mwifiex_rdeeprom_read()

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 1f9c6e1bc1ba5f8a10fcd6e99d170954d7c6d382 upstream. There were several bugs here. 1) The done label was in the wrong place so we didn't copy any information out when t

[PATCH 3.2 35/52] Btrfs: fix race leading to BUG_ON when running delalloc for nodatacow

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 1d512cb77bdbda80f0dd0620a3b260d697fd581d upstream. If we are using the NO_HOLES feature, we have a tiny time window when running delalloc for a nodatacow inode where we can

[PATCH 3.2 14/52] Btrfs: don't use ram_bytes for uncompressed inline items

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Chris Mason commit 514ac8ad8793a097c0c9d89202c642479d6dfa34 upstream. If we truncate an uncompressed inline item, ram_bytes isn't updated to reflect the new size. The fixe uses the size direct

[PATCH 3.2 43/52] FS-Cache: Don't override netfs's primary_index if registering failed

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Kinglong Mee commit b130ed5998e62879a66bad08931a2b5e832da95c upstream. Only override netfs->primary_index when registering success. Signed-off-by: Kinglong Mee Signed-off-by: David Howells S

[PATCH 3.2 05/52] wm831x_power: Use IRQF_ONESHOT to request threaded IRQs

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Valentin Rothberg commit 90adf98d9530054b8e665ba5a928de4307231d84 upstream. Since commit 1c6c69525b40 ("genirq: Reject bogus threaded irq requests") threaded IRQs without a primary handler need

[PATCH 3.2 01/52] PCI: Fix devfn for VPD access through function 0

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Williamson commit 9d9240756e63dd87d6cbf5da8b98ceb8f8192b55 upstream. Commit 932c435caba8 ("PCI: Add dev_flags bit to access VPD through function 0") passes PCI_SLOT(devfn) for the devfn pa

[PATCH 3.2 08/52] devres: fix a for loop bounds check

3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 1f35d04a02a652f14566f875aef3a6f2af4cb77b upstream. The iomap[] array has PCIM_IOMAP_MAX (6) elements and not DEVICE_COUNT_RESOURCE (16). This bug was found using a static

Re: [PATCH 3.2 39/52] scsi: Fix a bdi reregistration race

On 11/24/2015 02:35 PM, Ben Hutchings wrote: 3.2.74-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit bf2cf3baa20b0a6cd2d08707ef05dc0e992a8aa0 upstream. Hi Ben, This patch fixes one bug but introduces another one ... So it'

Re: [PATCH 3.2 31/52] firewire: ohci: fix JMicron JMB38x IT context discovery

On Nov 24 Ben Hutchings wrote: > commit 100ceb66d5c40cc0c7018e06a9474302470be73c upstream. ... > [bwh: Backported to 3.2: log with fw_notify() instead of ohci_notice()] Thanks for doing so, looks good to me. -- Stefan Richter -=-= =-== ==--= http://arcgraph.de/sr/ -- To unsubscribe from t

Re: [PATCH 3.2 46/52] fs: make dumpable=2 require fully qualified path

On Tue, 24 Nov 2015, Ben Hutchings wrote: > 3.2.74-rc1 review patch. If anyone has any objections, please let me know. > > -- > > From: Kees Cook > > commit 9520628e8ceb69fa9a4aee6b57f22675d9e1b709 upstream. > Reviewed-by: James Morris -- James Morris -- To unsubscribe

Re: [PATCH 3.2 00/52] 3.2.74-rc1 review

On 11/24/2015 02:33 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.2.74 release. There are 52 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: [PATCH 3.2 20/52] ACPI: Use correct IRQ when uninstalling ACPI interrupt handler

Hi, Ben, ok for me. thanks, Yu On Tue, 2015-11-24 at 22:33 +, Ben Hutchings wrote: > 3.2.74-rc1 review patch. If anyone has any objections, please let me know. > > -- > > From: Chen Yu > > commit 49e4b84333f338d4f183f28f1f3c1131b9fb2b5a upstream. > > Currently when the s

[PATCH] ARC: dw2 unwind: Remove falllback linear search thru FDE entries

Fixes STAR 9000953410: "perf callgraph profiling causing RCU stalls" | perf record -g -c 15000 -e cycles /sbin/hackbench | | INFO: rcu_preempt self-detected stall on CPU | 1: (1 GPs behind) idle=609/142/0 softirq=2914/2915 fqs=603 | Task dump for CPU 1: in-kernel dwarf unwinder has a

[PATCH v2 1/3] zram/zcomp: use GFP_NOIO to allocate streams

From: Sergey Senozhatsky We can end up allocating a new compression stream with GFP_KERNEL from within the IO path, which may result is nested (recursive) IO operations. That can introduce problems if the IO path in question is a reclaimer, holding some locks that will deadlock nested IOs. Alloc

Re: [PATCH] TTY: n_gsm, fix false positive WARN_ON

hi, Jiri This warning should blame on commit 5a640967 ("tty/n_gsm.c: fix a memory leak in gsmld_open()"). When gsm driver failed to activate one mux,there is memory leak. So I call this ->cleanup() to do the cleanup work. Seems I did not consider all cases. I have one confusion. As ther