[PATCH 3.10 06/53] iwlwifi: pcie: disable the SCD_BASE_ADDR when we resume from WoWLAN

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit cd8f438405032ac8ff88bd8f2eca5e0c0063b14b upstream. The base address of the scheduler in the device's memory (SRAM) comes from two different sources. The periphery

[PATCH 3.10 04/53] xfs: set superblock buffer type correctly

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit 3443a3bca54588f43286b725d8648d33a38c86f1 upstream. When the superblock is modified in a transaction, the commonly modified fields are not actually copied to the superblock

[PATCH 3.10 32/53] tty: Prevent untrappable signals from malicious program

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Hurley commit 37480a05685ed5b8e1b9bf5e5c53b5810258b149 upstream. Commit 26df6d13406d1a5 ("tty: Add EXTPROC support for LINEMODE") allows a process which has opened a pty master to send

Re: [PATCH] x86: Unbreak early processor microcode loading

On 04/03/2015 00:38, Borislav Petkov wrote: On Tue, Mar 03, 2015 at 11:10:44PM +0800, Daniel J Blueman wrote: The changes in 871b72dd "x86: microcode: use smp_call_function_single instead of set_cpus_allowed, cleanup of synchronization logic" introduced a check that prevents built-in microcode

[PATCH 3.10 33/53] USB: cp210x: add ID for RUGGEDCOM USB Serial Console

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Lennart Sorensen commit a6f0331236fa75afba14bbcf6668d42cebb55c43 upstream. Added the USB serial console device ID for Siemens Ruggedcom devices which have a USB port for their serial console.

[PATCH 3.10 00/53] 3.10.71-stable review

This is the start of the stable review cycle for the 3.10.71 release. There are 53 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 Mar 6 05:45:30 UTC 2015. Anything

[PATCH 3.10 07/53] iwlwifi: mvm: validate tid and sta_id in ba_notif

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Eyal Shapira commit 2cee4762c528a9bd2cdff793197bf591a2196c11 upstream. These are coming from the FW and are used to access arrays. Bad values can cause an out of bounds access so discard such

[PATCH 3.10 37/53] ARM: pxa: add regulator_has_full_constraints to corgi board file

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Eremin-Solenikov commit 271e80176aae4e5b481f4bb92df9768c6075bbca upstream. Add regulator_has_full_constraints() call to corgi board file to let regulator core know that we do not have

[PATCH 3.10 48/53] metag: Fix KSTK_EIP() and KSTK_ESP() macros

3.10-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit c2996cb29bfb73927a79dc96e598a718e843f01a upstream. The KSTK_EIP() and KSTK_ESP() macros should return the user program counter (PC) and stack pointer (A0StP) of the given

[PATCH 3.10 47/53] gpio: tps65912: fix wrong container_of arguments

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Saenz Julienne commit 2f97c20e5f7c3582c7310f65a04465bfb0fd0e85 upstream. The gpio_chip operations receive a pointer the gpio_chip struct which is contained in the driver's private

[PATCH 3.10 08/53] iwlwifi: mvm: fix failure path when power_update fails in add_interface

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Luciano Coelho commit fd66fc1cafd72ddf27dbec3a5e29e99839d1bc84 upstream. When iwl_mvm_power_update_mac() is called, we have already added the mac context, so if this call fails we should

[PATCH 3.10 46/53] arm64: compat Fix siginfo_t -> compat_siginfo_t conversion on big endian

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit 9d42d48a342aee208c1154696196497fdc556bbf upstream. The native (64-bit) sigval_t union contains sival_int (32-bit) and sival_ptr (64-bit). When a compat application

[PATCH 3.10 09/53] iwlwifi: mvm: always use mac color zero

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Luciano Coelho commit 5523d11cc46393a1e61b7ef4a0b2d4e7ed9521e4 upstream. We don't really need to use different mac colors when adding mac contexts, because they're not used anywhere. In

[PATCH 3.10 49/53] md/raid5: Fix livelock when array is both resyncing and degraded.

3.10-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 26ac107378c4742978216be1005b7291b799c7b2 upstream. Commit a7854487cd7128a30a7f4f5259de9f67d5efb95f: md: When RAID5 is dirty, force reconstruct-write instead of

[PATCH 3.10 38/53] ARM: pxa: add regulator_has_full_constraints to poodle board file

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Eremin-Solenikov commit 9bc78f32c2e430aebf6def965b316aa95e37a20c upstream. Add regulator_has_full_constraints() call to poodle board file to let regulator core know that we do not have

[PATCH 3.10 39/53] kdb: fix incorrect counts in KDB summary command output

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Jay Lan commit 146755923262037fc4c54abc28c04b1103f3cc51 upstream. The output of KDB 'summary' command should report MemTotal, MemFree and Buffers output in kB. Current codes report in unit of

[PATCH 3.10 52/53] blk-throttle: check stats_cpu before reading it from sysfs

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Thadeu Lima de Souza Cascardo commit 045c47ca306acf30c740c285a77a4b4bda6be7c5 upstream. When reading blkio.throttle.io_serviced in a recently created blkio cgroup, it's possible to race

[PATCH 3.10 51/53] jffs2: fix handling of corrupted summary length

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Chen Jie commit 164c24063a3eadee11b46575c5482b2f1417be49 upstream. sm->offset maybe wrong but magic maybe right, the offset do not have CRC. Badness at c00c7580 [verbose debug info

[PATCH 3.10 43/53] KVM: MIPS: Dont leak FPU/DSP to guest

3.10-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit f798217dfd038af981a18bbe4bc57027a08bb182 upstream. The FPU and DSP are enabled via the CP0 Status CU1 and MX bits by kvm_mips_set_c0_status() on a guest exit, presumably in

[PATCH 3.10 53/53] x86, mm/ASLR: Fix stack randomization on 64-bit systems

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Hector Marco-Gisbert commit 4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 upstream. The issue is that the stack for processes is not properly randomized on 64 bit architectures due to an integer

[PATCH 3.10 41/53] ARC: fix page address calculation if PAGE_OFFSET != LINUX_LINK_BASE

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit 06f34e1c28f3608b0ce5b310e41102d3fe7b65a1 upstream. We used to calculate page address differently in 2 cases: 1. In virt_to_page(x) we do --->8--- mem_map + (x -

[PATCH 3.10 44/53] KVM: x86: update masterclock values on TSC writes

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Tosatti commit 7f187922ddf6b67f2999a76dcb71663097b75497 upstream. When the guest writes to the TSC, the masterclock TSC copy must be updated as well along with the TSC_OFFSET update,

[PATCH 3.10 40/53] ntp: Fixup adjtimex freq validation on 32-bit systems

3.10-stable review patch. If anyone has any objections, please let me know. -- From: John Stultz commit 29183a70b0b828500816bd794b3fe192fce89f73 upstream. Additional validation of adjtimex freq values to avoid potential multiplication overflows were added in commit

[PATCH 3.14 01/73] Bluetooth: ath3k: workaround the compatibility issue with xHCI controller

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Adam Lee commit c561a5753dd631920c4459a067d22679b3d110d6 upstream. BugLink: https://bugs.launchpad.net/bugs/1400215 ath3k devices fail to load firmwares on xHCI buses, but work well on EHCI,

[PATCH 3.10 42/53] KVM: s390: floating irqs: fix user triggerable endless loop

3.10-stable review patch. If anyone has any objections, please let me know. -- From: David Hildenbrand commit 8e2207cdd087ebb031e9118d1fd0902c6533a5e5 upstream. If a vm with no VCPUs is created, the injection of a floating irq leads to an endless loop in the kernel. Let's

[PATCH 3.10 36/53] vt: provide notifications on selection changes

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Pitre commit 19e3ae6b4f07a87822c1c9e7ed99d31860e701af upstream. The vcs device's poll/fasync support relies on the vt notifier to signal changes to the screen content. Notifier

[PATCH 3.14 10/73] HID: i2c-hid: Limit reads to wMaxInputLength bytes for input events

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Seth Forshee commit 6d00f37e49d95e640a3937a4a1ae07dbe92a10cb upstream. d1c7e29e8d27 (HID: i2c-hid: prevent buffer overflow in early IRQ) changed hid_get_input() to read ihid->bufsize bytes,

[PATCH 3.10 45/53] hx4700: regulator: declare full constraints

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Martin Vajnar commit a52d209336f8fc7483a8c7f4a8a7d2a8e1692a6c upstream. Since the removal of CONFIG_REGULATOR_DUMMY option, the touchscreen stopped working. This patch enables the

Re: [PATCH] video: mxsfb: Make sure axi clock is enabled when accessing registers

On Wed, Mar 04, 2015 at 01:58:55PM +0800, Liu Ying wrote: > The LCDIF engines embedded in i.MX6sl and i.MX6sx SoCs need the axi clock > as the engine's system clock. The clock should be enabled when accessing > LCDIF registers, otherwise the kernel would hang up. We should also keep > the clock

[PATCH 3.14 02/73] xfs: ensure buffer types are set correctly

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit 0d612fb570b71ea2e49554a770cff4c489018b2c upstream. Jan Kara reported that log recovery was finding buffers with invalid types in them. This should not happen, and

[PATCH 3.14 03/73] xfs: inode unlink does not set AGI buffer type

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit f19b872b086711bb4b22c3a0f52f16aa920bcc61 upstream. This leads to log recovery throwing errors like: XFS (md0): Mounting V5 Filesystem XFS (md0): Starting recovery

[PATCH 3.14 04/73] xfs: set superblock buffer type correctly

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit 3443a3bca54588f43286b725d8648d33a38c86f1 upstream. When the superblock is modified in a transaction, the commonly modified fields are not actually copied to the superblock

[PATCH 3.14 08/73] iwlwifi: mvm: fix failure path when power_update fails in add_interface

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Luciano Coelho commit fd66fc1cafd72ddf27dbec3a5e29e99839d1bc84 upstream. When iwl_mvm_power_update_mac() is called, we have already added the mac context, so if this call fails we should

[PATCH 3.14 11/73] PCI: Generate uppercase hex for modalias var in uevent

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda Delgado commit 145b3fe579db66fbe999a2bc3fd5b63dffe9636d upstream. Some implementations of modprobe fail to load the driver for a PCI device automatically because the

[PATCH 3.14 09/73] iwlwifi: mvm: always use mac color zero

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Luciano Coelho commit 5523d11cc46393a1e61b7ef4a0b2d4e7ed9521e4 upstream. We don't really need to use different mac colors when adding mac contexts, because they're not used anywhere. In

[PATCH 3.14 00/73] 3.14.35-stable review

This is the start of the stable review cycle for the 3.14.35 release. There are 73 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 Mar 6 05:52:50 UTC 2015. Anything

[PATCH 3.14 28/73] MIPS: KVM: Deliver guest interrupts after local_irq_disable()

3.14-stable review patch. If anyone has any objections, please let me know. -- From: James Hogan commit 044f0f03eca0110e1835b2ea038a484b93950328 upstream. When about to run the guest, deliver guest interrupts after disabling host interrupts. This should prevent an hrtimer

[PATCH 3.14 05/73] fsnotify: fix handling of renames in audit

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 6ee8e25fc3e916193bce4ebb43d5439e1e2144ab upstream. Commit e9fd702a58c4 ("audit: convert audit watches to use fsnotify instead of inotify") broke handling of renames in audit.

[PATCH 3.14 07/73] iwlwifi: mvm: validate tid and sta_id in ba_notif

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Eyal Shapira commit 2cee4762c528a9bd2cdff793197bf591a2196c11 upstream. These are coming from the FW and are used to access arrays. Bad values can cause an out of bounds access so discard such

[PATCH 3.14 23/73] megaraid_sas: disable interrupt_mask before enabling hardware interrupts

3.14-stable review patch. If anyone has any objections, please let me know. -- From: "sumit.sax...@avagotech.com" commit c2ced1719a1b903350955a511e1666e6d05a7f5b upstream. Update driver "mask_interrupts" before enable/disable hardware interrupt in order to avoid missing

[PATCH 3.14 06/73] iwlwifi: pcie: disable the SCD_BASE_ADDR when we resume from WoWLAN

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit cd8f438405032ac8ff88bd8f2eca5e0c0063b14b upstream. The base address of the scheduler in the device's memory (SRAM) comes from two different sources. The periphery

Re: [PATCH 5/8] zram: add dynamic device add/remove functionality

On (03/04/15 16:29), Sergey Senozhatsky wrote: > > Why should user specifiy zram-device id to create? > > > > one of them will create a new device, the other one will get -EEXIST. > quite decent. > > I'm not sure I know how to return device id back to use space in > response to > echo -1

[PATCH 3.14 29/73] mm/hugetlb: pmd_huge() returns true for non-present hugepage

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Naoya Horiguchi commit cbef8478bee55775ac312a574aad48af7bb9cf9f upstream. Migrating hugepages and hwpoisoned hugepages are considered as non-present hugepages, and they are referenced via

[PATCH 3.14 34/73] ARM: dts: am335x-bone*: usb0 is hardwired for peripheral

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Robert Nelson commit 67fd14b3eca63b14429350e9eadc5fab709a8821 upstream. Fixes: http://bugs.elinux.org/issues/127 the bb.org community was seeing random reboots before this change.

[PATCH 3.14 26/73] mmc: sdhci-pxav3: fix setting of pdata->clk_delay_cycles

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Jisheng Zhang commit 14460dbaf7a5a0488963fdb8232ad5c8a8cca7b7 upstream. Current code checks "clk_delay_cycles > 0" to know whether the optional "mrvl,clk_delay_cycles" is set or not. But

[PATCH 3.14 30/73] tracing: Fix unmapping loop in tracing_mark_write

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Vikram Mulukutla commit 7215853e985a4bef1a6c14e00e89dfec84f1e457 upstream. Commit 6edb2a8a385f0cdef51dae37ff23e74d76d8a6ce introduced an array map_pages that contains the addresses returned

Re: [PATCH 11/15] twl4030_charger: enable manual enable/disable of usb charging.

On Mon, 2 Mar 2015 22:03:42 +0100 Pavel Machek wrote: > On Tue 2015-02-24 15:33:52, NeilBrown wrote: > > 'off' or 'auto' to > > > > /sys/class/power/twl4030_usb/mode > > > > will now enable or disable charging from USB port. Normally this is > > enabled on 'plug' and disabled on 'unplug'. >

[PATCH 3.14 33/73] ARM: dts: tegra20: fix GR3D, DSI unit and reg base addresses

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit de47699d005996b41cea590c6098078ac12058be upstream. Commit 58ecb23f64ee ("ARM: tegra: add missing unit addresses to DT") added unit address and changed reg base for GR3D

[PATCH 3.14 27/73] nfs: dont call blocking operations while !TASK_RUNNING

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Layton commit 6ffa30d3f734d4f6b478081dfc09592021028f90 upstream. Bruce reported seeing this warning pop when mounting using v4.1: [ cut here ] WARNING:

[PATCH 3.14 35/73] tpm_tis: verify interrupt during init

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Scot Doyle commit 448e9c55c12d6bd4fa90a7e31d802e045666d7c8 upstream. Some machines, such as the Acer C720 and Toshiba CB35, have TPMs that do not send IRQs while also having an ACPI TPM entry

[PATCH 3.14 36/73] TPM: Add new TPMs to the tail of the list to prevent inadvertent change of dev

3.14-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit 398a1e71dc827b994b7f2f56c7c2186fea7f8d75 upstream. Add newly registered TPMs to the tail of the list, not the beginning, so that things that are specifying TPM_ANY_NUM

[PATCH 3.14 32/73] ARM: DRA7: hwmod: Fix boot crash with DEBUG_LL enabled on UART3

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 1c7e36bfc3e2fb2df5e2d1989a4b6fb9055a0f9b upstream. With commit '7dedd34: ARM: OMAP2+: hwmod: Fix a crash in _setup_reset() with DEBUG_LL' we moved from parsing cmdline to

Re: [PATCH v2] drm/i915: gen4: work around hang during hibernation

On Mon, 02 Mar 2015, Bjørn Mork wrote: > Jani Nikula writes: > >> On Mon, 02 Mar 2015, Imre Deak wrote: >>> Bjørn reported that his machine hang during hibernation and eventually >>> bisected the problem to the following commit: >>> >>> commit da2bc1b9db3351addd293e5b82757efe1f77ed1d >>>

[PATCH 3.14 31/73] ARM: 8284/1: sa1100: clear RCSR_SMR on resume

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Eremin-Solenikov commit e461894dc2ce7778ccde1c3483c9b15a85a7fc5f upstream. StrongARM core uses RCSR SMR bit to tell to bootloader that it was reset by entering the sleep mode. After we

[PATCH 3.14 38/73] tpm: Fix NULL return in tpm_ibmvtpm_get_desired_dma

3.14-stable review patch. If anyone has any objections, please let me know. -- From: "Hon Ching (Vicky) Lo" commit 84eb186bc37c0900b53077ca21cf6dd15823a232 upstream. There was an oops in tpm_ibmvtpm_get_desired_dma, which caused kernel panic during boot when vTPM is enabled

[PATCH 3.14 41/73] NFSv4.1: Fix a kfree() of uninitialised pointers in decode_cb_sequence_args

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit d8ba1f971497c19cf80da1ea5391a46a5f9fbd41 upstream. If the call to decode_rc_list() fails due to a memory allocation error, then we need to truncate the array size to

Re: timerfd waking up before timer really expires

Lucas De Marchi wrote: > I was debugging my application and noticed that a timerfd event was being > triggered *before* the timer expires. > > I reduced the scope of the program to test a single timerfd and measure the > difference in the result of clock_gettime() between two reads. > >

[PATCH 3.14 15/73] cpufreq: s3c: remove incorrect __init annotations

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 61882b63171736571e1139ab5aa929e3bb336016 upstream. The two functions s3c2416_cpufreq_driver_init and s3c_cpufreq_register are marked init but are called from a context

Re: [PATCH] Staging: fbtft: move externs to header file

On Tue, Mar 03, 2015 at 08:04:10PM +0100, Noralf Trønnes wrote: > These functions are defined in fbtft-sysfs.c and internal to the > fbtft module. > I think it's better to put them in an 'internal.h' file. > The fbtft.h file will eventually live in include/linux/fbtft.h or > something like that.

[PATCH 3.14 39/73] tpm/tpm_i2c_stm_st33: Fix potential bug in tpm_stm_i2c_send

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Ricard commit 1ba3b0b6f218072afe8372d12f1b6bf26a26008e upstream. When sending data in tpm_stm_i2c_send, each loop iteration send buf. Send buf + i instead as the goal of this for

[PATCH 3.14 42/73] iscsi-target: Drop problematic active_ts_list usage

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit 3fd7b60f2c7418239d586e359e0c6d8503e10646 upstream. This patch drops legacy active_ts_list usage within iscsi_target_tq.c code. It was originally used to track the

[PATCH 3.14 16/73] xen/manage: Fix USB interaction issues when resuming

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ross Lagerwall commit 72978b2fe2f2cdf9f319c6c6dcdbe92b38de2be2 upstream. Commit 61a734d305e1 ("xen/manage: Always freeze/thaw processes when suspend/resuming") ensured that userspace

[PATCH 3.14 37/73] char: tpm: Add missing error check for devm_kzalloc

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Kiran Padwal commit bb95cd34ba4c9467114acc78eeddd53ab1c10085 upstream. Currently these driver are missing a check on the return value of devm_kzalloc, which would cause a NULL pointer

[PATCH 3.14 43/73] cfq-iosched: handle failure of cfq group allocation

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 69abaffec7d47a083739b79e3066cb3730eba72e upstream. Cfq_lookup_create_cfqg() allocates struct blkcg_gq using GFP_ATOMIC. In cfq_find_alloc_queue() possible

[PATCH 3.14 49/73] USB: fix use-after-free bug in usb_hcd_unlink_urb()

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit c99197902da284b4b723451c1471c45b18537cde upstream. The usb_hcd_unlink_urb() routine in hcd.c contains two possible use-after-free errors. The dev_dbg() statement at the end

[PATCH 3.14 48/73] USB: cp210x: add ID for RUGGEDCOM USB Serial Console

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Lennart Sorensen commit a6f0331236fa75afba14bbcf6668d42cebb55c43 upstream. Added the USB serial console device ID for Siemens Ruggedcom devices which have a USB port for their serial console.

Re: [PATCH 3.14 58/73] KVM: MIPS: Dont leak FPU/DSP to guest

Hi Greg, On Tue, Mar 03, 2015 at 10:13:26PM -0800, Greg Kroah-Hartman wrote: > 3.14-stable review patch. If anyone has any objections, please let me know. > > -- > > From: James Hogan > > commit f798217dfd038af981a18bbe4bc57027a08bb182 upstream. > > The FPU and DSP are

[PATCH 3.14 50/73] usb: core: buffer: smallest buffer should start at ARCH_DMA_MINALIGN

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 5efd2ea8c9f4f12916ffc8ba636792ce052f6911 upstream. the following error pops up during "testusb -a -t 10" | musb-hdrc musb-hdrc.1.auto: dma_pool_free

[PATCH 3.14 46/73] tty: Prevent untrappable signals from malicious program

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Hurley commit 37480a05685ed5b8e1b9bf5e5c53b5810258b149 upstream. Commit 26df6d13406d1a5 ("tty: Add EXTPROC support for LINEMODE") allows a process which has opened a pty master to send

[PATCH 3.14 51/73] vt: provide notifications on selection changes

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Pitre commit 19e3ae6b4f07a87822c1c9e7ed99d31860e701af upstream. The vcs device's poll/fasync support relies on the vt notifier to signal changes to the screen content. Notifier

[PATCH] Staging: fbtft: add header for internal functions

Remove extern keyword from function prototypes to suppress warning from checkpatch.pl with --strict option: https://lkml.org/lkml/2013/7/23/422 fbtft maintainer Noralf Tronnes advised these functions are internal to this module & suggested moving these prototypes to new internal.h file. He also

[PATCH 3.14 44/73] cfq-iosched: fix incorrect filing of rt async cfqq

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Moyer commit c6ce194325cef342313e3d27620411ce90a89c50 upstream. Hi, If you can manage to submit an async write as the first async I/O from the context of a process with realtime

Re: node-hotplug: is memset 0 safe in try_offline_node()?

On 2015/3/4 11:56, Gu Zheng wrote: > Hi Xishi, > On 03/04/2015 10:52 AM, Xishi Qiu wrote: > >> On 2015/3/4 10:22, Xishi Qiu wrote: >> >>> On 2015/3/3 18:20, Gu Zheng wrote: >>> Hi Xishi, On 03/03/2015 11:30 AM, Xishi Qiu wrote: > When hot-remove a numa node, we will clear

[PATCH 3.14 47/73] tty/serial: at91: fix error handling in atmel_serial_probe()

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Cyrille Pitchen commit 6fbb9bdf0f3fbe23aeff806489791aa876adaffb upstream. -EDEFER error wasn't handle properly by atmel_serial_probe(). As an example, when atmel_serial_probe() is called for

[PATCH 3.14 19/73] ALSA: hdspm - Constrain periods to 2 on older cards

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Knoth commit f0153c3d948c1764f6c920a0675d86fc1d75813e upstream. RME RayDAT and AIO use a fixed buffer size of 16384 samples. With period sizes of 32-4096, this translates to 4-512

[PATCH 3.14 18/73] ALSA: off by one bug in snd_riptide_joystick_probe()

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit e4940626defdf6c92da1052ad3f12741c1a28c90 upstream. The problem here is that we check: if (dev >= SNDRV_CARDS) Then we increment "dev". if

[PATCH 3.14 20/73] power_supply: 88pm860x: Fix leaked power supply on probe fail

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 24727b45b484e8937dcde53fa8d1aa70ac30ec0c upstream. Driver forgot to unregister power supply if request_threaded_irq() failed in probe(). In such case the memory

Re: 4.0.0-rc1-next-20150303: cgroup: BUG: unable to handle kernel NULL pointer dereference at

Caused by this commit: 295458e67284f57d1 cgroup: call cgroup_subsys->bind on cgroup subsys initialization cpuset_init() is called after cgroup_init(), so when cgroup_init() calls cpuset_bind() top_cpuset.cpus_allowed is NULL. I'll send out a fix soon. On 2015/3/4 13:17, Ming Lei wrote: > Hi

[PATCH 3.14 22/73] power: gpio-charger: balance enable/disable_irq_wake calls

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Eremin-Solenikov commit faeed51bb65ce0241052d8dc24ac331ade12e976 upstream. enable_irq_wakeup returns 0 in case it correctly enabled the IRQ to generate the wakeup event (and thus

[PATCH 3.14 45/73] axonram: Fix bug in direct_access

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Matthew Wilcox commit 91117a20245b59f70b563523edbf998a62fc6383 upstream. The 'pfn' returned by axonram was completely bogus, and has been since 2008. Signed-off-by: Matthew Wilcox

[PATCH 3.14 17/73] [media] lmedm04: Fix usb_submit_urb BOGUS urb xfer, pipe 1 != type 3 in interrupt urb

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Malcolm Priestley commit 15e1ce33182d1d5dbd8efe8d382b9352dc857527 upstream. A quirk of some older firmwares that report endpoint pipe type as PIPE_BULK but the endpoint otheriwse functions as

[PATCH v2 05/15] x86, kaslr: consolidate the mem_avoid filling

Now ZO sit end of the buffer, we can find out where is ZO text and data/bss etc. [input, input+input_size) is copied compressed kernel, not the whole ZO. [output, output+init_size) is the buffer for VO. [input+input_size, output+init_size) is [_text, _end) for ZO. that will be first range in

[PATCH v2 06/15] x86, boot: split kernel_ident_mapping_init into another file

We need to include that in boot::decompress_kernel stage to set new mapping. Signed-off-by: Yinghai Lu --- arch/x86/include/asm/page.h | 5 +++ arch/x86/mm/ident_map.c | 74 + arch/x86/mm/init_64.c | 74

[PATCH v2 04/15] x86, kaslr: get kaslr_enabled back correctly

commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") is using address as value for kaslr_enabled. That will random kaslr_enabled get that set or cleared. Will have problem for system really have kaslr enabled. -v2: update changelog. Fixes: f47233c2d34f ("x86/mm/ASLR:

[PATCH v2 01/15] x86, kaslr: Use init_size instead of run_size

commit e6023367d779 ("x86, kaslr: Prevent .bss from overlaping initrd") introduced one run_size for kaslr. We do not need to have home grown run_size. We should use real runtime size (include copy/decompress) aka init_size Please check arch/x86/boot/header.S about init_size for detail. Fixes:

[PATCH v2 07/15] x86, kaslr, 64bit: set new or extra ident_mapping

aslr will support to put random VO above 4G, so we need to set ident mapping for the range even we come from startup_32 path. At the same time, when boot from 64bit bootloader, bootloader will set ident mapping, and boot via ZO startup_64. Then pages for pagetable need to be avoided when

[PATCH v2 02/15] x86, boot: move ZO to end of buffer

bp found data from boot stage can not be used kernel stage. Actually those data area is overlapped with VO kernel bss stage, and clear_bss() clear them before code in arch/x86/kernel/setup.c access them. To make the data survive that later, we should avoid the overlapping. At first move

[PATCH v2 03/15] x86, boot: keep data from ZO boot stage to VO kernel stage.

bp found data from boot stage can not be used kernel stage. Actually those data area is overlapped with kernel bss stage, and clear_bss() clear them before code in arch/x86/kernel/setup.c access them. To make the data survive that later, we should avoid the overlapping. We already move

[PATCH v2 00/15] x86, boot: clean up kasl and setup_data handling

patch 1-7: are kasl related. 1. make ZO: arch/x86/boot/compressed/vmlinux data region is not overwritten by final VO: vmlinux after decompress. so could pass data from ZO to VO 2. create new ident mapping for kasl 64bit, so we can cover above 4G random kernel base, also don't need to track

[PATCH 3.14 63/73] gpio: tps65912: fix wrong container_of arguments

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Saenz Julienne commit 2f97c20e5f7c3582c7310f65a04465bfb0fd0e85 upstream. The gpio_chip operations receive a pointer the gpio_chip struct which is contained in the driver's private

[PATCH 3.14 62/73] gpiolib: of: allow of_gpiochip_find_and_xlate to find more than one chip per node

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans Holmberg commit 9cf75e9e4ddd587ac12e88e8751c358b7b27e95f upstream. The change: 7b8792bbdffdff3abda704f89c6a45ea97afdc62 gpiolib: of: Correct error handling in of_get_named_gpiod_flags

[PATCH v2 12/15] x86: kill not used setup_data handling code

Cc: Matt Fleming Signed-off-by: Yinghai Lu --- arch/x86/kernel/kdebugfs.c | 142 - arch/x86/kernel/setup.c| 17 -- 2 files changed, 159 deletions(-) diff --git a/arch/x86/kernel/kdebugfs.c b/arch/x86/kernel/kdebugfs.c index dc1404b..c8ca86c

[PATCH v2 11/15] x86, boot: Add add_pci handler for SETUP_PCI

Let it reserve setup_data, and keep it's own list. Also clear the hdr.setup_data, as all handler will handle or reserve setup_data locally already. Cc: Bjorn Helgaas Cc: Matt Fleming Cc: linux-...@vger.kernel.org Signed-off-by: Yinghai Lu --- arch/x86/include/asm/pci.h | 2 ++

[PATCH v2 14/15] x86, boot: copy rom to kernel space

As EFI stub code could put them high when on 32bit or with exactmap= on 64bit conf. Check is the range is mapped, otherwise allocate new one and have the rom data copied. So we could really avoid ioremap. Signed-off-by: Yinghai Lu --- arch/x86/pci/common.c | 47

[PATCH v2 13/15] x86, pci: convert SETUP_PCI data to list

So we could avoid ioremap every time later. Cc: Bjorn Helgaas Cc: linux-...@vger.kernel.org Signed-off-by: Yinghai Lu --- arch/x86/include/asm/pci.h | 2 ++ arch/x86/kernel/setup.c| 1 + arch/x86/pci/common.c | 77 +- 3 files changed, 65

Re: [Xen-devel] kasan_map_early_shadow() on Xen

>>> On 04.03.15 at 05:53, wrote: > On 03/03/2015 08:20 PM, Luis R. Rodriguez wrote: >> On Tue, Mar 3, 2015 at 2:06 AM, David Vrabel wrote: >>> On 03/03/15 09:40, Luis R. Rodriguez wrote: if X86_64 && SPARSEMEM_VMEMMAP Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to

[PATCH v2 08/15] x86: Kill E820_RESERVED_KERN

Now we are using memblock to do early resource reserver/allocation instead of using e820 map directly, and setup_data is reserved in memblock early already. Also kexec will generate setup_data and pass pointer to second kernel, so second kernel will reserve setup_data by their own. We can kill

[PATCH v2 09/15] x86, efi: copy SETUP_EFI data and access directly

the copy will be in __initdata, and it is small. We can use pointer to access the setup_data instead of keeping on early_memmap and early_memunmap everywhere. Cc: Matt Fleming Cc: linux-...@vger.kernel.org Signed-off-by: Yinghai Lu --- arch/x86/include/asm/efi.h | 2 +-

Re: [RFC 1/3] x86: Add this_cpu_sp0() to read sp0 for the current cpu

* Andy Lutomirski wrote: > We currently store references to the top of the kernel stack in > multiple places: kernel_stack (with an offset) and > init_tss.x86_tss.sp0 (no offset). The latter is defined by hardware > and is a clean canonical way to find the top of the stack. Add an Btw.,

[PATCH v2 15/15] x86, pci: export SETUP_PCI data via sysfs

So we could let kexec-tools to rebuild SETUP_PCI and pass it to second kernel. Now kexec-tools already build SETUP_EFI and SETUP_E820EXT. Cc: Bjorn Helgaas Cc: linux-...@vger.kernel.org Signed-off-by: Yinghai Lu --- arch/x86/pci/common.c | 175

<    7   8   9   10   11   12   13   14   15   16   >