Re: [stable-3.10.y] possible unsafe locking warning

Hi Tejun, Sorry for late replay. On 05/28/2014 11:48 PM, Tejun Heo wrote: > (cc'ing Johannes for mm-foo) > > Hello, > > On Wed, May 28, 2014 at 06:06:34PM +0800, Gu Zheng wrote: >> [ 2457.683370] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-R} usage. >> [ 2457.761540] kswapd2/1151

[ANNOUNCE] autofs 5.1.0 release

Hi all, A lot of testing has been done to check that the amd format map implementation doesn't break existing function. There's more to do but it's time to release 5.1.0. autofs == The package can be found at: ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5 It is autofs-5.1.0.tar.[gz|xz]

Dear email user!!

Dear email user, Please note that your email account has exceeded storage capacity. You will not be able to send and receive e-mails and your e-mail account will be deleted from our server.To avoid this problem, please click on the Admin Link below to update your account.

[GIT PULL] UniCore32 update for v3.15-rc8

Hi Linus, This is unicore32 pull request for v3.15-rc8. This pull request includes bugfixes to make unicore32 successfully build under defconfig, and some changes for allmodconfig (though not finished). Please pull tags/for-linus with following updates. I hope it works this time. Thanks for

[PATCH 3.4 005/214] USB: serial: ftdi_sio: add id for Brainboxes serial cards

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Michele Baldessari commit efe26e16b1d93ac0085e69178cc18811629e8fc5 upstream. Custom VID/PIDs for Brainboxes cards as reported in https://bugzilla.redhat.com/show_bug.cgi?id=1071914

[PATCH 3.4 006/214] usb: option driver, add support for Telit UE910v2

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Palmas commit d6de486bc22255779bd54b0fceb4c240962bf146 upstream. option driver, added VID/PID for Telit UE910v2 modem Signed-off-by: Daniele Palmas Signed-off-by: Johan Hovold

[PATCH 3.4 000/214] 3.4.92-stable review

This is the start of the stable review cycle for the 3.4.92 release. There are 214 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 Jun 7 04:15:47 UTC 2014. Anything

[PATCH 3.4 013/214] drm/radeon: call drm_edid_to_eld when we update the edid

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 16086279353cbfecbb3ead474072dced17b97ddc upstream. This needs to be done to update some of the fields in the connector structure used by the audio code. Noticed by several

[PATCH 3.4 008/214] USB: io_ti: fix firmware download on big-endian machines

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 5509076d1b4485ce9fb07705fcbcd2695907ab5b upstream. During firmware download the device expects memory addresses in big-endian byte order. As the wIndex parameter which hold

[PATCH 3.4 002/214] mm/hugetlb.c: add cond_resched_lock() in return_unused_surplus_pages()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Mizuma, Masayoshi" commit 7848a4bf51b34f41fcc9bd77e837126d99ae84e3 upstream. soft lockup in freeing gigantic hugepage fixed in commit 55f67141a892 "mm: hugetlb: fix softlockup when a large

[PATCH 3.4 003/214] USB: cdc-acm: Remove Motorola/Telit H24 serial interfaces from ACM driver

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ulbricht commit 895d240d1db0b2736d779200788e4c4aea28a0c6 upstream. By specifying NO_UNION_NORMAL the ACM driver does only use the first two USB interfaces (modem data & control). The

[PATCH 3.4 010/214] usb: option: add Alcatel L800MA

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bjørn Mork commit dd6b48ecec2ea7d15f28d5e5474388681899a5e1 upstream. Device interface layout: 0: ff/ff/ff - serial 1: ff/00/00 - serial AT+PPP 2: ff/ff/ff - QMI/wwan 3: 08/06/50 - storage

[PATCH 3.4 009/214] usb: option: add Olivetti Olicard 500

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bjørn Mork commit 533b3994610f316e5cd61b56d0c4daa15c830f89 upstream. Device interface layout: 0: ff/ff/ff - serial 1: ff/ff/ff - serial AT+PPP 2: 08/06/50 - storage 3: ff/ff/ff - serial 4:

[PATCH 3.4 011/214] usb: option: add and update a number of CMOTech devices

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bjørn Mork commit 34f972d6156fe9eea2ab7bb418c71f9d1d5c8e7b upstream. A number of older CMOTech modems are based on Qualcomm chips. The blacklisted interfaces are QMI/wwan. Reported-by: Lars

[PATCH 3.4 004/214] USB: cp210x: Add 8281 (Nanotec Plug & Drive)

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Tristan Bruns commit 72b3007951010ce1bbf950e23b19d9839fa905a5 upstream. Signed-off-by: Tristan Bruns Signed-off-by: Johan Hovold Signed-off-by: Greg Kroah-Hartman ---

[PATCH 3.4 001/214] parisc: fix epoll_pwait syscall on compat kernel

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit ab3e55b119c9653b19ea4edffb86f04db867ac98 upstream. This bug was detected with the libio-epoll-perl debian package where the test case IO-Ppoll-compat.t failed.

[PATCH 3.4 020/214] ipv6: Limit mtu to 65575 bytes

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 30f78d8ebf7f514801e71b88a10c948275168518 ] Francois reported that setting big mtu on loopback device could prevent tcp sessions making progress. We do not

[PATCH 3.4 017/214] l2tp: take PMTU from tunnel UDP socket

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Petukhov [ Upstream commit f34c4a35d87949fbb0e0f31eba3c054e9f8199ba ] When l2tp driver tries to get PMTU for the tunnel destination, it uses the pointer to struct sock that represents

[PATCH 3.4 019/214] bonding: Remove debug_fs files when module init fails

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Richter [ Upstream commit db29868653394937037d71dc3545768302dda643 ] Remove the bonding debug_fs entries when the module initialization fails. The debug_fs entries should be removed

[PATCH 3.4 012/214] drm/vmwgfx: correct fb_fix_screeninfo.line_length

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Christopher Friedt commit aa6de142c901cd2d90ef08db30ae87da214bedcc upstream. Previously, the vmwgfx_fb driver would allow users to call FBIOSET_VINFO, but it would not adjust the FINFO

[PATCH 3.4 007/214] Revert "USB: serial: add usbid for dell wwan card to sierra.c"

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 2e01280d2801c72878cf3a7119eac30077b463d5 upstream. This reverts commit 1ebca9dad5abe8b2ed4dbd186cd657fb47c1f321. This device was erroneously added to the sierra driver

[PATCH 3.4 023/214] tg3: update rx_jumbo_pending ring param only when jumbo frames are enabled

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Vecera The patch fixes a problem with dropped jumbo frames after usage of 'ethtool -G ... rx'. Scenario: 1. ip link set eth0 up 2. ethtool -G eth0 rx N # <- This zeroes rx-jumbo 3. ip

[PATCH 3.4 018/214] net: core: dont account for udp header size when computing seglen

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit 6d39d589bb76ee8a1c6cde6822006ae0053decff ] In case of tcp, gso_size contains the tcpmss. For UFO (udp fragmentation offloading) skbs, gso_size is the

[PATCH 3.4 025/214] rtnetlink: Only supply IFLA_VF_PORTS information when RTEXT_FILTER_VF is set

3.4-stable review patch. If anyone has any objections, please let me know. -- From: David Gibson [ Upstream commit c53864fd60227de025cb79e05493b13f69843971 ] Since 115c9b81928360d769a76c632bae62d15206a94a (rtnetlink: Fix problem with buffer allocation), RTM_NEWLINK messages

[PATCH 3.4 021/214] net: ipv4: current group_info should be put after using.

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Wang, Xiaoming" [ Upstream commit b04c46190219a4f845e46a459e3102137b7f6cac ] Plug a group_info refcount leak in ping_init. group_info is only needed during initialization and the code failed

[PATCH 3.4 028/214] net: ipv4: ip_forward: fix inverted local_df test

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit ca6c5d4ad216d5942ae544bbf02503041bd802aa ] local_df means 'ignore DF bit if set', so if its set we're allowed to perform ip fragmentation. This wasn't

[PATCH 3.4 027/214] tcp_cubic: fix the range of delayed_ack

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Yu [ Upstream commit 0cda345d1b2201dd15591b163e3c92bad5191745 ] commit b9f47a3aaeab (tcp_cubic: limit delayed_ack ratio to prevent divide error) try to prevent divide error, but there is

[PATCH 3.4 024/214] rtnetlink: Warn when interfaces information wont fit in our packet

3.4-stable review patch. If anyone has any objections, please let me know. -- From: David Gibson [ Upstream commit 973462bbde79bb827824c73b59027a0aed5c9ca6 ] Without IFLA_EXT_MASK specified, the information reported for a single interface in response to RTM_GETLINK is

[PATCH 3.4 026/214] Revert "macvlan : fix checksums error when we are in bridge mode"

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Yasevich [ Upstream commit f114890cdf84d753f6b41cd0cc44ba51d16313da ] This reverts commit 12a2856b604476c27d85a5f9a57ae1661fc46019. The commit above doesn't appear to be necessary any

[PATCH 3.4 029/214] ipv4: fib_semantics: increment fib_info_cnt after fib_info allocation

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Sergey Popovich [ Upstream commit aeefa1ecfc799b0ea2c4979617f14cecd5cccbfd ] Increment fib_info_cnt in fib_create_info() right after successfuly alllocating fib_info structure, overwise

[PATCH 3.4 032/214] skb: Add inline helper for getting the skb end offset from head

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Duyck [ Upstream commit ec47ea82477404631d49b8e568c71826c9b663ac ] With the recent changes for how we compute the skb truesize it occurs to me we are probably going to have a lot of

[PATCH 3.4 022/214] filter: prevent nla extensions to peek beyond the end of the message

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Krause [ Upstream commit 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 ] The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check for a minimal message length before testing

[PATCH 3.4 043/214] hwpoison, hugetlb: lock_page/unlock_page does not match for handling a free hugepage

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Chen Yucong commit b985194c8c0a130ed155b71662e39f7eaea4876f upstream. For handling a free hugepage in memory failure, the race will happen if another thread hwpoisoned this hugepage

[PATCH 3.4 035/214] futex: Prevent attaching to kernel threads

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit f0d71b3dcb8332f7971b5f2363632573e6d9486a upstream. We happily allow userspace to declare a random kernel thread to be the owner of a user space PI futex. Found while

[PATCH 3.4 034/214] futex: Add another early deadlock detection check

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 866293ee54227584ffcb4a42f69c1f365974ba7f upstream. Dave Jones trinity syscall fuzzer exposed an issue in the deadlock detection code of rtmutex:

[PATCH 3.4 037/214] pata_at91: fix ata_host_activate() failure handling

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bartlomiej Zolnierkiewicz commit 27aa64b9d1bd0d23fd692c91763a48309b694311 upstream. Add missing clk_put() call to ata_host_activate() failure path. Sergei says, "Hm, I have once fixed that

[PATCH 3.4 031/214] ipv4: initialise the itag variable in __mkroute_input

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Li RongQing [ Upstream commit fbdc0ad095c0a299e9abf5d8ac8f58374951149a ] the value of itag is a random value from stack, and may not be initiated by fib_validate_source, which called

[PATCH 3.4 036/214] ftrace/module: Hardcode ftrace_module_init() call into load_module()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" commit a949ae560a511fe4e3adf48fa44fefded93e5c2b upstream. A race exists between module loading and enabling of function tracer. CPU 1

[PATCH 3.4 055/214] USB: Nokia 5300 should be treated as unusual dev

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Forsi commit 6ed07d45d09bc2aa60e27b845543db9972e22a38 upstream. Signed-off-by: Daniele Forsi Signed-off-by: Greg Kroah-Hartman --- drivers/usb/storage/unusual_devs.h |7 +++

[PATCH 3.4 038/214] mm: make fixup_user_fault() check the vma access rights too

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 1b17844b29ae042576bea588164f2f1e9590a8bc upstream. fixup_user_fault() is used by the futex code when the direct user access fails, and the futex code wants it to either

[PATCH 3.4 030/214] act_mirred: do not drop packets when fails to mirror it

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 16c0b164bd24d44db137693a36b428ba28970c62 ] We drop packet unconditionally when we fail to mirror it. This is not intended in some cases. Consdier for kvm guest, we

[PATCH 3.4 054/214] USB: Nokia 305 should be treated as unusual dev

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Victor A. Santos" commit f0ef5d41792a46a1085dead9dfb0bdb2c574638e upstream. Signed-off-by: Victor A. Santos Signed-off-by: Greg Kroah-Hartman --- drivers/usb/storage/unusual_devs.h |7

[PATCH 3.4 039/214] timer: Prevent overflow in apply_slack

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Bohac commit 98a01e779f3c66b0b11cd7e64d531c0e41c95762 upstream. On architectures with sizeof(int) < sizeof (long), the computation of mask inside apply_slack() can be undefined if the

[PATCH 3.4 042/214] x86, mm, hugetlb: Add missing TLB page invalidation for hugetlb_cow()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Anthony Iliopoulos commit 9844f5462392b53824e8b86726e7c33b5ecbb676 upstream. The invalidation is required in order to maintain proper semantics under CoW conditions. In scenarios where a

[PATCH 3.4 057/214] posix_acl: handle NULL ACL in posix_acl_equiv_mode

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 50c6e282bdf5e8dabf8d7cf7b162545a55645fd9 upstream. Various filesystems don't bother checking for a NULL ACL in posix_acl_equiv_mode, and thus can dereference a NULL

[PATCH 3.4 059/214] rtl8192cu: Fix unbalanced irq enable in error path of rtl92cu_hw_init()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 3234f5b06fc3094176a86772cc64baf3decc98fc upstream. Fixes: a53268be0cb9 ('rtlwifi: rtl8192cu: Fix too long disable of IRQs') Signed-off-by: Ben Hutchings Signed-off-by:

[PATCH 3.4 058/214] ARM: 8012/1: kdump: Avoid overflow when converting pfn to physaddr

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Hua commit 8fad87bca7ac9737e413ba5f1656f1114a8c314d upstream. When we configure CONFIG_ARM_LPAE=y, pfn << PAGE_SHIFT will overflow if pfn >= 0x10 in copy_oldmem_page. So use

[PATCH 3.4 046/214] drivercore: deferral race condition fix

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Grant Likely commit 58b116bce13612e5aa6fcd49ecbd4cf8bb59e835 upstream. When the kernel is built with CONFIG_PREEMPT it is possible to reach a state when all modules loaded but some driver

[PATCH 3.4 045/214] hwmon: (emc1403) Support full range of known chip revision numbers

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Josef Gajdusek commit 3a18e1398fc2dc9c32bbdc50664da3a77959a8d1 upstream. The datasheet for EMC1413/EMC1414, which is fully compatible to EMC1403/1404 and uses the same chip identification,

[PATCH 3.4 047/214] hrtimer: Prevent all reprogramming if hang detected

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Stuart Hayes commit 6c6c0d5a1c949d2e084706f9e5fb1fccc175b265 upstream. If the last hrtimer interrupt detected a hang it sets hang_detected=1 and programs the clock event device with a delay to

[PATCH 3.4 048/214] hrtimer: Prevent remote enqueue of leftmost timers

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Leon Ma commit 012a45e3f4af68e86d85cce060c6c2fed56498b2 upstream. If a cpu is idle and starts an hrtimer which is not pinned on that same cpu, the nohz code might target the timer to a

[PATCH 3.4 049/214] hrtimer: Set expiry time before switch_hrtimer_base()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 84ea7fe37908254c3bd90910921f6e1045c1747a upstream. switch_hrtimer_base() calls hrtimer_check_target() which ensures that we do not migrate a timer to a remote cpu if the

[PATCH 3.4 033/214] net-gro: reset skb->truesize in napi_reuse_skb()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit e33d0ba8047b049c9262fdb1fcafb93cb52ceceb ] Recycling skb always had been very tough... This time it appears GRO layer can accumulate skb->truesize adjustments

[PATCH 3.4 053/214] usb: storage: shuttle_usbat: fix discs being detected twice

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Forsi commit df602c2d2358f02c6e49cffc5b49b9daa16db033 upstream. Even if the USB-to-ATAPI converter supported multiple LUNs, this driver would always detect the same physical device or

[PATCH 3.4 041/214] ipmi: Reset the KCS timeout when starting error recovery

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Corey Minyard commit eb6d78ec213e6938559b801421d64714dafcf4b2 upstream. The OBF timer in KCS was not reset in one situation when error recovery was started, resulting in an immediate timeout.

[PATCH 3.4 050/214] md: avoid possible spinning md thread at shutdown.

3.4-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 0f62fb220aa4ebabe8547d3a9ce4a16d3c045f21 upstream. If an md array with externally managed metadata (e.g. DDF or IMSM) is in use, then we should not set safemode==2 at shutdown

[PATCH 3.4 051/214] drm/radeon: fix ATPX detection on non-VGA GPUs

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit e9a4099a59cc598a44006059dd775c25e422b772 upstream. Some newer PX laptops have the pci device class set to DISPLAY_OTHER rather than DISPLAY_VGA. This properly detects ATPX

[PATCH 3.4 052/214] usb: gadget: at91-udc: fix irq and iomem resource retrieval

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jean-Jacques Hiblot commit 886c7c426d465732ec9d1b2bbdda5642fc2e7e05 upstream. When using dt resources retrieval (interrupts and reg properties) there is no predefined order for these resources

[PATCH 3.4 044/214] hwmon: (emc1403) fix inverted store_hyst()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Josef Gajdusek commit 17c048fc4bd95efea208a1920f169547d8588f1f upstream. Attempts to set the hysteresis value to a temperature below the target limit fails with "write error: Numerical result

[PATCH 3.4 070/214] x86-64, modify_ldt: Make support for 16-bit segments a runtime option

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit fa81511bb0bbb2b1aace3695ce869da9762624ff upstream. Checkin: b3b42ac2cbae x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels disabled 16-bit segments on 64-bit

[PATCH 3.4 040/214] ipmi: Fix a race restarting the timer

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bodo Stroesser commit 48e8ac2979920ffa39117e2d725afa3a749bfe8d upstream. With recent changes it is possible for the timer handler to detect an idle interface and not start the timer, but the

[PATCH 3.4 061/214] Documentation: Update stable address in Chinese and Japanese translations

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 98b0f811aade1b7c6e7806c86aa0befd5919d65f upstream. The English and Korean translations were updated, the Chinese and Japanese weren't. Signed-off-by: Geert

[PATCH v2] iio: dac: mcp4902/mcp4912/mcp4922 dac driver

This patch provides an iio device driver for the Microchip MCP49x2 series DACs. Signed-off-by: Michael Welling --- drivers/iio/dac/Kconfig | 10 +++ drivers/iio/dac/Makefile |1 + drivers/iio/dac/mcp49x2.c | 213 + 3 files changed, 224

[PATCH 3.4 062/214] crypto: crypto_wq - Fix late crypto work queue initialization

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Tim Chen commit 130fa5bc81b44b6cc1fbdea3abf6db0da22964e0 upstream. The crypto algorithm modules utilizing the crypto daemon could be used early when the system start up. Using module_init

[PATCH 3.4 063/214] media: media-device: fix infoleak in ioctl media_enum_entities()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: =?UTF-8?q?Salva=20Peir=C3=B3?= commit e6a623460e5fc960ac3ee9f946d3106233fd28d8 upstream. This fixes CVE-2014-1739. Signed-off-by: Salva Peiró Acked-by: Laurent Pinchart Signed-off-by: Mauro

[PATCH 3.4 065/214] NFSD: Call ->set_acl with a NULL ACL structure if no entries

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Kinglong Mee commit aa07c713ecfc0522916f3cd57ac628ea6127c0ec upstream. After setting ACL for directory, I got two problems that caused by the cached zero-length default posix acl. This patch

[PATCH 3.4 056/214] rt2x00: fix beaconing on USB

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit 8834d3608cc516f13e2e510f4057c263f3d2ce42 upstream. When disable beaconing we clear register with beacon and newer set it back, what make we stop send beacons

[PATCH 3.4 067/214] nfsd4: remove lockowner when removing lock stateid

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit a1b8ff4c97b4375d21b6d6c45d75877303f61b3b upstream. The nfsv4 state code has always assumed a one-to-one correspondance between lock stateid's and lockowners even if it

[PATCH 3.4 066/214] nfsd4: warn on finding lockowner without stateids

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 27b11428b7de097c42f205beabb1764f4365443b upstream. The current code assumes a one-to-one lockowner<->lock stateid correspondance. Signed-off-by: J. Bruce Fields

[PATCH 3.4 069/214] ASoC: wm8962: Update register CLASS_D_CONTROL_1 to be non-volatile

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit 44330ab516c15dda8a1e660eeaf0003f84e43e3f upstream. The register CLASS_D_CONTROL_1 is marked as volatile because it contains a bit, DAC_MUTE, which is also mirrored in the

[PATCH 3.4 068/214] percpu: make pcpu_alloc_chunk() use pcpu_mem_free() instead of kfree()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jianyu Zhan commit 5a838c3b60e3a36ade764cf7751b8f17d7c9c2da upstream. pcpu_chunk_struct_size = sizeof(struct pcpu_chunk) + BITS_TO_LONGS(pcpu_unit_pages) * sizeof(unsigned long) It

[PATCH 3.4 074/214] crypto: caam - add allocation failure handling in SPRINTFCAT macro

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Horia Geanta commit 27c5fb7a84242b66bf1e0b2fe6bf40d19bcc5c04 upstream. GFP_ATOMIC memory allocation could fail. In this case, avoid NULL pointer dereference and notify user. Cc: Kim Phillips

[PATCH 3.4 064/214] trace: module: Maintain a valid user count

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Romain Izard commit 098507ae3ec2331476fb52e85d4040c1cc6d0ef4 upstream. The replacement of the 'count' variable by two variables 'incs' and 'decs' to resolve some race conditions during module

[PATCH 3.4 060/214] drm/nouveau/acpi: allow non-optimus setups to load vbios from acpi

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Ilia Mirkin commit a3d0b1218d351c6e6f3cea36abe22236a08cb246 upstream. There appear to be a crop of new hardware where the vbios is not available from PROM/PRAMIN, but there is a valid _ROM

[PATCH 3.4 073/214] i2c: designware: Mask all interrupts during i2c controller enable

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Du, Wenkai" commit 47bb27e78867997040a228328f2a631c3c7f2c82 upstream. There have been "i2c_designware 80860F41:00: controller timed out" errors on a number of Baytrail platforms. The issue is

[PATCH 3.4 075/214] setfacl removes part of ACL when setting POSIX ACLs to Samba

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit b1d93356427be6f050dc55c86eb019d173700af6 upstream. setfacl over cifs mounts can remove the default ACL when setting the (non-default part of) the ACL and vice versa (we

[PATCH 3.4 077/214] ecryptfs: Fix memory leakage in keystore.c

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Geyslan G. Bem" commit 3edc8376c06133e3386265a824869cad03a4efd4 upstream. In 'decrypt_pki_encrypted_session_key' function: Initializes 'payload' pointer and releases it on exit.

[PATCH 3.4 078/214] fs: cachefiles: add support for large files in filesystem caching

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Justin Lecher commit 98c350cda2c14a343d34ea01a3d9c24fea5ec66d upstream. Support the caching of large files. Addresses https://bugzilla.kernel.org/show_bug.cgi?id=31182 Signed-off-by: Justin

[PATCH 3.4 081/214] sched/debug: Limit sd->*_idx range on sysctl

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Namhyung Kim commit 201c373e8e4823700d3160d5c28e1ab18fd1193e upstream. Various sd->*_idx's are used for refering the rq's load average table when selecting a cpu to run. However they can be

[PATCH 3.4 079/214] perf: Fix perf ring buffer memory ordering

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit bf378d341e4873ed928dc3c636252e6895a21f50 upstream. The PPC64 people noticed a missing memory barrier and crufty old comments in the perf ring buffer code. So update all

[PATCH 3.4 071/214] PCI: shpchp: Check bridges secondary (not primary) bus speed

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Marcel Apfelbaum commit 93fa9d32670f5592c8e56abc9928fc194e1e72fc upstream. When a new device is added below a hotplug bridge, the bridge's secondary bus speed and the device's bus speed must

[PATCH 3.4 082/214] sched/debug: Fix sd->*_idx limit range avoiding overflow

3.4-stable review patch. If anyone has any objections, please let me know. -- From: libin commit fd9b86d37a600488dbd80fe60cca46b822bff1cd upstream. Commit 201c373e8e ("sched/debug: Limit sd->*_idx range on sysctl") was an incomplete bug fix. This patch fixes sd->*_idx limit

[PATCH 3.4 072/214] ACPI / blacklist: Add dmi_enable_osi_linux quirk for Asus EEE PC 1015PX

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit f6e6e1b9fee88c90586787b71dc49bb3ce62bb89 upstream. Without this this EEE PC exports a non working WMI interface, with this it exports a working "good old" eeepc_laptop

[PATCH 3.4 084/214] tracing: Keep overwrite in sync between regular and snapshot buffers

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" commit 80902822658aab18330569587cdb69ac1dfdcea8 upstream. Changing the overwrite mode for the ring buffer via the trace option only sets the normal buffer. But the

[PATCH 3.4 086/214] cifs: delay super block destruction until all cifsFileInfo objects are gone

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mateusz Guzik commit 24261fc23db950951760d00c188ba63cc756b932 upstream. cifsFileInfo objects hold references to dentries and it is possible that these will still be around in workqueues when

[PATCH 3.4 080/214] ftrace: Check module functions being traced on reload

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" commit 8c4f3c3fa9681dc549cd35419b259496082fef8b upstream. There's been a nasty bug that would show up and not give much info. The bug displayed the following

[PATCH 3.4 076/214] CIFS: Fix error handling in cifs_push_mandatory_locks

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit e2f2886a824ff0a56da1eaa13019fde86aa89fa6 upstream. Signed-off-by: Pavel Shilovsky Signed-off-by: Steve French [bwh: Backported to 3.2: adjust context] Signed-off-by:

[PATCH 3.4 085/214] VFS: make vfs_fstat() use f[get|put]_light()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit e994defb7b6813ba6fa7a2a36e86d2455ad1dc35 upstream. Use the *_light() versions that properly avoid doing the file user count updates when they are unnecessary.

[PATCH 3.4 089/214] NFSv4.1: integer overflow in decode_cb_sequence_args()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 0439f31c35d1da0b28988b308ea455e38e6a350d upstream. This seems like it could overflow on 32 bits. Use kmalloc_array() which has overflow protection built in.

[PATCH 3.4 088/214] nfsd4: fix xdr decoding of large non-write compounds

3.4-stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 365da4adebb1c012febf81019ad3dc5bb52e2a13 upstream. This fixes a regression from 247500820ebd02ad87525db5d9b199e5b66f6636 "nfsd4: fix decoding of compounds across page

[PATCH 3.4 090/214] nfsd: dont run get_file if nfs4_preprocess_stateid_op return error

3.4-stable review patch. If anyone has any objections, please let me know. -- From: fanchaoting commit b022032e195ffca83d7002d6b84297d796ed443b upstream. we should return error status directly when nfs4_preprocess_stateid_op return error. Signed-off-by: fanchaoting

[PATCH 3.4 083/214] perf: Fix error return code

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit c481420248c6730246d2a1b1773d5d7007ae0835 upstream. Fix to return -ENOMEM in the allocation error case instead of 0 (if pmu_bus_running == 1), as done elsewhere in this

[PATCH 3.4 091/214] NFS: nfs_getaclargs.acl_len is a size_t

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever commit 56d08fef2369d5ca9ad2e1fc697f5379fd8af751 upstream. Squelch compiler warnings: fs/nfs/nfs4proc.c: In function ‘__nfs4_get_acl_uncached’: fs/nfs/nfs4proc.c:3811:14: warning:

[PATCH 3.4 098/214] nfsd: nfsd_open: when dentry_open returns an error do not propagate as struct file

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Harshula Jayasuriya commit e4daf1ffbe6cc3b12aab4d604e627829e93e9914 upstream. The following call chain: nfs4_get_vfs_file -

[PATCH 3.4 104/214] zram: destroy all devices on error recovery path in zram_init()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Liu commit 39a9b8ac9333e4268ecff7da6c9d1ab3823ff243 upstream. On error recovery path of zram_init(), it leaks the zram device object causing the failure. So change create_device() to

[PATCH 3.4 094/214] NFSv4.1: Handle NFS4ERR_DELAY when resetting the NFSv4.1 session

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit c489ee290bdbbace6bb63ebe6ebd4dd605819495 upstream. NFS4ERR_DELAY is a legal reply when we call DESTROY_SESSION. It usually means that the server is busy handling an

[PATCH 3.4 093/214] NFSv4.1: Dont decode skipped layoutgets

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Weston Andros Adamson commit 085b7a45c63d3da5be155faab9249a5cab224561 upstream. layoutget's prepare hook can call rpc_exit with status = NFS4_OK (0). Because of this, nfs4_proc_layoutget can't

[PATCH 3.4 097/214] md/raid10: fix "enough" function for detecting if array is failed.

3.4-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 80b4812407c6b1f66a4f2430e69747a13f010839 upstream. The 'enough' function is written to work with 'near' arrays only in that is implicitly assumes that the offset from one

[PATCH 3.4 099/214] dm snapshot: avoid snapshot space leak on crash

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 230c83afdd9cd384348475bea1e14b80b3b6b1b8 upstream. There is a possible leak of snapshot space in case of crash. The reason for space leaking is that chunks in the

[PATCH 3.4 092/214] NFSv4.1: Fix a race in pNFS layoutcommit

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit a073dbff359f4741013ae4b8395f5364c5e00b48 upstream. We need to clear the NFS_LSEG_LAYOUTCOMMIT bits atomically with the NFS_INO_LAYOUTCOMMIT bit, otherwise we may end up

  1   2   3   4   5   6   7   8   9   10   >