3.10.60-stable review
Subsystems (4)
Greg Kroah-Hartman
maintainercover 3.10.60-stable review
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.60-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.10.60-rc1
Ilya Dryomov <[email protected]>
libceph: ceph-msgr workqueue needs a resque worker
Chris Mason <[email protected]>
Btrfs: fix kfree on list_head in btrfs_lookup_csums_range error cleanup
Grant Likely <[email protected]>
of: Fix overflow bug in string property parsing functions
Yijing Wang <[email protected]>
sysfs: driver core: Fix glue dir race condition by gdp_mutex
Wolfram Sang <[email protected]>
i2c: at91: don't account as iowait
Hans de Goede <[email protected]>
acer-wmi: Add acpi_backlight=video quirk for the Acer KAV80
Jan Kara <[email protected]>
rbd: Fix error recovery in rbd_obj_read_sync()
Alex Deucher <[email protected]>
drm/radeon: remove invalid pci id
Felipe Balbi <[email protected]>
usb: gadget: udc: core: fix kernel oops with soft-connect
Felipe Balbi <[email protected]>
usb: gadget: function: acm: make f_acm pass USB20CV Chapter9
Felipe Balbi <[email protected]>
usb: dwc3: gadget: fix set_halt() bug with pending transfers
Ondrej Kozina <[email protected]>
crypto: algif - avoid excessive use of socket buffer in skcipher
Jan Kara <[email protected]>
mm: Remove false WARN_ON from pagecache_isize_extended()
Andy Lutomirski <[email protected]>
x86, apic: Handle a bad TSC more gracefully
Mathias Krause <[email protected]>
posix-timers: Fix stack info leak in timer_create()
Karl Beldan <[email protected]>
mac80211: fix typo in starting baserate for rts_cts_rate_idx
Imre Deak <[email protected]>
PM / Sleep: fix recovery during resuming from hibernation
Peter Hurley <[email protected]>
tty: Fix high cpu load if tty is unreleaseable
Jan Kara <[email protected]>
quota: Properly return errors from dquot_writeback_dquots()
Jan Kara <[email protected]>
ext3: Don't check quota format when there are no quota files
J. Bruce Fields <[email protected]>
nfsd4: fix crash on unknown operation number
Jason Baron <[email protected]>
cpc925_edac: Report UE events properly
Jason Baron <[email protected]>
e7xxx_edac: Report CE events properly
Jason Baron <[email protected]>
i3200_edac: Report CE events properly
Jason Baron <[email protected]>
i82860_edac: Report CE events properly
Jan Kara <[email protected]>
scsi: Fix error handling in SCSI_IOCTL_SEND_COMMAND
Jan Kara <[email protected]>
lib/bitmap.c: fix undefined shift in __bitmap_shift_{left|right}()
Wang Nan <[email protected]>
cgroup/kmemleak: add kmemleak_free() for cgroup deallocations.
Hans de Goede <[email protected]>
usb: Do not allow usb_alloc_streams on unconfigured devices
Johan Hovold <[email protected]>
USB: opticon: fix non-atomic allocation in write path
Alan Stern <[email protected]>
usb-storage: handle a skipped data phase
Dmitry Eremin-Solenikov <[email protected]>
spi: pxa2xx: toggle clocks on suspend if not disabled by runtime PM
Ray Jui <[email protected]>
spi: pl022: Fix incorrect dma_unmap_sg
Jack Pham <[email protected]>
usb: dwc3: gadget: Properly initialize LINK TRB
Cyril Brulebois <[email protected]>
wireless: rt2x00: add new rt2800usb device
Dan Williams <[email protected]>
USB: option: add Haier CE81B CDMA modem
Daniele Palmas <[email protected]>
usb: option: add support for Telit LE910
Johan Hovold <[email protected]>
USB: cdc-acm: only raise DTR on transitions from B0
Johan Hovold <[email protected]>
USB: cdc-acm: add device id for GW Instek AFG-2225
Perry Hung <[email protected]>
usb: serial: ftdi_sio: add "bricked" FTDI device PID
Frans Klaver <[email protected]>
usb: serial: ftdi_sio: add Awinda Station and Dongle products
Nathaniel Ting <[email protected]>
USB: serial: cp210x: add Silicon Labs 358x VID and PID
Peter Hurley <[email protected]>
serial: Fix divide-by-zero fault in uart_get_divisor()
Lars-Peter Clausen <[email protected]>
staging:iio:ade7758: Remove "raw" from channel name
Lars-Peter Clausen <[email protected]>
staging:iio:ade7758: Fix check if channels are enabled in prenable
Lars-Peter Clausen <[email protected]>
staging:iio:ade7758: Fix NULL pointer deref when enabling buffer
Lars-Peter Clausen <[email protected]>
staging:iio:ad5933: Drop "raw" from channel names
Lars-Peter Clausen <[email protected]>
staging:iio:ad5933: Fix NULL pointer deref when enabling buffer
Michal Hocko <[email protected]>
OOM, PM: OOM killed task shouldn't escape PM suspend
Cong Wang <[email protected]>
freezer: Do not freeze tasks killed by OOM killer
Jan Kara <[email protected]>
ext4: fix oops when loading block bitmap failed
Pali Rohár <[email protected]>
cpufreq: intel_pstate: Fix setting max_perf_pct in performance policy
Jan Kara <[email protected]>
ext4: fix overflow when updating superblock backups after resize
Darrick J. Wong <[email protected]>
ext4: check s_chksum_driver when looking for bg csum presence
Eric Sandeen <[email protected]>
ext4: fix reservation overflow in ext4_da_write_begin
Theodore Ts'o <[email protected]>
ext4: add ext4_iget_normal() which is to be used for dir tree lookups
Dmitry Monakhov <[email protected]>
ext4: grab missed write_count for EXT4_IOC_SWAP_BOOT
Jan Kara <[email protected]>
ext4: don't check quota format when there are no quota files
Darrick J. Wong <[email protected]>
ext4: check EA value offset when loading
Darrick J. Wong <[email protected]>
jbd2: free bh when descriptor block checksum fails
David Daney <[email protected]>
MIPS: tlbex: Properly fix HUGE TLB Refill exception handler
Nicholas Bellinger <[email protected]>
target: Fix APTPL metadata handling for dynamic MappedLUNs
Quinn Tran <[email protected]>
target: Fix queue full status NULL pointer for SCF_TRANSPORT_TASK_SENSE
Joern Engel <[email protected]>
qla_target: don't delete changed nacls
Anton Kolesov <[email protected]>
ARC: Update order of registers in KGDB to match GDB 7.5
Vineet Gupta <[email protected]>
ARC: [nsimosci] Allow "headless" models to boot
Nadav Amit <[email protected]>
KVM: x86: Emulator fixes for eip canonical checks on near branches
Nadav Amit <[email protected]>
KVM: x86: Fix wrong masking on relative jump/call
Michael S. Tsirkin <[email protected]>
kvm: x86: don't kill guest on unknown exit reason
Nadav Amit <[email protected]>
KVM: x86: Check non-canonical addresses upon WRMSR
Andy Honig <[email protected]>
KVM: x86: Improve thread safety in pit
Andy Honig <[email protected]>
KVM: x86: Prevent host from panicking on shared MSR writes.
Quentin Casasnovas <[email protected]>
kvm: fix excessive pages un-pinning in kvm_iommu_map error path.
Axel Lin <[email protected]>
media: tda7432: Fix setting TDA7432_MUTE bit for TDA7432_RF register
Ulrich Eckhardt <[email protected]>
media: ds3000: fix LNB supply voltage on Tevii S480 on initialization
Frank Schaefer <[email protected]>
media: em28xx-v4l: give back all active video buffers to the vb2 core properly on streaming stop
Maciej Matraszek <[email protected]>
media: v4l2-common: fix overflow in v4l_bound_align_image()
Ben Skeggs <[email protected]>
drm/nouveau/bios: memset dcb struct to zero before parsing
Ezequiel Garcia <[email protected]>
drm/tilcdc: Fix the error path in tilcdc_load()
Benjamin Herrenschmidt <[email protected]>
drm/ast: Fix HW cursor image
Hans de Goede <[email protected]>
Input: i8042 - quirks for Fujitsu Lifebook A544 and Lifebook AH544
Hans de Goede <[email protected]>
Input: i8042 - add noloop quirk for Asus X750LN
Mikulas Patocka <[email protected]>
framebuffer: fix border color
Prarit Bhargava <[email protected]>
modules, lock around setting of MODULE_STATE_UNFORMED
Alexey Khoroshilov <[email protected]>
dm log userspace: fix memory leak in dm_ulog_tfr_init failure path
Mike Snitzer <[email protected]>
block: fix alignment_offset math that assumes io_min is a power-of-2
Lai Jiangshan <[email protected]>
drbd: compute the end before rb_insert_augmented()
Joe Thornber <[email protected]>
dm bufio: update last_accessed when relinking a buffer
Michael S. Tsirkin <[email protected]>
virtio_pci: fix virtio spec compliance on restore
Stephen Smalley <[email protected]>
selinux: fix inode security list corruption
Valdis Kletnieks <[email protected]>
pstore: Fix duplicate {console,ftrace}-efi entries
Chris Ball <[email protected]>
mfd: rtsx_pcr: Fix MSI enable error handling
Eric W. Biederman <[email protected]>
mnt: Prevent pivot_root from creating a loop in the mount tree
Richard Genoud <[email protected]>
UBI: add missing kmem_cache_free() in process_pool_aeb error path
Daniel Borkmann <[email protected]>
random: add and use memzero_explicit() for clearing data
Cesar Eduardo Barros <[email protected]>
crypto: more robust crypto_memneq
Al Viro <[email protected]>
fix misuses of f_count() in ppp and netlink
Al Viro <[email protected]>
kill wbuf_queued/wbuf_dwork_lock
Takashi Iwai <[email protected]>
ALSA: pcm: Zero-clear reserved fields of PCM status ioctl in compat mode
Dmitry Kasatkin <[email protected]>
evm: check xattr value length and type in evm_inode_setxattr()
Dexuan Cui <[email protected]>
x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE
Andy Lutomirski <[email protected]>
x86_64, entry: Fix out of bounds read on sysenter
Andy Lutomirski <[email protected]>
x86_64, entry: Filter RFLAGS.NT on entry from userspace
H. Peter Anvin <[email protected]>
x86, flags: Rename X86_EFLAGS_BIT1 to X86_EFLAGS_FIXED
Oleg Nesterov <[email protected]>
x86, fpu: shift drop_init_fpu() from save_xstate_sig() to handle_signal()
Oleg Nesterov <[email protected]>
x86, fpu: __restore_xstate_sig()->math_state_restore() needs preempt_disable()
Ben Hutchings <[email protected]>
x86: Reject x32 executables if x32 ABI not supported
Jan Kara <[email protected]>
vfs: fix data corruption when blocksize < pagesize for mmaped data
Artem Bityutskiy <[email protected]>
UBIFS: fix free log space calculation
Artem Bityutskiy <[email protected]>
UBIFS: fix a race condition
Artem Bityutskiy <[email protected]>
UBIFS: remove mst_mutex
Tetsuo Handa <[email protected]>
fs: Fix theoretical division by 0 in super_cache_scan().
Mikulas Patocka <[email protected]>
fs: make cont_expand_zero interruptible
Roger Tseng <[email protected]>
mmc: rtsx_pci_sdmmc: fix incorrect last byte in R2 response
Ondrej Zary <[email protected]>
libata-sff: Fix controllers with no ctl port
Scott Carter <[email protected]>
pata_serverworks: disable 64-KB DMA transfers on Broadcom OSB4 IDE Controller
Guenter Roeck <[email protected]>
Revert "percpu: free percpu allocation info for uniprocessor system"
Benjamin Coddington <[email protected]>
lockd: Try to reconnect if statd has moved
Ben Hutchings <[email protected]>
drivers/net: macvtap and tun depend on INET
Vasily Averin <[email protected]>
ipv4: dst_entry leak in ip_send_unicast_reply()
Ian Morgan <[email protected]>
ax88179_178a: fix bonding failure
Jiri Pirko <[email protected]>
ipv4: fix nexthop attlen check in fib_nh_match
Rabin Vincent <[email protected]>
tracing/syscalls: Ignore numbers outside NR_syscalls' range
-------------
Diffstat:
Makefile | 4 +- arch/arc/boot/dts/nsimosci.dts | 2 +- arch/arc/include/asm/kgdb.h | 32 ++++---- arch/mips/mm/tlbex.c | 6 +- arch/x86/ia32/ia32entry.S | 18 ++++- arch/x86/include/asm/elf.h | 5 +- arch/x86/include/asm/kvm_host.h | 16 +++- arch/x86/include/uapi/asm/processor-flags.h | 2 +- arch/x86/kernel/apic/apic.c | 4 +- arch/x86/kernel/cpu/common.c | 2 +- arch/x86/kernel/entry_64.S | 2 +- arch/x86/kernel/process_32.c | 2 +- arch/x86/kernel/process_64.c | 2 +- arch/x86/kernel/signal.c | 5 ++ arch/x86/kernel/tsc.c | 5 +- arch/x86/kernel/xsave.c | 7 +- arch/x86/kvm/emulate.c | 99 ++++++++++++++++++------- arch/x86/kvm/i8254.c | 2 + arch/x86/kvm/svm.c | 8 +- arch/x86/kvm/vmx.c | 17 +++-- arch/x86/kvm/x86.c | 38 +++++++++- arch/x86/mm/pageattr.c | 2 +- block/blk-settings.c | 4 +- block/scsi_ioctl.c | 3 +- crypto/algif_skcipher.c | 2 +- drivers/ata/libata-sff.c | 20 +++-- drivers/ata/pata_serverworks.c | 13 +++- drivers/base/core.c | 4 +- drivers/block/drbd/drbd_interval.c | 4 + drivers/block/rbd.c | 2 +- drivers/char/random.c | 10 +-- drivers/cpufreq/intel_pstate.c | 1 + drivers/edac/cpc925_edac.c | 2 +- drivers/edac/e7xxx_edac.c | 2 +- drivers/edac/i3200_edac.c | 4 +- drivers/edac/i82860_edac.c | 2 +- drivers/gpu/drm/ast/ast_mode.c | 4 +- drivers/gpu/drm/nouveau/core/subdev/bios/dcb.c | 1 + drivers/gpu/drm/tilcdc/tilcdc_drv.c | 60 ++++++++++++--- drivers/i2c/busses/i2c-at91.c | 2 +- drivers/input/serio/i8042-x86ia64io.h | 22 ++++++ drivers/lguest/x86/core.c | 2 +- drivers/md/dm-bufio.c | 1 + drivers/md/dm-log-userspace-transfer.c | 2 +- drivers/media/dvb-frontends/ds3000.c | 7 ++ drivers/media/i2c/tda7432.c | 2 +- drivers/media/usb/em28xx/em28xx-video.c | 10 ++- drivers/media/v4l2-core/v4l2-common.c | 9 +-- drivers/mfd/rtsx_pcr.c | 2 +- drivers/mmc/host/rtsx_pci_sdmmc.c | 7 ++ drivers/mtd/ubi/fastmap.c | 1 + drivers/net/Kconfig | 2 + drivers/net/ppp/ppp_generic.c | 2 +- drivers/net/usb/ax88179_178a.c | 7 +- drivers/net/wireless/rt2x00/rt2800usb.c | 1 + drivers/of/base.c | 88 ++++++---------------- drivers/of/selftest.c | 64 ++++++++++++++-- drivers/platform/x86/acer-wmi.c | 11 +++ drivers/scsi/qla2xxx/tcm_qla2xxx.c | 11 ++- drivers/spi/spi-pl022.c | 2 +- drivers/spi/spi-pxa2xx.c | 7 +- drivers/staging/iio/impedance-analyzer/ad5933.c | 15 ++-- drivers/staging/iio/meter/ade7758.h | 1 - drivers/staging/iio/meter/ade7758_core.c | 57 +++----------- drivers/staging/iio/meter/ade7758_ring.c | 5 +- drivers/target/target_core_device.c | 3 +- drivers/target/target_core_pr.c | 6 +- drivers/target/target_core_pr.h | 2 +- drivers/target/target_core_tpg.c | 8 ++ drivers/target/target_core_transport.c | 3 +- drivers/tty/serial/serial_core.c | 2 +- drivers/tty/tty_io.c | 7 +- drivers/usb/class/cdc-acm.c | 6 +- drivers/usb/core/hcd.c | 2 + drivers/usb/dwc3/ep0.c | 4 +- drivers/usb/dwc3/gadget.c | 19 +++-- drivers/usb/dwc3/gadget.h | 2 +- drivers/usb/gadget/f_acm.c | 7 +- drivers/usb/gadget/udc-core.c | 5 ++ drivers/usb/serial/cp210x.c | 1 + drivers/usb/serial/ftdi_sio.c | 3 + drivers/usb/serial/ftdi_sio_ids.h | 12 ++- drivers/usb/serial/opticon.c | 2 +- drivers/usb/serial/option.c | 10 +++ drivers/usb/storage/transport.c | 26 +++++++ drivers/video/console/bitblit.c | 3 +- drivers/video/console/fbcon_ccw.c | 3 +- drivers/video/console/fbcon_cw.c | 3 +- drivers/video/console/fbcon_ud.c | 3 +- drivers/virtio/virtio_pci.c | 33 ++++++++- fs/btrfs/file-item.c | 2 +- fs/buffer.c | 8 ++ fs/ext3/super.c | 7 -- fs/ext4/ext4.h | 5 +- fs/ext4/ialloc.c | 4 + fs/ext4/inode.c | 24 +++++- fs/ext4/ioctl.c | 10 ++- fs/ext4/namei.c | 4 +- fs/ext4/resize.c | 2 +- fs/ext4/super.c | 13 ++-- fs/ext4/xattr.c | 32 ++++++-- fs/jbd2/recovery.c | 1 + fs/jffs2/jffs2_fs_sb.h | 2 - fs/jffs2/wbuf.c | 17 +---- fs/lockd/mon.c | 6 ++ fs/namespace.c | 3 + fs/nfsd/nfs4proc.c | 3 +- fs/pstore/inode.c | 4 +- fs/quota/dquot.c | 2 +- fs/super.c | 2 + fs/ubifs/commit.c | 10 +-- fs/ubifs/log.c | 19 +++-- fs/ubifs/master.c | 7 +- fs/ubifs/super.c | 1 - fs/ubifs/ubifs.h | 2 - include/drm/drm_pciids.h | 1 - include/linux/blkdev.h | 5 +- include/linux/compiler-gcc.h | 3 + include/linux/compiler-intel.h | 7 ++ include/linux/compiler.h | 4 + include/linux/mm.h | 1 + include/linux/of.h | 84 +++++++++++++++++---- include/linux/oom.h | 3 + include/linux/string.h | 5 +- kernel/freezer.c | 3 + kernel/module.c | 2 + kernel/posix-timers.c | 1 + kernel/power/hibernate.c | 8 +- kernel/power/process.c | 40 +++++++++- kernel/trace/trace_syscalls.c | 8 +- lib/bitmap.c | 8 +- lib/string.c | 16 ++++ mm/oom_kill.c | 17 +++++ mm/page_alloc.c | 8 ++ mm/page_cgroup.c | 1 + mm/percpu.c | 2 - mm/truncate.c | 58 ++++++++++++++- net/ceph/messenger.c | 3 +- net/ipv4/fib_semantics.c | 2 +- net/ipv4/ip_output.c | 12 ++- net/mac80211/rate.c | 2 +- net/netlink/af_netlink.c | 2 +- security/integrity/evm/evm_main.c | 9 ++- security/selinux/hooks.c | 2 +- sound/core/pcm_compat.c | 2 + virt/kvm/iommu.c | 8 +- 146 files changed, 1029 insertions(+), 421 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/123 tracing/syscalls: Ignore numbers outside NR_syscalls range
3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rabin Vincent <[email protected]>
commit 086ba77a6db00ed858ff07451bedee197df868c9 upstream.
ARM has some private syscalls (for example, set_tls(2)) which lie outside the range of NR_syscalls. If any of these are called while syscall tracing is being performed, out-of-bounds array access will occur in the ftrace and perf sys_{enter,exit} handlers.
# trace-cmd record -e raw_syscalls:* true && trace-cmd report ... true-653 [000] 384.675777: sys_enter: NR 192 (0, 1000, 3, 4000022, ffffffff, 0) true-653 [000] 384.675812: sys_exit: NR 192 = 1995915264 true-653 [000] 384.675971: sys_enter: NR 983045 (76f74480, 76f74000, 76f74b28, 76f74480, 76f76f74, 1) true-653 [000] 384.675988: sys_exit: NR 983045 = 0 ...
# trace-cmd record -e syscalls:* true [ 17.289329] Unable to handle kernel paging request at virtual address aaaaaace [ 17.289590] pgd = 9e71c000 [ 17.289696] [aaaaaace] *pgd=00000000 [ 17.289985] Internal error: Oops: 5 [#1] PREEMPT SMP ARM [ 17.290169] Modules linked in: [ 17.290391] CPU: 0 PID: 704 Comm: true Not tainted 3.18.0-rc2+ #21 [ 17.290585] task: 9f4dab00 ti: 9e710000 task.ti: 9e710000 [ 17.290747] PC is at ftrace_syscall_enter+0x48/0x1f8 [ 17.290866] LR is at syscall_trace_enter+0x124/0x184
Fix this by ignoring out-of-NR_syscalls-bounds syscall numbers.
Commit cd0980fc8add "tracing: Check invalid syscall nr while tracing syscalls" added the check for less than zero, but it should have also checked for greater than NR_syscalls.
--- kernel/trace/trace_syscalls.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
kernel/trace/trace_syscalls.c +4 -4
@@ -312,7 +312,7 @@ static void ftrace_syscall_enter(void *dint size; syscall_nr =trace_get_syscall_nr (current, regs); -if (syscall_nr <0 ) +if (syscall_nr <0 || syscall_nr >= NR_syscalls)return ;if (!test_bit (syscall_nr, tr->enabled_enter_syscalls))return ;
@@ -354,7 +354,7 @@ static void ftrace_syscall_exit(void *daint syscall_nr; syscall_nr =trace_get_syscall_nr (current, regs); -if (syscall_nr <0 ) +if (syscall_nr <0 || syscall_nr >= NR_syscalls)return ;if (!test_bit (syscall_nr, tr->enabled_exit_syscalls))return ;
@@ -557,7 +557,7 @@ static void perf_syscall_enter(void *ignint size; syscall_nr =trace_get_syscall_nr (current, regs); -if (syscall_nr <0 ) +if (syscall_nr <0 || syscall_nr >= NR_syscalls)return ;if (!test_bit (syscall_nr, enabled_perf_enter_syscalls))return ;
@@ -633,7 +633,7 @@ static void perf_syscall_exit(void *ignoint size; syscall_nr =trace_get_syscall_nr (current, regs); -if (syscall_nr <0 ) +if (syscall_nr <0 || syscall_nr >= NR_syscalls)return ;if (!test_bit (syscall_nr, enabled_perf_exit_syscalls))return ;
Greg Kroah-Hartman
maintainerPATCH 2/123 ipv4: fix nexthop attlen check in fib_nh_match
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jiri Pirko <[email protected]>
[ Upstream commit f76936d07c4eeb36d8dbb64ebd30ab46ff85d9f7 ]
fib_nh_match does not match nexthops correctly. Example:
ip route add 172.16.10/24 nexthop via 192.168.122.12 dev eth0 \
nexthop via 192.168.122.13 dev eth0
ip route del 172.16.10/24 nexthop via 192.168.122.14 dev eth0 \
nexthop via 192.168.122.15 dev eth0Del command is successful and route is removed. After this patch applied, the route is correctly matched and result is:
RTNETLINK answers: No such process
Please consider this for stable trees as well.
--- net/ipv4/fib_semantics.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/fib_semantics.c +1 -1
@@ -533,7 +533,7 @@ int fib_nh_match(struct fib_config *cfg,return 1 ; attrlen =rtnh_attrlen (rtnh); -if (attrlen <0 ) { +if (attrlen >0 ) {struct nlattr *nla, *attrs =rtnh_attrs (rtnh); nla =nla_find (attrs, attrlen,RTA_GATEWAY );
Greg Kroah-Hartman
maintainerPATCH 3/123 ax88179_178a: fix bonding failure
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ian Morgan <[email protected]>
[ Upstream commit 95ff88688781db2f64042e69bd499e518bbb36e5 ]
The following patch fixes a bug which causes the ax88179_178a driver to be incapable of being added to a bond.
When I brought up the issue with the bonding maintainers, they indicated that the real problem was with the NIC driver which must return zero for success (of setting the MAC address). I see that several other NIC drivers follow that pattern by either simply always returing zero, or by passing through a negative (error) result while rewriting any positive return code to zero. With that same philisophy applied to the ax88179_178a driver, it allows it to work correctly with the bonding driver.
I believe this is suitable for queuing in -stable, as it's a small, simple, and obvious fix that corrects a defect with no other known workaround.
This patch is against vanilla 3.17(.0).
--- drivers/net/usb/ax88179_178a.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/net/usb/ax88179_178a.c +6 -1
@@ -695,6 +695,7 @@ static int ax88179_set_mac_addr(struct n {struct usbnet *dev =netdev_priv (net);struct sockaddr *addr = p; +int ret;if (netif_running (net))return -EBUSY ;
@@ -704,8 +705,12 @@ static int ax88179_set_mac_addr(struct nmemcpy (net->dev_addr, addr->sa_data,ETH_ALEN );/* Set the MAC address */ -return ax88179_write_cmd (dev,AX_ACCESS_MAC ,AX_NODE_ID ,ETH_ALEN , + ret =ax88179_write_cmd (dev,AX_ACCESS_MAC ,AX_NODE_ID ,ETH_ALEN ,ETH_ALEN , net->dev_addr); +if (ret <0 ) +return ret; + +return 0 ; }static const struct net_device_ops ax88179_netdev_ops = {
Greg Kroah-Hartman
maintainerPATCH 4/123 ipv4: dst_entry leak in ip_send_unicast_reply()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Vasily Averin <[email protected]>
[ Upstream commit 4062090e3e5caaf55bed4523a69f26c3265cc1d2 ]
ip_setup_cork() called inside ip_append_data() steals dst entry from rt to cork and in case errors in __ip_append_data() nobody frees stolen dst entry
--- net/ipv4/ip_output.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
net/ipv4/ip_output.c +9 -3
@@ -1481,6 +1481,7 @@ void ip_send_unicast_reply(struct net *nstruct sk_buff *nskb;struct sock *sk;struct inet_sock *inet; +int err;if (ip_options_echo (&replyopts.opt.opt, skb))return ;
@@ -1517,8 +1518,13 @@ void ip_send_unicast_reply(struct net *nsock_net_set (sk, net);__skb_queue_head_init (&sk->sk_write_queue); sk->sk_sndbuf = sysctl_wmem_default; -ip_append_data (sk, &fl4, ip_reply_glue_bits, arg->iov->iov_base, len,0 , - &ipc, &rt,MSG_DONTWAIT ); + err =ip_append_data (sk, &fl4, ip_reply_glue_bits, arg->iov->iov_base, + len,0 , &ipc, &rt,MSG_DONTWAIT ); +if (unlikely (err)) { +ip_flush_pending_frames (sk); + goto out; + } + nskb =skb_peek (&sk->sk_write_queue);if (nskb) {if (arg->csumoffset >=0 )
@@ -1530,7 +1536,7 @@ void ip_send_unicast_reply(struct net *nskb_set_queue_mapping (nskb,skb_get_queue_mapping (skb));ip_push_pending_frames (sk, &fl4); } - +out:put_cpu_var (unicast_sock);ip_rt_put (rt);
Greg Kroah-Hartman
maintainerPATCH 5/123 drivers/net: macvtap and tun depend on INET
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
[ Upstream commit de11b0e8c569b96c2cf6a811e3805b7aeef498a3 ]
These drivers now call ipv6_proxy_select_ident(), which is defined only if CONFIG_INET is enabled. However, they have really depended on CONFIG_INET for as long as they have allowed sending GSO packets from userland.
--- drivers/net/Kconfig | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/Kconfig +2 -0
@@ -139,6 +139,7 @@ config MACVLAN config MACVTAP tristate "MAC-VLAN based tap driver" depends on MACVLAN + depends on INET help This adds a specialized tap character device driver that is based on the MAC-VLAN network interface, called macvtap. A macvtap device
@@ -209,6 +210,7 @@ config RIONET_RX_SIZE config TUN tristate "Universal TUN/TAP device driver support" + depends on INET select CRC32 ---help--- TUN/TAP provides packet reception and transmission for user space
Greg Kroah-Hartman
maintainerPATCH 6/123 lockd: Try to reconnect if statd has moved
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Benjamin Coddington <[email protected]>
commit 173b3afceebe76fa2205b2c8808682d5b541fe3c upstream.
If rpc.statd is restarted, upcalls to monitor hosts can fail with ECONNREFUSED. In that case force a lookup of statd's new port and retry the upcall.
--- fs/lockd/mon.c | 6 ++++++ 1 file changed, 6 insertions(+)
fs/lockd/mon.c +6 -0
@@ -159,6 +159,12 @@ static int nsm_mon_unmon(struct nsm_hand msg.rpc_proc = &clnt->cl_procinfo[proc]; status =rpc_call_sync (clnt, &msg,RPC_TASK_SOFTCONN ); +if (status == -ECONNREFUSED ) { +dprintk ("lockd: NSM upcall RPC failed, status=%d, forcing rebind\n" , + status); +rpc_force_rebind (clnt); + status =rpc_call_sync (clnt, &msg,RPC_TASK_SOFTCONN ); + }if (status <0 )dprintk ("lockd: NSM upcall RPC failed, status=%d\n" , status);
Greg Kroah-Hartman
maintainerPATCH 7/123 Revert "percpu: free percpu allocation info for uniprocessor system"
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Guenter Roeck <[email protected]>
commit bb2e226b3bef596dd56be97df655d857b4603923 upstream.
This reverts commit 3189eddbcafc ("percpu: free percpu allocation info for uniprocessor system").
The commit causes a hang with a crisv32 image. This may be an architecture problem, but at least for now the revert is necessary to be able to boot a crisv32 image.
--- mm/percpu.c | 2 -- 1 file changed, 2 deletions(-)
mm/percpu.c +0 -2
@@ -1910,8 +1910,6 @@ void __init setup_per_cpu_areas(void)if (pcpu_setup_first_chunk (ai, fc) <0 ) panic("Failed to initialize percpu areas."); - - pcpu_free_alloc_info(ai); }#endif /* CONFIG_SMP */
Greg Kroah-Hartman
maintainerPATCH 8/123 pata_serverworks: disable 64-KB DMA transfers on Broadcom OSB4 IDE Controller
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Scott Carter <[email protected]>
commit 37017ac6849e772e67dd187ba2fbd056c4afa533 upstream.
The Broadcom OSB4 IDE Controller (vendor and device IDs: 1166:0211) does not support 64-KB DMA transfers.
Whenever a 64-KB DMA transfer is attempted,
the transfer fails and messages similar to the following are written to the console log:
[ 2431.851125] sr 0:0:0:0: [sr0] Unhandled sense code [ 2431.851139] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2431.851152] sr 0:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 2431.851166] sr 0:0:0:0: [sr0] Add. Sense: Logical unit communication time-out [ 2431.851182] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 76 f4 00 00 40 00 [ 2431.851210] end_request: I/O error, dev sr0, sector 121808
When the libata and pata_serverworks modules
are recompiled with ATA_DEBUG and ATA_VERBOSE_DEBUG defined in libata.h, the 64-KB transfer size in the scatter-gather list can be seen in the console log:
[ 2664.897267] sr 9:0:0:0: [sr0] Send: [ 2664.897274] 0xf63d85e0 [ 2664.897283] sr 9:0:0:0: [sr0] CDB: [ 2664.897288] Read(10): 28 00 00 00 7f b4 00 00 40 00 [ 2664.897319] buffer = 0xf6d6fbc0, bufflen = 131072, queuecommand 0xf81b7700 [ 2664.897331] ata_scsi_dump_cdb: CDB (1:0,0,0) 28 00 00 00 7f b4 00 00 40 [ 2664.897338] ata_scsi_translate: ENTER [ 2664.897345] ata_sg_setup: ENTER, ata1 [ 2664.897356] ata_sg_setup: 3 sg elements mapped [ 2664.897364] ata_bmdma_fill_sg: PRD[0] = (0x66FD2000, 0xE000) [ 2664.897371] ata_bmdma_fill_sg: PRD[1] = (0x65000000, 0x10000) ------------------------------------------------------> ======= [ 2664.897378] ata_bmdma_fill_sg: PRD[2] = (0x66A10000, 0x2000) [ 2664.897386] ata1: ata_dev_select: ENTER, device 0, wait 1 [ 2664.897422] ata_sff_tf_load: feat 0x1 nsect 0x0 lba 0x0 0x0 0xFC [ 2664.897428] ata_sff_tf_load: device 0xA0 [ 2664.897448] ata_sff_exec_command: ata1: cmd 0xA0 [ 2664.897457] ata_scsi_translate: EXIT [ 2664.897462] leaving scsi_dispatch_cmnd() [ 2664.897497] Doing sr request, dev = sr0, block = 0 [ 2664.897507] sr0 : reading 64/256 512 byte blocks. [ 2664.897553] ata_sff_hsm_move: ata1: protocol 7 task_state 1 (dev_stat 0x58) [ 2664.897560] atapi_send_cdb: send cdb [ 2666.910058] ata_bmdma_port_intr: ata1: host_stat 0x64 [ 2666.910079] __ata_sff_port_intr: ata1: protocol 7 task_state 3 [ 2666.910093] ata_sff_hsm_move: ata1: protocol 7 task_state 3 (dev_stat 0x51) [ 2666.910101] ata_sff_hsm_move: ata1: protocol 7 task_state 4 (dev_stat 0x51) [ 2666.910129] sr 9:0:0:0: [sr0] Done: [ 2666.910136] 0xf63d85e0 TIMEOUT
lspci shows that the driver used for the Broadcom OSB4 IDE Controller is pata_serverworks:
00:0f.1 IDE interface: Broadcom OSB4 IDE Controller (prog-if 8e [Master SecP SecO PriP])
Flags: bus master, medium devsel, latency 64
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=4]
I/O ports at 1440 [size=16]
Kernel driver in use: pata_serverworksThe pata_serverworks driver supports five distinct device IDs, one being the OSB4 and the other four belonging to the CSB series. The CSB series appears to support 64-KB DMA transfers,
as tests on a machine with an SAI2 motherboard
containing a Broadcom CSB5 IDE Controller (vendor and device IDs: 1166:0212) showed no problems with 64-KB DMA transfers.
This problem was first discovered when attempting to install openSUSE from a DVD on a machine with an STL2 motherboard.
Using the pata_serverworks module,
older releases of openSUSE will not install at all due to the timeouts. Releases of openSUSE prior to 11.3 can be installed by disabling the pata_serverworks module using the brokenmodules boot parameter, which causes the serverworks module to be used instead.
Recent releases of openSUSE (12.2 and later) include better error recovery and will install, though very slowly.
On all openSUSE releases, the problem can be recreated
on a machine containing a Broadcom OSB4 IDE Controller
by mounting an install DVD and running a command similar to the following:
find /mnt -type f -print | xargs cat > /dev/null
The patch below corrects the problem.
Similar to the other ATA drivers that do not support 64-KB DMA transfers, the patch changes the ata_port_operations qc_prep vector to point to a routine that breaks any 64-KB segment into two 32-KB segments and
changes the scsi_host_template sg_tablesize element to reduce by half the number of scatter/gather elements allowed.
These two changes affect only the OSB4.
--- drivers/ata/pata_serverworks.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
drivers/ata/pata_serverworks.c +11 -2
@@ -252,12 +252,18 @@ static void serverworks_set_dmamode(strupci_write_config_byte (pdev,0x54 , ultra_cfg); } -static struct scsi_host_template serverworks_sht = { +static struct scsi_host_template serverworks_osb4_sht = { +ATA_BMDMA_SHT (DRV_NAME ), + .sg_tablesize =LIBATA_DUMB_MAX_PRD , +}; + +static struct scsi_host_template serverworks_csb_sht = {ATA_BMDMA_SHT (DRV_NAME ), };static struct ata_port_operations serverworks_osb4_port_ops = { .inherits = &ata_bmdma_port_ops, + .qc_prep = ata_bmdma_dumb_qc_prep, .cable_detect = serverworks_cable_detect, .mode_filter = serverworks_osb4_filter, .set_piomode = serverworks_set_piomode,
@@ -266,6 +272,7 @@ static struct ata_port_operations serverstatic struct ata_port_operations serverworks_csb_port_ops = { .inherits = &serverworks_osb4_port_ops, + .qc_prep = ata_bmdma_qc_prep, .mode_filter = serverworks_csb_filter, };
@@ -405,6 +412,7 @@ static int serverworks_init_one(struct p } };const struct ata_port_info *ppi[] = { &info[id->driver_data],NULL }; +struct scsi_host_template *sht = &serverworks_csb_sht;int rc; rc =pcim_enable_device (pdev);
@@ -418,6 +426,7 @@ static int serverworks_init_one(struct p/* Select non UDMA capable OSB4 if we can't do fixups */ if (rc <0 ) ppi[0 ] = &info[1 ]; + sht = &serverworks_osb4_sht; }/* setup CSB5/CSB6 : South Bridge and IDE option RAID */ else if ((pdev->device == PCI_DEVICE_ID_SERVERWORKS_CSB5IDE) ||
@@ -434,7 +443,7 @@ static int serverworks_init_one(struct p ppi[1 ] = &ata_dummy_port_info; } -return ata_pci_bmdma_init_one (pdev, ppi, &serverworks_sht,NULL ,0 ); +return ata_pci_bmdma_init_one (pdev, ppi, sht,NULL ,0 ); }#ifdef CONFIG_PM
Greg Kroah-Hartman
maintainerPATCH 9/123 libata-sff: Fix controllers with no ctl port
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ondrej Zary <[email protected]>
commit 6d8ca28fa688a9354bc9fbc935bdaeb3651b6677 upstream.
Currently, ata_sff_softreset is skipped for controllers with no ctl port. But that also skips ata_sff_dev_classify required for device detection. This means that libata is currently broken on controllers with no ctl port.
No device connected:
[ 1.872480] pata_isapnp 01:01.02: activated [ 1.889823] scsi2 : pata_isapnp [ 1.890109] ata3: PATA max PIO0 cmd 0x1e8 ctl 0x0 irq 11 [ 6.888110] ata3.01: qc timeout (cmd 0xec) [ 6.888179] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x5) [ 16.888085] ata3.01: qc timeout (cmd 0xec) [ 16.888147] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x5) [ 46.888086] ata3.01: qc timeout (cmd 0xec) [ 46.888148] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x5) [ 51.888100] ata3.00: qc timeout (cmd 0xec) [ 51.888160] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x5) [ 61.888079] ata3.00: qc timeout (cmd 0xec) [ 61.888141] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x5) [ 91.888089] ata3.00: qc timeout (cmd 0xec) [ 91.888152] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x5)
ATAPI device connected:
[ 1.882061] pata_isapnp 01:01.02: activated [ 1.893430] scsi2 : pata_isapnp [ 1.893719] ata3: PATA max PIO0 cmd 0x1e8 ctl 0x0 irq 11 [ 6.892107] ata3.01: qc timeout (cmd 0xec) [ 6.892171] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x5) [ 16.892079] ata3.01: qc timeout (cmd 0xec) [ 16.892138] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x5) [ 46.892079] ata3.01: qc timeout (cmd 0xec) [ 46.892138] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x5) [ 46.908586] ata3.00: ATAPI: ACER CD-767E/O, V1.5X, max PIO2, CDB intr [ 46.924570] ata3.00: configured for PIO0 (device error ignored) [ 46.926295] scsi 2:0:0:0: CD-ROM ACER CD-767E/O 1.5X PQ: 0 ANSI: 5 [ 46.984519] sr0: scsi3-mmc drive: 6x/6x xa/form2 tray [ 46.984592] cdrom: Uniform CD-ROM driver Revision: 3.20
So don't skip ata_sff_softreset, just skip the reset part of ata_bus_softreset if the ctl port is not available.
This makes IDE port on ES968 behave correctly:
No device connected:
[ 4.670888] pata_isapnp 01:01.02: activated [ 4.673207] scsi host2: pata_isapnp [ 4.673675] ata3: PATA max PIO0 cmd 0x1e8 ctl 0x0 irq 11 [ 7.081840] Adding 2541652k swap on /dev/sda2. Priority:-1 extents:1 across:2541652k
ATAPI device connected:
[ 4.704362] pata_isapnp 01:01.02: activated [ 4.706620] scsi host2: pata_isapnp [ 4.706877] ata3: PATA max PIO0 cmd 0x1e8 ctl 0x0 irq 11 [ 4.872782] ata3.00: ATAPI: ACER CD-767E/O, V1.5X, max PIO2, CDB intr [ 4.888673] ata3.00: configured for PIO0 (device error ignored) [ 4.893984] scsi 2:0:0:0: CD-ROM ACER CD-767E/O 1.5X PQ: 0 ANSI: 5 [ 7.015578] Adding 2541652k swap on /dev/sda2. Priority:-1 extents:1 across:2541652k
--- drivers/ata/libata-sff.c | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-)
drivers/ata/libata-sff.c +9 -11
@@ -2008,13 +2008,15 @@ static int ata_bus_softreset(struct ata_DPRINTK ("ata%u: bus reset via SRST\n" , ap->print_id); -/* software reset. causes dev0 to be selected */ -iowrite8 (ap->ctl, ioaddr->ctl_addr); -udelay (20 );/* FIXME: flush */ -iowrite8 (ap->ctl |ATA_SRST , ioaddr->ctl_addr); -udelay (20 );/* FIXME: flush */ -iowrite8 (ap->ctl, ioaddr->ctl_addr); - ap->last_ctl = ap->ctl; +if (ap->ioaddr.ctl_addr) { +/* software reset. causes dev0 to be selected */ +iowrite8 (ap->ctl, ioaddr->ctl_addr); +udelay (20 );/* FIXME: flush */ +iowrite8 (ap->ctl |ATA_SRST , ioaddr->ctl_addr); +udelay (20 );/* FIXME: flush */ +iowrite8 (ap->ctl, ioaddr->ctl_addr); + ap->last_ctl = ap->ctl; + }/* wait the port to become ready */ return ata_sff_wait_after_reset (&ap->link, devmask, deadline);
@@ -2215,10 +2217,6 @@ void ata_sff_error_handler(struct ata_pospin_unlock_irqrestore (ap->lock, flags); -/* ignore ata_sff_softreset if ctl isn't accessible */ -if (softreset == ata_sff_softreset && !ap->ioaddr.ctl_addr) - softreset =NULL ; -/* ignore built-in hardresets if SCR access is not available */ if ((hardreset == sata_std_hardreset || hardreset == sata_sff_hardreset) && !sata_scr_valid (&ap->link))
Greg Kroah-Hartman
maintainerPATCH 10/123 mmc: rtsx_pci_sdmmc: fix incorrect last byte in R2 response
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Roger Tseng <[email protected]>
commit d1419d50c1bf711e9fd27b516a739c86b23f7cf9 upstream.
Current code erroneously fill the last byte of R2 response with an undefined value. In addition, the controller actually 'offloads' the last byte (CRC7, end bit) while receiving R2 response and thus it's impossible to get the actual value. This could cause mmc stack to obtain inconsistent CID from the same card after resume and misidentify it as a different card.
Fix by assigning dummy CRC and end bit: {7'b0, 1} = 0x1 to the last byte of R2.
--- drivers/mmc/host/rtsx_pci_sdmmc.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/mmc/host/rtsx_pci_sdmmc.c +7 -0
@@ -341,6 +341,13 @@ static void sd_send_cmd_get_rsp(struct r }if (rsp_type ==SD_RSP_TYPE_R2 ) { +/* +* The controller offloads the last byte {CRC-7, end bit 1'b1} +* of response type R2. Assign dummy CRC, 0, and end bit to the +* byte(ptr[16], goes into the LSB of resp[3] later). +*/ + ptr[16 ] =1 ; +for (i =0 ; i <4 ; i++) { cmd->resp[i] =get_unaligned_be32 (ptr +1 + i *4 ); dev_dbg(sdmmc_dev(host), "cmd->resp[%d] = 0x%08x\n",
Greg Kroah-Hartman
maintainerPATCH 11/123 fs: make cont_expand_zero interruptible
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mikulas Patocka <[email protected]>
commit c2ca0fcd202863b14bd041a7fece2e789926c225 upstream.
This patch makes it possible to kill a process looping in cont_expand_zero. A process may spend a lot of time in this function, so it is desirable to be able to kill it.
It happened to me that I wanted to copy a piece data from the disk to a file. By mistake, I used the "seek" parameter to dd instead of "skip". Due to the "seek" parameter, dd attempted to extend the file and became stuck doing so - the only possibility was to reset the machine or wait many hours until the filesystem runs out of space and cont_expand_zero fails. We need this patch to be able to terminate the process.
--- fs/buffer.c | 5 +++++ 1 file changed, 5 insertions(+)
fs/buffer.c +5 -0
@@ -2254,6 +2254,11 @@ static int cont_expand_zero(struct file err =0 ;balance_dirty_pages_ratelimited (mapping); + +if (unlikely (fatal_signal_pending (current))) { + err = -EINTR ; + goto out; + } }/* page covers the boundary, find the boundary offset */
Greg Kroah-Hartman
maintainerPATCH 12/123 fs: Fix theoretical division by 0 in super_cache_scan().
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tetsuo Handa <[email protected]>
commit 475d0db742e3755c6b267f48577ff7cbb7dfda0d upstream.
total_objects could be 0 and is used as a denom.
While total_objects is a "long", total_objects == 0 unlikely happens for 3.12 and later kernels because 32-bit architectures would not be able to hold (1 << 32) objects. However, total_objects == 0 may happen for kernels between 3.1 and 3.11 because total_objects in prune_super() was an "int" and (e.g.) x86_64 architecture might be able to hold (1 << 32) objects.
--- fs/super.c | 2 ++ 1 file changed, 2 insertions(+)
fs/super.c +2 -0
@@ -76,6 +76,8 @@ static int prune_super(struct shrinker * total_objects = sb->s_nr_dentry_unused + sb->s_nr_inodes_unused + fs_objects +1 ; +if (!total_objects) + total_objects =1 ;if (sc->nr_to_scan) {int dentries;
Greg Kroah-Hartman
maintainerPATCH 13/123 UBIFS: remove mst_mutex
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Artem Bityutskiy <[email protected]>
commit 07e19dff63e3d5d6500d831e36554ac9b1b0560e upstream.
The 'mst_mutex' is not needed since because 'ubifs_write_master()' is only called on the mount path and commit path. The mount path is sequential and there is no parallelism, and the commit path is also serialized - there is only one commit going on at a time.
--- fs/ubifs/commit.c | 2 -- fs/ubifs/master.c | 7 +++---- fs/ubifs/super.c | 1 - fs/ubifs/ubifs.h | 2 -- 4 files changed, 3 insertions(+), 9 deletions(-)
fs/ubifs/commit.c +0 -2
@@ -174,7 +174,6 @@ static int do_commit(struct ubifs_info *if (err) goto out; -mutex_lock (&c->mst_mutex); c->mst_node->cmt_no =cpu_to_le64 (c->cmt_no); c->mst_node->log_lnum =cpu_to_le32 (new_ltail_lnum); c->mst_node->root_lnum =cpu_to_le32 (zroot.lnum);
@@ -204,7 +203,6 @@ static int do_commit(struct ubifs_info *else c->mst_node->flags &= ~cpu_to_le32 (UBIFS_MST_NO_ORPHS ); err =ubifs_write_master (c); -mutex_unlock (&c->mst_mutex);if (err) goto out;
fs/ubifs/master.c +3 -4
@@ -352,10 +352,9 @@ int ubifs_read_master(struct ubifs_info* ubifs_write_master - write master node. * @c: UBIFS file-system description object * -* This function writes the master node. The caller has to take the -* @c->mst_mutex lock before calling this function. Returns zero in case of -* success and a negative error code in case of failure. The master node is -* written twice to enable recovery. +* This function writes the master node. Returns zero in case of success and a +* negative error code in case of failure. The master node is written twice to +* enable recovery. */ int ubifs_write_master (struct ubifs_info *c) {
fs/ubifs/super.c +0 -1
@@ -1970,7 +1970,6 @@ static struct ubifs_info *alloc_ubifs_inmutex_init (&c->lp_mutex);mutex_init (&c->tnc_mutex);mutex_init (&c->log_mutex); -mutex_init (&c->mst_mutex);mutex_init (&c->umount_mutex);mutex_init (&c->bu_mutex);mutex_init (&c->write_reserve_mutex);
fs/ubifs/ubifs.h +0 -2
@@ -1042,7 +1042,6 @@ struct ubifs_debug_info;* * @mst_node: master node * @mst_offs: offset of valid master node -* @mst_mutex: protects the master node area, @mst_node, and @mst_offs * * @max_bu_buf_len: maximum bulk-read buffer length * @bu_mutex: protects the pre-allocated bulk-read buffer and @c->bu
@@ -1282,7 +1281,6 @@ struct ubifs_info {struct ubifs_mst_node *mst_node;int mst_offs; -struct mutex mst_mutex;int max_bu_buf_len;struct mutex bu_mutex;
Greg Kroah-Hartman
maintainerPATCH 14/123 UBIFS: fix a race condition
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Artem Bityutskiy <[email protected]>
commit 052c28073ff26f771d44ef33952a41d18dadd255 upstream.
Hu ([email protected]) discovered a race condition which may lead to a situation when UBIFS is unable to mount the file-system after an unclean reboot. The problem is theoretical, though.
In UBIFS, we have the log, which basically a set of LEBs in a certain area. The log has the tail and the head.
Every time user writes data to the file-system, the UBIFS journal grows, and the log grows as well, because we append new reference nodes to the head of the log. So the head moves forward all the time, while the log tail stays at the same position.
At any time, the UBIFS master node points to the tail of the log. When we mount the file-system, we scan the log, and we always start from its tail, because this is where the master node points to. The only occasion when the tail of the log changes is the commit operation.
The commit operation has 2 phases - "commit start" and "commit end". The former is relatively short, and does not involve much I/O. During this phase we mostly just build various in-memory lists of the things which have to be written to the flash media during "commit end" phase.
During the commit start phase, what we do is we "clean" the log. Indeed, the commit operation will index all the data in the journal, so the entire journal "disappears", and therefore the data in the log become unneeded. So we just move the head of the log to the next LEB, and write the CS node there. This LEB will be the tail of the new log when the commit operation finishes.
When the "commit start" phase finishes, users may write more data to the file-system, in parallel with the ongoing "commit end" operation. At this point the log tail was not changed yet, it is the same as it had been before we started the commit. The log head keeps moving forward, though.
The commit operation now needs to write the new master node, and the new master node should point to the new log tail. After this the LEBs between the old log tail and the new log tail can be unmapped and re-used again.
And here is the possible problem. We do 2 operations: (a) We first update the log tail position in memory (see 'ubifs_log_end_commit()'). (b) And then we write the master node (see the big lock of code in 'do_commit()').
But nothing prevents the log head from moving forward between (a) and (b), and the log head may "wrap" now to the old log tail. And when the "wrap" happens, the contends of the log tail gets erased. Now a power cut happens and we are in trouble. We end up with the old master node pointing to the old tail, which was erased. And replay fails because it expects the master node to point to the correct log tail at all times.
This patch merges the abovementioned (a) and (b) operations by moving the master node change code to the 'ubifs_log_end_commit()' function, so that it runs with the log mutex locked, which will prevent the log from being changed benween operations (a) and (b).
--- fs/ubifs/commit.c | 8 +++----- fs/ubifs/log.c | 11 ++++++++--- 2 files changed, 11 insertions(+), 8 deletions(-)
fs/ubifs/commit.c +3 -5
@@ -166,10 +166,6 @@ static int do_commit(struct ubifs_info * err =ubifs_orphan_end_commit (c);if (err) goto out; - old_ltail_lnum = c->ltail_lnum; - err =ubifs_log_end_commit (c, new_ltail_lnum); -if (err) - goto out; err =dbg_check_old_index (c, &zroot);if (err) goto out;
@@ -202,7 +198,9 @@ static int do_commit(struct ubifs_info * c->mst_node->flags |=cpu_to_le32 (UBIFS_MST_NO_ORPHS ); else c->mst_node->flags &= ~cpu_to_le32(UBIFS_MST_NO_ORPHS); - err =ubifs_write_master (c); + + old_ltail_lnum = c->ltail_lnum; + err =ubifs_log_end_commit (c, new_ltail_lnum);if (err) goto out;
fs/ubifs/log.c +8 -3
@@ -447,9 +447,9 @@ out:* @ltail_lnum: new log tail LEB number * * This function is called on when the commit operation was finished. It -* moves log tail to new position and unmaps LEBs which contain obsolete data. -* Returns zero in case of success and a negative error code in case of -* failure. +* moves log tail to new position and updates the master node so that it stores +* the new log tail LEB number. Returns zero in case of success and a negative +* error code in case of failure. */ int ubifs_log_end_commit (struct ubifs_info *c,int ltail_lnum) {
@@ -477,7 +477,12 @@ int ubifs_log_end_commit(struct ubifs_inspin_unlock (&c->buds_lock); err =dbg_check_bud_bytes (c); +if (err) + goto out; + err =ubifs_write_master (c); + +out:mutex_unlock (&c->log_mutex);return err; }
Greg Kroah-Hartman
maintainerPATCH 15/123 UBIFS: fix free log space calculation
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Artem Bityutskiy <[email protected]>
commit ba29e721eb2df6df8f33c1f248388bb037a47914 upstream.
Hu (hujianyang <[email protected]>) discovered an issue in the 'empty_log_bytes()' function, which calculates how many bytes are left in the log:
"
If 'c->lhead_lnum + 1 == c->ltail_lnum' and 'c->lhead_offs == c->leb_size', 'h' would equalent to 't' and 'empty_log_bytes()' would return 'c->log_bytes' instead of 0.
"
At this point it is not clear what would be the consequences of this, and whether this may lead to any problems, but this patch addresses the issue just in case.
--- fs/ubifs/log.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
fs/ubifs/log.c +6 -2
@@ -106,10 +106,14 @@ static inline long long empty_log_bytes( h = (long long )c->lhead_lnum * c->leb_size + c->lhead_offs; t = (long long )c->ltail_lnum * c->leb_size; -if (h >= t) +if (h > t)return c->log_bytes - h + t; -else +else if (h != t)return t - h; +else if (c->lhead_lnum != c->ltail_lnum) +return 0 ; +else +return c->log_bytes; }/**
Greg Kroah-Hartman
maintainerPATCH 16/123 vfs: fix data corruption when blocksize < pagesize for mmaped data
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 90a8020278c1598fafd071736a0846b38510309c upstream.
->page_mkwrite() is used by filesystems to allocate blocks under a page which is becoming writeably mmapped in some process' address space. This allows a filesystem to return a page fault if there is not enough space available, user exceeds quota or similar problem happens, rather than silently discarding data later when writepage is called.
However VFS fails to call ->page_mkwrite() in all the cases where filesystems need it when blocksize < pagesize. For example when blocksize = 1024, pagesize = 4096 the following is problematic:
ftruncate(fd, 0);
pwrite(fd, buf, 1024, 0);
map = mmap(NULL, 1024, PROT_WRITE, MAP_SHARED, fd, 0);
map[0] = 'a'; ----> page_mkwrite() for index 0 is called
ftruncate(fd, 10000); /* or even pwrite(fd, buf, 1, 10000) */ mremap(map, 1024, 10000, 0);
map[4095] = 'a'; ----> no page_mkwrite() called
At the moment ->page_mkwrite() is called, filesystem can allocate only one block for the page because i_size == 1024. Otherwise it would create blocks beyond i_size which is generally undesirable. But later at ->writepage() time, we also need to store data at offset 4095 but we don't have block allocated for it.
This patch introduces a helper function filesystems can use to have ->page_mkwrite() called at all the necessary moments.
--- fs/buffer.c | 3 ++ include/linux/mm.h | 1 mm/truncate.c | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++--- 3 files changed, 60 insertions(+), 3 deletions(-)
fs/buffer.c +3 -0
@@ -2018,6 +2018,7 @@ int generic_write_end(struct file *file, struct page *page, void *fsdata) { struct inode *inode = mapping->host; +loff_t old_size = inode->i_size;int i_size_changed =0 ; copied =block_write_end (file, mapping, pos, len, copied, page, fsdata);
@@ -2037,6 +2038,8 @@ int generic_write_end(struct file *file,unlock_page (page);page_cache_release (page); +if (old_size < pos) +pagecache_isize_extended (inode, old_size, pos);/* * Don't mark the inode dirty under page lock. First, it unnecessarily * makes the holding time of page lock longer. Second, it forces lock
include/linux/mm.h +1 -0
@@ -1004,6 +1004,7 @@ static inline void unmap_shared_mapping_extern void truncate_pagecache (struct inode *inode,loff_t old,loff_t new);extern void truncate_setsize (struct inode *inode,loff_t newsize); +void pagecache_isize_extended (struct inode *inode,loff_t from,loff_t to);void truncate_pagecache_range (struct inode *inode,loff_t offset,loff_t end);int truncate_inode_page (struct address_space *mapping,struct page *page);int generic_error_remove_page (struct address_space *mapping,struct page *page);
mm/truncate.c +56 -3
78 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 17/123 x86: Reject x32 executables if x32 ABI not supported
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
commit 0e6d3112a4e95d55cf6dca88f298d5f4b8f29bd1 upstream.
It is currently possible to execve() an x32 executable on an x86_64 kernel that has only ia32 compat enabled. However all its syscalls will fail, even _exit(). This usually causes it to segfault.
Change the ELF compat architecture check so that x32 executables are rejected if we don't support the x32 ABI.
--- arch/x86/include/asm/elf.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
arch/x86/include/asm/elf.h +3 -2
@@ -155,8 +155,9 @@ do { \#define elf_check_arch (x) \ ((x)->e_machine == EM_X86_64) -#define compat_elf_check_arch (x) \ - (elf_check_arch_ia32(x) || (x)->e_machine == EM_X86_64) +#define compat_elf_check_arch (x) \ + (elf_check_arch_ia32(x) || \ + (IS_ENABLED(CONFIG_X86_X32_ABI) && (x)->e_machine == EM_X86_64))#if __USER32_DS != __USER_DS# error "The following code assumes __USER32_DS == __USER_DS"
Greg Kroah-Hartman
maintainerPATCH 18/123 x86, fpu: __restore_xstate_sig()->math_state_restore() needs preempt_disable()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oleg Nesterov <[email protected]>
commit df24fb859a4e200d9324e2974229fbb7adf00aef upstream.
Add preempt_disable() + preempt_enable() around math_state_restore() in __restore_xstate_sig(). Otherwise __switch_to() after __thread_fpu_begin() can overwrite fpu->state we are going to restore.
--- arch/x86/kernel/xsave.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
arch/x86/kernel/xsave.c +4 -1
@@ -400,8 +400,11 @@ int __restore_xstate_sig(void __user *buset_used_math (); } -if (use_eager_fpu ()) +if (use_eager_fpu ()) { +preempt_disable ();math_state_restore (); +preempt_enable (); + }return err; }else {
Greg Kroah-Hartman
maintainerPATCH 19/123 x86, fpu: shift drop_init_fpu() from save_xstate_sig() to handle_signal()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oleg Nesterov <[email protected]>
commit 66463db4fc5605d51c7bb81d009d5bf30a783a2c upstream.
save_xstate_sig()->drop_init_fpu() doesn't look right. setup_rt_frame() can fail after that, in this case the next setup_rt_frame() triggered by SIGSEGV won't save fpu simply because the old state was lost. This obviously mean that fpu won't be restored after sys_rt_sigreturn() from SIGSEGV handler.
Shift drop_init_fpu() into !failed branch in handle_signal().
Test-case (needs -O2):
#include <stdio.h>
#include <signal.h>
#include <unistd.h>
#include <sys/syscall.h>
#include <sys/mman.h>
#include <pthread.h>
#include <assert.h>
volatile double D;
void test(double d)
{
int pid = getpid();
for (D = d; D == d; ) {
/* sys_tkill(pid, SIGHUP); asm to avoid save/reload
* fp regs around "C" call */
asm ("" : : "a"(200), "D"(pid), "S"(1));
asm ("syscall" : : : "ax");
}
printf("ERR!!\n");
}
void sigh(int sig)
{
}
char altstack[4096 * 10] __attribute__((aligned(4096)));
void *tfunc(void *arg)
{
for (;;) {
mprotect(altstack, sizeof(altstack), PROT_READ);
mprotect(altstack, sizeof(altstack), PROT_READ|PROT_WRITE);
}
}
int main(void)
{
stack_t st = {
.ss_sp = altstack,
.ss_size = sizeof(altstack),
.ss_flags = SS_ONSTACK,
};
struct sigaction sa = {
.sa_handler = sigh,
};
pthread_t pt;
sigaction(SIGSEGV, &sa, NULL);
sigaltstack(&st, NULL);
sa.sa_flags = SA_ONSTACK;
sigaction(SIGHUP, &sa, NULL);
pthread_create(&pt, NULL, tfunc, NULL);
test(123.456);
return 0;
}--- arch/x86/kernel/signal.c | 5 +++++ arch/x86/kernel/xsave.c | 2 -- 2 files changed, 5 insertions(+), 2 deletions(-)
arch/x86/kernel/signal.c +5 -0
@@ -677,6 +677,11 @@ handle_signal(struct ksignal *ksig, stru* handler too. */ regs->flags &= ~X86_EFLAGS_TF ; +/* +* Ensure the signal handler starts with the new fpu state. +*/ +if (used_math ()) +drop_init_fpu (current); }signal_setup_done (failed, ksig,test_thread_flag (TIF_SINGLESTEP )); }
arch/x86/kernel/xsave.c +0 -2
@@ -268,8 +268,6 @@ int save_xstate_sig(void __user *buf, voif (use_fxsr () &&save_xstate_epilog (buf_fx, ia32_fxstate))return -1 ; -drop_init_fpu (tsk);/* trigger finit */ -return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 20/123 x86, flags: Rename X86_EFLAGS_BIT1 to X86_EFLAGS_FIXED
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "H. Peter Anvin" <[email protected]>
commit 1adfa76a95fe4444124a502f7cc858a39d5b8e01 upstream.
Bit 1 in the x86 EFLAGS is always set. Name the macro something that actually tries to explain what it is all about, rather than being a tautology.
--- arch/x86/include/uapi/asm/processor-flags.h | 2 +- arch/x86/kernel/entry_64.S | 2 +- arch/x86/kernel/process_32.c | 2 +- arch/x86/kernel/process_64.c | 2 +- arch/x86/kvm/vmx.c | 2 +- drivers/lguest/x86/core.c | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-)
arch/x86/include/uapi/asm/processor-flags.h +1 -1
@@ -6,7 +6,7 @@* EFLAGS bits */ #define X86_EFLAGS_CF 0x00000001/* Carry Flag */ -#define X86_EFLAGS_BIT1 0x00000002/* Bit 1 - always on */ +#define X86_EFLAGS_FIXED 0x00000002/* Bit 1 - always on */ #define X86_EFLAGS_PF 0x00000004/* Parity Flag */ #define X86_EFLAGS_AF 0x00000010/* Auxiliary carry Flag */ #define X86_EFLAGS_ZF 0x00000040/* Zero Flag */
arch/x86/kernel/entry_64.S +1 -1
@@ -366,7 +366,7 @@ ENDPROC(native_usergs_sysret64) /*CFI_REL_OFFSET ss,0*/ pushq_cfi %rax /* rsp */ CFI_REL_OFFSET rsp,0 - pushq_cfi $(X86_EFLAGS_IF|X86_EFLAGS_BIT1) /* eflags - interrupts on */ + pushq_cfi $(X86_EFLAGS_IF|X86_EFLAGS_FIXED) /* eflags - interrupts on */ /*CFI_REL_OFFSET rflags,0*/ pushq_cfi $__KERNEL_CS /* cs */ /*CFI_REL_OFFSET cs,0*/
arch/x86/kernel/process_32.c +1 -1
@@ -147,7 +147,7 @@ int copy_thread(unsigned long clone_flag childregs->bp = arg; childregs->orig_ax =-1 ; childregs->cs = __KERNEL_CS |get_kernel_rpl (); - childregs->flags =X86_EFLAGS_IF |X86_EFLAGS_BIT1 ; + childregs->flags =X86_EFLAGS_IF |X86_EFLAGS_FIXED ; p->fpu_counter =0 ; p->thread.io_bitmap_ptr =NULL ;memset (p->thread.ptrace_bps,0 ,sizeof (p->thread.ptrace_bps));
arch/x86/kernel/process_64.c +1 -1
@@ -176,7 +176,7 @@ int copy_thread(unsigned long clone_flag childregs->bp = arg; childregs->orig_ax =-1 ; childregs->cs = __KERNEL_CS |get_kernel_rpl (); - childregs->flags =X86_EFLAGS_IF |X86_EFLAGS_BIT1 ; + childregs->flags =X86_EFLAGS_IF |X86_EFLAGS_FIXED ;return 0 ; } *childregs = *current_pt_regs ();
arch/x86/kvm/vmx.c +1 -1
@@ -7949,7 +7949,7 @@ static void load_vmcs12_host_state(struckvm_register_write (vcpu,VCPU_REGS_RSP , vmcs12->host_rsp);kvm_register_write (vcpu,VCPU_REGS_RIP , vmcs12->host_rip); -vmx_set_rflags (vcpu,X86_EFLAGS_BIT1 ); +vmx_set_rflags (vcpu,X86_EFLAGS_FIXED );/* * Note that calling vmx_set_cr0 is important, even if cr0 hasn't * actually changed, because it depends on the current state of
drivers/lguest/x86/core.c +1 -1
@@ -700,7 +700,7 @@ void lguest_arch_setup_regs(struct lg_cp* interrupts are enabled. We always leave interrupts enabled while * running the Guest. */ - regs->eflags =X86_EFLAGS_IF |X86_EFLAGS_BIT1 ; + regs->eflags =X86_EFLAGS_IF |X86_EFLAGS_FIXED ;/* * The "Extended Instruction Pointer" register says where the Guest is
Greg Kroah-Hartman
maintainerPATCH 21/123 x86_64, entry: Filter RFLAGS.NT on entry from userspace
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Lutomirski <[email protected]>
commit 8c7aa698baca5e8f1ba9edb68081f1e7a1abf455 upstream.
The NT flag doesn't do anything in long mode other than causing IRET to #GP. Oddly, CPL3 code can still set NT using popf.
Entry via hardware or software interrupt clears NT automatically, so the only relevant entries are fast syscalls.
If user code causes kernel code to run with NT set, then there's at least some (small) chance that it could cause trouble. For example, user code could cause a call to EFI code with NT set, and who knows what would happen? Apparently some games on Wine sometimes do this (!), and, if an IRET return happens, they will segfault. That segfault cannot be handled, because signal delivery fails, too.
This patch programs the CPU to clear NT on entry via SYSCALL (both 32-bit and 64-bit, by my reading of the AMD APM), and it clears NT in software on entry via SYSENTER.
To save a few cycles, this borrows a trick from Jan Beulich in Xen:
it checks whether NT is set before trying to clear it. As a result, it seems to have very little effect on SYSENTER performance on my machine.
There's another minor bug fix in here: it looks like the CFI annotations were wrong if CONFIG_AUDITSYSCALL=n.
Testers beware: on Xen, SYSENTER with NT set turns into a GPF.
I haven't touched anything on 32-bit kernels.
The syscall mask change comes from a variant of this patch by Anish Bhatt.
Note to stable maintainers: there is no known security issue here. A misguided program can set NT and cause the kernel to try and fail to deliver SIGSEGV, crashing the program. This patch fixes Far Cry on Wine: https://bugs.winehq.org/show_bug.cgi?id=33275
--- arch/x86/ia32/ia32entry.S | 18 +++++++++++++++++- arch/x86/kernel/cpu/common.c | 2 +- 2 files changed, 18 insertions(+), 2 deletions(-)
arch/x86/ia32/ia32entry.S +17 -1
@@ -151,6 +151,16 @@ ENTRY(ia32_sysenter_target) 1: movl (%rbp),%ebp _ASM_EXTABLE(1b,ia32_badarg) ASM_CLAC + + /* + * Sysenter doesn't filter flags, so we need to clear NT + * ourselves. To save a few cycles, we can check whether + * NT was set instead of doing an unconditional popfq. + */ + testl $X86_EFLAGS_NT,EFLAGS(%rsp) /* saved EFLAGS match cpu */ + jnz sysenter_fix_flags +sysenter_flags_fixed: + orl $TS_COMPAT,TI_status+THREAD_INFO(%rsp,RIP-ARGOFFSET) testl $_TIF_WORK_SYSCALL_ENTRY,TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET) CFI_REMEMBER_STATE
@@ -184,6 +194,8 @@ sysexit_from_sys_call: TRACE_IRQS_ON ENABLE_INTERRUPTS_SYSEXIT32 + CFI_RESTORE_STATE + #ifdef CONFIG_AUDITSYSCALL .macro auditsys_entry_common movl %esi,%r9d /* 6th arg: 4th syscall arg */
@@ -226,7 +238,6 @@ sysexit_from_sys_call: .endm sysenter_auditsys: - CFI_RESTORE_STATE auditsys_entry_common movl %ebp,%r9d /* reload 6th syscall arg */ jmp sysenter_dispatch
@@ -235,6 +246,11 @@ sysexit_audit: auditsys_exit sysexit_from_sys_call #endif +sysenter_fix_flags: + pushq_cfi $(X86_EFLAGS_IF|X86_EFLAGS_FIXED) + popfq_cfi + jmp sysenter_flags_fixed + sysenter_tracesys: #ifdef CONFIG_AUDITSYSCALL testl $(_TIF_WORK_SYSCALL_ENTRY & ~_TIF_SYSCALL_AUDIT),TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
arch/x86/kernel/cpu/common.c +1 -1
@@ -1134,7 +1134,7 @@ void syscall_init(void)/* Flags to clear on syscall */ wrmsrl (MSR_SYSCALL_MASK ,X86_EFLAGS_TF |X86_EFLAGS_DF |X86_EFLAGS_IF | -X86_EFLAGS_IOPL |X86_EFLAGS_AC ); +X86_EFLAGS_IOPL |X86_EFLAGS_AC |X86_EFLAGS_NT ); }/*
Greg Kroah-Hartman
maintainerPATCH 22/123 x86_64, entry: Fix out of bounds read on sysenter
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Lutomirski <[email protected]>
commit 653bc77af60911ead1f423e588f54fc2547c4957 upstream.
Rusty noticed a Really Bad Bug (tm) in my NT fix. The entry code reads out of bounds, causing the NT fix to be unreliable. But, and this is much, much worse, if your stack is somehow just below the top of the direct map (or a hole), you read out of bounds and crash.
Excerpt from the crash:
[ 1.129513] RSP: 0018:ffff88001da4bf88 EFLAGS: 00010296
2b:* f7 84 24 90 00 00 00 testl $0x4000,0x90(%rsp)
That read is deterministically above the top of the stack. I thought I even single-stepped through this code when I wrote it to check the offset, but I clearly screwed it up.
--- arch/x86/ia32/ia32entry.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/ia32/ia32entry.S +1 -1
@@ -157,7 +157,7 @@ ENTRY(ia32_sysenter_target) * ourselves. To save a few cycles, we can check whether * NT was set instead of doing an unconditional popfq. */ - testl $X86_EFLAGS_NT,EFLAGS(%rsp) /* saved EFLAGS match cpu */ + testl $X86_EFLAGS_NT,EFLAGS-ARGOFFSET(%rsp) jnz sysenter_fix_flags sysenter_flags_fixed:
Greg Kroah-Hartman
maintainerPATCH 23/123 x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dexuan Cui <[email protected]>
commit d1cd1210834649ce1ca6bafe5ac25d2f40331343 upstream.
pte_pfn() returns a PFN of long (32 bits in 32-PAE), so "long << PAGE_SHIFT" will overflow for PFNs above 4GB.
Due to this issue, some Linux 32-PAE distros, running as guests on Hyper-V, with 5GB memory assigned, can't load the netvsc driver successfully and hence the synthetic network device can't work (we can use the kernel parameter mem=3000M to work around the issue).
Cast pte_pfn() to phys_addr_t before shifting.
--- arch/x86/mm/pageattr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/mm/pageattr.c +1 -1
@@ -389,7 +389,7 @@ phys_addr_t slow_virt_to_phys(void *__vi psize =page_level_size (level); pmask =page_level_mask (level); offset = virt_addr & ~pmask; - phys_addr =pte_pfn (*pte) <<PAGE_SHIFT ; + phys_addr = (phys_addr_t )pte_pfn (*pte) <<PAGE_SHIFT ;return (phys_addr | offset); }EXPORT_SYMBOL_GPL (slow_virt_to_phys);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Greg Kroah-Hartman
maintainerPATCH 24/123 evm: check xattr value length and type in evm_inode_setxattr()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Kasatkin <[email protected]>
commit 3b1deef6b1289a99505858a3b212c5b50adf0c2f upstream.
evm_inode_setxattr() can be called with no value. The function does not check the length so that following command can be used to produce the kernel oops: setfattr -n security.evm FOO. This patch fixes it.
Changes in v3:
* there is no reason to return different error codes for EVM_XATTR_HMAC and non EVM_XATTR_HMAC. Remove unnecessary test then.
Changes in v2:
* testing for validity of xattr type
[ 1106.396921] BUG: unable to handle kernel NULL pointer dereference at (null) [ 1106.398192] IP: [<ffffffff812af7b8>] evm_inode_setxattr+0x2a/0x48 [ 1106.399244] PGD 29048067 PUD 290d7067 PMD 0 [ 1106.399953] Oops: 0000 [#1] SMP [ 1106.400020] Modules linked in: bridge stp llc evdev serio_raw i2c_piix4 button fuse [ 1106.400020] CPU: 0 PID: 3635 Comm: setxattr Not tainted 3.16.0-kds+ #2936 [ 1106.400020] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 1106.400020] task: ffff8800291a0000 ti: ffff88002917c000 task.ti: ffff88002917c000 [ 1106.400020] RIP: 0010:[<ffffffff812af7b8>] [<ffffffff812af7b8>] evm_inode_setxattr+0x2a/0x48 [ 1106.400020] RSP: 0018:ffff88002917fd50 EFLAGS: 00010246 [ 1106.400020] RAX: 0000000000000000 RBX: ffff88002917fdf8 RCX: 0000000000000000 [ 1106.400020] RDX: 0000000000000000 RSI: ffffffff818136d3 RDI: ffff88002917fdf8 [ 1106.400020] RBP: ffff88002917fd68 R08: 0000000000000000 R09: 00000000003ec1df [ 1106.400020] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8800438a0a00 [ 1106.400020] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 1106.400020] FS: 00007f7dfa7d7740(0000) GS:ffff88005da00000(0000) knlGS:0000000000000000 [ 1106.400020] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1106.400020] CR2: 0000000000000000 CR3: 000000003763e000 CR4: 00000000000006f0 [ 1106.400020] Stack: [ 1106.400020] ffff8800438a0a00 ffff88002917fdf8 0000000000000000 ffff88002917fd98 [ 1106.400020] ffffffff812a1030 ffff8800438a0a00 ffff88002917fdf8 0000000000000000 [ 1106.400020] 0000000000000000 ffff88002917fde0 ffffffff8116d08a ffff88002917fdc8 [ 1106.400020] Call Trace: [ 1106.400020] [<ffffffff812a1030>] security_inode_setxattr+0x5d/0x6a [ 1106.400020] [<ffffffff8116d08a>] vfs_setxattr+0x6b/0x9f [ 1106.400020] [<ffffffff8116d1e0>] setxattr+0x122/0x16c [ 1106.400020] [<ffffffff811687e8>] ? mnt_want_write+0x21/0x45 [ 1106.400020] [<ffffffff8114d011>] ? __sb_start_write+0x10f/0x143 [ 1106.400020] [<ffffffff811687e8>] ? mnt_want_write+0x21/0x45 [ 1106.400020] [<ffffffff811687c0>] ? __mnt_want_write+0x48/0x4f [ 1106.400020] [<ffffffff8116d3e6>] SyS_setxattr+0x6e/0xb0 [ 1106.400020] [<ffffffff81529da9>] system_call_fastpath+0x16/0x1b [ 1106.400020] Code: c3 0f 1f 44 00 00 55 48 89 e5 41 55 49 89 d5 41 54 49 89 fc 53 48 89 f3 48 c7 c6 d3 36 81 81 48 89 df e8 18 22 04 00 85 c0 75 07 <41> 80 7d 00 02 74 0d 48 89 de 4c 89 e7 e8 5a fe ff ff eb 03 83 [ 1106.400020] RIP [<ffffffff812af7b8>] evm_inode_setxattr+0x2a/0x48 [ 1106.400020] RSP <ffff88002917fd50> [ 1106.400020] CR2: 0000000000000000 [ 1106.428061] ---[ end trace ae08331628ba3050 ]---
--- security/integrity/evm/evm_main.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
security/integrity/evm/evm_main.c +6 -3
@@ -286,9 +286,12 @@ int evm_inode_setxattr(struct dentry *de {const struct evm_ima_xattr_data *xattr_data = xattr_value; -if ((strcmp (xattr_name,XATTR_NAME_EVM ) ==0 ) - && (xattr_data->type ==EVM_XATTR_HMAC )) -return -EPERM ; +if (strcmp (xattr_name,XATTR_NAME_EVM ) ==0 ) { +if (!xattr_value_len) +return -EINVAL ; +if (xattr_data->type !=EVM_IMA_XATTR_DIGSIG ) +return -EPERM ; + }return evm_protect_xattr (dentry, xattr_name, xattr_value, xattr_value_len); }
Greg Kroah-Hartman
maintainerPATCH 25/123 ALSA: pcm: Zero-clear reserved fields of PCM status ioctl in compat mode
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 317168d0c766defd14b3d0e9c2c4a9a258b803ee upstream.
In compat mode, we copy each field of snd_pcm_status struct but don't touch the reserved fields, and this leaves uninitialized values there. Meanwhile the native ioctl does zero-clear the whole structure, so we should follow the same rule in compat mode, too.
--- sound/core/pcm_compat.c | 2 ++ 1 file changed, 2 insertions(+)
sound/core/pcm_compat.c +2 -0
@@ -206,6 +206,8 @@ static int snd_pcm_status_user_compat(stif (err <0 )return err; +if (clear_user (src,sizeof (*src))) +return -EFAULT ; if (put_user(status.state, &src->state) || compat_put_timespec(&status.trigger_tstamp, &src->trigger_tstamp) || compat_put_timespec(&status.tstamp, &src->tstamp) ||
Greg Kroah-Hartman
maintainerPATCH 26/123 kill wbuf_queued/wbuf_dwork_lock
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
commit 99358a1ca53e8e6ce09423500191396f0e6584d2 upstream.
schedule_delayed_work() happening when the work is already pending is a cheap no-op. Don't bother with ->wbuf_queued logics - it's both broken (cancelling ->wbuf_dwork leaves it set, as spotted by Jeff Harris) and pointless. It's cheaper to let schedule_delayed_work() handle that case.
--- fs/jffs2/jffs2_fs_sb.h | 2 -- fs/jffs2/wbuf.c | 17 ++--------------- 2 files changed, 2 insertions(+), 17 deletions(-)
fs/jffs2/jffs2_fs_sb.h +0 -2
@@ -134,8 +134,6 @@ struct jffs2_sb_info {struct rw_semaphore wbuf_sem;/* Protects the write buffer */ struct delayed_work wbuf_dwork;/* write-buffer write-out work */ -int wbuf_queued;/* non-zero delayed work is queued */ -spinlock_t wbuf_dwork_lock;/* protects wbuf_dwork and and wbuf_queued */ unsigned char *oobbuf;int oobavail;/* How many bytes are available for JFFS2 in OOB */
fs/jffs2/wbuf.c +2 -15
@@ -1162,10 +1162,6 @@ static void delayed_wbuf_sync(struct worstruct jffs2_sb_info *c =work_to_sb (work);struct super_block *sb =OFNI_BS_2SFFJ (c); -spin_lock (&c->wbuf_dwork_lock); - c->wbuf_queued =0 ; -spin_unlock (&c->wbuf_dwork_lock); -if (!(sb->s_flags &MS_RDONLY )) {jffs2_dbg (1 ,"%s()\n" , __func__);jffs2_flush_wbuf_gc (c,0 );
@@ -1180,14 +1176,9 @@ void jffs2_dirty_trigger(struct jffs2_sbif (sb->s_flags &MS_RDONLY )return ; -spin_lock (&c->wbuf_dwork_lock); -if (!c->wbuf_queued) { + delay =msecs_to_jiffies (dirty_writeback_interval *10 ); +if (queue_delayed_work (system_long_wq, &c->wbuf_dwork, delay))jffs2_dbg (1 ,"%s()\n" , __func__); - delay =msecs_to_jiffies (dirty_writeback_interval *10 ); -queue_delayed_work (system_long_wq, &c->wbuf_dwork, delay); - c->wbuf_queued =1 ; - } -spin_unlock (&c->wbuf_dwork_lock); }int jffs2_nand_flash_setup (struct jffs2_sb_info *c)
@@ -1211,7 +1202,6 @@ int jffs2_nand_flash_setup(struct jffs2_/* Initialise write buffer */ init_rwsem (&c->wbuf_sem); -spin_lock_init (&c->wbuf_dwork_lock);INIT_DELAYED_WORK (&c->wbuf_dwork, delayed_wbuf_sync); c->wbuf_pagesize = c->mtd->writesize; c->wbuf_ofs =0xFFFFFFFF ;
@@ -1251,7 +1241,6 @@ int jffs2_dataflash_setup(struct jffs2_s/* Initialize write buffer */ init_rwsem (&c->wbuf_sem); -spin_lock_init (&c->wbuf_dwork_lock);INIT_DELAYED_WORK (&c->wbuf_dwork, delayed_wbuf_sync); c->wbuf_pagesize = c->mtd->erasesize;
@@ -1311,7 +1300,6 @@ int jffs2_nor_wbuf_flash_setup(struct jf/* Initialize write buffer */ init_rwsem (&c->wbuf_sem); -spin_lock_init (&c->wbuf_dwork_lock);INIT_DELAYED_WORK (&c->wbuf_dwork, delayed_wbuf_sync); c->wbuf_pagesize = c->mtd->writesize;
@@ -1346,7 +1334,6 @@ int jffs2_ubivol_setup(struct jffs2_sb_ireturn 0 ;init_rwsem (&c->wbuf_sem); -spin_lock_init (&c->wbuf_dwork_lock);INIT_DELAYED_WORK (&c->wbuf_dwork, delayed_wbuf_sync); c->wbuf_pagesize = c->mtd->writesize;
Greg Kroah-Hartman
maintainerPATCH 27/123 fix misuses of f_count() in ppp and netlink
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
commit 24dff96a37a2ca319e75a74d3929b2de22447ca6 upstream.
we used to check for "nobody else could start doing anything with that opened file" by checking that refcount was 2 or less - one for descriptor table and one we'd acquired in fget() on the way to wherever we are. That was race-prone (somebody else might have had a reference to descriptor table and do fget() just as we'd been checking) and it had become flat-out incorrect back when we switched to fget_light() on those codepaths - unlike fget(), it doesn't grab an extra reference unless the descriptor table is shared. The same change allowed a race-free check, though - we are safe exactly when refcount is less than 2.
It was a long time ago; pre-2.6.12 for ioctl() (the codepath leading to ppp one) and 2.6.17 for sendmsg() (netlink one). OTOH, netlink hadn't grown that check until 3.9 and ppp used to live in drivers/net, not drivers/net/ppp until 3.1. The bug existed well before that, though, and the same fix used to apply in old location of file.
--- drivers/net/ppp/ppp_generic.c | 2 +- net/netlink/af_netlink.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
drivers/net/ppp/ppp_generic.c +1 -1
@@ -601,7 +601,7 @@ static long ppp_ioctl(struct file *file,if (file == ppp->owner)ppp_shutdown_interface (ppp); } -if (atomic_long_read (&file->f_count) <=2 ) { +if (atomic_long_read (&file->f_count) <2 ) {ppp_release (NULL , file); err =0 ; }else
net/netlink/af_netlink.c +1 -1
@@ -571,7 +571,7 @@ static int netlink_mmap_sendmsg(struct s* after validation, the socket and the ring may only be used by a * single process, otherwise we fall back to copying. */ -if (atomic_long_read (&sk->sk_socket->file->f_count) >2 || +if (atomic_long_read (&sk->sk_socket->file->f_count) >1 ||atomic_read (&nlk->mapped) >1 ) excl = false;
Greg Kroah-Hartman
maintainerPATCH 28/123 crypto: more robust crypto_memneq
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cesar Eduardo Barros <[email protected]>
commit fe8c8a126806fea4465c43d62a1f9d273a572bf5 upstream.
[Only use the compiler.h portion of this patch, to get the OPTIMIZER_HIDE_VAR() macro, which we need for other -stable patches
- gregkh]
Disabling compiler optimizations can be fragile, since a new optimization could be added to -O0 or -Os that breaks the assumptions the code is making.
Instead of disabling compiler optimizations, use a dummy inline assembly (based on RELOC_HIDE) to block the problematic kinds of optimization, while still allowing other optimizations to be applied to the code.
The dummy inline assembly is added after every OR, and has the accumulator variable as its input and output. The compiler is forced to assume that the dummy inline assembly could both depend on the accumulator variable and change the accumulator variable, so it is forced to compute the value correctly before the inline assembly, and cannot assume anything about its value after the inline assembly.
This change should be enough to make crypto_memneq work correctly (with data-independent timing) even if it is inlined at its call sites. That can be done later in a followup patch.
Compile-tested on x86_64.
--- include/linux/compiler-gcc.h | 3 +++ include/linux/compiler-intel.h | 7 +++++++ include/linux/compiler.h | 4 ++++ 3 files changed, 14 insertions(+)
include/linux/compiler-gcc.h +3 -0
@@ -37,6 +37,9 @@ __asm__ ("" :"=r" (__ptr) :"0" (ptr)); \ (typeof(ptr)) (__ptr + (off)); }) +/* Make the optimizer believe the variable can be manipulated arbitrarily. */ +#define OPTIMIZER_HIDE_VAR (var) __asm__ ("" : "=r" (var) : "0" (var)) +#ifdef __CHECKER__#define __must_be_array (arr) 0#else
include/linux/compiler-intel.h +7 -0
@@ -15,6 +15,7 @@*/ #undef barrier#undef RELOC_HIDE +#undef OPTIMIZER_HIDE_VAR#define barrier () __memory_barrier()
@@ -23,6 +24,12 @@ __ptr = (unsigned long ) (ptr); \ (typeof(ptr)) (__ptr + (off)); }) +/* This should act as an optimization barrier on var. +* Given that this compiler does not have inline assembly, a compiler barrier +* is the best we can do. +*/ +#define OPTIMIZER_HIDE_VAR (var) barrier() +/* Intel ECC compiler doesn't support __builtin_types_compatible_p() */ #define __must_be_array (a) 0
include/linux/compiler.h +4 -0
@@ -170,6 +170,10 @@ void ftrace_likely_update(struct ftrace_ (typeof(ptr)) (__ptr + (off)); })#endif +#ifndef OPTIMIZER_HIDE_VAR +#define OPTIMIZER_HIDE_VAR (var) barrier() +#endif +/* Not-quite-unique ID. */ #ifndef __UNIQUE_ID# define __UNIQUE_ID (prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix), __LINE__)
Greg Kroah-Hartman
maintainerPATCH 29/123 random: add and use memzero_explicit() for clearing data
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
commit d4c5efdb97773f59a2b711754ca0953f24516739 upstream.
zatimend has reported that in his environment (3.16/gcc4.8.3/corei7) memset() calls which clear out sensitive data in extract_{buf,entropy, entropy_user}() in random driver are being optimized away by gcc.
Add a helper memzero_explicit() (similarly as explicit_bzero() variants) that can be used in such cases where a variable with sensitive data is being cleared out in the end. Other use cases might also be in crypto code. [ I have put this into lib/string.c though, as it's always built-in and doesn't need any dependencies then. ]
Fixes kernel bugzilla: 82041
--- drivers/char/random.c | 10 +++++----- include/linux/string.h | 5 +++-- lib/string.c | 16 ++++++++++++++++ 3 files changed, 24 insertions(+), 7 deletions(-)
drivers/char/random.c +5 -5
@@ -933,8 +933,8 @@ static void extract_buf(struct entropy_s* pool while mixing, and hash one final time. */ sha_transform (hash.w, extract, workspace); -memset (extract,0 ,sizeof (extract)); -memset (workspace,0 ,sizeof (workspace)); +memzero_explicit (extract,sizeof (extract)); +memzero_explicit (workspace,sizeof (workspace));/* * In case the hash function has some recognizable output
@@ -957,7 +957,7 @@ static void extract_buf(struct entropy_s }memcpy (out, &hash,EXTRACT_SIZE ); -memset (&hash,0 ,sizeof (hash)); +memzero_explicit (&hash,sizeof (hash)); } static ssize_t extract_entropy(struct entropy_store *r, void *buf,
@@ -1005,7 +1005,7 @@ static ssize_t extract_entropy(struct en }/* Wipe data just returned from memory */ -memset (tmp,0 ,sizeof (tmp)); +memzero_explicit (tmp,sizeof (tmp));return ret; }
@@ -1043,7 +1043,7 @@ static ssize_t extract_entropy_user(stru }/* Wipe data just returned from memory */ -memset (tmp,0 ,sizeof (tmp)); +memzero_explicit (tmp,sizeof (tmp));return ret; }
include/linux/string.h +3 -2
@@ -129,7 +129,7 @@ int bprintf(u32 *bin_buf, size_t size, c#endif extern ssize_t memory_read_from_buffer (void *to,size_t count,loff_t *ppos, -const void *from,size_t available); +const void *from,size_t available);/** * strstarts - does @str start with @prefix?
@@ -141,7 +141,8 @@ static inline bool strstarts(const charreturn strncmp (str, prefix,strlen (prefix)) ==0 ; } -extern size_t memweight (const void *ptr,size_t bytes); +size_t memweight (const void *ptr,size_t bytes); +void memzero_explicit (void *s,size_t count);/** * kbasename - return the last part of a pathname.
lib/string.c +16 -0
@@ -586,6 +586,22 @@ void *memset(void *s, int c, size_t counEXPORT_SYMBOL (memset);#endif +/** +* memzero_explicit - Fill a region of memory (e.g. sensitive +* keying data) with 0s. +* @s: Pointer to the start of the area. +* @count: The size of the area. +* +* memzero_explicit() doesn't need an arch-specific version as +* it just invokes the one of memset() implicitly. +*/ +void memzero_explicit (void *s,size_t count) +{ +memset (s,0 , count); +OPTIMIZER_HIDE_VAR (s); +} +EXPORT_SYMBOL (memzero_explicit); +#ifndef __HAVE_ARCH_MEMCPY/** * memcpy - Copy one area of memory to another
Greg Kroah-Hartman
maintainerPATCH 30/123 UBI: add missing kmem_cache_free() in process_pool_aeb error path
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Richard Genoud <[email protected]>
commit 1bf1890e86869032099b539bc83b098be12fc5a7 upstream.
I ran into this error after a ubiupdatevol, because I forgot to backport e9110361a9a4 UBI: fix the volumes tree sorting criteria.
UBI error: process_pool_aeb: orphaned volume in fastmap pool UBI error: ubi_scan_fastmap: Attach by fastmap failed, doing a full scan! kmem_cache_destroy ubi_ainf_peb_slab: Slab cache still has objects
CPU: 0 PID: 1 Comm: swapper Not tainted 3.14.18-00053-gf05cac8dbf85 #1 [<c000d298>] (unwind_backtrace) from [<c000baa8>] (show_stack+0x10/0x14) [<c000baa8>] (show_stack) from [<c01b7a68>] (destroy_ai+0x230/0x244) [<c01b7a68>] (destroy_ai) from [<c01b8fd4>] (ubi_attach+0x98/0x1ec) [<c01b8fd4>] (ubi_attach) from [<c01ade90>] (ubi_attach_mtd_dev+0x2b8/0x868) [<c01ade90>] (ubi_attach_mtd_dev) from [<c038b510>] (ubi_init+0x1dc/0x2ac) [<c038b510>] (ubi_init) from [<c0008860>] (do_one_initcall+0x94/0x140) [<c0008860>] (do_one_initcall) from [<c037aadc>] (kernel_init_freeable+0xe8/0x1b0) [<c037aadc>] (kernel_init_freeable) from [<c02730ac>] (kernel_init+0x8/0xe4) [<c02730ac>] (kernel_init) from [<c00093f0>] (ret_from_fork+0x14/0x24)
UBI: scanning is finished
Freeing the cache in the error path fixes the Slab error.
Tested on at91sam9g35 (3.14.18+fastmap backports)
--- drivers/mtd/ubi/fastmap.c | 1 + 1 file changed, 1 insertion(+)
drivers/mtd/ubi/fastmap.c +1 -0
@@ -330,6 +330,7 @@ static int process_pool_aeb(struct ubi_d av = tmp_av; else {ubi_err ("orphaned volume in fastmap pool!" ); +kmem_cache_free (ai->aeb_slab_cache, new_aeb);return UBI_BAD_FASTMAP ; }
Greg Kroah-Hartman
maintainerPATCH 31/123 mnt: Prevent pivot_root from creating a loop in the mount tree
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Eric W. Biederman" <[email protected]>
commit 0d0826019e529f21c84687521d03f60cd241ca7d upstream.
Andy Lutomirski recently demonstrated that when chroot is used to set the root path below the path for the new ``root'' passed to pivot_root the pivot_root system call succeeds and leaks mounts.
In examining the code I see that starting with a new root that is below the current root in the mount tree will result in a loop in the mount tree after the mounts are detached and then reattached to one another. Resulting in all kinds of ugliness including a leak of that mounts involved in the leak of the mount loop.
Prevent this problem by ensuring that the new mount is reachable from the current root of the mount tree.
[Added stable cc. Fixes CVE-2014-7970. --Andy]
--- fs/namespace.c | 3 +++ 1 file changed, 3 insertions(+)
fs/namespace.c +3 -0
@@ -2696,6 +2696,9 @@ SYSCALL_DEFINE2(pivot_root, const char _/* make sure we can reach put_old from new_root */ if (!is_path_reachable (old_mnt, old.dentry, &new)) goto out4; +/* make certain new is below the root */ +if (!is_path_reachable (new_mnt, new.dentry, &root)) + goto out4; root_mp->m_count++;/* pin it so it won't go away */ br_write_lock (&vfsmount_lock);detach_mnt (new_mnt, &parent_path);
Greg Kroah-Hartman
maintainerPATCH 32/123 mfd: rtsx_pcr: Fix MSI enable error handling
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chris Ball <[email protected]>
commit 5152970538a5e16c03bbcb9f1c780489a795ed40 upstream.
pci_enable_msi() can return failure with both positive and negative integers -- it returns 0 for success -- but is only tested here for "if (ret < 0)". This causes us to try to use MSI on the RTS5249 SD reader in the Dell XPS 11 when enabling MSI failed, causing:
[ 1.737110] rtsx_pci: probe of 0000:05:00.0 failed with error -110
--- drivers/mfd/rtsx_pcr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mfd/rtsx_pcr.c +1 -1
@@ -1137,7 +1137,7 @@ static int rtsx_pci_probe(struct pci_dev pcr->msi_en = msi_en;if (pcr->msi_en) { ret =pci_enable_msi (pcidev); -if (ret <0 ) +if (ret) pcr->msi_en = false; }
Greg Kroah-Hartman
maintainerPATCH 33/123 pstore: Fix duplicate {console,ftrace}-efi entries
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Valdis Kletnieks <[email protected]>
commit d4bf205da618bbd0b038e404d646f14e76915718 upstream.
The pstore filesystem still creates duplicate filename/inode pairs for some pstore types. Add the id to the filename to prevent that.
Before patch:
[/sys/fs/pstore] ls -li
total 0
1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi 1250 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi
After:
[/sys/fs/pstore] ls -li
total 0
1232 -r--r--r--. 1 root root 148 Sep 29 17:09 console-efi-141202499100000 1231 -r--r--r--. 1 root root 67 Sep 29 17:09 console-efi-141202499200000 1230 -r--r--r--. 1 root root 148 Sep 29 17:44 console-efi-141202705400000 1229 -r--r--r--. 1 root root 67 Sep 29 17:44 console-efi-141202705500000 1228 -r--r--r--. 1 root root 67 Sep 29 20:42 console-efi-141203772600000 1227 -r--r--r--. 1 root root 148 Sep 29 23:42 console-efi-141204854900000 1226 -r--r--r--. 1 root root 67 Sep 29 23:42 console-efi-141204855000000 1225 -r--r--r--. 1 root root 148 Sep 29 23:59 console-efi-141204954200000 1224 -r--r--r--. 1 root root 67 Sep 29 23:59 console-efi-141204954400000
--- fs/pstore/inode.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/pstore/inode.c +2 -2
@@ -316,10 +316,10 @@ int pstore_mkfile(enum pstore_type_id tysprintf (name,"dmesg-%s-%lld" , psname, id);break ;case PSTORE_TYPE_CONSOLE : -sprintf (name,"console-%s" , psname); +sprintf (name,"console-%s-%lld" , psname, id);break ;case PSTORE_TYPE_FTRACE : -sprintf (name,"ftrace-%s" , psname); +sprintf (name,"ftrace-%s-%lld" , psname, id);break ;case PSTORE_TYPE_MCE :sprintf (name,"mce-%s-%lld" , psname, id);
Greg Kroah-Hartman
maintainerPATCH 34/123 selinux: fix inode security list corruption
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stephen Smalley <[email protected]>
commit 923190d32de4428afbea5e5773be86bea60a9925 upstream.
sb_finish_set_opts() can race with inode_free_security() when initializing inode security structures for inodes created prior to initial policy load or by the filesystem
during ->mount(). This appears to have always been
a possible race, but commit 3dc91d4 ("SELinux: Fix possible NULL pointer dereference in selinux_inode_permission()") made it more evident by immediately reusing the unioned list/rcu element of the inode security structure for call_rcu() upon an inode_free_security(). But the underlying issue was already present before that commit as a possible use-after-free of isec.
Shivnandan Kumar reported the list corruption and proposed a patch to split the list and rcu elements out of the union as separate fields of the inode_security_struct so that setting the rcu element would not affect the list element. However, this would merely hide the issue and not truly fix the code.
This patch instead moves up the deletion of the list entry prior to dropping the sbsec->isec_lock initially. Then, if the inode is dropped subsequently, there will be no further references to the isec.
--- security/selinux/hooks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
security/selinux/hooks.c +1 -1
@@ -437,6 +437,7 @@ next_inode:list_entry (sbsec->isec_head.next, struct inode_security_struct, list);struct inode *inode = isec->inode; +list_del_init (&isec->list);spin_unlock (&sbsec->isec_lock); inode =igrab (inode);if (inode) {
@@ -445,7 +446,6 @@ next_inode:iput (inode); }spin_lock (&sbsec->isec_lock); -list_del_init (&isec->list); goto next_inode; }spin_unlock (&sbsec->isec_lock);
Greg Kroah-Hartman
maintainerPATCH 35/123 virtio_pci: fix virtio spec compliance on restore
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Michael S. Tsirkin" <[email protected]>
commit 6fbc198cf623944ab60a1db6d306a4d55cdd820d upstream.
On restore, virtio pci does the following:
+ set features
+ init vqs etc - device can be used at this point!
+ set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits
This is in violation of the virtio spec, which
requires the following order:
- ACKNOWLEDGE
- DRIVER
- init vqs
- DRIVER_OK
This behaviour will break with hypervisors that assume spec compliant behaviour. It seems like a good idea to have this patch applied to stable branches to reduce the support butden for the hypervisors.
--- drivers/virtio/virtio_pci.c | 33 ++++++++++++++++++++++++++++++--- 1 file changed, 30 insertions(+), 3 deletions(-)
drivers/virtio/virtio_pci.c +30 -3
@@ -791,6 +791,7 @@ static int virtio_pci_restore(struct devstruct pci_dev *pci_dev =to_pci_dev (dev);struct virtio_pci_device *vp_dev =pci_get_drvdata (pci_dev);struct virtio_driver *drv; +unsigned status =0 ;int ret; drv = container_of(vp_dev->vdev.dev.driver,
@@ -801,14 +802,40 @@ static int virtio_pci_restore(struct devreturn ret;pci_set_master (pci_dev); +/* We always start by resetting the device, in case a previous +* driver messed it up. */ +vp_reset (&vp_dev->vdev); + +/* Acknowledge that we've seen the device. */ + status |=VIRTIO_CONFIG_S_ACKNOWLEDGE ; +vp_set_status (&vp_dev->vdev, status); + +/* Maybe driver failed before freeze. +* Restore the failed status, for debugging. */ + status |= vp_dev->saved_status &VIRTIO_CONFIG_S_FAILED ; +vp_set_status (&vp_dev->vdev, status); + +if (!drv) +return 0 ; + +/* We have a driver! */ + status |=VIRTIO_CONFIG_S_DRIVER ; +vp_set_status (&vp_dev->vdev, status); +vp_finalize_features (&vp_dev->vdev); -if (drv && drv->restore) +if (drv->restore) { ret = drv->restore (&vp_dev->vdev); +if (ret) { + status |=VIRTIO_CONFIG_S_FAILED ; +vp_set_status (&vp_dev->vdev, status); +return ret; + } + }/* Finally, tell the device we're all set */ -if (!ret) -vp_set_status (&vp_dev->vdev, vp_dev->saved_status); + status |=VIRTIO_CONFIG_S_DRIVER_OK ; +vp_set_status (&vp_dev->vdev, status);return ret; }
Greg Kroah-Hartman
maintainerPATCH 36/123 dm bufio: update last_accessed when relinking a buffer
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Joe Thornber <[email protected]>
commit eb76faf53b1ff7a77ce3f78cc98ad392ac70c2a0 upstream.
The 'last_accessed' member of the dm_buffer structure was only set when the the buffer was created. This led to each buffer being discarded after dm_bufio_max_age time even if it was used recently. In practice this resulted in all thinp metadata being evicted soon after being read -- this is particularly problematic for metadata intensive workloads like multithreaded small random IO.
'last_accessed' is now updated each time the buffer is moved to the head of the LRU list, so the buffer is now properly discarded if it was not used in dm_bufio_max_age time.
--- drivers/md/dm-bufio.c | 1 + 1 file changed, 1 insertion(+)
drivers/md/dm-bufio.c +1 -0
@@ -462,6 +462,7 @@ static void __relink_lru(struct dm_buffe c->n_buffers[dirty]++; b->list_mode = dirty;list_move (&b->lru_list, &c->lru[dirty]); + b->last_accessed = jiffies; }/*----------------------------------------------------------------
Greg Kroah-Hartman
maintainerPATCH 37/123 drbd: compute the end before rb_insert_augmented()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lai Jiangshan <[email protected]>
commit 82cfb90bc99d7b7e0ec62d0505b9d4f06805d5db upstream.
Commit 98683650 "Merge branch 'drbd-8.4_ed6' into for-3.8-drivers-drbd-8.4_ed6" switches to the new augment API, but the new API requires that the tree is augmented before rb_insert_augmented() is called, which is missing.
So we add the augment-code to drbd_insert_interval() when it travels the tree up to down before rb_insert_augmented(). See the example in include/linux/interval_tree_generic.h or Documentation/rbtree.txt.
drbd_insert_interval() may cancel the insertion when traveling, in this case, the just added augment-code does nothing before cancel since the @this node is already in the subtrees in this case.
--- drivers/block/drbd/drbd_interval.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/block/drbd/drbd_interval.c +4 -0
@@ -79,6 +79,7 @@ bool drbd_insert_interval(struct rb_root *root, struct drbd_interval *this) { struct rb_node **new = &root->rb_node, *parent = NULL; +sector_t this_end = this->sector + (this->size >>9 );BUG_ON (!IS_ALIGNED (this->size,512 ));
@@ -87,6 +88,8 @@ drbd_insert_interval(struct rb_root *roo rb_entry(*new, struct drbd_interval, rb); parent = *new; +if (here->end < this_end) + here->end = this_end;if (this->sector < here->sector) new = &(*new)->rb_left;else if (this->sector > here->sector)
@@ -99,6 +102,7 @@ drbd_insert_interval(struct rb_root *rooreturn false; } + this->end = this_end;rb_link_node (&this->rb, parent, new);rb_insert_augmented (&this->rb, root, &augment_callbacks);return true;
Greg Kroah-Hartman
maintainerPATCH 38/123 block: fix alignment_offset math that assumes io_min is a power-of-2
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mike Snitzer <[email protected]>
commit b8839b8c55f3fdd60dc36abcda7e0266aff7985c upstream.
The math in both blk_stack_limits() and queue_limit_alignment_offset() assume that a block device's io_min (aka minimum_io_size) is always a power-of-2. Fix the math such that it works for non-power-of-2 io_min.
This issue (of alignment_offset != 0) became apparent when testing dm-thinp with a thinp blocksize that matches a RAID6 stripesize of 1280K. Commit fdfb4c8c1 ("dm thin: set minimum_io_size to pool's data block size") unlocked the potential for alignment_offset != 0 due to the dm-thin-pool's io_min possibly being a non-power-of-2.
--- block/blk-settings.c | 4 ++-- include/linux/blkdev.h | 5 ++--- 2 files changed, 4 insertions(+), 5 deletions(-)
block/blk-settings.c +2 -2
@@ -553,7 +553,7 @@ int blk_stack_limits(struct queue_limits bottom =max (b->physical_block_size, b->io_min) + alignment;/* Verify that top and bottom intervals line up */ -if (max (top, bottom) & (min (top, bottom) -1 )) { +if (max (top, bottom) %min (top, bottom)) { t->misaligned =1 ; ret =-1 ; }
@@ -594,7 +594,7 @@ int blk_stack_limits(struct queue_limits/* Find lowest common alignment_offset */ t->alignment_offset =lcm (t->alignment_offset, alignment) - & (max (t->physical_block_size, t->io_min) -1 ); + %max (t->physical_block_size, t->io_min);/* Verify that new alignment_offset is on a logical block boundary */ if (t->alignment_offset & (t->logical_block_size -1 )) {
include/linux/blkdev.h +2 -3
@@ -1187,10 +1187,9 @@ static inline int queue_alignment_offsetstatic inline int queue_limit_alignment_offset (struct queue_limits *lim,sector_t sector) {unsigned int granularity =max (lim->physical_block_size, lim->io_min); -unsigned int alignment = (sector <<9 ) & (granularity -1 ); +unsigned int alignment =sector_div (sector, granularity >>9 ) <<9 ; -return (granularity + lim->alignment_offset - alignment) - & (granularity -1 ); +return (granularity + lim->alignment_offset - alignment) % granularity; }static inline int bdev_alignment_offset (struct block_device *bdev)
Greg Kroah-Hartman
maintainerPATCH 39/123 dm log userspace: fix memory leak in dm_ulog_tfr_init failure path
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexey Khoroshilov <[email protected]>
commit 56ec16cb1e1ce46354de8511eef962a417c32c92 upstream.
If cn_add_callback() fails in dm_ulog_tfr_init(), it does not deallocate prealloced memory but calls cn_del_callback().
Found by Linux Driver Verification project (linuxtesting.org).
--- drivers/md/dm-log-userspace-transfer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/md/dm-log-userspace-transfer.c +1 -1
@@ -272,7 +272,7 @@ int dm_ulog_tfr_init(void) r =cn_add_callback (&ulog_cn_id,"dmlogusr" , cn_ulog_callback);if (r) { -cn_del_callback (&ulog_cn_id); +kfree (prealloced_cn_msg);return r; }
Greg Kroah-Hartman
maintainerPATCH 40/123 modules, lock around setting of MODULE_STATE_UNFORMED
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prarit Bhargava <[email protected]>
commit d3051b489aa81ca9ba62af366149ef42b8dae97c upstream.
A panic was seen in the following sitation.
There are two threads running on the system. The first thread is a system monitoring thread that is reading /proc/modules. The second thread is loading and unloading a module (in this example I'm using my simple dummy-module.ko). Note, in the "real world" this occurred with the qlogic driver module.
When doing this, the following panic occurred:
------------[ cut here ]------------ kernel BUG at kernel/module.c:3739! invalid opcode: 0000 [#1] SMP Modules linked in: binfmt_misc sg nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel lrw igb gf128mul glue_helper iTCO_wdt iTCO_vendor_support ablk_helper ptp sb_edac cryptd pps_core edac_core shpchp i2c_i801 pcspkr wmi lpc_ich ioatdma mfd_core dca ipmi_si nfsd ipmi_msghandler auth_rpcgss nfs_acl lockd sunrpc xfs libcrc32c sr_mod cdrom sd_mod crc_t10dif crct10dif_common mgag200 syscopyarea sysfillrect sysimgblt i2c_algo_bit drm_kms_helper ttm isci drm libsas ahci libahci scsi_transport_sas libata i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: dummy_module] CPU: 37 PID: 186343 Comm: cat Tainted: GF O-------------- 3.10.0+ #7 Hardware name: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.00.29.D696.1311111329 11/11/2013 task: ffff8807fd2d8000 ti: ffff88080fa7c000 task.ti: ffff88080fa7c000 RIP: 0010:[<ffffffff810d64c5>] [<ffffffff810d64c5>] module_flags+0xb5/0xc0 RSP: 0018:ffff88080fa7fe18 EFLAGS: 00010246 RAX: 0000000000000003 RBX: ffffffffa03b5200 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffff88080fa7fe38 RDI: ffffffffa03b5000 RBP: ffff88080fa7fe28 R08: 0000000000000010 R09: 0000000000000000 R10: 0000000000000000 R11: 000000000000000f R12: ffffffffa03b5000 R13: ffffffffa03b5008 R14: ffffffffa03b5200 R15: ffffffffa03b5000 FS: 00007f6ae57ef740(0000) GS:ffff88101e7a0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000404f70 CR3: 0000000ffed48000 CR4: 00000000001407e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Stack: ffffffffa03b5200 ffff8810101e4800 ffff88080fa7fe70 ffffffff810d666c ffff88081e807300 000000002e0f2fbf 0000000000000000 ffff88100f257b00 ffffffffa03b5008 ffff88080fa7ff48 ffff8810101e4800 ffff88080fa7fee0 Call Trace: [<ffffffff810d666c>] m_show+0x19c/0x1e0 [<ffffffff811e4d7e>] seq_read+0x16e/0x3b0 [<ffffffff812281ed>] proc_reg_read+0x3d/0x80 [<ffffffff811c0f2c>] vfs_read+0x9c/0x170 [<ffffffff811c1a58>] SyS_read+0x58/0xb0 [<ffffffff81605829>] system_call_fastpath+0x16/0x1b Code: 48 63 c2 83 c2 01 c6 04 03 29 48 63 d2 eb d9 0f 1f 80 00 00 00 00 48 63 d2 c6 04 13 2d 41 8b 0c 24 8d 50 02 83 f9 01 75 b2 eb cb <0f> 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 RIP [<ffffffff810d64c5>] module_flags+0xb5/0xc0 RSP <ffff88080fa7fe18>
Consider the two processes running on the system.
CPU 0 (/proc/modules reader)
CPU 1 (loading/unloading module)
CPU 0 opens /proc/modules, and starts displaying data for each module by traversing the modules list via fs/seq_file.c:seq_open() and fs/seq_file.c:seq_read(). For each module in the modules list, seq_read does
op->start() <-- this is a pointer to m_start()
op->show() <- this is a pointer to m_show()
op->stop() <-- this is a pointer to m_stop()
The m_start(), m_show(), and m_stop() module functions are defined in kernel/module.c. The m_start() and m_stop() functions acquire and release the module_mutex respectively.
ie) When reading /proc/modules, the module_mutex is acquired and released for each module.
m_show() is called with the module_mutex held. It accesses the module struct data and attempts to write out module data. It is in this code path that the above BUG_ON() warning is encountered, specifically m_show() calls
static char *module_flags(struct module *mod, char *buf) {
int bx = 0;
BUG_ON(mod->state == MODULE_STATE_UNFORMED);
...
The other thread, CPU 1, in unloading the module calls the syscall delete_module() defined in kernel/module.c. The module_mutex is acquired for a short time, and then released. free_module() is called without the module_mutex. free_module() then sets mod->state = MODULE_STATE_UNFORMED, also without the module_mutex. Some additional code is called and then the module_mutex is reacquired to remove the module from the modules list:
/* Now we can delete it from the lists */
mutex_lock(&module_mutex);
stop_machine(__unlink_module, mod, NULL);
mutex_unlock(&module_mutex);
This is the sequence of events that leads to the panic.
CPU 1 is removing dummy_module via delete_module(). It acquires the module_mutex, and then releases it. CPU 1 has NOT set dummy_module->state to MODULE_STATE_UNFORMED yet.
CPU 0, which is reading the /proc/modules, acquires the module_mutex and acquires a pointer to the dummy_module which is still in the modules list. CPU 0 calls m_show for dummy_module. The check in m_show() for MODULE_STATE_UNFORMED passed for dummy_module even though it is being torn down.
Meanwhile CPU 1, which has been continuing to remove dummy_module without holding the module_mutex, now calls free_module() and sets dummy_module->state to MODULE_STATE_UNFORMED.
CPU 0 now calls module_flags() with dummy_module and ...
static char *module_flags(struct module *mod, char *buf)
{
int bx = 0;
BUG_ON(mod->state == MODULE_STATE_UNFORMED);and BOOM.
Acquire and release the module_mutex lock around the setting of MODULE_STATE_UNFORMED in the teardown path, which should resolve the problem.
Testing: In the unpatched kernel I can panic the system within 1 minute by doing
while (true) do insmod dummy_module.ko; rmmod dummy_module.ko; done
and
while (true) do cat /proc/modules; done
in separate terminals.
In the patched kernel I was able to run just over one hour without seeing any issues. I also verified the output of panic via sysrq-c and the output of /proc/modules looks correct for all three states for the dummy_module.
dummy_module 12661 0 - Unloading 0xffffffffa03a5000 (OE-)
dummy_module 12661 0 - Live 0xffffffffa03bb000 (OE)
dummy_module 14015 1 - Loading 0xffffffffa03a5000 (OE+)--- kernel/module.c | 2 ++ 1 file changed, 2 insertions(+)
kernel/module.c +2 -0
@@ -1866,7 +1866,9 @@ static void free_module(struct module *m/* We leave it in list to prevent duplicate loads, but make sure * that noone uses it while it's being deconstructed. */ +mutex_lock (&module_mutex); mod->state =MODULE_STATE_UNFORMED ; +mutex_unlock (&module_mutex);/* Remove dynamic debug info */ ddebug_remove_module (mod->name);
Greg Kroah-Hartman
maintainerPATCH 41/123 framebuffer: fix border color
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mikulas Patocka <[email protected]>
commit f74a289b9480648a654e5afd8458c2263c03a1e1 upstream.
The framebuffer code uses the current background color to fill the border when switching consoles, however, this results in inconsistent behavior. For example:
- start Midnigh Commander
- the border is black
- switch to another console and switch back
- the border is cyan
- type something into the command line in mc
- the border is cyan
- switch to another console and switch back
- the border is black
- press F9 to go to menu
- the border is black
- switch to another console and switch back
- the border is dark blue
When switching to a console with Midnight Commander, the border is random color that was left selected by the slang subsystem.
This patch fixes this inconsistency by always using black as the background color when switching consoles.
--- drivers/video/console/bitblit.c | 3 +-- drivers/video/console/fbcon_ccw.c | 3 +-- drivers/video/console/fbcon_cw.c | 3 +-- drivers/video/console/fbcon_ud.c | 3 +-- 4 files changed, 4 insertions(+), 8 deletions(-)
drivers/video/console/bitblit.c +1 -2
@@ -205,7 +205,6 @@ static void bit_putcs(struct vc_data *vcstatic void bit_clear_margins (struct vc_data *vc,struct fb_info *info,int bottom_only) { -int bgshift = (vc->vc_hi_font_mask) ?13 :12 ;unsigned int cw = vc->vc_font.width;unsigned int ch = vc->vc_font.height;unsigned int rw = info->var.xres - (vc->vc_cols*cw);
@@ -214,7 +213,7 @@ static void bit_clear_margins(struct vc_unsigned int bs = info->var.yres - bh;struct fb_fillrect region; - region.color =attr_bgcol_ec (bgshift, vc, info); + region.color =0 ; region.rop =ROP_COPY ;if (rw && !bottom_only) {
drivers/video/console/fbcon_ccw.c +1 -2
@@ -197,9 +197,8 @@ static void ccw_clear_margins(struct vc_unsigned int bh = info->var.xres - (vc->vc_rows*ch);unsigned int bs = vc->vc_rows*ch;struct fb_fillrect region; -int bgshift = (vc->vc_hi_font_mask) ?13 :12 ; - region.color =attr_bgcol_ec (bgshift,vc,info); + region.color =0 ; region.rop =ROP_COPY ;if (rw && !bottom_only) {
drivers/video/console/fbcon_cw.c +1 -2
@@ -180,9 +180,8 @@ static void cw_clear_margins(struct vc_dunsigned int bh = info->var.xres - (vc->vc_rows*ch);unsigned int rs = info->var.yres - rw;struct fb_fillrect region; -int bgshift = (vc->vc_hi_font_mask) ?13 :12 ; - region.color =attr_bgcol_ec (bgshift,vc,info); + region.color =0 ; region.rop =ROP_COPY ;if (rw && !bottom_only) {
drivers/video/console/fbcon_ud.c +1 -2
@@ -227,9 +227,8 @@ static void ud_clear_margins(struct vc_dunsigned int rw = info->var.xres - (vc->vc_cols*cw);unsigned int bh = info->var.yres - (vc->vc_rows*ch);struct fb_fillrect region; -int bgshift = (vc->vc_hi_font_mask) ?13 :12 ; - region.color =attr_bgcol_ec (bgshift,vc,info); + region.color =0 ; region.rop =ROP_COPY ;if (rw && !bottom_only) {
Greg Kroah-Hartman
maintainerPATCH 42/123 Input: i8042 - add noloop quirk for Asus X750LN
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit 9ff84a17302aeb8913ff244ecc0d8f9d219fecb5 upstream.
Without this the aux port does not get detected, and consequently the touchpad will not work.
https://bugzilla.redhat.com/show_bug.cgi?id=1110011
--- drivers/input/serio/i8042-x86ia64io.h | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/input/serio/i8042-x86ia64io.h +6 -0
@@ -101,6 +101,12 @@ static const struct dmi_system_id __init }, { .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"ASUSTeK COMPUTER INC." ), + DMI_MATCH(DMI_PRODUCT_NAME, "X750LN"), + }, + }, + { + .matches = {DMI_MATCH (DMI_SYS_VENDOR ,"Compaq" ),DMI_MATCH (DMI_PRODUCT_NAME ,"ProLiant" ), DMI_MATCH(DMI_PRODUCT_VERSION, "8500"),
Greg Kroah-Hartman
maintainerPATCH 43/123 Input: i8042 - quirks for Fujitsu Lifebook A544 and Lifebook AH544
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit 993b3a3f80a7842a48cd46c2b41e1b3ef6302468 upstream.
These models need i8042.notimeout, otherwise the touchpad will not work.
--- drivers/input/serio/i8042-x86ia64io.h | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
drivers/input/serio/i8042-x86ia64io.h +16 -0
@@ -615,6 +615,22 @@ static const struct dmi_system_id __init }, }, { +/* Fujitsu A544 laptop */ +/* https://bugzilla.redhat.com/show_bug.cgi?id=1111138 */ + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"FUJITSU" ), + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK A544"), + }, + }, + { +/* Fujitsu AH544 laptop */ +/* https://bugzilla.kernel.org/show_bug.cgi?id=69731 */ + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"FUJITSU" ), + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK AH544"), + }, + }, + {/* Fujitsu U574 laptop */ /* https://bugzilla.kernel.org/show_bug.cgi?id=69731 */ .matches = {
Greg Kroah-Hartman
maintainerPATCH 44/123 drm/ast: Fix HW cursor image
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Benjamin Herrenschmidt <[email protected]>
commit 1e99cfa8de0f0879091e33cd65fd60418d006ad9 upstream.
The translation from the X driver to the KMS one typo'ed a couple of array indices, causing the HW cursor to look weird (blocky with leaking edge colors). This fixes it.
--- drivers/gpu/drm/ast/ast_mode.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/ast/ast_mode.c +2 -2
@@ -1012,8 +1012,8 @@ static u32 copy_cursor_image(u8 *src, u8 srcdata32[1 ].ul = *((u32 *)(srcxor +4 )) &0xf0f0f0f0 ; data32.b[0 ] = srcdata32[0 ].b[1 ] | (srcdata32[0 ].b[0 ] >>4 ); data32.b[1 ] = srcdata32[0 ].b[3 ] | (srcdata32[0 ].b[2 ] >>4 ); - data32.b[2 ] = srcdata32[0 ].b[1 ] | (srcdata32[1 ].b[0 ] >>4 ); - data32.b[3 ] = srcdata32[0 ].b[3 ] | (srcdata32[1 ].b[2 ] >>4 ); + data32.b[2 ] = srcdata32[1 ].b[1 ] | (srcdata32[1 ].b[0 ] >>4 ); + data32.b[3 ] = srcdata32[1 ].b[3 ] | (srcdata32[1 ].b[2 ] >>4 );writel (data32.ul, dstxor); csum += data32.ul;
Greg Kroah-Hartman
maintainerPATCH 45/123 drm/tilcdc: Fix the error path in tilcdc_load()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ezequiel Garcia <[email protected]>
commit b478e336b3e75505707a11e78ef8b964ef0a03af upstream.
The current error path calls tilcdc_unload() in case of an error to release the resources. However, this is wrong because not all resources have been allocated by the time an error occurs in tilcdc_load().
To fix it, this commit adds proper labels to bail out at the different stages in the load function, and release only the resources actually allocated.
--- drivers/gpu/drm/tilcdc/tilcdc_drv.c | 60 ++++++++++++++++++++++++++++++------ 1 file changed, 50 insertions(+), 10 deletions(-)
drivers/gpu/drm/tilcdc/tilcdc_drv.c +50 -10
@@ -78,6 +78,7 @@ static int modeset_init(struct drm_devicif ((priv->num_encoders ==0 ) || (priv->num_connectors ==0 )) {/* oh nos! */ dev_err (dev->dev,"no encoders/connectors found\n" ); +drm_mode_config_cleanup (dev);return -ENXIO ; }
@@ -170,33 +171,37 @@ static int tilcdc_load(struct drm_device dev->dev_private = priv; priv->wq =alloc_ordered_workqueue ("tilcdc" ,0 ); +if (!priv->wq) { + ret = -ENOMEM ; + goto fail_free_priv; + } res =platform_get_resource (pdev,IORESOURCE_MEM ,0 );if (!res) {dev_err (dev->dev,"failed to get memory resource\n" ); ret = -EINVAL ; - goto fail; + goto fail_free_wq; } priv->mmio =ioremap_nocache (res->start,resource_size (res));if (!priv->mmio) {dev_err (dev->dev,"failed to ioremap\n" ); ret = -ENOMEM ; - goto fail; + goto fail_free_wq; } priv->clk =clk_get (dev->dev,"fck" );if (IS_ERR (priv->clk)) {dev_err (dev->dev,"failed to get functional clock\n" ); ret = -ENODEV ; - goto fail; + goto fail_iounmap; } priv->disp_clk =clk_get (dev->dev,"dpll_disp_ck" );if (IS_ERR (priv->clk)) {dev_err (dev->dev,"failed to get display clock\n" ); ret = -ENODEV ; - goto fail; + goto fail_put_clk; }#ifdef CONFIG_CPU_FREQ
@@ -206,7 +211,7 @@ static int tilcdc_load(struct drm_device CPUFREQ_TRANSITION_NOTIFIER);if (ret) {dev_err (dev->dev,"failed to register cpufreq notifier\n" ); - goto fail; + goto fail_put_disp_clk; }#endif
@@ -238,13 +243,13 @@ static int tilcdc_load(struct drm_device ret =modeset_init (dev);if (ret <0 ) {dev_err (dev->dev,"failed to initialize mode setting\n" ); - goto fail; + goto fail_cpufreq_unregister; } ret =drm_vblank_init (dev,1 );if (ret <0 ) {dev_err (dev->dev,"failed to initialize vblank\n" ); - goto fail; + goto fail_mode_config_cleanup; }pm_runtime_get_sync (dev->dev);
@@ -252,7 +257,7 @@ static int tilcdc_load(struct drm_devicepm_runtime_put_sync (dev->dev);if (ret <0 ) {dev_err (dev->dev,"failed to install IRQ handler\n" ); - goto fail; + goto fail_vblank_cleanup; }platform_set_drvdata (pdev, dev);
@@ -260,13 +265,48 @@ static int tilcdc_load(struct drm_device priv->fbdev =drm_fbdev_cma_init (dev,16 , dev->mode_config.num_crtc, dev->mode_config.num_connector); +if (IS_ERR (priv->fbdev)) { + ret =PTR_ERR (priv->fbdev); + goto fail_irq_uninstall; + }drm_kms_helper_poll_init (dev);return 0 ; -fail: -tilcdc_unload (dev); +fail_irq_uninstall: +pm_runtime_get_sync (dev->dev); +drm_irq_uninstall (dev); +pm_runtime_put_sync (dev->dev); + +fail_vblank_cleanup: +drm_vblank_cleanup (dev); + +fail_mode_config_cleanup: +drm_mode_config_cleanup (dev); + +fail_cpufreq_unregister: +pm_runtime_disable (dev->dev); +#ifdef CONFIG_CPU_FREQ +cpufreq_unregister_notifier (&priv->freq_transition, +CPUFREQ_TRANSITION_NOTIFIER ); +fail_put_disp_clk: +clk_put (priv->disp_clk); +#endif + +fail_put_clk: +clk_put (priv->clk); + +fail_iounmap: +iounmap (priv->mmio); + +fail_free_wq: +flush_workqueue (priv->wq); +destroy_workqueue (priv->wq); + +fail_free_priv: + dev->dev_private =NULL ; +kfree (priv);return ret; }
Greg Kroah-Hartman
maintainerPATCH 46/123 drm/nouveau/bios: memset dcb struct to zero before parsing
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Skeggs <[email protected]>
commit 595d373f1e9c9ce0fc946457fdb488e8a58972cd upstream.
Fixes type/mask calculation being based on uninitialised data for VGA outputs.
--- drivers/gpu/drm/nouveau/core/subdev/bios/dcb.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/nouveau/core/subdev/bios/dcb.c +1 -0
@@ -124,6 +124,7 @@ dcb_outp_parse(struct nouveau_bios *bios struct dcb_output *outp) {u16 dcb =dcb_outp (bios, idx, ver, len); +memset (outp,0x00 ,sizeof (*outp));if (dcb) {if (*ver >=0x20 ) {u32 conn =nv_ro32 (bios, dcb +0x00 );
Greg Kroah-Hartman
maintainerPATCH 47/123 media: v4l2-common: fix overflow in v4l_bound_align_image()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Maciej Matraszek <[email protected]>
commit 3bacc10cd4a85bc70bc0b6c001d3bf995c7fe04c upstream.
Fix clamp_align() used in v4l_bound_align_image() to prevent overflow when passed large value like UINT32_MAX.
In the current implementation:
clamp_align(UINT32_MAX, 8, 8192, 3)
returns 8, because in line:
x = (x + (1 << (align - 1))) & mask;
x overflows to (-1 + 4) & 0x7 = 3, while expected value is 8192.
v4l_bound_align_image() is heavily used in VIDIOC_S_FMT and VIDIOC_SUBDEV_S_FMT ioctls handlers, and documentation of the latter explicitly states that:
"The modified format should be as close as possible to the original request."
-- http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-subdev-g-fmt.html
Thus one would expect, that passing UINT32_MAX as format width and height will result in setting maximum possible resolution for the device. Particularly, when the driver doesn't support VIDIOC_ENUM_FRAMESIZES ioctl, which is common in the codebase.
Fixes changeset: b0d3159be9a3
--- drivers/media/v4l2-core/v4l2-common.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-)
drivers/media/v4l2-core/v4l2-common.c +3 -6
@@ -485,16 +485,13 @@ static unsigned int clamp_align(unsigned/* Bits that must be zero to be aligned */ unsigned int mask = ~((1 << align) -1 ); +/* Clamp to aligned min and max */ + x =clamp (x, (min + ~mask) & mask, max & mask); +/* Round to nearest aligned value */ if (align) x = (x + (1 << (align -1 ))) & mask; -/* Clamp to aligned value of min and max */ -if (x < min) - x = (min + ~mask) & mask; -else if (x > max) - x = max & mask; -return x; }
Greg Kroah-Hartman
maintainerPATCH 49/123 media: ds3000: fix LNB supply voltage on Tevii S480 on initialization
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ulrich Eckhardt <[email protected]>
commit 8c5bcded11cb607b1bb5920de3b9c882136d27db upstream.
The Tevii S480 outputs 18V on startup for the LNB supply voltage and does not automatically power down. This blocks other receivers connected to a satellite channel router (EN50494), since the receivers can not send the required DiSEqC sequences when the Tevii card is connected to a the same SCR.
This patch switches off the LNB supply voltage on initialization of the frontend.
[[email protected]: add a comment about why we're explicitly
turning off voltage at device init]
--- drivers/media/dvb-frontends/ds3000.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/media/dvb-frontends/ds3000.c +7 -0
@@ -864,6 +864,13 @@ struct dvb_frontend *ds3000_attach(constmemcpy (&state->frontend.ops, &ds3000_ops,sizeof (struct dvb_frontend_ops )); state->frontend.demodulator_priv = state; + +/* +* Some devices like T480 starts with voltage on. Be sure +* to turn voltage off during init, as this can otherwise +* interfere with Unicable SCR systems. +*/ +ds3000_set_voltage (&state->frontend,SEC_VOLTAGE_OFF );return &state->frontend; error3:
Greg Kroah-Hartman
maintainerPATCH 50/123 media: tda7432: Fix setting TDA7432_MUTE bit for TDA7432_RF register
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Axel Lin <[email protected]>
commit 91ba0e59babdb3c7aca836a65f1095b3eaff7b06 upstream.
Fix a copy-paste bug when converting to the control framework.
--- drivers/media/i2c/tda7432.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/i2c/tda7432.c +1 -1
@@ -293,7 +293,7 @@ static int tda7432_s_ctrl(struct v4l2_ctif (t->mute->val) { lf |=TDA7432_MUTE ; lr |=TDA7432_MUTE ; - lf |=TDA7432_MUTE ; + rf |=TDA7432_MUTE ; rr |=TDA7432_MUTE ; }/* Mute & update balance*/
Greg Kroah-Hartman
maintainerPATCH 51/123 kvm: fix excessive pages un-pinning in kvm_iommu_map error path.
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Quentin Casasnovas <[email protected]>
commit 3d32e4dbe71374a6780eaf51d719d76f9a9bf22f upstream.
The third parameter of kvm_unpin_pages() when called from kvm_iommu_map_pages() is wrong, it should be the number of pages to un-pin and not the page size.
This error was facilitated with an inconsistent API: kvm_pin_pages() takes a size, but kvn_unpin_pages() takes a number of pages, so fix the problem by matching the two.
This was introduced by commit 350b8bd ("kvm: iommu: fix the third parameter of kvm_iommu_put_pages (CVE-2014-3601)"), which fixes the lack of un-pinning for pages intended to be un-pinned (i.e. memory leak) but unfortunately potentially aggravated the number of pages we un-pin that should have stayed pinned. As far as I understand though, the same practical mitigations apply.
This issue was found during review of Red Hat 6.6 patches to prepare Ksplice rebootless updates.
Thanks to Vegard for his time on a late Friday evening to help me in understanding this code.
--- virt/kvm/iommu.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
virt/kvm/iommu.c +4 -4
@@ -43,13 +43,13 @@ static void kvm_iommu_put_pages(struct k gfn_t base_gfn, unsigned long npages);static pfn_t kvm_pin_pages (struct kvm_memory_slot *slot,gfn_t gfn, -unsigned long size) +unsigned long npages) {gfn_t end_gfn;pfn_t pfn; pfn =gfn_to_pfn_memslot (slot, gfn); - end_gfn = gfn + (size >>PAGE_SHIFT ); + end_gfn = gfn + npages; gfn +=1 ;if (is_error_noslot_pfn (pfn))
@@ -119,7 +119,7 @@ int kvm_iommu_map_pages(struct kvm *kvm,* Pin all pages we are about to map in memory. This is * important because we unmap and unpin in 4kb steps later. */ - pfn =kvm_pin_pages (slot, gfn, page_size); + pfn =kvm_pin_pages (slot, gfn, page_size >>PAGE_SHIFT );if (is_error_noslot_pfn (pfn)) { gfn +=1 ;continue ;
@@ -131,7 +131,7 @@ int kvm_iommu_map_pages(struct kvm *kvm,if (r) {printk (KERN_ERR "kvm_iommu_map_address:" "iommu failed to map pfn=%llx\n" , pfn); -kvm_unpin_pages (kvm, pfn, page_size); +kvm_unpin_pages (kvm, pfn, page_size >>PAGE_SHIFT ); goto unmap_pages; }
Greg Kroah-Hartman
maintainerPATCH 52/123 KVM: x86: Prevent host from panicking on shared MSR writes.
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Honig <[email protected]>
commit 8b3c3104c3f4f706e99365c3e0d2aa61b95f969f upstream.
The previous patch blocked invalid writes directly when the MSR is written. As a precaution, prevent future similar mistakes by gracefulling handle GPs caused by writes to shared MSRs.
--- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/vmx.c | 7 +++++-- arch/x86/kvm/x86.c | 11 ++++++++--- 3 files changed, 14 insertions(+), 6 deletions(-)
arch/x86/include/asm/kvm_host.h +1 -1
@@ -1011,7 +1011,7 @@ int kvm_cpu_get_interrupt(struct kvm_vcpvoid kvm_vcpu_reset (struct kvm_vcpu *vcpu);void kvm_define_shared_msr (unsigned index,u32 msr); -void kvm_set_shared_msr (unsigned index,u64 val,u64 mask); +int kvm_set_shared_msr (unsigned index,u64 val,u64 mask);bool kvm_is_linear_rip (struct kvm_vcpu *vcpu,unsigned long linear_rip);
arch/x86/kvm/vmx.c +5 -2
@@ -2493,12 +2493,15 @@ static int vmx_set_msr(struct kvm_vcpu *break ; msr =find_msr_entry (vmx, msr_index);if (msr) { +u64 old_msr_data = msr->data; msr->data = data;if (msr - vmx->guest_msrs < vmx->save_nmsrs) {preempt_disable (); -kvm_set_shared_msr (msr->index, msr->data, - msr->mask); + ret =kvm_set_shared_msr (msr->index, msr->data, + msr->mask);preempt_enable (); +if (ret) + msr->data = old_msr_data; }break ; }
arch/x86/kvm/x86.c +8 -3
@@ -225,20 +225,25 @@ static void kvm_shared_msr_cpu_online(voshared_msr_update (i, shared_msrs_global.msrs[i]); } -void kvm_set_shared_msr (unsigned slot,u64 value,u64 mask) +int kvm_set_shared_msr (unsigned slot,u64 value,u64 mask) {unsigned int cpu =smp_processor_id ();struct kvm_shared_msrs *smsr =per_cpu_ptr (shared_msrs, cpu); +int err;if (((value ^ smsr->values[slot].curr) & mask) ==0 ) -return ; +return 0 ; smsr->values[slot].curr = value; -wrmsrl (shared_msrs_global.msrs[slot], value); + err =wrmsrl_safe (shared_msrs_global.msrs[slot], value); +if (err) +return 1 ; +if (!smsr->registered) { smsr->urn.on_user_return = kvm_on_user_return;user_return_notifier_register (&smsr->urn); smsr->registered = true; } +return 0 ; }EXPORT_SYMBOL_GPL (kvm_set_shared_msr);
Greg Kroah-Hartman
maintainerPATCH 53/123 KVM: x86: Improve thread safety in pit
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Honig <[email protected]>
commit 2febc839133280d5a5e8e1179c94ea674489dae2 upstream.
There's a race condition in the PIT emulation code in KVM. In __kvm_migrate_pit_timer the pit_timer object is accessed without synchronization. If the race condition occurs at the wrong time this can crash the host kernel.
This fixes CVE-2014-3611.
--- arch/x86/kvm/i8254.c | 2 ++ 1 file changed, 2 insertions(+)
arch/x86/kvm/i8254.c +2 -0
@@ -262,8 +262,10 @@ void __kvm_migrate_pit_timer(struct kvm_return ; timer = &pit->pit_state.timer; +mutex_lock (&pit->pit_state.lock);if (hrtimer_cancel (timer))hrtimer_start_expires (timer,HRTIMER_MODE_ABS ); +mutex_unlock (&pit->pit_state.lock); }static void destroy_pit_timer (struct kvm_pit *pit)
Greg Kroah-Hartman
maintainerPATCH 54/123 KVM: x86: Check non-canonical addresses upon WRMSR
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nadav Amit <[email protected]>
commit 854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 upstream.
Upon WRMSR, the CPU should inject #GP if a non-canonical value (address) is written to certain MSRs. The behavior is "almost" identical for AMD and Intel (ignoring MSRs that are not implemented in either architecture since they would anyhow #GP). However, IA32_SYSENTER_ESP and IA32_SYSENTER_EIP cause #GP if non-canonical address is written on Intel but not on AMD (which ignores the top 32-bits).
Accordingly, this patch injects a #GP on the MSRs which behave identically on Intel and AMD. To eliminate the differences between the architecutres, the value which is written to IA32_SYSENTER_ESP and IA32_SYSENTER_EIP is turned to canonical value before writing instead of injecting a #GP.
Some references from Intel and AMD manuals:
According to Intel SDM description of WRMSR instruction #GP is expected on WRMSR "If the source register contains a non-canonical address and ECX specifies one of the following MSRs: IA32_DS_AREA, IA32_FS_BASE, IA32_GS_BASE, IA32_KERNEL_GS_BASE, IA32_LSTAR, IA32_SYSENTER_EIP, IA32_SYSENTER_ESP."
According to AMD manual instruction manual:
LSTAR/CSTAR (SYSCALL): "The WRMSR instruction loads the target RIP into the LSTAR and CSTAR registers. If an RIP written by WRMSR is not in canonical form, a general-protection exception (#GP) occurs."IA32_GS_BASE and IA32_FS_BASE (WRFSBASE/WRGSBASE): "The address written to the base field must be in canonical form or a #GP fault will occur." IA32_KERNEL_GS_BASE (SWAPGS): "The address stored in the KernelGSbase MSR must be in canonical form."
This patch fixes CVE-2014-3610.
--- arch/x86/include/asm/kvm_host.h | 14 ++++++++++++++ arch/x86/kvm/svm.c | 2 +- arch/x86/kvm/vmx.c | 2 +- arch/x86/kvm/x86.c | 27 ++++++++++++++++++++++++++- 4 files changed, 42 insertions(+), 3 deletions(-)
arch/x86/include/asm/kvm_host.h +14 -0
@@ -953,6 +953,20 @@ static inline void kvm_inject_gp(structkvm_queue_exception_e (vcpu,GP_VECTOR , error_code); } +static inline u64 get_canonical (u64 la) +{ +return ((int64_t )la <<16 ) >>16 ; +} + +static inline bool is_noncanonical_address (u64 la) +{ +#ifdef CONFIG_X86_64 +return get_canonical (la) != la; +#else +return false; +#endif +} +#define TSS_IOPB_BASE_OFFSET 0x66#define TSS_BASE_SIZE 0x68#define TSS_IOPB_SIZE (65536 / 8)
arch/x86/kvm/svm.c +1 -1
@@ -3196,7 +3196,7 @@ static int wrmsr_interception(struct vcp msr.host_initiated = false; svm->next_rip =kvm_rip_read (&svm->vcpu) +2 ; -if (svm_set_msr (&svm->vcpu, &msr)) { +if (kvm_set_msr (&svm->vcpu, &msr)) {trace_kvm_msr_write_ex (ecx, data);kvm_inject_gp (&svm->vcpu,0 ); }else {
arch/x86/kvm/vmx.c +1 -1
@@ -5065,7 +5065,7 @@ static int handle_wrmsr(struct kvm_vcpu msr.data = data; msr.index = ecx; msr.host_initiated = false; -if (vmx_set_msr (vcpu, &msr) !=0 ) { +if (kvm_set_msr (vcpu, &msr) !=0 ) {trace_kvm_msr_write_ex (ecx, data);kvm_inject_gp (vcpu,0 );return 1 ;
arch/x86/kvm/x86.c +26 -1
@@ -925,7 +925,6 @@ void kvm_enable_efer_bits(u64 mask) }EXPORT_SYMBOL_GPL (kvm_enable_efer_bits); -/* * Writes msr value into into the appropriate "register". * Returns 0 on success, non-0 otherwise.
@@ -933,8 +932,34 @@ EXPORT_SYMBOL_GPL(kvm_enable_efer_bits);*/ int kvm_set_msr (struct kvm_vcpu *vcpu,struct msr_data *msr) { +switch (msr->index) { +case MSR_FS_BASE : +case MSR_GS_BASE : +case MSR_KERNEL_GS_BASE : +case MSR_CSTAR : +case MSR_LSTAR : +if (is_noncanonical_address (msr->data)) +return 1 ; +break ; +case MSR_IA32_SYSENTER_EIP : +case MSR_IA32_SYSENTER_ESP : +/* +* IA32_SYSENTER_ESP and IA32_SYSENTER_EIP cause #GP if +* non-canonical address is written on Intel but not on +* AMD (which ignores the top 32-bits, because it does +* not implement 64-bit SYSENTER). +* +* 64-bit code should hence be able to write a non-canonical +* value on AMD. Making the address canonical ensures that +* vmentry does not fail on Intel after writing a non-canonical +* value, and that something deterministic happens if the guest +* invokes 64-bit SYSENTER. +*/ + msr->data =get_canonical (msr->data); + }return kvm_x86_ops->set_msr (vcpu, msr); } +EXPORT_SYMBOL_GPL (kvm_set_msr);/* * Adapt set_msr() to msr_io()'s calling convention
Greg Kroah-Hartman
maintainerPATCH 55/123 kvm: x86: dont kill guest on unknown exit reason
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Michael S. Tsirkin" <[email protected]>
commit 2bc19dc3754fc066c43799659f0d848631c44cfe upstream.
KVM_EXIT_UNKNOWN is a kvm bug, we don't really know whether it was triggered by a priveledged application. Let's not kill the guest: WARN and inject #UD instead.
--- arch/x86/kvm/svm.c | 6 +++--- arch/x86/kvm/vmx.c | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-)
arch/x86/kvm/svm.c +3 -3
@@ -3478,9 +3478,9 @@ static int handle_exit(struct kvm_vcpu *if (exit_code >=ARRAY_SIZE (svm_exit_handlers) || !svm_exit_handlers[exit_code]) { - kvm_run->exit_reason =KVM_EXIT_UNKNOWN ; - kvm_run->hw.hardware_exit_reason = exit_code; -return 0 ; +WARN_ONCE (1 ,"vmx: unexpected exit reason 0x%x\n" , exit_code); +kvm_queue_exception (vcpu,UD_VECTOR ); +return 1 ; }return svm_exit_handlers[exit_code](svm);
arch/x86/kvm/vmx.c +3 -3
@@ -6654,10 +6654,10 @@ static int vmx_handle_exit(struct kvm_vc && kvm_vmx_exit_handlers[exit_reason]) return kvm_vmx_exit_handlers[exit_reason](vcpu); else { - vcpu->run->exit_reason =KVM_EXIT_UNKNOWN ; - vcpu->run->hw.hardware_exit_reason = exit_reason; +WARN_ONCE (1 ,"vmx: unexpected exit reason 0x%x\n" , exit_reason); +kvm_queue_exception (vcpu,UD_VECTOR ); +return 1 ; } -return 0 ; }static void update_cr8_intercept (struct kvm_vcpu *vcpu,int tpr,int irr)
Greg Kroah-Hartman
maintainerPATCH 56/123 KVM: x86: Fix wrong masking on relative jump/call
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nadav Amit <[email protected]>
commit 05c83ec9b73c8124555b706f6af777b10adf0862 upstream.
Relative jumps and calls do the masking according to the operand size, and not according to the address size as the KVM emulator does today.
This patch fixes KVM behavior.
--- arch/x86/kvm/emulate.c | 27 ++++++++++++++++++++++----- 1 file changed, 22 insertions(+), 5 deletions(-)
arch/x86/kvm/emulate.c +22 -5
@@ -663,11 +663,6 @@ static void rsp_increment(struct x86_emumasked_increment (reg_rmw (ctxt,VCPU_REGS_RSP ),stack_mask (ctxt), inc); } -static inline void jmp_rel (struct x86_emulate_ctxt *ctxt,int rel) -{ -register_address_increment (ctxt, &ctxt->_eip, rel); -} -static u32 desc_limit_scaled (struct desc_struct *desc) {u32 limit =get_desc_limit (desc);
@@ -741,6 +736,28 @@ static int emulate_nm(struct x86_emulatereturn emulate_exception (ctxt,NM_VECTOR ,0 , false); } +static inline void assign_eip_near (struct x86_emulate_ctxt *ctxt,ulong dst) +{ +switch (ctxt->op_bytes) { +case 2 : + ctxt->_eip = (u16 )dst; +break ; +case 4 : + ctxt->_eip = (u32 )dst; +break ; +case 8 : + ctxt->_eip = dst; +break ; +default : +WARN (1 ,"unsupported eip assignment size\n" ); + } +} + +static inline void jmp_rel (struct x86_emulate_ctxt *ctxt,int rel) +{ +assign_eip_near (ctxt, ctxt->_eip + rel); +} +static u16 get_segment_selector (struct x86_emulate_ctxt *ctxt,unsigned seg) {u16 selector;
Greg Kroah-Hartman
maintainerPATCH 57/123 KVM: x86: Emulator fixes for eip canonical checks on near branches
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nadav Amit <[email protected]>
commit 234f3ce485d54017f15cf5e0699cff4100121601 upstream.
Before changing rip (during jmp, call, ret, etc.) the target should be asserted to be canonical one, as real CPUs do. During sysret, both target rsp and rip should be canonical. If any of these values is noncanonical, a #GP exception should occur. The exception to this rule are syscall and sysenter instructions in which the assigned rip is checked during the assignment to the relevant MSRs.
This patch fixes the emulator to behave as real CPUs do for near branches. Far branches are handled by the next patch.
This fixes CVE-2014-3647.
--- arch/x86/kvm/emulate.c | 78 +++++++++++++++++++++++++++++++++---------------- 1 file changed, 54 insertions(+), 24 deletions(-)
arch/x86/kvm/emulate.c +54 -24
@@ -736,7 +736,8 @@ static int emulate_nm(struct x86_emulatereturn emulate_exception (ctxt,NM_VECTOR ,0 , false); } -static inline void assign_eip_near (struct x86_emulate_ctxt *ctxt,ulong dst) +static inline int assign_eip_far (struct x86_emulate_ctxt *ctxt,ulong dst, +int cs_l) {switch (ctxt->op_bytes) {case 2 :
@@ -746,16 +747,25 @@ static inline void assign_eip_near(struc ctxt->_eip = (u32 )dst;break ;case 8 : +if ((cs_l &&is_noncanonical_address (dst)) || + (!cs_l && (dst & ~(u32)-1 ))) +return emulate_gp (ctxt,0 ); ctxt->_eip = dst;break ;default :WARN (1 ,"unsupported eip assignment size\n" ); } +return X86EMUL_CONTINUE ; +} + +static inline int assign_eip_near (struct x86_emulate_ctxt *ctxt,ulong dst) +{ +return assign_eip_far (ctxt, dst, ctxt->mode ==X86EMUL_MODE_PROT64 ); } -static inline void jmp_rel (struct x86_emulate_ctxt *ctxt,int rel) +static inline int jmp_rel (struct x86_emulate_ctxt *ctxt,int rel) { -assign_eip_near (ctxt, ctxt->_eip + rel); +return assign_eip_near (ctxt, ctxt->_eip + rel); }static u16 get_segment_selector (struct x86_emulate_ctxt *ctxt,unsigned seg)
@@ -2178,13 +2188,15 @@ static int em_grp45(struct x86_emulate_ccase 2 :/* call near abs */ {long int old_eip; old_eip = ctxt->_eip; - ctxt->_eip = ctxt->src.val; + rc =assign_eip_near (ctxt, ctxt->src.val); +if (rc !=X86EMUL_CONTINUE ) +break ; ctxt->src.val = old_eip; rc =em_push (ctxt);break ; }case 4 :/* jmp abs */ - ctxt->_eip = ctxt->src.val; + rc =assign_eip_near (ctxt, ctxt->src.val);break ;case 5 :/* jmp far */ rc =em_jmp_far (ctxt);
@@ -2216,10 +2228,14 @@ static int em_cmpxchg8b(struct x86_emulastatic int em_ret (struct x86_emulate_ctxt *ctxt) { - ctxt->dst.type =OP_REG ; - ctxt->dst.addr.reg = &ctxt->_eip; - ctxt->dst.bytes = ctxt->op_bytes; -return em_pop (ctxt); +int rc; +unsigned long eip; + + rc =emulate_pop (ctxt, &eip, ctxt->op_bytes); +if (rc !=X86EMUL_CONTINUE ) +return rc; + +return assign_eip_near (ctxt, eip); }static int em_ret_far (struct x86_emulate_ctxt *ctxt)
@@ -2486,7 +2502,7 @@ static int em_sysexit(struct x86_emulate {const struct x86_emulate_ops *ops = ctxt->ops;struct desc_struct cs, ss; -u64 msr_data; +u64 msr_data, rcx, rdx;int usermode;u16 cs_sel =0 , ss_sel =0 ;
@@ -2502,6 +2518,9 @@ static int em_sysexit(struct x86_emulateelse usermode =X86EMUL_MODE_PROT32 ; + rcx =reg_read (ctxt,VCPU_REGS_RCX ); + rdx =reg_read (ctxt,VCPU_REGS_RDX ); + cs.dpl =3 ; ss.dpl =3 ; ops->get_msr (ctxt,MSR_IA32_SYSENTER_CS , &msr_data);
@@ -2519,6 +2538,9 @@ static int em_sysexit(struct x86_emulate ss_sel = cs_sel +8 ; cs.d =0 ; cs.l =1 ; +if (is_noncanonical_address (rcx) || +is_noncanonical_address (rdx)) +return emulate_gp (ctxt,0 );break ; } cs_sel |=SELECTOR_RPL_MASK ;
@@ -2527,8 +2549,8 @@ static int em_sysexit(struct x86_emulate ops->set_segment (ctxt, cs_sel, &cs,0 ,VCPU_SREG_CS ); ops->set_segment (ctxt, ss_sel, &ss,0 ,VCPU_SREG_SS ); - ctxt->_eip =reg_read (ctxt,VCPU_REGS_RDX ); - *reg_write (ctxt,VCPU_REGS_RSP ) =reg_read (ctxt,VCPU_REGS_RCX ); + ctxt->_eip = rdx; + *reg_write (ctxt,VCPU_REGS_RSP ) = rcx;return X86EMUL_CONTINUE ; }
@@ -3067,10 +3089,13 @@ static int em_aad(struct x86_emulate_ctxstatic int em_call (struct x86_emulate_ctxt *ctxt) { +int rc;long rel = ctxt->src.val; ctxt->src.val = (unsigned long )ctxt->_eip; -jmp_rel (ctxt, rel); + rc =jmp_rel (ctxt, rel); +if (rc !=X86EMUL_CONTINUE ) +return rc;return em_push (ctxt); }
@@ -3102,11 +3127,12 @@ static int em_call_far(struct x86_emulatstatic int em_ret_near_imm (struct x86_emulate_ctxt *ctxt) {int rc; +unsigned long eip; - ctxt->dst.type =OP_REG ; - ctxt->dst.addr.reg = &ctxt->_eip; - ctxt->dst.bytes = ctxt->op_bytes; - rc =emulate_pop (ctxt, &ctxt->dst.val, ctxt->op_bytes); + rc =emulate_pop (ctxt, &eip, ctxt->op_bytes); +if (rc !=X86EMUL_CONTINUE ) +return rc; + rc =assign_eip_near (ctxt, eip);if (rc !=X86EMUL_CONTINUE )return rc;rsp_increment (ctxt, ctxt->src.val);
@@ -3396,20 +3422,24 @@ static int em_lmsw(struct x86_emulate_ctstatic int em_loop (struct x86_emulate_ctxt *ctxt) { +int rc =X86EMUL_CONTINUE ; +register_address_increment (ctxt,reg_rmw (ctxt,VCPU_REGS_RCX ),-1 );if ((address_mask (ctxt,reg_read (ctxt,VCPU_REGS_RCX )) !=0 ) && (ctxt->b ==0xe2 ||test_cc (ctxt->b ^0x5 , ctxt->eflags))) -jmp_rel (ctxt, ctxt->src.val); + rc =jmp_rel (ctxt, ctxt->src.val); -return X86EMUL_CONTINUE ; +return rc; }static int em_jcxz (struct x86_emulate_ctxt *ctxt) { +int rc =X86EMUL_CONTINUE ; +if (address_mask (ctxt,reg_read (ctxt,VCPU_REGS_RCX )) ==0 ) -jmp_rel (ctxt, ctxt->src.val); + rc =jmp_rel (ctxt, ctxt->src.val); -return X86EMUL_CONTINUE ; +return rc; }static int em_in (struct x86_emulate_ctxt *ctxt)
@@ -4738,7 +4768,7 @@ special_insn:break ; case 0x70 ... 0x7f: /* jcc (short) */if (test_cc (ctxt->b, ctxt->eflags)) -jmp_rel (ctxt, ctxt->src.val); + rc =jmp_rel (ctxt, ctxt->src.val);break ;case 0x8d :/* lea r16/r32, m */ ctxt->dst.val = ctxt->src.addr.mem.ea;
@@ -4767,7 +4797,7 @@ special_insn:break ;case 0xe9 :/* jmp rel */ case 0xeb :/* jmp rel short */ -jmp_rel (ctxt, ctxt->src.val); + rc =jmp_rel (ctxt, ctxt->src.val); ctxt->dst.type =OP_NONE ;/* Disable writeback. */ break ;case 0xf4 :/* hlt */
@@ -4879,7 +4909,7 @@ twobyte_insn:break ; case 0x80 ... 0x8f: /* jnz rel, etc*/if (test_cc (ctxt->b, ctxt->eflags)) -jmp_rel (ctxt, ctxt->src.val); + rc =jmp_rel (ctxt, ctxt->src.val);break ; case 0x90 ... 0x9f: /* setcc r/m8 */ ctxt->dst.val =test_cc (ctxt->b, ctxt->eflags);
Greg Kroah-Hartman
maintainerPATCH 58/123 ARC: [nsimosci] Allow "headless" models to boot
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Vineet Gupta <[email protected]>
commit 5c05483e2db91890faa9a7be0a831701a3f442d6 upstream.
There are certain test configuration of virtual platform which don't have any real console device (uart/pgu). So add tty0 as a fallback console device to allow system to boot and be accessible via telnet
Otherwise with ttyS0 as only console, but 8250 disabled in kernel build, init chokes.
--- arch/arc/boot/dts/nsimosci.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arc/boot/dts/nsimosci.dts +1 -1
@@ -20,7 +20,7 @@ /* this is for console on PGU */ /* bootargs = "console=tty0 consoleblank=0"; */ /* this is for console on serial */ - bootargs = "earlycon=uart8250,mmio32,0xc0000000,115200n8 console=ttyS0,115200n8 consoleblank=0 debug"; + bootargs = "earlycon=uart8250,mmio32,0xc0000000,115200n8 console=tty0 console=ttyS0,115200n8 consoleblank=0 debug"; }; aliases {
Greg Kroah-Hartman
maintainerPATCH 59/123 ARC: Update order of registers in KGDB to match GDB 7.5
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Anton Kolesov <[email protected]>
commit ebc0c74e76cec9c4dd860eb0ca1c0b39dc63c482 upstream.
Order of registers has changed in GDB moving from 6.8 to 7.5. This patch updates KGDB to work properly with GDB 7.5, though makes it incompatible with 6.8.
--- arch/arc/include/asm/kgdb.h | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-)
arch/arc/include/asm/kgdb.h +18 -14
@@ -19,7 +19,7 @@* register API yet */ #undef DBG_MAX_REG_NUM -#define GDB_MAX_REGS 39 +#define GDB_MAX_REGS 87#define BREAK_INSTR_SIZE 2#define CACHE_FLUSH_IS_SAFE 1
@@ -33,23 +33,27 @@ static inline void arch_kgdb_breakpoint(extern void kgdb_trap (struct pt_regs *regs,int param); -enum arc700_linux_regnums { +/* This is the numbering of registers according to the GDB. See GDB's +* arc-tdep.h for details. +* +* Registers are ordered for GDB 7.5. It is incompatible with GDB 6.8. */ +enum arc_linux_regnums { _R0 =0 , _R1, _R2, _R3, _R4, _R5, _R6, _R7, _R8, _R9, _R10, _R11, _R12, _R13, _R14, _R15, _R16, _R17, _R18, _R19, _R20, _R21, _R22, _R23, _R24, _R25, _R26, - _BTA =27 , - _LP_START =28 , - _LP_END =29 , - _LP_COUNT =30 , - _STATUS32 =31 , - _BLINK =32 , - _FP =33 , - __SP =34 , - _EFA =35 , - _RET =36 , - _ORIG_R8 =37 , - _STOP_PC =38 + _FP =27 , + __SP =28 , + _R30 =30 , + _BLINK =31 , + _LP_COUNT =60 , + _STOP_PC =64 , + _RET =64 , + _LP_START =65 , + _LP_END =66 , + _STATUS32 =67 , + _ECR =76 , + _BTA =82 , };#else
Greg Kroah-Hartman
maintainerPATCH 60/123 qla_target: dont delete changed nacls
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Joern Engel <[email protected]>
commit f4c24db1b7ad0ce84409e15744d26c6f86a96840 upstream.
The code is currently riddled with "drop the hardware_lock to avoid a deadlock" bugs that expose races. One of those races seems to expose a valid warning in tcm_qla2xxx_clear_nacl_from_fcport_map. Add some bandaid to it.
--- drivers/scsi/qla2xxx/tcm_qla2xxx.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
drivers/scsi/qla2xxx/tcm_qla2xxx.c +10 -1
@@ -762,7 +762,16 @@ static void tcm_qla2xxx_clear_nacl_from_pr_debug ("fc_rport domain: port_id 0x%06x\n" , nacl->nport_id); node =btree_remove32 (&lport->lport_fcport_map, nacl->nport_id); -WARN_ON (node && (node != se_nacl)); +if (WARN_ON (node && (node != se_nacl))) { +/* +* The nacl no longer matches what we think it should be. +* Most likely a new dynamic acl has been added while +* someone dropped the hardware lock. It clearly is a +* bug elsewhere, but this bit can't make things worse. +*/ +btree_insert32 (&lport->lport_fcport_map, nacl->nport_id, + node,GFP_ATOMIC ); + }pr_debug ("Removed from fcport_map: %p for WWNN: 0x%016LX, port_id: 0x%06x\n" , se_nacl, nacl->nport_wwnn, nacl->nport_id);
Greg Kroah-Hartman
maintainerPATCH 61/123 target: Fix queue full status NULL pointer for SCF_TRANSPORT_TASK_SENSE
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Quinn Tran <[email protected]>
commit 082f58ac4a48d3f5cb4597232cb2ac6823a96f43 upstream.
During temporary resource starvation at lower transport layer, command is placed on queue full retry path, which expose this problem. The TCM queue full handling of SCF_TRANSPORT_TASK_SENSE currently sends the same cmd twice to lower layer. The 1st time led to cmd normal free path. The 2nd time cause Null pointer access.
This regression bug was originally introduced v3.1-rc code in the following commit:
commit e057f53308a5f071556ee80586b99ee755bf07f5
Author: Christoph Hellwig <[email protected]> Date: Mon Oct 17 13:56:41 2011 -0400
target: remove the transport_qf_callback se_cmd callback
--- drivers/target/target_core_transport.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/target/target_core_transport.c +1 -2
@@ -1788,8 +1788,7 @@ static void transport_complete_qf(structif (cmd->se_cmd_flags &SCF_TRANSPORT_TASK_SENSE ) { ret = cmd->se_tfo->queue_status (cmd); -if (ret) - goto out; + goto out; }switch (cmd->data_direction) {
Greg Kroah-Hartman
maintainerPATCH 62/123 target: Fix APTPL metadata handling for dynamic MappedLUNs
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Bellinger <[email protected]>
commit e24805637d2d270d7975502e9024d473de86afdb upstream.
This patch fixes a bug in handling of SPC-3 PR Activate Persistence across Target Power Loss (APTPL) logic where re-creation of state for MappedLUNs from dynamically generated NodeACLs did not occur during I_T Nexus establishment.
It adds the missing core_scsi3_check_aptpl_registration() call during core_tpg_check_initiator_node_acl() -> core_tpg_add_node_to_devs() in order to replay any pre-loaded APTPL metadata state associated with the newly connected SCSI Initiator Port.
--- drivers/target/target_core_device.c | 3 ++- drivers/target/target_core_pr.c | 6 +++--- drivers/target/target_core_pr.h | 2 +- drivers/target/target_core_tpg.c | 8 ++++++++ 4 files changed, 14 insertions(+), 5 deletions(-)
drivers/target/target_core_device.c +2 -1
@@ -1293,7 +1293,8 @@ int core_dev_add_initiator_node_lun_acl(* Check to see if there are any existing persistent reservation APTPL * pre-registrations that need to be enabled for this LUN ACL.. */ -core_scsi3_check_aptpl_registration (lun->lun_se_dev, tpg, lun, lacl); +core_scsi3_check_aptpl_registration (lun->lun_se_dev, tpg, lun, nacl, + lacl->mapped_lun);return 0 ; }
drivers/target/target_core_pr.c +3 -3
@@ -945,10 +945,10 @@ int core_scsi3_check_aptpl_registration(struct se_device *dev, struct se_portal_group *tpg, struct se_lun *lun, - struct se_lun_acl *lun_acl) + struct se_node_acl *nacl, + u32 mapped_lun) { - struct se_node_acl *nacl = lun_acl->se_lun_nacl; -struct se_dev_entry *deve = nacl->device_list[lun_acl->mapped_lun]; + struct se_dev_entry *deve = nacl->device_list[mapped_lun];if (dev->dev_reservation_flags &DRF_SPC2_RESERVATIONS )return 0 ;
drivers/target/target_core_pr.h +1 -1
@@ -55,7 +55,7 @@ extern int core_scsi3_alloc_aptpl_regist unsigned char *, u16, u32, int, int, u8);extern int core_scsi3_check_aptpl_registration (struct se_device *,struct se_portal_group *,struct se_lun *, -struct se_lun_acl *); +struct se_node_acl *,u32 );extern void core_scsi3_free_pr_reg_from_nacl (struct se_device *,struct se_node_acl *);extern void core_scsi3_free_all_registrations (struct se_device *);
drivers/target/target_core_tpg.c +8 -0
@@ -40,6 +40,7 @@#include <target/target_core_fabric.h> #include "target_core_internal.h" +#include "target_core_pr.h" extern struct se_device *g_lun0_dev;
@@ -165,6 +166,13 @@ void core_tpg_add_node_to_devs(core_enable_device_list_for_node (lun,NULL , lun->unpacked_lun, lun_access, acl, tpg); +/* +* Check to see if there are any existing persistent reservation +* APTPL pre-registrations that need to be enabled for this dynamic +* LUN ACL now.. +*/ +core_scsi3_check_aptpl_registration (dev, tpg, lun, acl, + lun->unpacked_lun);spin_lock (&tpg->tpg_lun_lock); }spin_unlock (&tpg->tpg_lun_lock);
Greg Kroah-Hartman
maintainerPATCH 63/123 MIPS: tlbex: Properly fix HUGE TLB Refill exception handler
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Daney <[email protected]>
commit 9e0f162a36914937a937358fcb45e0609ef2bfc4 upstream.
In commit 8393c524a25609 (MIPS: tlbex: Fix a missing statement for HUGETLB), the TLB Refill handler was fixed so that non-OCTEON targets would work properly with huge pages. The change was incorrect in that it broke the OCTEON case.
The problem is shown here:
xxx0: df7a0000 ld k0,0(k1)
.
.
.
xxxc0: df610000 ld at,0(k1)
xxxc4: 335a0ff0 andi k0,k0,0xff0
xxxc8: e825ffcd bbit1 at,0x5,0x0
xxxcc: 003ad82d daddu k1,at,k0
.
.
.In the non-octeon case there is a destructive test for the huge PTE bit, and then at 0, $k0 is reloaded (that is what the 8393c524a25609 patch added).
In the octeon case, we modify k1 in the branch delay slot, but we never need k0 again, so the new load is not needed, but since k1 is modified, if we do the load, we load from a garbage location and then get a nested TLB Refill, which is seen in userspace as either SIGBUS or SIGSEGV (depending on the garbage).
The real fix is to only do this reloading if it is needed, and never where it is harmful.
Patchwork: https://patchwork.linux-mips.org/patch/8151/
--- arch/mips/mm/tlbex.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
arch/mips/mm/tlbex.c +5 -1
@@ -1091,6 +1091,7 @@ static void __cpuinit build_update_entristruct mips_huge_tlb_info {int huge_pte;int restore_scratch; +bool need_reload_pte; }; static struct mips_huge_tlb_info __cpuinit
@@ -1105,6 +1106,7 @@ build_fast_tlb_refill_handler (u32 **p, rv.huge_pte = scratch; rv.restore_scratch =0 ; + rv.need_reload_pte = false;if (check_for_high_segbits) {UASM_i_MFC0 (p, tmp,C0_BADVADDR );
@@ -1293,6 +1295,7 @@ static void __cpuinit build_r4000_tlb_re }else { htlb_info.huge_pte =K0 ; htlb_info.restore_scratch =0 ; + htlb_info.need_reload_pte = true; vmalloc_mode = refill_noscratch;/* * create the plain linear handler
@@ -1329,7 +1332,8 @@ static void __cpuinit build_r4000_tlb_re }#ifdef CONFIG_MIPS_HUGE_TLB_SUPPORT uasm_l_tlb_huge_update (&l, p); -UASM_i_LW (&p,K0 ,0 ,K1 ); +if (htlb_info.need_reload_pte) +UASM_i_LW (&p, htlb_info.huge_pte,0 ,K1 );build_huge_update_entries (&p, htlb_info.huge_pte,K1 );build_huge_tlb_write_entry (&p, &l, &r,K0 , tlb_random, htlb_info.restore_scratch);
Greg Kroah-Hartman
maintainerPATCH 64/123 jbd2: free bh when descriptor block checksum fails
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Darrick J. Wong" <[email protected]>
commit 064d83892e9ba547f7d4eae22cbca066d95210ce upstream.
Free the buffer head if the journal descriptor block fails checksum verification.
This is the jbd2 port of the e2fsprogs patch "e2fsck: free bh on csum verify error in do_one_pass".
--- fs/jbd2/recovery.c | 1 + 1 file changed, 1 insertion(+)
fs/jbd2/recovery.c +1 -0
@@ -522,6 +522,7 @@ static int do_one_pass(journal_t *journa !jbd2_descr_block_csum_verify(journal, bh->b_data)) { err = -EIO ; +brelse (bh); goto failed; }
Greg Kroah-Hartman
maintainerPATCH 65/123 ext4: check EA value offset when loading
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Darrick J. Wong" <[email protected]>
commit a0626e75954078cfacddb00a4545dde821170bc5 upstream.
When loading extended attributes, check each entry's value offset to make sure it doesn't collide with the entries.
Without this check it is easy to crash the kernel by mounting a malicious FS containing a file with an EA wherein e_value_offs = 0 and e_value_size > 0 and then deleting the EA, which corrupts the name list.
(See the f_ea_value_crash test's FS image in e2fsprogs for an example.)
--- fs/ext4/xattr.c | 32 ++++++++++++++++++++++++-------- 1 file changed, 24 insertions(+), 8 deletions(-)
fs/ext4/xattr.c +24 -8
@@ -189,14 +189,28 @@ ext4_listxattr(struct dentry *dentry, ch }static int -ext4_xattr_check_names (struct ext4_xattr_entry *entry,void *end) +ext4_xattr_check_names (struct ext4_xattr_entry *entry,void *end, +void *value_start) { -while (!IS_LAST_ENTRY (entry)) { -struct ext4_xattr_entry *next =EXT4_XATTR_NEXT (entry); +struct ext4_xattr_entry *e = entry; + +while (!IS_LAST_ENTRY (e)) { +struct ext4_xattr_entry *next =EXT4_XATTR_NEXT (e);if ((void *)next >= end)return -EIO ; - entry = next; + e = next; } + +while (!IS_LAST_ENTRY (entry)) { +if (entry->e_value_size !=0 && + (value_start +le16_to_cpu (entry->e_value_offs) < + (void *)e +sizeof (__u32) || + value_start +le16_to_cpu (entry->e_value_offs) + +le32_to_cpu (entry->e_value_size) > end)) +return -EIO ; + entry =EXT4_XATTR_NEXT (entry); + } +return 0 ; }
@@ -213,7 +227,8 @@ ext4_xattr_check_block(struct inode *inoreturn -EIO ;if (!ext4_xattr_block_csum_verify (inode, bh->b_blocknr,BHDR (bh)))return -EIO ; - error =ext4_xattr_check_names (BFIRST (bh), bh->b_data + bh->b_size); + error =ext4_xattr_check_names (BFIRST (bh), bh->b_data + bh->b_size, + bh->b_data);if (!error)set_buffer_verified (bh);return error;
@@ -329,7 +344,7 @@ ext4_xattr_ibody_get(struct inode *inode header =IHDR (inode, raw_inode); entry =IFIRST (header); end = (void *)raw_inode +EXT4_SB (inode->i_sb)->s_inode_size; - error =ext4_xattr_check_names (entry, end); + error =ext4_xattr_check_names (entry, end, entry);if (error) goto cleanup; error = ext4_xattr_find_entry(&entry, name_index, name,
@@ -457,7 +472,7 @@ ext4_xattr_ibody_list(struct dentry *den raw_inode =ext4_raw_inode (&iloc); header =IHDR (inode, raw_inode); end = (void *)raw_inode +EXT4_SB (inode->i_sb)->s_inode_size; - error =ext4_xattr_check_names (IFIRST (header), end); + error =ext4_xattr_check_names (IFIRST (header), end,IFIRST (header));if (error) goto cleanup; error = ext4_xattr_list_entries(dentry, IFIRST(header),
@@ -972,7 +987,8 @@ int ext4_xattr_ibody_find(struct inode * is->s.here = is->s.first; is->s.end = (void *)raw_inode +EXT4_SB (inode->i_sb)->s_inode_size;if (ext4_test_inode_state (inode,EXT4_STATE_XATTR )) { - error =ext4_xattr_check_names (IFIRST (header), is->s.end); + error =ext4_xattr_check_names (IFIRST (header), is->s.end, +IFIRST (header));if (error)return error;/* Find the named attribute. */
Greg Kroah-Hartman
maintainerPATCH 66/123 ext4: dont check quota format when there are no quota files
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 279bf6d390933d5353ab298fcc306c391a961469 upstream.
The check whether quota format is set even though there are no quota files with journalled quota is pointless and it actually makes it impossible to turn off journalled quotas (as there's no way to unset journalled quota format). Just remove the check.
--- fs/ext4/super.c | 7 ------- 1 file changed, 7 deletions(-)
fs/ext4/super.c +0 -7
@@ -1632,13 +1632,6 @@ static int parse_options(char *options, "not specified"); return 0; } - }else { -if (sbi->s_jquota_fmt) { -ext4_msg (sb,KERN_ERR ,"journaled quota format " -"specified with no journaling " -"enabled" ); -return 0 ; - } }#endif if (test_opt (sb,DIOREAD_NOLOCK )) {
Greg Kroah-Hartman
maintainerPATCH 67/123 ext4: grab missed write_count for EXT4_IOC_SWAP_BOOT
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Monakhov <[email protected]>
commit 3e67cfad22230ebed85c56cbe413876f33fea82b upstream.
Otherwise this provokes complain like follows:
WARNING: CPU: 12 PID: 5795 at fs/ext4/ext4_jbd2.c:48 ext4_journal_check_start+0x4e/0xa0() Modules linked in: brd iTCO_wdt lpc_ich mfd_core igb ptp dm_mirror dm_region_hash dm_log dm_mod CPU: 12 PID: 5795 Comm: python Not tainted 3.17.0-rc2-00175-gae5344f #158 Hardware name: Intel Corporation W2600CR/W2600CR, BIOS SE5C600.86B.99.99.x028.061320111235 06/13/2011 0000000000000030 ffff8808116cfd28 ffffffff815c7dfc 0000000000000030 0000000000000000 ffff8808116cfd68 ffffffff8106ce8c ffff8808116cfdc8 ffff880813b16000 ffff880806ad6ae8 ffffffff81202008 0000000000000000 Call Trace: [<ffffffff815c7dfc>] dump_stack+0x51/0x6d [<ffffffff8106ce8c>] warn_slowpath_common+0x8c/0xc0 [<ffffffff81202008>] ? ext4_ioctl+0x9e8/0xeb0 [<ffffffff8106ceda>] warn_slowpath_null+0x1a/0x20 [<ffffffff8122867e>] ext4_journal_check_start+0x4e/0xa0 [<ffffffff81228c10>] __ext4_journal_start_sb+0x90/0x110 [<ffffffff81202008>] ext4_ioctl+0x9e8/0xeb0 [<ffffffff8107b0bd>] ? ptrace_stop+0x24d/0x2f0 [<ffffffff81088530>] ? alloc_pid+0x480/0x480 [<ffffffff8107b1f2>] ? ptrace_do_notify+0x92/0xb0 [<ffffffff81186545>] do_vfs_ioctl+0x4e5/0x550 [<ffffffff815cdbcb>] ? _raw_spin_unlock_irq+0x2b/0x40 [<ffffffff81186603>] SyS_ioctl+0x53/0x80 [<ffffffff815ce2ce>] tracesys+0xd0/0xd5
--- fs/ext4/ioctl.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
fs/ext4/ioctl.c +9 -1
@@ -549,9 +549,17 @@ group_add_out: }case EXT4_IOC_SWAP_BOOT : + { +int err;if (!(filp->f_mode &FMODE_WRITE ))return -EBADF ; -return swap_inode_boot_loader (sb, inode); + err =mnt_want_write_file (filp); +if (err) +return err; + err =swap_inode_boot_loader (sb, inode); +mnt_drop_write_file (filp); +return err; + }case EXT4_IOC_RESIZE_FS : {ext4_fsblk_t n_blocks_count;
Greg Kroah-Hartman
maintainerPATCH 68/123 ext4: add ext4_iget_normal() which is to be used for dir tree lookups
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Theodore Ts'o <[email protected]>
commit f4bb2981024fc91b23b4d09a8817c415396dbabb upstream.
If there is a corrupted file system which has directory entries that point at reserved, metadata inodes, prohibit them from being used by treating them the same way we treat Boot Loader inodes --- that is, mark them to be bad inodes. This prohibits them from being opened, deleted, or modified via chmod, chown, utimes, etc.
In particular, this prevents a corrupted file system which has a directory entry which points at the journal inode from being deleted and its blocks released, after which point Much Hilarity Ensues.
--- fs/ext4/ext4.h | 1 + fs/ext4/inode.c | 7 +++++++ fs/ext4/namei.c | 4 ++-- fs/ext4/super.c | 2 +- 4 files changed, 11 insertions(+), 3 deletions(-)
fs/ext4/ext4.h +1 -0
@@ -2088,6 +2088,7 @@ int do_journal_get_write_access(handle_t#define CONVERT_INLINE_DATA 2extern struct inode *ext4_iget (struct super_block *,unsigned long ); +extern struct inode *ext4_iget_normal (struct super_block *,unsigned long );extern int ext4_write_inode (struct inode *,struct writeback_control *);extern int ext4_setattr (struct dentry *,struct iattr *); extern int ext4_getattr(struct vfsmount *mnt, struct dentry *dentry,
fs/ext4/inode.c +7 -0
@@ -4351,6 +4351,13 @@ bad_inode:return ERR_PTR (ret); } +struct inode *ext4_iget_normal (struct super_block *sb,unsigned long ino) +{ +if (ino <EXT4_FIRST_INO (sb) && ino !=EXT4_ROOT_INO ) +return ERR_PTR (-EIO ); +return ext4_iget (sb, ino); +} +static int ext4_inode_blocks_set (handle_t *handle,struct ext4_inode *raw_inode,struct ext4_inode_info *ei)
fs/ext4/namei.c +2 -2
@@ -1430,7 +1430,7 @@ static struct dentry *ext4_lookup(struct dentry->d_name.name);return ERR_PTR (-EIO ); } - inode =ext4_iget (dir->i_sb, ino); + inode =ext4_iget_normal (dir->i_sb, ino);if (inode ==ERR_PTR (-ESTALE )) { EXT4_ERROR_INODE(dir, "deleted inode referenced: %u",
@@ -1461,7 +1461,7 @@ struct dentry *ext4_get_parent(struct dereturn ERR_PTR (-EIO ); } -return d_obtain_alias (ext4_iget (child->d_inode->i_sb, ino)); +return d_obtain_alias (ext4_iget_normal (child->d_inode->i_sb, ino)); }/*
fs/ext4/super.c +1 -1
@@ -964,7 +964,7 @@ static struct inode *ext4_nfs_get_inode(* Currently we don't know the generation for parent directory, so * a generation of 0 means "accept any" */ - inode =ext4_iget (sb, ino); + inode =ext4_iget_normal (sb, ino);if (IS_ERR (inode))return ERR_CAST (inode);if (generation && inode->i_generation != generation) {
Greg Kroah-Hartman
maintainerPATCH 69/123 ext4: fix reservation overflow in ext4_da_write_begin
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Sandeen <[email protected]>
commit 0ff8947fc5f700172b37cbca811a38eb9cb81e08 upstream.
Delalloc write journal reservations only reserve 1 credit, to update the inode if necessary. However, it may happen once in a filesystem's lifetime that a file will cross the 2G threshold, and require the LARGE_FILE feature to be set in the superblock as well, if it was not set already.
This overruns the transaction reservation, and can be demonstrated simply on any ext4 filesystem without the LARGE_FILE feature already set:
dd if=/dev/zero of=testfile bs=1 seek=2147483646 count=1 \
conv=notrunc of=testfile
sync
dd if=/dev/zero of=testfile bs=1 seek=2147483647 count=1 \
conv=notrunc of=testfile
leads to:
EXT4-fs: ext4_do_update_inode:4296: aborting transaction: error 28 in __ext4_handle_dirty_super EXT4-fs error (device loop0) in ext4_do_update_inode:4301: error 28
EXT4-fs error (device loop0) in ext4_reserve_inode_write:4757: Readonly filesystem EXT4-fs error (device loop0) in ext4_dirty_inode:4876: error 28
EXT4-fs error (device loop0) in ext4_da_write_end:2685: error 28
Adjust the number of credits based on whether the flag is already set, and whether the current write may extend past the LARGE_FILE limit.
--- fs/ext4/inode.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
fs/ext4/inode.c +16 -1
@@ -2647,6 +2647,20 @@ static int ext4_nonda_switch(struct supereturn 0 ; } +/* We always reserve for an inode update; the superblock could be there too */ +static int ext4_da_write_credits (struct inode *inode,loff_t pos,unsigned len) +{ +if (likely (EXT4_HAS_RO_COMPAT_FEATURE (inode->i_sb, +EXT4_FEATURE_RO_COMPAT_LARGE_FILE ))) +return 1 ; + +if (pos + len <=0x7fffffffULL ) +return 1 ; + +/* We might need to update the superblock to set LARGE_FILE */ +return 2 ; +} +static int ext4_da_write_begin (struct file *file,struct address_space *mapping,loff_t pos,unsigned len,unsigned flags,struct page **pagep,void **fsdata)
@@ -2697,7 +2711,8 @@ retry_grab:* of file which has an already mapped buffer. */ retry_journal: - handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE ,1 ); + handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE , +ext4_da_write_credits (inode, pos, len));if (IS_ERR (handle)) {page_cache_release (page);return PTR_ERR (handle);
Greg Kroah-Hartman
maintainerPATCH 70/123 ext4: check s_chksum_driver when looking for bg csum presence
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Darrick J. Wong" <[email protected]>
commit 813d32f91333e4c33d5a19b67167c4bae42dae75 upstream.
Convert the ext4_has_group_desc_csum predicate to look for a checksum driver instead of the metadata_csum flag and change the bg checksum calculation function to look for GDT_CSUM before taking the crc16 path.
Without this patch, if we mount with ^uninit_bg,^metadata_csum and later metadata_csum gets turned on by accident, the block group checksum functions will incorrectly assume that checksumming is enabled (metadata_csum) but that crc16 should be used (!s_chksum_driver). This is totally wrong, so fix the predicate and the checksum formula selection.
(Granted, if the metadata_csum feature bit gets enabled on a live FS then something underhanded is going on, but we could at least avoid writing garbage into the on-disk fields.)
--- fs/ext4/ext4.h | 4 ++-- fs/ext4/super.c | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-)
fs/ext4/ext4.h +2 -2
@@ -2261,8 +2261,8 @@ extern int ext4_register_li_request(strustatic inline int ext4_has_group_desc_csum (struct super_block *sb) {return EXT4_HAS_RO_COMPAT_FEATURE (sb, -EXT4_FEATURE_RO_COMPAT_GDT_CSUM | -EXT4_FEATURE_RO_COMPAT_METADATA_CSUM ); +EXT4_FEATURE_RO_COMPAT_GDT_CSUM ) || + (EXT4_SB (sb)->s_chksum_driver !=NULL ); }static inline ext4_fsblk_t ext4_blocks_count (struct ext4_super_block *es)
fs/ext4/super.c +4 -0
@@ -1950,6 +1950,10 @@ static __le16 ext4_group_desc_csum(struc }/* old crc16 code */ +if (!(sbi->s_es->s_feature_ro_compat & +cpu_to_le32 (EXT4_FEATURE_RO_COMPAT_GDT_CSUM ))) +return 0 ; + offset = offsetof(struct ext4_group_desc , bg_checksum); crc =crc16 (~0 , sbi->s_es->s_uuid,sizeof (sbi->s_es->s_uuid));
Greg Kroah-Hartman
maintainerPATCH 71/123 ext4: fix overflow when updating superblock backups after resize
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 9378c6768e4fca48971e7b6a9075bc006eda981d upstream.
When there are no meta block groups update_backups() will compute the backup block in 32-bit arithmetics thus possibly overflowing the block number and corrupting the filesystem. OTOH filesystems without meta block groups larger than 16 TB should be rare. Fix the problem by doing the counting in 64-bit arithmetics.
Coverity-id: 741252
--- fs/ext4/resize.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/resize.c +1 -1
@@ -1066,7 +1066,7 @@ static void update_backups(struct super_break ;if (meta_bg ==0 ) - backup_block = group * bpg + blk_off; + backup_block = ((ext4_fsblk_t )group) * bpg + blk_off;else backup_block = (ext4_group_first_block_no (sb, group) +ext4_bg_has_super (sb, group));
Greg Kroah-Hartman
maintainerPATCH 73/123 ext4: fix oops when loading block bitmap failed
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 599a9b77ab289d85c2d5c8607624efbe1f552b0f upstream.
When we fail to load block bitmap in __ext4_new_inode() we will dereference NULL pointer in ext4_journal_get_write_access(). So check for error from ext4_read_block_bitmap().
Coverity-id: 989065
--- fs/ext4/ialloc.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/ext4/ialloc.c +4 -0
@@ -793,6 +793,10 @@ got:struct buffer_head *block_bitmap_bh; block_bitmap_bh =ext4_read_block_bitmap (sb, group); +if (!block_bitmap_bh) { + err = -EIO ; + goto out; + }BUFFER_TRACE (block_bitmap_bh,"get block bitmap access" ); err =ext4_journal_get_write_access (handle, block_bitmap_bh);if (err) {
Greg Kroah-Hartman
maintainerPATCH 74/123 freezer: Do not freeze tasks killed by OOM killer
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cong Wang <[email protected]>
commit 51fae6da640edf9d266c94f36bc806c63c301991 upstream.
Since f660daac474c6f (oom: thaw threads if oom killed thread is frozen before deferring) OOM killer relies on being able to thaw a frozen task to handle OOM situation but a3201227f803 (freezer: make freezing() test freeze conditions in effect instead of TIF_FREEZE) has reorganized the code and stopped clearing freeze flag in __thaw_task. This means that the target task only wakes up and goes into the fridge again because the freezing condition hasn't changed for it. This reintroduces the bug fixed by f660daac474c6f.
Fix the issue by checking for TIF_MEMDIE thread flag in freezing_slow_path and exclude the task from freezing completely. If a task was already frozen it would get woken by __thaw_task from OOM killer and get out of freezer after rechecking freezing().
Changes since v1
- put TIF_MEMDIE check into freezing_slowpath rather than in __refrigerator as per Oleg
- return __thaw_task into oom_scan_process_thread because oom_kill_process will not wake task in the fridge because it is sleeping uninterruptible
--- kernel/freezer.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/freezer.c +3 -0
@@ -42,6 +42,9 @@ bool freezing_slow_path(struct task_struif (p->flags &PF_NOFREEZE )return false; +if (test_thread_flag (TIF_MEMDIE )) +return false; +if (pm_nosig_freezing ||cgroup_freezing (p))return true;
Greg Kroah-Hartman
maintainerPATCH 75/123 OOM, PM: OOM killed task shouldnt escape PM suspend
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michal Hocko <[email protected]>
commit 5695be142e203167e3cb515ef86a88424f3524eb upstream.
PM freezer relies on having all tasks frozen by the time devices are getting frozen so that no task will touch them while they are getting frozen. But OOM killer is allowed to kill an already frozen task in order to handle OOM situtation. In order to protect from late wake ups OOM killer is disabled after all tasks are frozen. This, however, still keeps a window open when a killed task didn't manage to die by the time freeze_processes finishes.
Reduce the race window by checking all tasks after OOM killer has been disabled. This is still not race free completely unfortunately because oom_killer_disable cannot stop an already ongoing OOM killer so a task might still wake up from the fridge and get killed without freeze_processes noticing. Full synchronization of OOM and freezer is, however, too heavy weight for this highly unlikely case.
Introduce and check oom_kills counter which gets incremented early when the allocator enters __alloc_pages_may_oom path and only check all the tasks if the counter changes during the freezing attempt. The counter is updated so early to reduce the race window since allocator checked oom_killer_disabled which is set by PM-freezing code. A false positive will push the PM-freezer into a slow path but that is not a big deal.
Changes since v1
- push the re-check loop out of freeze_processes into check_frozen_processes and invert the condition to make the code more readable as per Rafael
--- include/linux/oom.h | 3 +++ kernel/power/process.c | 40 +++++++++++++++++++++++++++++++++++++++- mm/oom_kill.c | 17 +++++++++++++++++ mm/page_alloc.c | 8 ++++++++ 4 files changed, 67 insertions(+), 1 deletion(-)
include/linux/oom.h +3 -0
@@ -50,6 +50,9 @@ static inline bool oom_task_origin(constextern unsigned long oom_badness (struct task_struct *p,struct mem_cgroup *memcg,const nodemask_t *nodemask,unsigned long totalpages); + +extern int oom_kills_count (void ); +extern void note_oom_kill (void ); extern void oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, unsigned int points, unsigned long totalpages, struct mem_cgroup *memcg, nodemask_t *nodemask,
kernel/power/process.c +39 -1
@@ -103,6 +103,28 @@ static int try_to_freeze_tasks(bool userreturn todo ? -EBUSY :0 ; } +/* +* Returns true if all freezable tasks (except for current) are frozen already +*/ +static bool check_frozen_processes (void ) +{ +struct task_struct *g, *p; +bool ret = true; + +read_lock (&tasklist_lock); +for_each_process_thread (g, p) { +if (p != current && !freezer_should_skip (p) && + !frozen (p)) { + ret = false; + goto done; + } + } +done: +read_unlock (&tasklist_lock); + +return ret; +} +/** * freeze_processes - Signal user space processes to enter the refrigerator. *
@@ -111,6 +133,7 @@ static int try_to_freeze_tasks(bool userint freeze_processes (void ) {int error; +int oom_kills_saved; error =__usermodehelper_disable (UMH_FREEZING );if (error)
@@ -121,12 +144,27 @@ int freeze_processes(void)printk ("Freezing user space processes ... " ); pm_freezing = true; + oom_kills_saved =oom_kills_count (); error =try_to_freeze_tasks (true);if (!error) { -printk ("done." );__usermodehelper_set_disable_depth (UMH_DISABLED );oom_killer_disable (); + +/* +* There might have been an OOM kill while we were +* freezing tasks and the killed task might be still +* on the way out so we have to double check for race. +*/ +if (oom_kills_count () != oom_kills_saved && + !check_frozen_processes ()) { +__usermodehelper_set_disable_depth (UMH_ENABLED ); +printk ("OOM in progress." ); + error = -EBUSY ; + goto done; + } +printk ("done." ); } +done:printk ("\n" );BUG_ON (in_atomic ());
mm/oom_kill.c +17 -0
@@ -402,6 +402,23 @@ static void dump_header(struct task_strudump_tasks (memcg, nodemask); } +/* +* Number of OOM killer invocations (including memcg OOM killer). +* Primarily used by PM freezer to check for potential races with +* OOM killed frozen task. +*/ +static atomic_t oom_kills =ATOMIC_INIT (0 ); + +int oom_kills_count (void ) +{ +return atomic_read (&oom_kills); +} + +void note_oom_kill (void ) +{ +atomic_inc (&oom_kills); +} +#define K (x) ((x) << (PAGE_SHIFT-10))/* * Must be called while holding a reference to p, which will be released upon
mm/page_alloc.c +8 -0
@@ -2120,6 +2120,14 @@ __alloc_pages_may_oom(gfp_t gfp_mask, un }/* +* PM-freezer should be notified that there might be an OOM killer on +* its way to kill and wake somebody up. This is too early and we might +* end up not killing anything but false positives are acceptable. +* See freeze_processes. +*/ +note_oom_kill (); + +/* * Go through the zonelist yet one more time, keep very high watermark * here, this is only to catch a parallel oom killing, we must fail if * we're still under heavy pressure.
Greg Kroah-Hartman
maintainerPATCH 76/123 staging:iio:ad5933: Fix NULL pointer deref when enabling buffer
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit 824269c5868d2a7a26417e5ef3841a27d42c6139 upstream.
In older versions of the IIO framework it was possible to pass a completely different set of channels to iio_buffer_register() as the one that is assigned to the IIO device. Commit 959d2952d124 ("staging:iio: make iio_sw_buffer_preenable much more general.") introduced a restriction that requires that the set of channels that is passed to iio_buffer_register() is a subset of the channels assigned to the IIO device as the IIO core will use the list of channels that is assigned to the device to lookup a channel by scan index in iio_compute_scan_bytes(). If it can not find the channel the function will crash. This patch fixes the issue by making sure that the same set of channels is assigned to the IIO device and passed to iio_buffer_register().
Fixes the follow NULL pointer derefernce kernel crash:
Unable to handle kernel NULL pointer dereference at virtual address 00000016 pgd = d53d0000 [00000016] *pgd=1534e831, *pte=00000000, *ppte=00000000 Internal error: Oops: 17 [#1] PREEMPT SMP ARM Modules linked in: CPU: 1 PID: 1626 Comm: bash Not tainted 3.15.0-19969-g2a180eb-dirty #9545 task: d6c124c0 ti: d539a000 task.ti: d539a000 PC is at iio_compute_scan_bytes+0x34/0xa8 LR is at iio_compute_scan_bytes+0x34/0xa8 pc : [<c03052e4>] lr : [<c03052e4>] psr: 60070013 sp : d539beb8 ip : 00000001 fp : 00000000 r10: 00000002 r9 : 00000000 r8 : 00000001 r7 : 00000000 r6 : d6dc8800 r5 : d7571000 r4 : 00000002 r3 : d7571000 r2 : 00000044 r1 : 00000001 r0 : 00000000 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 18c5387d Table: 153d004a DAC: 00000015 Process bash (pid: 1626, stack limit = 0xd539a240) Stack: (0xd539beb8 to 0xd539c000) bea0: c02fc0e4 d7571000 bec0: d76c1640 d6dc8800 d757117c 00000000 d757112c c0305b04 d76c1690 d76c1640 bee0: d7571188 00000002 00000000 d7571000 d539a000 00000000 000dd1c8 c0305d54 bf00: d7571010 0160b868 00000002 c69d3900 d7573278 d7573308 c69d3900 c01ece90 bf20: 00000002 c0103fac c0103f6c d539bf88 00000002 c69d3b00 c69d3b0c c0103468 bf40: 00000000 00000000 d7694a00 00000002 000af408 d539bf88 c000dd84 c00b2f94 bf60: d7694a00 000af408 00000002 d7694a00 d7694a00 00000002 000af408 c000dd84 bf80: 00000000 c00b32d0 00000000 00000000 00000002 b6f1aa78 00000002 000af408 bfa0: 00000004 c000dc00 b6f1aa78 00000002 00000001 000af408 00000002 00000000 bfc0: b6f1aa78 00000002 000af408 00000004 be806a4c 000a6094 00000000 000dd1c8 bfe0: 00000000 be8069cc b6e8ab77 b6ec125c 40070010 00000001 22940489 154a5007 [<c03052e4>] (iio_compute_scan_bytes) from [<c0305b04>] (__iio_update_buffers+0x248/0x438) [<c0305b04>] (__iio_update_buffers) from [<c0305d54>] (iio_buffer_store_enable+0x60/0x7c) [<c0305d54>] (iio_buffer_store_enable) from [<c01ece90>] (dev_attr_store+0x18/0x24) [<c01ece90>] (dev_attr_store) from [<c0103fac>] (sysfs_kf_write+0x40/0x4c) [<c0103fac>] (sysfs_kf_write) from [<c0103468>] (kernfs_fop_write+0x110/0x154) [<c0103468>] (kernfs_fop_write) from [<c00b2f94>] (vfs_write+0xd0/0x160) [<c00b2f94>] (vfs_write) from [<c00b32d0>] (SyS_write+0x40/0x78) [<c00b32d0>] (SyS_write) from [<c000dc00>] (ret_fast_syscall+0x0/0x30) Code: ea00000e e1a01008 e1a00005 ebfff6fc (e5d0a016)
--- drivers/staging/iio/impedance-analyzer/ad5933.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)
drivers/staging/iio/impedance-analyzer/ad5933.c +4 -7
@@ -115,6 +115,7 @@ static const struct iio_chan_spec ad5933 .channel = 0, .info_mask_separate = BIT(IIO_CHAN_INFO_PROCESSED), .address = AD5933_REG_TEMP_DATA, + .scan_index = -1, .scan_type = { .sign = 's', .realbits = 14,
@@ -125,8 +126,6 @@ static const struct iio_chan_spec ad5933 .indexed = 1, .channel = 0, .extend_name = "real_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) | - BIT(IIO_CHAN_INFO_SCALE), .address = AD5933_REG_REAL_DATA, .scan_index = 0, .scan_type = {
@@ -139,8 +138,6 @@ static const struct iio_chan_spec ad5933 .indexed = 1, .channel = 0, .extend_name = "imag_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) | - BIT(IIO_CHAN_INFO_SCALE), .address = AD5933_REG_IMAG_DATA, .scan_index = 1, .scan_type = {
@@ -746,14 +743,14 @@ static int ad5933_probe(struct i2c_clien indio_dev->name = id->name; indio_dev->modes =INDIO_DIRECT_MODE ; indio_dev->channels = ad5933_channels; - indio_dev->num_channels =1 ;/* only register temp0_input */ + indio_dev->num_channels =ARRAY_SIZE (ad5933_channels); ret =ad5933_register_ring_funcs_and_init (indio_dev);if (ret) goto error_disable_reg; -/* skip temp0_input, register in0_(real|imag)_raw */ - ret =iio_buffer_register (indio_dev, &ad5933_channels[1 ],2 ); + ret =iio_buffer_register (indio_dev, ad5933_channels, +ARRAY_SIZE (ad5933_channels));if (ret) goto error_unreg_ring;
Greg Kroah-Hartman
maintainerPATCH 77/123 staging:iio:ad5933: Drop "raw" from channel names
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit 6822ee34ad57b29a3b44df2c2829910f03c34fa4 upstream.
"raw" is the name of a channel property, but should not be part of the channel name itself.
--- drivers/staging/iio/impedance-analyzer/ad5933.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/staging/iio/impedance-analyzer/ad5933.c +2 -2
@@ -125,7 +125,7 @@ static const struct iio_chan_spec ad5933 .type = IIO_VOLTAGE, .indexed = 1, .channel = 0, - .extend_name = "real_raw", + .extend_name = "real", .address = AD5933_REG_REAL_DATA, .scan_index = 0, .scan_type = {
@@ -137,7 +137,7 @@ static const struct iio_chan_spec ad5933 .type = IIO_VOLTAGE, .indexed = 1, .channel = 0, - .extend_name = "imag_raw", + .extend_name = "imag", .address = AD5933_REG_IMAG_DATA, .scan_index = 1, .scan_type = {
Greg Kroah-Hartman
maintainerPATCH 78/123 staging:iio:ade7758: Fix NULL pointer deref when enabling buffer
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit e10554738cab4224e097c2f9d975ea781a4fcde4 upstream.
In older versions of the IIO framework it was possible to pass a completely different set of channels to iio_buffer_register() as the one that is assigned to the IIO device. Commit 959d2952d124 ("staging:iio: make iio_sw_buffer_preenable much more general.") introduced a restriction that requires that the set of channels that is passed to iio_buffer_register() is a subset of the channels assigned to the IIO device as the IIO core will use the list of channels that is assigned to the device to lookup a channel by scan index in iio_compute_scan_bytes(). If it can not find the channel the function will crash. This patch fixes the issue by making sure that the same set of channels is assigned to the IIO device and passed to iio_buffer_register().
Note that we need to remove the IIO_CHAN_INFO_RAW and IIO_CHAN_INFO_SCALE info attributes from the channels since we don't actually want those to be registered.
Fixes the following crash:
Unable to handle kernel NULL pointer dereference at virtual address 00000016 pgd = d2094000 [00000016] *pgd=16e39831, *pte=00000000, *ppte=00000000 Internal error: Oops: 17 [#1] PREEMPT SMP ARM Modules linked in: CPU: 1 PID: 1695 Comm: bash Not tainted 3.17.0-06329-g29461ee #9686 task: d7768040 ti: d5bd4000 task.ti: d5bd4000 PC is at iio_compute_scan_bytes+0x38/0xc0 LR is at iio_compute_scan_bytes+0x34/0xc0 pc : [<c0316de8>] lr : [<c0316de4>] psr: 60070013 sp : d5bd5ec0 ip : 00000000 fp : 00000000 r10: d769f934 r9 : 00000000 r8 : 00000001 r7 : 00000000 r6 : c8fc6240 r5 : d769f800 r4 : 00000000 r3 : d769f800 r2 : 00000000 r1 : ffffffff r0 : 00000000 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 18c5387d Table: 1209404a DAC: 00000015 Process bash (pid: 1695, stack limit = 0xd5bd4240) Stack: (0xd5bd5ec0 to 0xd5bd6000) 5ec0: d769f800 d7435640 c8fc6240 d769f984 00000000 c03175a4 d7435690 d7435640 5ee0: d769f990 00000002 00000000 d769f800 d5bd4000 00000000 000b43a8 c03177f4 5f00: d769f810 0162b8c8 00000002 c8fc7e00 d77f1d08 d77f1da8 c8fc7e00 c01faf1c 5f20: 00000002 c010694c c010690c d5bd5f88 00000002 c8fc6840 c8fc684c c0105e08 5f40: 00000000 00000000 d20d1580 00000002 000af408 d5bd5f88 c000de84 c00b76d4 5f60: d20d1580 000af408 00000002 d20d1580 d20d1580 00000002 000af408 c000de84 5f80: 00000000 c00b7a44 00000000 00000000 00000002 b6ebea78 00000002 000af408 5fa0: 00000004 c000dd00 b6ebea78 00000002 00000001 000af408 00000002 00000000 5fc0: b6ebea78 00000002 000af408 00000004 bee96a4c 000a6094 00000000 000b43a8 5fe0: 00000000 bee969cc b6e2eb77 b6e6525c 40070010 00000001 00000000 00000000 [<c0316de8>] (iio_compute_scan_bytes) from [<c03175a4>] (__iio_update_buffers+0x248/0x438) [<c03175a4>] (__iio_update_buffers) from [<c03177f4>] (iio_buffer_store_enable+0x60/0x7c) [<c03177f4>] (iio_buffer_store_enable) from [<c01faf1c>] (dev_attr_store+0x18/0x24) [<c01faf1c>] (dev_attr_store) from [<c010694c>] (sysfs_kf_write+0x40/0x4c) [<c010694c>] (sysfs_kf_write) from [<c0105e08>] (kernfs_fop_write+0x110/0x154) [<c0105e08>] (kernfs_fop_write) from [<c00b76d4>] (vfs_write+0xbc/0x170) [<c00b76d4>] (vfs_write) from [<c00b7a44>] (SyS_write+0x40/0x78) [<c00b7a44>] (SyS_write) from [<c000dd00>] (ret_fast_syscall+0x0/0x30)
--- drivers/staging/iio/meter/ade7758.h | 1 drivers/staging/iio/meter/ade7758_core.c | 33 +------------------------------ drivers/staging/iio/meter/ade7758_ring.c | 3 -- 3 files changed, 3 insertions(+), 34 deletions(-)
drivers/staging/iio/meter/ade7758.h +0 -1
@@ -119,7 +119,6 @@ struct ade7758_state {u8 *tx;u8 *rx;struct mutex buf_lock; -const struct iio_chan_spec *ade7758_ring_channels;struct spi_transfer ring_xfer[4 ];struct spi_message ring_msg;/*
drivers/staging/iio/meter/ade7758_core.c +2 -31
@@ -649,8 +649,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 0, .extend_name = "raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_A, AD7758_VOLTAGE), .scan_index = 0, .scan_type = {
@@ -663,8 +661,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 0, .extend_name = "raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_A, AD7758_CURRENT), .scan_index = 1, .scan_type = {
@@ -677,8 +673,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 0, .extend_name = "apparent_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_A, AD7758_APP_PWR), .scan_index = 2, .scan_type = {
@@ -691,8 +685,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 0, .extend_name = "active_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_A, AD7758_ACT_PWR), .scan_index = 3, .scan_type = {
@@ -705,8 +697,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 0, .extend_name = "reactive_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_A, AD7758_REACT_PWR), .scan_index = 4, .scan_type = {
@@ -719,8 +709,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 1, .extend_name = "raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_B, AD7758_VOLTAGE), .scan_index = 5, .scan_type = {
@@ -733,8 +721,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 1, .extend_name = "raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_B, AD7758_CURRENT), .scan_index = 6, .scan_type = {
@@ -747,8 +733,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 1, .extend_name = "apparent_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_B, AD7758_APP_PWR), .scan_index = 7, .scan_type = {
@@ -761,8 +745,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 1, .extend_name = "active_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_B, AD7758_ACT_PWR), .scan_index = 8, .scan_type = {
@@ -775,8 +757,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 1, .extend_name = "reactive_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_B, AD7758_REACT_PWR), .scan_index = 9, .scan_type = {
@@ -789,8 +769,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 2, .extend_name = "raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_C, AD7758_VOLTAGE), .scan_index = 10, .scan_type = {
@@ -803,8 +781,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 2, .extend_name = "raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_C, AD7758_CURRENT), .scan_index = 11, .scan_type = {
@@ -817,8 +793,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 2, .extend_name = "apparent_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_C, AD7758_APP_PWR), .scan_index = 12, .scan_type = {
@@ -831,8 +805,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 2, .extend_name = "active_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_C, AD7758_ACT_PWR), .scan_index = 13, .scan_type = {
@@ -845,8 +817,6 @@ static const struct iio_chan_spec ade775 .indexed = 1, .channel = 2, .extend_name = "reactive_raw", - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), .address = AD7758_WT(AD7758_PHASE_C, AD7758_REACT_PWR), .scan_index = 14, .scan_type = {
@@ -890,13 +860,14 @@ static int ade7758_probe(struct spi_devi goto error_free_rx; } st->us = spi; - st->ade7758_ring_channels = &ade7758_channels[0 ];mutex_init (&st->buf_lock); indio_dev->name = spi->dev.driver->name; indio_dev->dev.parent = &spi->dev; indio_dev->info = &ade7758_info; indio_dev->modes =INDIO_DIRECT_MODE ; + indio_dev->channels = ade7758_channels; + indio_dev->num_channels =ARRAY_SIZE (ade7758_channels); ret =ade7758_configure_ring (indio_dev);if (ret)
drivers/staging/iio/meter/ade7758_ring.c +1 -2
@@ -89,7 +89,6 @@ static irqreturn_t ade7758_trigger_handl**/ static int ade7758_ring_preenable (struct iio_dev *indio_dev) { -struct ade7758_state *st =iio_priv (indio_dev);unsigned channel;int ret;
@@ -104,7 +103,7 @@ static int ade7758_ring_preenable(struct indio_dev->masklength);ade7758_write_waveform_type (&indio_dev->dev, - st->ade7758_ring_channels[channel].address); + indio_dev->channels[channel].address);return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 79/123 staging:iio:ade7758: Fix check if channels are enabled in prenable
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit 79fa64eb2ee8ccb4bcad7f54caa2699730b10b22 upstream.
We should check if a channel is enabled, not if no channels are enabled.
--- drivers/staging/iio/meter/ade7758_ring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/staging/iio/meter/ade7758_ring.c +1 -1
@@ -92,7 +92,7 @@ static int ade7758_ring_preenable(structunsigned channel;int ret; -if (!bitmap_empty (indio_dev->active_scan_mask, indio_dev->masklength)) +if (bitmap_empty (indio_dev->active_scan_mask, indio_dev->masklength))return -EINVAL ; ret =iio_sw_buffer_preenable (indio_dev);
Greg Kroah-Hartman
maintainerPATCH 80/123 staging:iio:ade7758: Remove "raw" from channel name
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit b598aacc29331e7e638cd509108600e916c6331b upstream.
"raw" is a property of a channel, but should not be part of the name of channel.
--- drivers/staging/iio/meter/ade7758_core.c | 24 +++++++++--------------- 1 file changed, 9 insertions(+), 15 deletions(-)
drivers/staging/iio/meter/ade7758_core.c +9 -15
@@ -648,7 +648,6 @@ static const struct iio_chan_spec ade775 .type = IIO_VOLTAGE, .indexed = 1, .channel = 0, - .extend_name = "raw", .address = AD7758_WT(AD7758_PHASE_A, AD7758_VOLTAGE), .scan_index = 0, .scan_type = {
@@ -660,7 +659,6 @@ static const struct iio_chan_spec ade775 .type = IIO_CURRENT, .indexed = 1, .channel = 0, - .extend_name = "raw", .address = AD7758_WT(AD7758_PHASE_A, AD7758_CURRENT), .scan_index = 1, .scan_type = {
@@ -672,7 +670,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 0, - .extend_name = "apparent_raw", + .extend_name = "apparent", .address = AD7758_WT(AD7758_PHASE_A, AD7758_APP_PWR), .scan_index = 2, .scan_type = {
@@ -684,7 +682,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 0, - .extend_name = "active_raw", + .extend_name = "active", .address = AD7758_WT(AD7758_PHASE_A, AD7758_ACT_PWR), .scan_index = 3, .scan_type = {
@@ -696,7 +694,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 0, - .extend_name = "reactive_raw", + .extend_name = "reactive", .address = AD7758_WT(AD7758_PHASE_A, AD7758_REACT_PWR), .scan_index = 4, .scan_type = {
@@ -708,7 +706,6 @@ static const struct iio_chan_spec ade775 .type = IIO_VOLTAGE, .indexed = 1, .channel = 1, - .extend_name = "raw", .address = AD7758_WT(AD7758_PHASE_B, AD7758_VOLTAGE), .scan_index = 5, .scan_type = {
@@ -720,7 +717,6 @@ static const struct iio_chan_spec ade775 .type = IIO_CURRENT, .indexed = 1, .channel = 1, - .extend_name = "raw", .address = AD7758_WT(AD7758_PHASE_B, AD7758_CURRENT), .scan_index = 6, .scan_type = {
@@ -732,7 +728,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 1, - .extend_name = "apparent_raw", + .extend_name = "apparent", .address = AD7758_WT(AD7758_PHASE_B, AD7758_APP_PWR), .scan_index = 7, .scan_type = {
@@ -744,7 +740,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 1, - .extend_name = "active_raw", + .extend_name = "active", .address = AD7758_WT(AD7758_PHASE_B, AD7758_ACT_PWR), .scan_index = 8, .scan_type = {
@@ -756,7 +752,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 1, - .extend_name = "reactive_raw", + .extend_name = "reactive", .address = AD7758_WT(AD7758_PHASE_B, AD7758_REACT_PWR), .scan_index = 9, .scan_type = {
@@ -768,7 +764,6 @@ static const struct iio_chan_spec ade775 .type = IIO_VOLTAGE, .indexed = 1, .channel = 2, - .extend_name = "raw", .address = AD7758_WT(AD7758_PHASE_C, AD7758_VOLTAGE), .scan_index = 10, .scan_type = {
@@ -780,7 +775,6 @@ static const struct iio_chan_spec ade775 .type = IIO_CURRENT, .indexed = 1, .channel = 2, - .extend_name = "raw", .address = AD7758_WT(AD7758_PHASE_C, AD7758_CURRENT), .scan_index = 11, .scan_type = {
@@ -792,7 +786,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 2, - .extend_name = "apparent_raw", + .extend_name = "apparent", .address = AD7758_WT(AD7758_PHASE_C, AD7758_APP_PWR), .scan_index = 12, .scan_type = {
@@ -804,7 +798,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 2, - .extend_name = "active_raw", + .extend_name = "active", .address = AD7758_WT(AD7758_PHASE_C, AD7758_ACT_PWR), .scan_index = 13, .scan_type = {
@@ -816,7 +810,7 @@ static const struct iio_chan_spec ade775 .type = IIO_POWER, .indexed = 1, .channel = 2, - .extend_name = "reactive_raw", + .extend_name = "reactive", .address = AD7758_WT(AD7758_PHASE_C, AD7758_REACT_PWR), .scan_index = 14, .scan_type = {
Greg Kroah-Hartman
maintainerPATCH 82/123 USB: serial: cp210x: add Silicon Labs 358x VID and PID
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nathaniel Ting <[email protected]>
commit 35cc83eab097e5720a9cc0ec12bdc3a726f58381 upstream.
Enable Silicon Labs Ember VID chips to enumerate with the cp210x usb serial driver. EM358x devices operating with the Ember Z-Net 5.1.2 stack may now connect to host PCs over a USB serial link.
--- drivers/usb/serial/cp210x.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/cp210x.c +1 -0
@@ -155,6 +155,7 @@ static const struct usb_device_id id_tab { USB_DEVICE(0x18EF, 0xE00F) }, /* ELV USB-I2C-Interface */ { USB_DEVICE(0x1ADB, 0x0001) }, /* Schweitzer Engineering C662 Cable */ { USB_DEVICE(0x1B1C, 0x1C00) }, /* Corsair USB Dongle */ + { USB_DEVICE(0x1BA4, 0x0002) }, /* Silicon Labs 358x factory default */ { USB_DEVICE(0x1BE3, 0x07A6) }, /* WAGO 750-923 USB Service Cable */ { USB_DEVICE(0x1D6F, 0x0010) }, /* Seluxit ApS RF Dongle */ { USB_DEVICE(0x1E29, 0x0102) }, /* Festo CPX-USB */
Greg Kroah-Hartman
maintainerPATCH 83/123 usb: serial: ftdi_sio: add Awinda Station and Dongle products
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Frans Klaver <[email protected]>
commit edd74ffab1f6909eee400c7de8ce621870aacac9 upstream.
Add new IDs for the Xsens Awinda Station and Awinda Dongle.
While at it, order the definitions by PID and add a logical separation between devices using Xsens' VID and those using FTDI's VID.
--- drivers/usb/serial/ftdi_sio.c | 2 ++ drivers/usb/serial/ftdi_sio_ids.h | 6 +++++- 2 files changed, 7 insertions(+), 1 deletion(-)
drivers/usb/serial/ftdi_sio.c +2 -0
@@ -677,6 +677,8 @@ static struct usb_device_id id_table_com { USB_DEVICE(FTDI_VID, XSENS_CONVERTER_5_PID) }, { USB_DEVICE(FTDI_VID, XSENS_CONVERTER_6_PID) }, { USB_DEVICE(FTDI_VID, XSENS_CONVERTER_7_PID) }, + { USB_DEVICE(XSENS_VID, XSENS_AWINDA_DONGLE_PID) }, + { USB_DEVICE(XSENS_VID, XSENS_AWINDA_STATION_PID) }, { USB_DEVICE(XSENS_VID, XSENS_CONVERTER_PID) }, { USB_DEVICE(XSENS_VID, XSENS_MTW_PID) }, { USB_DEVICE(FTDI_VID, FTDI_OMNI1509) },
drivers/usb/serial/ftdi_sio_ids.h +5 -1
@@ -143,8 +143,12 @@* Xsens Technologies BV products (http://www.xsens.com). */ #define XSENS_VID 0x2639 -#define XSENS_CONVERTER_PID 0xD00D/* Xsens USB-serial converter */ +#define XSENS_AWINDA_STATION_PID 0x0101 +#define XSENS_AWINDA_DONGLE_PID 0x0102#define XSENS_MTW_PID 0x0200/* Xsens MTw */ +#define XSENS_CONVERTER_PID 0xD00D/* Xsens USB-serial converter */ + +/* Xsens devices using FTDI VID */ #define XSENS_CONVERTER_0_PID 0xD388/* Xsens USB converter */ #define XSENS_CONVERTER_1_PID 0xD389/* Xsens Wireless Receiver */ #define XSENS_CONVERTER_2_PID 0xD38A
Greg Kroah-Hartman
maintainerPATCH 84/123 usb: serial: ftdi_sio: add "bricked" FTDI device PID
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Perry Hung <[email protected]>
commit 7f2719f0003da1ad13124ef00f48d7514c79e30d upstream.
An official recent Windows driver from FTDI detects counterfeit devices and reprograms the internal EEPROM containing the USB PID to 0, effectively bricking the device.
Add support for this VID/PID pair to correctly bind the driver on these devices.
See:
http://hackaday.com/2014/10/22/watch-that-windows-update-ftdi-drivers-are-killing-fake-chips/
--- drivers/usb/serial/ftdi_sio.c | 1 + drivers/usb/serial/ftdi_sio_ids.h | 6 ++++++ 2 files changed, 7 insertions(+)
drivers/usb/serial/ftdi_sio.c +1 -0
@@ -148,6 +148,7 @@ static struct ftdi_sio_quirk ftdi_8u2232* /sys/bus/usb/ftdi_sio/new_id, then send patch/report! */ static struct usb_device_id id_table_combined [] = { + {USB_DEVICE (FTDI_VID ,FTDI_BRICK_PID ) }, {USB_DEVICE (FTDI_VID ,FTDI_ZEITCONTROL_TAGTRACE_MIFARE_PID ) }, {USB_DEVICE (FTDI_VID ,FTDI_CTI_MINI_PID ) }, {USB_DEVICE (FTDI_VID ,FTDI_CTI_NANO_PID ) },
drivers/usb/serial/ftdi_sio_ids.h +6 -0
@@ -30,6 +30,12 @@/*** third-party PIDs (using FTDI_VID) ***/ +/* +* Certain versions of the official Windows FTDI driver reprogrammed +* counterfeit FTDI devices to PID 0. Support these devices anyway. +*/ +#define FTDI_BRICK_PID 0x0000 +#define FTDI_LUMEL_PD12_PID 0x6002/*
Greg Kroah-Hartman
maintainerPATCH 85/123 USB: cdc-acm: add device id for GW Instek AFG-2225
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit cf84a691a61606a2e7269907d3727e2d9fa148ee upstream.
Add device-id entry for GW Instek AFG-2225, which has a byte swapped bInterfaceSubClass (0x20).
--- drivers/usb/class/cdc-acm.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/class/cdc-acm.c +1 -0
@@ -1588,6 +1588,7 @@ static const struct usb_device_id acm_id { USB_DEVICE(0x0572, 0x1328), /* Shiro / Aztech USB MODEM UM-3100 */ .driver_info =NO_UNION_NORMAL ,/* has no union descriptor */ }, + { USB_DEVICE(0x2184, 0x001c) }, /* GW Instek AFG-2225 */ { USB_DEVICE(0x22b8, 0x6425), /* Motorola MOTOMAGX phones */ },/* Motorola H24 HSPA module: */
Greg Kroah-Hartman
maintainerPATCH 86/123 USB: cdc-acm: only raise DTR on transitions from B0
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 4473d054ceb572557954f9536731d39b20937b0c upstream.
Make sure to only raise DTR on transitions from B0 in set_termios.
Also allow set_termios to be called from open with a termios_old of NULL. Note that DTR will not be raised prematurely in this case.
--- drivers/usb/class/cdc-acm.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/usb/class/cdc-acm.c +3 -2
@@ -883,11 +883,12 @@ static void acm_tty_set_termios(struct t/* FIXME: Needs to clear unsupported bits in the termios */ acm->clocal = ((termios->c_cflag &CLOCAL ) !=0 ); -if (!newline.dwDTERate) { +if (C_BAUD (tty) ==B0 ) { newline.dwDTERate = acm->line.dwDTERate; newctrl &= ~ACM_CTRL_DTR ; - }else + }else if (termios_old && (termios_old->c_cflag &CBAUD ) ==B0 ) { newctrl |=ACM_CTRL_DTR ; + }if (newctrl != acm->ctrlout)acm_set_control (acm, acm->ctrlout = newctrl);
Greg Kroah-Hartman
maintainerPATCH 87/123 usb: option: add support for Telit LE910
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniele Palmas <[email protected]>
commit 2d0eb862dd477c3c4f32b201254ca0b40e6f465c upstream.
Add VID/PID for Telit LE910 modem. Interfaces description is almost the same than LE920, except that the qmi interface is number 2 (instead than 5).
--- drivers/usb/serial/option.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/usb/serial/option.c +8 -0
@@ -269,6 +269,7 @@ static void option_instat_callback(struc#define TELIT_PRODUCT_DE910_DUAL 0x1010#define TELIT_PRODUCT_UE910_V2 0x1012#define TELIT_PRODUCT_LE920 0x1200 +#define TELIT_PRODUCT_LE910 0x1201/* ZTE PRODUCTS */ #define ZTE_VENDOR_ID 0x19d2
@@ -588,6 +589,11 @@ static const struct option_blacklist_inf .reserved = BIT(3) | BIT(4), }; +static const struct option_blacklist_info telit_le910_blacklist = { + .sendsetup =BIT (0 ), + .reserved =BIT (1 ) |BIT (2 ), +}; +static const struct option_blacklist_info telit_le920_blacklist = { .sendsetup =BIT (0 ), .reserved =BIT (1 ) |BIT (5 ),
@@ -1137,6 +1143,8 @@ static const struct usb_device_id option { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_CC864_SINGLE) }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_DE910_DUAL) }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_UE910_V2) }, + { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_LE910), + .driver_info = (kernel_ulong_t)&telit_le910_blacklist }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_LE920), .driver_info = (kernel_ulong_t)&telit_le920_blacklist }, { USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, ZTE_PRODUCT_MF622, 0xff, 0xff, 0xff) }, /* ZTE WCDMA products */
Greg Kroah-Hartman
maintainerPATCH 88/123 USB: option: add Haier CE81B CDMA modem
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Williams <[email protected]>
commit 012eee1522318b5ccd64d277d50ac32f7e9974fe upstream.
Port layout:
0: QCDM/DIAG
1: NMEA
2: AT
3: AT/PPP
--- drivers/usb/serial/option.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/serial/option.c +2 -0
@@ -362,6 +362,7 @@ static void option_instat_callback(struc/* Haier products */ #define HAIER_VENDOR_ID 0x201e +#define HAIER_PRODUCT_CE81B 0x10f8#define HAIER_PRODUCT_CE100 0x2009/* Cinterion (formerly Siemens) products */
@@ -1620,6 +1621,7 @@ static const struct usb_device_id option { USB_DEVICE(LONGCHEER_VENDOR_ID, ZOOM_PRODUCT_4597) }, { USB_DEVICE(LONGCHEER_VENDOR_ID, IBALL_3_5G_CONNECT) }, { USB_DEVICE(HAIER_VENDOR_ID, HAIER_PRODUCT_CE100) }, + { USB_DEVICE_AND_INTERFACE_INFO(HAIER_VENDOR_ID, HAIER_PRODUCT_CE81B, 0xff, 0xff, 0xff) },/* Pirelli */ { USB_DEVICE_INTERFACE_CLASS(PIRELLI_VENDOR_ID, PIRELLI_PRODUCT_C100_1, 0xff) }, { USB_DEVICE_INTERFACE_CLASS(PIRELLI_VENDOR_ID, PIRELLI_PRODUCT_C100_2, 0xff) },
Greg Kroah-Hartman
maintainerPATCH 89/123 wireless: rt2x00: add new rt2800usb device
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cyril Brulebois <[email protected]>
commit 664d6a792785cc677c2091038ce10322c8d04ae1 upstream.
0x1b75 0xa200 AirLive WN-200USB wireless 11b/g/n dongle
References: https://bugs.debian.org/766802
--- drivers/net/wireless/rt2x00/rt2800usb.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/wireless/rt2x00/rt2800usb.c +1 -0
@@ -1091,6 +1091,7 @@ static struct usb_device_id rt2800usb_de/* Ovislink */ { USB_DEVICE(0x1b75, 0x3071) }, { USB_DEVICE(0x1b75, 0x3072) }, + { USB_DEVICE(0x1b75, 0xa200) },/* Para */ { USB_DEVICE(0x20b8, 0x8888) },/* Pegatron */
Greg Kroah-Hartman
maintainerPATCH 90/123 usb: dwc3: gadget: Properly initialize LINK TRB
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jack Pham <[email protected]>
commit 1200a82a59b6aa65758ccc92c3447b98c53cd7a2 upstream.
On ISOC endpoints the last trb_pool entry used as a LINK TRB is not getting zeroed out correctly due to memset being called incorrectly and in the wrong place. If pool allocated from DMA was not zero-initialized to begin with this will result in the size and ctrl values being random garbage. Call memset correctly after assignment of the trb_link pointer.
--- drivers/usb/dwc3/gadget.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/usb/dwc3/gadget.c +1 -2
@@ -550,12 +550,11 @@ static int __dwc3_gadget_ep_enable(strucif (!usb_endpoint_xfer_isoc (desc))return 0 ; -memset (&trb_link,0 ,sizeof (trb_link)); -/* Link TRB for ISOC. The HWO bit is never reset */ trb_st_hw = &dep->trb_pool[0 ]; trb_link = &dep->trb_pool[DWC3_TRB_NUM -1 ]; +memset (trb_link,0 ,sizeof (*trb_link)); trb_link->bpl =lower_32_bits (dwc3_trb_dma_offset (dep, trb_st_hw)); trb_link->bph =upper_32_bits (dwc3_trb_dma_offset (dep, trb_st_hw));
Greg Kroah-Hartman
maintainerPATCH 91/123 spi: pl022: Fix incorrect dma_unmap_sg
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ray Jui <[email protected]>
commit 3ffa6158f002e096d28ede71be4e0ee8ab20baa2 upstream.
When mapped RX DMA entries are unmapped in an error condition when DMA is firstly configured in the driver, the number of TX DMA entries was passed in, which is incorrect
--- drivers/spi/spi-pl022.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-pl022.c +1 -1
@@ -1080,7 +1080,7 @@ err_rxdesc: pl022->sgt_tx.nents, DMA_TO_DEVICE); err_tx_sgmap:dma_unmap_sg (rxchan->device->dev, pl022->sgt_rx.sgl, - pl022->sgt_tx.nents,DMA_FROM_DEVICE ); + pl022->sgt_rx.nents,DMA_FROM_DEVICE ); err_rx_sgmap:sg_free_table (&pl022->sgt_tx); err_alloc_tx_sg:
Greg Kroah-Hartman
maintainerPATCH 92/123 spi: pxa2xx: toggle clocks on suspend if not disabled by runtime PM
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Eremin-Solenikov <[email protected]>
commit 2b9375b91bef65b837bed61a05fb387159b38ddf upstream.
If PM_RUNTIME is enabled, it is easy to trigger the following backtrace on pxa2xx hosts:
------------[ cut here ]------------ WARNING: CPU: 0 PID: 1 at /home/lumag/linux/arch/arm/mach-pxa/clock.c:35 clk_disable+0xa0/0xa8() Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted 3.17.0-00007-g1b3d2ee-dirty #104 [<c000de68>] (unwind_backtrace) from [<c000c078>] (show_stack+0x10/0x14) [<c000c078>] (show_stack) from [<c001d75c>] (warn_slowpath_common+0x6c/0x8c) [<c001d75c>] (warn_slowpath_common) from [<c001d818>] (warn_slowpath_null+0x1c/0x24) [<c001d818>] (warn_slowpath_null) from [<c0015e80>] (clk_disable+0xa0/0xa8) [<c0015e80>] (clk_disable) from [<c02507f8>] (pxa2xx_spi_suspend+0x2c/0x34) [<c02507f8>] (pxa2xx_spi_suspend) from [<c0200360>] (platform_pm_suspend+0x2c/0x54) [<c0200360>] (platform_pm_suspend) from [<c0207fec>] (dpm_run_callback.isra.14+0x2c/0x74) [<c0207fec>] (dpm_run_callback.isra.14) from [<c0209254>] (__device_suspend+0x120/0x2f8) [<c0209254>] (__device_suspend) from [<c0209a94>] (dpm_suspend+0x50/0x208) [<c0209a94>] (dpm_suspend) from [<c00455ac>] (suspend_devices_and_enter+0x8c/0x3a0) [<c00455ac>] (suspend_devices_and_enter) from [<c0045ad4>] (pm_suspend+0x214/0x2a8) [<c0045ad4>] (pm_suspend) from [<c04b5c34>] (test_suspend+0x14c/0x1dc) [<c04b5c34>] (test_suspend) from [<c000880c>] (do_one_initcall+0x8c/0x1fc) [<c000880c>] (do_one_initcall) from [<c04aecfc>] (kernel_init_freeable+0xf4/0x1b4) [<c04aecfc>] (kernel_init_freeable) from [<c0378078>] (kernel_init+0x8/0xec) [<c0378078>] (kernel_init) from [<c0009590>] (ret_from_fork+0x14/0x24) ---[ end trace 46524156d8faa4f6 ]---
This happens because suspend function tries to disable a clock that is already disabled by runtime_suspend callback. Add if (!pm_runtime_suspended()) checks to suspend/resume path.
--- drivers/spi/spi-pxa2xx.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/spi/spi-pxa2xx.c +5 -2
@@ -1324,7 +1324,9 @@ static int pxa2xx_spi_suspend(struct devif (status !=0 )return status;write_SSCR0 (0 , drv_data->ioaddr); -clk_disable_unprepare (ssp->clk); + +if (!pm_runtime_suspended (dev)) +clk_disable_unprepare (ssp->clk);return 0 ; }
@@ -1338,7 +1340,8 @@ static int pxa2xx_spi_resume(struct devipxa2xx_spi_dma_resume (drv_data);/* Enable the SSP clock */ -clk_prepare_enable (ssp->clk); +if (!pm_runtime_suspended (dev)) +clk_prepare_enable (ssp->clk);/* Start the queue running */ status =spi_master_resume (drv_data->master);
Greg Kroah-Hartman
maintainerPATCH 93/123 usb-storage: handle a skipped data phase
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alan Stern <[email protected]>
commit 93c9bf4d1838d5851a18ca398b0ad66397f05056 upstream.
Sometimes mass-storage devices using the Bulk-only transport will mistakenly skip the data phase of a command. Rather than sending the data expected by the host or sending a zero-length packet, they go directly to the status phase and send the CSW.
This causes problems for usb-storage, for obvious reasons. The driver will interpret the CSW as a short data transfer and will wait to receive a CSW. The device won't have anything left to send, so the command eventually times out.
The SCSI layer doesn't retry commands after they time out (this is a relatively recent change). Therefore we should do our best to detect a skipped data phase and handle it promptly.
This patch adds code to do that. If usb-storage receives a short 13-byte data transfer from the device, and if the first four bytes of the data match the CSW signature, the driver will set the residue to the full transfer length and interpret the data as a CSW.
This fixes Bugzilla #86611.
--- drivers/usb/storage/transport.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
drivers/usb/storage/transport.c +26 -0
@@ -1118,6 +1118,31 @@ int usb_stor_Bulk_transport(struct scsi_*/ if (result ==USB_STOR_XFER_LONG ) fake_sense =1 ; + +/* +* Sometimes a device will mistakenly skip the data phase +* and go directly to the status phase without sending a +* zero-length packet. If we get a 13-byte response here, +* check whether it really is a CSW. +*/ +if (result ==USB_STOR_XFER_SHORT && + srb->sc_data_direction ==DMA_FROM_DEVICE && + transfer_length -scsi_get_resid (srb) == +US_BULK_CS_WRAP_LEN ) { +struct scatterlist *sg =NULL ; +unsigned int offset =0 ; + +if (usb_stor_access_xfer_buf ((unsigned char *) bcs, +US_BULK_CS_WRAP_LEN , srb, &sg, + &offset,FROM_XFER_BUF ) == +US_BULK_CS_WRAP_LEN && + bcs->Signature == +cpu_to_le32 (US_BULK_CS_SIGN )) { +usb_stor_dbg (us,"Device skipped data phase\n" ); +scsi_set_resid (srb, transfer_length); + goto skipped_data_phase; + } + } }/* See flow chart on pg 15 of the Bulk Only Transport spec for
@@ -1153,6 +1178,7 @@ int usb_stor_Bulk_transport(struct scsi_if (result !=USB_STOR_XFER_GOOD )return USB_STOR_TRANSPORT_ERROR ; + skipped_data_phase:/* check bulk status */ residue =le32_to_cpu (bcs->Residue); usb_stor_dbg(us, "Bulk Status S 0x%x T 0x%x R %u Stat 0x%x\n",
Greg Kroah-Hartman
maintainerPATCH 94/123 USB: opticon: fix non-atomic allocation in write path
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit e681286de221af78fc85db9222b6a203148c005a upstream.
Write may be called from interrupt context so make sure to use GFP_ATOMIC for all allocations in write.
--- drivers/usb/serial/opticon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/serial/opticon.c +1 -1
@@ -219,7 +219,7 @@ static int opticon_write(struct tty_stru/* The conncected devices do not have a bulk write endpoint, * to transmit data to de barcode device the control endpoint is used */ - dr =kmalloc (sizeof (struct usb_ctrlrequest ),GFP_NOIO ); + dr =kmalloc (sizeof (struct usb_ctrlrequest ),GFP_ATOMIC );if (!dr) {dev_err (&port->dev,"out of memory\n" ); count = -ENOMEM ;
Greg Kroah-Hartman
maintainerPATCH 95/123 usb: Do not allow usb_alloc_streams on unconfigured devices
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit 90a646c770c50cc206ceba0d7b50453c46c13c36 upstream.
This commit fixes the following oops:
[10238.622067] scsi host3: uas_eh_bus_reset_handler start [10240.766164] usb 3-4: reset SuperSpeed USB device number 3 using xhci_hcd [10245.779365] usb 3-4: device descriptor read/8, error -110 [10245.883331] usb 3-4: reset SuperSpeed USB device number 3 using xhci_hcd [10250.897603] usb 3-4: device descriptor read/8, error -110 [10251.058200] BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 [10251.058244] IP: [<ffffffff815ac6e1>] xhci_check_streams_endpoint+0x91/0x140 <snip> [10251.059473] Call Trace: [10251.059487] [<ffffffff815aca6c>] xhci_calculate_streams_and_bitmask+0xbc/0x130 [10251.059520] [<ffffffff815aeb5f>] xhci_alloc_streams+0x10f/0x5a0 [10251.059548] [<ffffffff810a4685>] ? check_preempt_curr+0x75/0xa0 [10251.059575] [<ffffffff810a46dc>] ? ttwu_do_wakeup+0x2c/0x100 [10251.059601] [<ffffffff810a49e6>] ? ttwu_do_activate.constprop.111+0x66/0x70 [10251.059635] [<ffffffff815779ab>] usb_alloc_streams+0xab/0xf0 [10251.059662] [<ffffffffc0616b48>] uas_configure_endpoints+0x128/0x150 [uas] [10251.059694] [<ffffffffc0616bac>] uas_post_reset+0x3c/0xb0 [uas] [10251.059722] [<ffffffff815727d9>] usb_reset_device+0x1b9/0x2a0 [10251.059749] [<ffffffffc0616f42>] uas_eh_bus_reset_handler+0xb2/0x190 [uas] [10251.059781] [<ffffffff81514293>] scsi_try_bus_reset+0x53/0x110 [10251.059808] [<ffffffff815163b7>] scsi_eh_bus_reset+0xf7/0x270
<snip>
The problem is the following call sequence (simplified):
1) usb_reset_device
2) usb_reset_and_verify_device
2) hub_port_init
3) hub_port_finish_reset
3) xhci_discover_or_reset_device
This frees xhci->devs[slot_id]->eps[ep_index].ring for all eps but 0
4) usb_get_device_descriptor
This fails
5) hub_port_init fails
6) usb_reset_and_verify_device fails, does not restore device config
7) uas_post_reset
8) xhci_alloc_streams
NULL deref on the free-ed ring
This commit fixes this by not allowing usb_alloc_streams to continue if the device is not configured.
Note that we do allow usb_free_streams to continue after a (logical) disconnect, as it is necessary to explicitly free the streams at the xhci controller level.
--- drivers/usb/core/hcd.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/core/hcd.c +2 -0
@@ -1947,6 +1947,8 @@ int usb_alloc_streams(struct usb_interfareturn -EINVAL ;if (dev->speed !=USB_SPEED_SUPER )return -EINVAL ; +if (dev->state <USB_STATE_CONFIGURED ) +return -ENODEV ;/* Streams only apply to bulk endpoints. */ for (i =0 ; i < num_eps; i++)
Greg Kroah-Hartman
maintainerPATCH 96/123 cgroup/kmemleak: add kmemleak_free() for cgroup deallocations.
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wang Nan <[email protected]>
commit 401507d67d5c2854f5a88b3f93f64fc6f267bca5 upstream.
Commit ff7ee93f4715 ("cgroup/kmemleak: Annotate alloc_page() for cgroup allocations") introduces kmemleak_alloc() for alloc_page_cgroup(), but corresponding kmemleak_free() is missing, which makes kmemleak be wrongly disabled after memory offlining. Log is pasted at the end of this commit message.
This patch add kmemleak_free() into free_page_cgroup(). During page offlining, this patch removes corresponding entries in kmemleak rbtree. After that, the freed memory can be allocated again by other subsystems without killing kmemleak.
bash # for x in 1 2 3 4; do echo offline > /sys/devices/system/memory/memory$x/state ; sleep 1; done ; dmesg | grep leak
Offlined Pages 32768
kmemleak: Cannot insert 0xffff880016969000 into the object search tree (overlaps existing)
CPU: 0 PID: 412 Comm: sleep Not tainted 3.17.0-rc5+ #86
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
Call Trace:
dump_stack+0x46/0x58
create_object+0x266/0x2c0
kmemleak_alloc+0x26/0x50
kmem_cache_alloc+0xd3/0x160
__sigqueue_alloc+0x49/0xd0
__send_signal+0xcb/0x410
send_signal+0x45/0x90
__group_send_sig_info+0x13/0x20
do_notify_parent+0x1bb/0x260
do_exit+0x767/0xa40
do_group_exit+0x44/0xa0
SyS_exit_group+0x17/0x20
system_call_fastpath+0x16/0x1b kmemleak: Kernel memory leak detector disabled
kmemleak: Object 0xffff880016900000 (size 524288):
kmemleak: comm "swapper/0", pid 0, jiffies 4294667296
kmemleak: min_count = 0
kmemleak: count = 0
kmemleak: flags = 0x1
kmemleak: checksum = 0
kmemleak: backtrace:
log_early+0x63/0x77
kmemleak_alloc+0x4b/0x50
init_section_page_cgroup+0x7f/0xf5
page_cgroup_init+0xc5/0xd0
start_kernel+0x333/0x408
x86_64_start_reservations+0x2a/0x2c
x86_64_start_kernel+0xf5/0xfc--- mm/page_cgroup.c | 1 + 1 file changed, 1 insertion(+)
mm/page_cgroup.c +1 -0
@@ -170,6 +170,7 @@ static void free_page_cgroup(void *addr)sizeof (struct page_cgroup ) *PAGES_PER_SECTION ;BUG_ON (PageReserved (page)); +kmemleak_free (addr);free_pages_exact (addr, table_size); } }
Greg Kroah-Hartman
maintainerPATCH 97/123 lib/bitmap.c: fix undefined shift in __bitmap_shift_{left|right}()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit ea5d05b34aca25c066e0699512d0ffbd8ee6ac3e upstream.
If __bitmap_shift_left() or __bitmap_shift_right() are asked to shift by a multiple of BITS_PER_LONG, they will try to shift a long value by BITS_PER_LONG bits which is undefined. Change the functions to avoid the undefined shift.
Coverity id: 1192175
Coverity id: 1192174
--- lib/bitmap.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
lib/bitmap.c +6 -2
@@ -131,7 +131,9 @@ void __bitmap_shift_right(unsigned long lower = src[off + k];if (left && off + k == lim -1 ) lower &= mask; - dst[k] = upper << (BITS_PER_LONG - rem) | lower >> rem; + dst[k] = lower >> rem; +if (rem) + dst[k] |= upper << (BITS_PER_LONG - rem);if (left && k == lim -1 ) dst[k] &= mask; }
@@ -172,7 +174,9 @@ void __bitmap_shift_left(unsigned long * upper = src[k];if (left && k == lim -1 ) upper &= (1UL << left) -1 ; - dst[k + off] = lower >> (BITS_PER_LONG - rem) | upper << rem; + dst[k + off] = upper << rem; +if (rem) + dst[k + off] |= lower >> (BITS_PER_LONG - rem);if (left && k + off == lim -1 ) dst[k + off] &= (1UL << left) -1 ; }
Greg Kroah-Hartman
maintainerPATCH 98/123 scsi: Fix error handling in SCSI_IOCTL_SEND_COMMAND
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 84ce0f0e94ac97217398b3b69c21c7a62ebeed05 upstream.
When sg_scsi_ioctl() fails to prepare request to submit in blk_rq_map_kern() we jump to a label where we just end up copying (luckily zeroed-out) kernel buffer to userspace instead of reporting error. Fix the problem by jumping to the right label.
CC: Jens Axboe <[email protected]>
CC: [email protected]
Coverity-id: 1226871
Fixed up the, now unused, out label.
--- block/scsi_ioctl.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
block/scsi_ioctl.c +1 -2
@@ -506,7 +506,7 @@ int sg_scsi_ioctl(struct request_queue *if (bytes &&blk_rq_map_kern (q, rq, buffer, bytes, __GFP_WAIT)) { err =DRIVER_ERROR <<24 ; - goto out; + goto error; }memset (sense,0 ,sizeof (sense));
@@ -516,7 +516,6 @@ int sg_scsi_ioctl(struct request_queue *blk_execute_rq (q, disk, rq,0 ); -out: err = rq->errors &0xff ;/* only 8 bit SCSI status */ if (err) {if (rq->sense_len && rq->sense) {
Greg Kroah-Hartman
maintainerPATCH 99/123 i82860_edac: Report CE events properly
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Baron <[email protected]>
commit ab0543de6ff0877474f57a5aafbb51a61e88676f upstream.
Fix CE event being reported as HW_EVENT_ERR_UNCORRECTED.
--- drivers/edac/i82860_edac.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/edac/i82860_edac.c +1 -1
@@ -124,7 +124,7 @@ static int i82860_process_error_info(str dimm->location[0 ], dimm->location[1 ],-1 , "i82860 UE", ""); else - edac_mc_handle_error(HW_EVENT_ERR_UNCORRECTED, mci, 1, + edac_mc_handle_error(HW_EVENT_ERR_CORRECTED, mci, 1, info->eap, 0, info->derrsyn, dimm->location[0], dimm->location[1], -1, "i82860 CE", "");
Greg Kroah-Hartman
maintainerPATCH 100/123 i3200_edac: Report CE events properly
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Baron <[email protected]>
commit 8a3f075d6c9b3612b4a5fb2af8db82b38b20caf0 upstream.
Fix CE event being reported as HW_EVENT_ERR_UNCORRECTED.
--- drivers/edac/i3200_edac.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/edac/i3200_edac.c +2 -2
@@ -242,11 +242,11 @@ static void i3200_process_error_info(str-1 ,-1 , "i3000 UE", ""); }else if (log &I3200_ECCERRLOG_CE ) { -edac_mc_handle_error (HW_EVENT_ERR_UNCORRECTED , mci,1 , +edac_mc_handle_error (HW_EVENT_ERR_CORRECTED , mci,1 ,0 ,0 ,eccerrlog_syndrome (log),eccerrlog_row (channel, log),-1 ,-1 , -"i3000 UE" ,"" ); +"i3000 CE" ,"" ); } } }
Greg Kroah-Hartman
maintainerPATCH 101/123 e7xxx_edac: Report CE events properly
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Baron <[email protected]>
commit 8030122a9ccf939186f8db96c318dbb99b5463f6 upstream.
Fix CE event being reported as HW_EVENT_ERR_UNCORRECTED.
--- drivers/edac/e7xxx_edac.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/edac/e7xxx_edac.c +1 -1
@@ -226,7 +226,7 @@ static void process_ce(struct mem_ctl_instatic void process_ce_no_info (struct mem_ctl_info *mci) {edac_dbg (3 ,"\n" ); -edac_mc_handle_error (HW_EVENT_ERR_UNCORRECTED , mci,1 ,0 ,0 ,0 ,-1 ,-1 ,-1 , +edac_mc_handle_error (HW_EVENT_ERR_CORRECTED , mci,1 ,0 ,0 ,0 ,-1 ,-1 ,-1 ,"e7xxx CE log register overflow" ,"" ); }
Greg Kroah-Hartman
maintainerPATCH 102/123 cpc925_edac: Report UE events properly
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Baron <[email protected]>
commit fa19ac4b92bc2b5024af3e868f41f81fa738567a upstream.
Fix UE event being reported as HW_EVENT_ERR_CORRECTED.
--- drivers/edac/cpc925_edac.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/edac/cpc925_edac.c +1 -1
@@ -562,7 +562,7 @@ static void cpc925_mc_check(struct mem_cif (apiexcp &UECC_EXCP_DETECTED ) {cpc925_mc_printk (mci,KERN_INFO ,"DRAM UECC Fault\n" ); -edac_mc_handle_error (HW_EVENT_ERR_CORRECTED , mci,1 , +edac_mc_handle_error (HW_EVENT_ERR_UNCORRECTED , mci,1 , pfn, offset,0 , csrow,-1 ,-1 , mci->ctl_name,"" );
Greg Kroah-Hartman
maintainerPATCH 103/123 nfsd4: fix crash on unknown operation number
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "J. Bruce Fields" <[email protected]>
commit 51904b08072a8bf2b9ed74d1bd7a5300a614471d upstream.
Unknown operation numbers are caught in nfsd4_decode_compound() which sets op->opnum to OP_ILLEGAL and op->status to nfserr_op_illegal. The error causes the main loop in nfsd4_proc_compound() to skip most processing. But nfsd4_proc_compound also peeks ahead at the next operation in one case and doesn't take similar precautions there.
--- fs/nfsd/nfs4proc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/nfsd/nfs4proc.c +2 -1
@@ -1191,7 +1191,8 @@ static bool need_wrongsec_check(struct s*/ if (argp->opcnt == resp->opcnt)return false; - +if (next->opnum ==OP_ILLEGAL ) +return false; nextd =OPDESC (next);/* * Rest of 2.6.3.1.1: certain operations will return WRONGSEC
Greg Kroah-Hartman
maintainerPATCH 104/123 ext3: Dont check quota format when there are no quota files
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 7938db449bbc55bbeb164bec7af406212e7e98f1 upstream.
The check whether quota format is set even though there are no quota files with journalled quota is pointless and it actually makes it impossible to turn off journalled quotas (as there's no way to unset journalled quota format). Just remove the check.
--- fs/ext3/super.c | 7 ------- 1 file changed, 7 deletions(-)
fs/ext3/super.c +0 -7
@@ -1300,13 +1300,6 @@ set_qf_format: "not specified."); return 0; } - }else { -if (sbi->s_jquota_fmt) { -ext3_msg (sb,KERN_ERR ,"error: journaled quota format " -"specified with no journaling " -"enabled." ); -return 0 ; - } }#endif return 1 ;
Greg Kroah-Hartman
maintainerPATCH 105/123 quota: Properly return errors from dquot_writeback_dquots()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 474d2605d119479e5aa050f738632e63589d4bb5 upstream.
Due to a switched left and right side of an assignment, dquot_writeback_dquots() never returned error. This could result in errors during quota writeback to not be reported to userspace properly. Fix it.
Coverity-id: 1226884
--- fs/quota/dquot.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/quota/dquot.c +1 -1
@@ -637,7 +637,7 @@ int dquot_writeback_dquots(struct super_dqstats_inc (DQST_LOOKUPS ); err = sb->dq_op->write_dquot (dquot);if (!ret && err) - err = ret; + ret = err;dqput (dquot);spin_lock (&dq_list_lock); }
Greg Kroah-Hartman
maintainerPATCH 106/123 tty: Fix high cpu load if tty is unreleaseable
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Hurley <[email protected]>
commit 37b164578826406a173ca7c20d9ba7430134d23e upstream.
Kernel oops can cause the tty to be unreleaseable (for example, if n_tty_read() crashes while on the read_wait queue). This will cause tty_release() to endlessly loop without sleeping.
Use a killable sleep timeout which grows by 2n+1 jiffies over the interval [0, 120 secs.) and then jumps to forever (but still killable).
NB: killable just allows for the task to be rewoken manually, not to be terminated.
--- drivers/tty/tty_io.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/tty/tty_io.c +6 -1
@@ -1698,6 +1698,7 @@ int tty_release(struct inode *inode, strint pty_master, tty_closing, o_tty_closing, do_sleep;int idx;char buf[64 ]; +long timeout =0 ;if (tty_paranoia_check (tty, inode, __func__))return 0 ;
@@ -1782,7 +1783,11 @@ int tty_release(struct inode *inode, str __func__, tty_name(tty, buf));tty_unlock_pair (tty, o_tty);mutex_unlock (&tty_mutex); -schedule (); +schedule_timeout_killable (timeout); +if (timeout <120 *HZ ) + timeout =2 * timeout +1 ; +else + timeout =MAX_SCHEDULE_TIMEOUT ; }/*
Greg Kroah-Hartman
maintainerPATCH 107/123 PM / Sleep: fix recovery during resuming from hibernation
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Imre Deak <[email protected]>
commit 94fb823fcb4892614f57e59601bb9d4920f24711 upstream.
If a device's dev_pm_ops::freeze callback fails during the QUIESCE phase, we don't rollback things correctly calling the thaw and complete callbacks. This could leave some devices in a suspended state in case of an error during resuming from hibernation.
--- kernel/power/hibernate.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
kernel/power/hibernate.c +7 -1
@@ -491,8 +491,14 @@ int hibernation_restore(int platform_mod error =dpm_suspend_start (PMSG_QUIESCE );if (!error) { error =resume_target_kernel (platform_mode); -dpm_resume_end (PMSG_RECOVER ); +/* +* The above should either succeed and jump to the new kernel, +* or return with an error. Otherwise things are just +* undefined, so let's be paranoid. +*/ +BUG_ON (!error); } +dpm_resume_end (PMSG_RECOVER );pm_restore_gfp_mask ();ftrace_start ();resume_console ();
Greg Kroah-Hartman
maintainerPATCH 108/123 mac80211: fix typo in starting baserate for rts_cts_rate_idx
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Karl Beldan <[email protected]>
commit c7abf25af0f41be4b50d44c5b185d52eea360cb8 upstream.
It affects non-(V)HT rates and can lead to selecting an rts_cts rate that is not a basic rate or way superior to the reference rate (ATM rates[0] used for the 1st attempt of the protected frame data).
E.g, assuming drivers register growing (bitrate) sorted tables of ieee80211_rate-s, having :
- rates[0].idx == d'2 and basic_rates == b'10100
will select rts_cts idx b'10011 & ~d'(BIT(2)-1), i.e. 1, likewise
- rates[0].idx == d'2 and basic_rates == b'10001
will select rts_cts idx b'10000
The first is not a basic rate and the second is > rates[0].
Also, wrt severity of the addressed misbehavior, ATM we only have one rts_cts_rate_idx rather than one per rate table entry, so this idx might still point to bitrates > rates[1..MAX_RATES].
--- net/mac80211/rate.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/mac80211/rate.c +1 -1
@@ -448,7 +448,7 @@ static void rate_fixup_ratelist(struct i*/ if (!(rates[0 ].flags &IEEE80211_TX_RC_MCS )) {u32 basic_rates = vif->bss_conf.basic_rates; -s8 baserate = basic_rates ?ffs (basic_rates -1 ) :0 ; +s8 baserate = basic_rates ?ffs (basic_rates) -1 :0 ; rate = &sband->bitrates[rates[0 ].idx];
Greg Kroah-Hartman
maintainerPATCH 109/123 posix-timers: Fix stack info leak in timer_create()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mathias Krause <[email protected]>
commit 6891c4509c792209c44ced55a60f13954cb50ef4 upstream.
If userland creates a timer without specifying a sigevent info, we'll create one ourself, using a stack local variable. Particularly will we use the timer ID as sival_int. But as sigev_value is a union containing a pointer and an int, that assignment will only partially initialize sigev_value on systems where the size of a pointer is bigger than the size of an int. On such systems we'll copy the uninitialized stack bytes from the timer_create() call to userland when the timer actually fires and we're going to deliver the signal.
Initialize sigev_value with 0 to plug the stack info leak.
Found in the PaX patch, written by the PaX Team.
--- kernel/posix-timers.c | 1 + 1 file changed, 1 insertion(+)
kernel/posix-timers.c +1 -0
@@ -634,6 +634,7 @@ SYSCALL_DEFINE3(timer_create, const cloc goto out; } }else { +memset (&event.sigev_value,0 ,sizeof (event.sigev_value)); event.sigev_notify =SIGEV_SIGNAL ; event.sigev_signo =SIGALRM ; event.sigev_value.sival_int = new_timer->it_id;
Greg Kroah-Hartman
maintainerPATCH 110/123 x86, apic: Handle a bad TSC more gracefully
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Lutomirski <[email protected]>
commit b47dcbdc5161d3d5756f430191e2840d9b855492 upstream.
If the TSC is unusable or disabled, then this patch fixes:
- Confusion while trying to clear old APIC interrupts.
- Division by zero and incorrect programming of the TSC deadline timer.
This fixes boot if the CPU has a TSC deadline timer but a missing or broken TSC. The failure to boot can be observed with qemu using -cpu qemu64,-tsc,+tsc-deadline
This also happens to me in nested KVM for unknown reasons. With this patch, I can boot cleanly (although without a TSC).
--- arch/x86/kernel/apic/apic.c | 4 ++-- arch/x86/kernel/tsc.c | 5 ++++- 2 files changed, 6 insertions(+), 3 deletions(-)
arch/x86/kernel/apic/apic.c +2 -2
@@ -1263,7 +1263,7 @@ void __cpuinit setup_local_APIC(void)unsigned int value, queued;int i, j, acked =0 ;unsigned long long tsc =0 , ntsc; -long long max_loops = cpu_khz; +long long max_loops = cpu_khz ? cpu_khz :1000000 ;if (cpu_has_tsc)rdtscll (tsc);
@@ -1360,7 +1360,7 @@ void __cpuinit setup_local_APIC(void)break ; }if (queued) { -if (cpu_has_tsc) { +if (cpu_has_tsc && cpu_khz) {rdtscll (ntsc); max_loops = (cpu_khz <<10 ) - (ntsc - tsc); }else
arch/x86/kernel/tsc.c +4 -1
@@ -968,14 +968,17 @@ void __init tsc_init(void) x86_init.timers.tsc_pre_init (); -if (!cpu_has_tsc) +if (!cpu_has_tsc) { +setup_clear_cpu_cap (X86_FEATURE_TSC_DEADLINE_TIMER );return ; + } tsc_khz = x86_platform.calibrate_tsc (); cpu_khz = tsc_khz;if (!tsc_khz) {mark_tsc_unstable ("could not calculate TSC khz" ); +setup_clear_cpu_cap (X86_FEATURE_TSC_DEADLINE_TIMER );return ; }
Greg Kroah-Hartman
maintainerPATCH 111/123 mm: Remove false WARN_ON from pagecache_isize_extended()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit f55fefd1a5a339b1bd08c120b93312d6eb64a9fb upstream.
The WARN_ON checking whether i_mutex is held in pagecache_isize_extended() was wrong because some filesystems (e.g. XFS) use different locks for serialization of truncates / writes. So just remove the check.
--- mm/truncate.c | 1 - 1 file changed, 1 deletion(-)
mm/truncate.c +0 -1
@@ -603,7 +603,6 @@ void pagecache_isize_extended(struct inostruct page *page;pgoff_t index; -WARN_ON (!mutex_is_locked (&inode->i_mutex));WARN_ON (to > inode->i_size);if (from >= to || bsize ==PAGE_CACHE_SIZE )
Greg Kroah-Hartman
maintainerPATCH 112/123 crypto: algif - avoid excessive use of socket buffer in skcipher
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ondrej Kozina <[email protected]>
commit e2cffb5f493a8b431dc87124388ea59b79f0bccb upstream.
On archs with PAGE_SIZE >= 64 KiB the function skcipher_alloc_sgl() fails with -ENOMEM no matter what user space actually requested. This is caused by the fact sock_kmalloc call inside the function tried to allocate more memory than allowed by the default kernel socket buffer size (kernel param net.core.optmem_max).
--- crypto/algif_skcipher.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
crypto/algif_skcipher.c +1 -1
@@ -49,7 +49,7 @@ struct skcipher_ctx {struct ablkcipher_request req; }; -#define MAX_SGL_ENTS ((PAGE_SIZE - sizeof(struct skcipher_sg_list)) / \ +#define MAX_SGL_ENTS ((4096 - sizeof(struct skcipher_sg_list)) / \ sizeof(struct scatterlist) - 1)static inline int skcipher_sndbuf (struct sock *sk)
Greg Kroah-Hartman
maintainerPATCH 113/123 usb: dwc3: gadget: fix set_halt() bug with pending transfers
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felipe Balbi <[email protected]>
[ Upstream commit 7a60855972f0d3c014093046cb6f013a1ee5bb19 ]
According to our Gadget Framework API documentation, ->set_halt() *must* return -EAGAIN if we have pending transfers (on either direction) or FIFO isn't empty (on TX endpoints).
Fix this bug so that the mass storage gadget can be used without stall=0 parameter.
This patch should be backported to all kernels since v3.2.
--- drivers/usb/dwc3/ep0.c | 4 ++-- drivers/usb/dwc3/gadget.c | 16 ++++++++++++---- drivers/usb/dwc3/gadget.h | 2 +- 3 files changed, 15 insertions(+), 7 deletions(-)
drivers/usb/dwc3/ep0.c +2 -2
@@ -270,7 +270,7 @@ static void dwc3_ep0_stall_and_restart(s/* stall is always issued on EP0 */ dep = dwc->eps[0 ]; -__dwc3_gadget_ep_set_halt (dep,1 ); +__dwc3_gadget_ep_set_halt (dep,1 , false); dep->flags =DWC3_EP_ENABLED ; dwc->delayed_status = false;
@@ -480,7 +480,7 @@ static int dwc3_ep0_handle_feature(strucreturn -EINVAL ;if (set ==0 && (dep->flags &DWC3_EP_WEDGE ))break ; - ret =__dwc3_gadget_ep_set_halt (dep, set); + ret =__dwc3_gadget_ep_set_halt (dep, set, true);if (ret)return -EINVAL ;break ;
drivers/usb/dwc3/gadget.c +12 -4
@@ -605,7 +605,7 @@ static int __dwc3_gadget_ep_disable(stru/* make sure HW endpoint isn't stalled */ if (dep->flags &DWC3_EP_STALL ) -__dwc3_gadget_ep_set_halt (dep,0 ); +__dwc3_gadget_ep_set_halt (dep,0 , false); reg =dwc3_readl (dwc->regs,DWC3_DALEPENA ); reg &= ~DWC3_DALEPENA_EP (dep->number);
@@ -1205,7 +1205,7 @@ out0:return ret; } -int __dwc3_gadget_ep_set_halt (struct dwc3_ep *dep,int value) +int __dwc3_gadget_ep_set_halt (struct dwc3_ep *dep,int value,int protocol) {struct dwc3_gadget_ep_cmd_params params;struct dwc3 *dwc = dep->dwc;
@@ -1214,6 +1214,14 @@ int __dwc3_gadget_ep_set_halt(struct dwcmemset (¶ms,0x00 ,sizeof (params));if (value) { +if (!protocol && ((dep->direction && dep->flags &DWC3_EP_BUSY ) || + (!list_empty (&dep->req_queued) || + !list_empty (&dep->request_list)))) { +dev_dbg (dwc->dev,"%s: pending request, cannot halt\n" , + dep->name); +return -EAGAIN ; + } + ret =dwc3_send_gadget_ep_cmd (dwc, dep->number,DWC3_DEPCMD_SETSTALL , ¶ms);if (ret)
@@ -1253,7 +1261,7 @@ static int dwc3_gadget_ep_set_halt(struc goto out; } - ret =__dwc3_gadget_ep_set_halt (dep, value); + ret =__dwc3_gadget_ep_set_halt (dep, value, false); out:spin_unlock_irqrestore (&dwc->lock, flags);
@@ -1273,7 +1281,7 @@ static int dwc3_gadget_ep_set_wedge(struif (dep->number ==0 || dep->number ==1 )return dwc3_gadget_ep0_set_halt (ep,1 );else -return dwc3_gadget_ep_set_halt (ep,1 ); +return __dwc3_gadget_ep_set_halt (dep,1 , false); }/* -------------------------------------------------------------------------- */
drivers/usb/dwc3/gadget.h +1 -1
@@ -114,7 +114,7 @@ void dwc3_ep0_out_start(struct dwc3 *dwcint dwc3_gadget_ep0_set_halt (struct usb_ep *ep,int value);int dwc3_gadget_ep0_queue (struct usb_ep *ep,struct usb_request *request,gfp_t gfp_flags); -int __dwc3_gadget_ep_set_halt (struct dwc3_ep *dep,int value); +int __dwc3_gadget_ep_set_halt (struct dwc3_ep *dep,int value,int protocol);int dwc3_send_gadget_ep_cmd (struct dwc3 *dwc,unsigned ep,unsigned cmd,struct dwc3_gadget_ep_cmd_params *params);int dwc3_send_gadget_generic_command (struct dwc3 *dwc,int cmd,u32 param);
Greg Kroah-Hartman
maintainerPATCH 114/123 usb: gadget: function: acm: make f_acm pass USB20CV Chapter9
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felipe Balbi <[email protected]>
[ Upstream commit 52ec49a5e56a27c5b6f8217708783eff39f24c16 ]
During Halt Endpoint Test, our interrupt endpoint will be disabled, which will clear out ep->desc to NULL. Unless we call config_ep_by_speed() again, we will not be able to enable this endpoint which will make us fail that test.
inside the struct usb_ep on disable)
--- drivers/usb/gadget/f_acm.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/usb/gadget/f_acm.c +4 -3
@@ -430,11 +430,12 @@ static int acm_set_alt(struct usb_functiif (acm->notify->driver_data) {VDBG (cdev,"reset acm control interface %d\n" , intf);usb_ep_disable (acm->notify); - }else { -VDBG (cdev,"init acm ctrl interface %d\n" , intf); + } + +if (!acm->notify->desc)if (config_ep_by_speed (cdev->gadget, f, acm->notify))return -EINVAL ; - } +usb_ep_enable (acm->notify); acm->notify->driver_data = acm;
Greg Kroah-Hartman
maintainerPATCH 115/123 usb: gadget: udc: core: fix kernel oops with soft-connect
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felipe Balbi <[email protected]>
[ Upstream commit bfa6b18c680450c17512c741ed1d818695747621 ]
Currently, there's no guarantee that udc->driver will be valid when using soft_connect sysfs interface. In fact, we can very easily trigger a NULL pointer dereference by trying to disconnect when a gadget driver isn't loaded.
Fix this bug:
~# echo disconnect > soft_connect
[ 33.685743] Unable to handle kernel NULL pointer dereference at virtual address 00000014 [ 33.694221] pgd = ed0cc000 [ 33.697174] [00000014] *pgd=ae351831, *pte=00000000, *ppte=00000000 [ 33.703766] Internal error: Oops: 17 [#1] SMP ARM [ 33.708697] Modules linked in: xhci_plat_hcd xhci_hcd snd_soc_davinci_mcasp snd_soc_tlv320aic3x snd_soc_edma snd_soc_omap snd_soc_evm snd_soc_core dwc3 snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd lis3lv02d_i2c matrix_keypad lis3lv02d dwc3_omap input_polldev soundcore [ 33.734372] CPU: 0 PID: 1457 Comm: bash Not tainted 3.17.0-09740-ga93416e-dirty #345 [ 33.742457] task: ee71ce00 ti: ee68a000 task.ti: ee68a000 [ 33.748116] PC is at usb_udc_softconn_store+0xa4/0xec [ 33.753416] LR is at mark_held_locks+0x78/0x90 [ 33.758057] pc : [<c04df128>] lr : [<c00896a4>] psr: 20000013 [ 33.758057] sp : ee68bec8 ip : c0c00008 fp : ee68bee4 [ 33.770050] r10: ee6b394c r9 : ee68bf80 r8 : ee6062c0 [ 33.775508] r7 : 00000000 r6 : ee6062c0 r5 : 0000000b r4 : ee739408 [ 33.782346] r3 : 00000000 r2 : 00000000 r1 : ee71d390 r0 : ee664170 [ 33.789168] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 33.796636] Control: 10c5387d Table: ad0cc059 DAC: 00000015 [ 33.802638] Process bash (pid: 1457, stack limit = 0xee68a248) [ 33.808740] Stack: (0xee68bec8 to 0xee68c000) [ 33.813299] bec0: 0000000b c0411284 ee6062c0 00000000 ee68bef4 ee68bee8 [ 33.821862] bee0: c04112ac c04df090 ee68bf14 ee68bef8 c01c2868 c0411290 0000000b ee6b3940 [ 33.830419] bf00: 00000000 00000000 ee68bf4c ee68bf18 c01c1a24 c01c2818 00000000 00000000 [ 33.838990] bf20: ee61b940 ee2f47c0 0000000b 000ce408 ee68bf80 c000f304 ee68a000 00000000 [ 33.847544] bf40: ee68bf7c ee68bf50 c0152dd8 c01c1960 ee68bf7c c0170af8 ee68bf7c ee2f47c0 [ 33.856099] bf60: ee2f47c0 000ce408 0000000b c000f304 ee68bfa4 ee68bf80 c0153330 c0152d34 [ 33.864653] bf80: 00000000 00000000 0000000b 000ce408 b6e7fb50 00000004 00000000 ee68bfa8 [ 33.873204] bfa0: c000f080 c01532e8 0000000b 000ce408 00000001 000ce408 0000000b 00000000 [ 33.881763] bfc0: 0000000b 000ce408 b6e7fb50 00000004 0000000b 00000000 000c5758 00000000 [ 33.890319] bfe0: 00000000 bec2c924 b6de422d b6e1d226 40000030 00000001 75716d2f 00657565 [ 33.898890] [<c04df128>] (usb_udc_softconn_store) from [<c04112ac>] (dev_attr_store+0x28/0x34) [ 33.907920] [<c04112ac>] (dev_attr_store) from [<c01c2868>] (sysfs_kf_write+0x5c/0x60) [ 33.916200] [<c01c2868>] (sysfs_kf_write) from [<c01c1a24>] (kernfs_fop_write+0xd0/0x194) [ 33.924773] [<c01c1a24>] (kernfs_fop_write) from [<c0152dd8>] (vfs_write+0xb0/0x1bc) [ 33.932874] [<c0152dd8>] (vfs_write) from [<c0153330>] (SyS_write+0x54/0xb0) [ 33.940247] [<c0153330>] (SyS_write) from [<c000f080>] (ret_fast_syscall+0x0/0x48) [ 33.948160] Code: e1a01007 e12fff33 e5140004 e5143008 (e5933014) [ 33.954625] ---[ end trace f849bead94eab7ea ]---
--- drivers/usb/gadget/udc-core.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/usb/gadget/udc-core.c +5 -0
@@ -439,6 +439,11 @@ static ssize_t usb_udc_softconn_store(st { struct usb_udc *udc = container_of(dev, struct usb_udc, dev); +if (!udc->driver) { +dev_err (dev,"soft-connect without a gadget driver\n" ); +return -EOPNOTSUPP ; + } +if (sysfs_streq (buf,"connect" )) {usb_gadget_udc_start (udc->gadget, udc->driver);usb_gadget_connect (udc->gadget);
Greg Kroah-Hartman
maintainerPATCH 116/123 drm/radeon: remove invalid pci id
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 8c3e434769b1707fd2d24de5a2eb25fedc634c4a upstream.
0x4c6e is a secondary device id so should not be used by the driver.
--- include/drm/drm_pciids.h | 1 - 1 file changed, 1 deletion(-)
include/drm/drm_pciids.h +0 -1
@@ -52,7 +52,6 @@ {0x1002, 0x4C64, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250|RADEON_IS_MOBILITY}, \ {0x1002, 0x4C66, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250|RADEON_IS_MOBILITY}, \ {0x1002, 0x4C67, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250|RADEON_IS_MOBILITY}, \ - {0x1002, 0x4C6E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280|RADEON_IS_MOBILITY}, \ {0x1002, 0x4E44, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \ {0x1002, 0x4E45, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \ {0x1002, 0x4E46, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
Greg Kroah-Hartman
maintainerPATCH 117/123 rbd: Fix error recovery in rbd_obj_read_sync()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit a8d4205623ae965e36c68629db306ca0695a2771 upstream.
When we fail to allocate page vector in rbd_obj_read_sync() we just basically ignore the problem and continue which will result in an oops later. Fix the problem by returning proper error.
CC: Yehuda Sadeh <[email protected]>
CC: Sage Weil <[email protected]>
CC: [email protected]
Coverity-id: 1226882
--- drivers/block/rbd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/block/rbd.c +1 -1
@@ -3227,7 +3227,7 @@ static int rbd_obj_read_sync(struct rbd_ page_count = (u32 )calc_pages_for (offset, length); pages =ceph_alloc_page_vector (page_count,GFP_KERNEL );if (IS_ERR (pages)) - ret =PTR_ERR (pages); +return PTR_ERR (pages); ret = -ENOMEM ; obj_request = rbd_obj_request_create(object_name, offset, length,
Greg Kroah-Hartman
maintainerPATCH 118/123 acer-wmi: Add acpi_backlight=video quirk for the Acer KAV80
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit 183fd8fcd7f8afb7ac5ec68f83194872f9fecc84 upstream.
The acpi-video backlight interface on the Acer KAV80 is broken, and worse it causes the entire machine to slow down significantly after a suspend/resume.
Blacklist it, and use the acer-wmi backlight interface instead. Note that the KAV80 is somewhat unique in that it is the only Acer model where we fall back to acer-wmi after blacklisting, rather then using the native (e.g. intel) backlight driver. This is done because there is no native backlight interface on this model.
--- drivers/platform/x86/acer-wmi.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/platform/x86/acer-wmi.c +11 -0
@@ -572,6 +572,17 @@ static const struct dmi_system_id video_ DMI_MATCH(DMI_PRODUCT_NAME, "Aspire 5750"), }, }, + { + /* + * Note no video_set_backlight_video_vendor, we must use the + * acer interface, as there is no native backlight interface. + */ + .ident = "Acer KAV80", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "Acer"), + DMI_MATCH(DMI_PRODUCT_NAME, "KAV80"), + }, + }, {} };
Greg Kroah-Hartman
maintainerPATCH 119/123 i2c: at91: dont account as iowait
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wolfram Sang <[email protected]>
commit 11cfbfb098b22d3e57f1f2be217cad20e2d48463 upstream.
iowait is for blkio [1]. I2C shouldn't use it.
[1] https://lkml.org/lkml/2014/11/3/317
--- drivers/i2c/busses/i2c-at91.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-at91.c +1 -1
@@ -435,7 +435,7 @@ static int at91_do_twi_transfer(struct a } } - ret =wait_for_completion_io_timeout (&dev->cmd_complete, + ret =wait_for_completion_timeout (&dev->cmd_complete, dev->adapter.timeout);if (ret ==0 ) {dev_err (dev->dev,"controller timed out\n" );
Greg Kroah-Hartman
maintainerPATCH 120/123 sysfs: driver core: Fix glue dir race condition by gdp_mutex
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yijing Wang <[email protected]>
commit e4a60d139060975eb956717e4f63ae348d4d8cc5 upstream.
There is a race condition when removing glue directory. It can be reproduced in following test:
path 1: Add first child devicedevice_add()
get_device_parent()
/*find parent from glue_dirs.list*/
list_for_each_entry(k, &dev->class->p->glue_dirs.list, entry)
if (k->parent == parent_kobj) {
kobj = kobject_get(k);
break;
}
....
class_dir_create_and_add()path2: Remove last child device under glue dir device_del()
cleanup_device_parent()
cleanup_glue_dir()
kobject_put(glue_dir);If path2 has been called cleanup_glue_dir(), but not call kobject_put(glue_dir), the glue dir is still in parent's kset list. Meanwhile, path1 find the glue dir from the glue_dirs.list. Path2 may release glue dir before path1 call kobject_get(). So kernel will report the warning and bug_on.
This is a "classic" problem we have of a kref in a list that can be found while the last instance could be removed at the same time.
This patch reuse gdp_mutex to fix this race condition.
The following calltrace is captured in kernel 3.4, but the latest kernel still has this bug.
-----------------------------------------------------
<4>[ 3965.441471] WARNING: at ...include/linux/kref.h:41 kobject_get+0x33/0x40() <4>[ 3965.441474] Hardware name: Romley <4>[ 3965.441475] Modules linked in: isd_iop(O) isd_xda(O)... ... <4>[ 3965.441605] Call Trace: <4>[ 3965.441611] [<ffffffff8103717a>] warn_slowpath_common+0x7a/0xb0 <4>[ 3965.441615] [<ffffffff810371c5>] warn_slowpath_null+0x15/0x20 <4>[ 3965.441618] [<ffffffff81215963>] kobject_get+0x33/0x40 <4>[ 3965.441624] [<ffffffff812d1e45>] get_device_parent.isra.11+0x135/0x1f0 <4>[ 3965.441627] [<ffffffff812d22d4>] device_add+0xd4/0x6d0 <4>[ 3965.441631] [<ffffffff812d0dbc>] ? dev_set_name+0x3c/0x40 .... <2>[ 3965.441912] kernel BUG at ..../fs/sysfs/group.c:65! <4>[ 3965.441915] invalid opcode: 0000 [#1] SMP ... <4>[ 3965.686743] [<ffffffff811a677e>] sysfs_create_group+0xe/0x10 <4>[ 3965.686748] [<ffffffff810cfb04>] blk_trace_init_sysfs+0x14/0x20 <4>[ 3965.686753] [<ffffffff811fcabb>] blk_register_queue+0x3b/0x120 <4>[ 3965.686756] [<ffffffff812030bc>] add_disk+0x1cc/0x490
....
-------------------------------------------------------
--- drivers/base/core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/base/core.c +3 -1
@@ -765,12 +765,12 @@ class_dir_create_and_add(struct class *creturn &dir->kobj; } +static DEFINE_MUTEX (gdp_mutex);static struct kobject *get_device_parent (struct device *dev,struct device *parent) {if (dev->class) { -static DEFINE_MUTEX (gdp_mutex);struct kobject *kobj =NULL ;struct kobject *parent_kobj;struct kobject *k;
@@ -834,7 +834,9 @@ static void cleanup_glue_dir(struct devi glue_dir->kset != &dev->class->p->glue_dirs) return; +mutex_lock (&gdp_mutex);kobject_put (glue_dir); +mutex_unlock (&gdp_mutex); }static void cleanup_device_parent (struct device *dev)
Greg Kroah-Hartman
maintainerPATCH 121/123 of: Fix overflow bug in string property parsing functions
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Grant Likely <[email protected]>
commit a87fa1d81a9fb5e9adca9820e16008c40ad09f33 upstream.
The string property read helpers will run off the end of the buffer if it is handed a malformed string property. Rework the parsers to make sure that doesn't happen. At the same time add new test cases to make sure the functions behave themselves.
The original implementations of of_property_read_string_index() and of_property_count_strings() both open-coded the same block of parsing code, each with it's own subtly different bugs. The fix here merges functions into a single helper and makes the original functions static inline wrappers around the helper.
One non-bugfix aspect of this patch is the addition of a new wrapper, of_property_read_string_array(). The new wrapper is needed by the device_properties feature that Rafael is working on and planning to merge for v3.19. The implementation is identical both with and without the new static inline wrapper, so it just got left in to reduce the churn on the header file.
--- drivers/of/base.c | 88 ++++++++++++-------------------------------------- drivers/of/selftest.c | 64 +++++++++++++++++++++++++++++++++--- include/linux/of.h | 84 +++++++++++++++++++++++++++++++++++++++-------- 3 files changed, 151 insertions(+), 85 deletions(-)
drivers/of/base.c +22 -66
@@ -963,52 +963,6 @@ int of_property_read_string(struct devicEXPORT_SYMBOL_GPL (of_property_read_string);/** -* of_property_read_string_index - Find and read a string from a multiple -* strings property. -* @np: device node from which the property value is to be read. -* @propname: name of the property to be searched. -* @index: index of the string in the list of strings -* @out_string: pointer to null terminated return string, modified only if -* return value is 0. -* -* Search for a property in a device tree node and retrieve a null -* terminated string value (pointer to data, not a copy) in the list of strings -* contained in that property. -* Returns 0 on success, -EINVAL if the property does not exist, -ENODATA if -* property does not have a value, and -EILSEQ if the string is not -* null-terminated within the length of the property data. -* -* The out_string pointer is modified only if a valid string can be decoded. -*/ -int of_property_read_string_index (struct device_node *np,const char *propname, -int index,const char **output) -{ -struct property *prop =of_find_property (np, propname,NULL ); -int i =0 ; -size_t l =0 , total =0 ; -const char *p; - -if (!prop) -return -EINVAL ; -if (!prop->value) -return -ENODATA ; -if (strnlen (prop->value, prop->length) >= prop->length) -return -EILSEQ ; - - p = prop->value; - -for (i =0 ; total < prop->length; total += l, p += l) { - l =strlen (p) +1 ; -if (i++ == index) { - *output = p; -return 0 ; - } - } -return -ENODATA ; -} -EXPORT_SYMBOL_GPL (of_property_read_string_index); - -/** * of_property_match_string() - Find string in a list and return index * @np: pointer to node containing string list property * @propname: string list property name
@@ -1034,7 +988,7 @@ int of_property_match_string(struct devi end = p + prop->length;for (i =0 ; p < end; i++, p += l) { - l =strlen (p) +1 ; + l =strnlen (p, end - p) +1 ;if (p + l > end)return -EILSEQ ;pr_debug ("comparing %s with %s\n" , string, p);
@@ -1046,39 +1000,41 @@ int of_property_match_string(struct deviEXPORT_SYMBOL_GPL (of_property_match_string);/** -* of_property_count_strings - Find and return the number of strings from a -* multiple strings property. +* of_property_read_string_util() - Utility helper for parsing string properties * @np: device node from which the property value is to be read. * @propname: name of the property to be searched. +* @out_strs: output array of string pointers. +* @sz: number of array elements to read. +* @skip: Number of strings to skip over at beginning of list. * -* Search for a property in a device tree node and retrieve the number of null -* terminated string contain in it. Returns the number of strings on -* success, -EINVAL if the property does not exist, -ENODATA if property -* does not have a value, and -EILSEQ if the string is not null-terminated -* within the length of the property data. +* Don't call this function directly. It is a utility helper for the +* of_property_read_string*() family of functions. */ -int of_property_count_strings (struct device_node *np,const char *propname) +int of_property_read_string_helper (struct device_node *np,const char *propname, +const char **out_strs,size_t sz,int skip) {struct property *prop =of_find_property (np, propname,NULL ); -int i =0 ; -size_t l =0 , total =0 ; -const char *p; +int l =0 , i =0 ; +const char *p, *end;if (!prop)return -EINVAL ;if (!prop->value)return -ENODATA ; -if (strnlen (prop->value, prop->length) >= prop->length) -return -EILSEQ ; - p = prop->value; + end = p + prop->length; -for (i =0 ; total < prop->length; total += l, p += l, i++) - l =strlen (p) +1 ; - -return i; +for (i =0 ; p < end && (!out_strs || i < skip + sz); i++, p += l) { + l =strnlen (p, end - p) +1 ; +if (p + l > end) +return -EILSEQ ; +if (out_strs && i >= skip) + *out_strs++ = p; + } + i -= skip; +return i <=0 ? -ENODATA : i; } -EXPORT_SYMBOL_GPL (of_property_count_strings); +EXPORT_SYMBOL_GPL (of_property_read_string_helper);/** * of_parse_phandle - Resolve a phandle property to a device_node pointer
drivers/of/selftest.c +59 -5
80 lines not on this page · raw message
include/linux/of.h +70 -14
105 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 122/123 Btrfs: fix kfree on list_head in btrfs_lookup_csums_range error cleanup
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chris Mason <[email protected]>
commit 6e5aafb27419f32575b27ef9d6a31e5d54661aca upstream.
If we hit any errors in btrfs_lookup_csums_range, we'll loop through all the csums we allocate and free them. But the code was using list_entry incorrectly, and ended up trying to free the on-stack list_head instead.
This bug came from commit 0678b6185
btrfs: Don't BUG_ON kzalloc error in btrfs_lookup_csums_range()
--- fs/btrfs/file-item.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/btrfs/file-item.c +1 -1
@@ -403,7 +403,7 @@ int btrfs_lookup_csums_range(struct btrf ret =0 ; fail:while (ret <0 && !list_empty (&tmplist)) { - sums = list_entry(&tmplist, struct btrfs_ordered_sum, list); + sums = list_entry(tmplist.next, struct btrfs_ordered_sum, list);list_del (&sums->list);kfree (sums); }
Greg Kroah-Hartman
maintainerPATCH 123/123 libceph: ceph-msgr workqueue needs a resque worker
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ilya Dryomov <[email protected]>
commit f9865f06f7f18c6661c88d0511f05c48612319cc upstream.
Commit f363e45fd118 ("net/ceph: make ceph_msgr_wq non-reentrant") effectively removed WQ_MEM_RECLAIM flag from ceph_msgr_wq. This is wrong - libceph is very much a memory reclaim path, so restore it.
--- net/ceph/messenger.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/ceph/messenger.c +2 -1
@@ -290,7 +290,8 @@ int ceph_msgr_init(void)if (ceph_msgr_slab_init ())return -ENOMEM ; - ceph_msgr_wq =alloc_workqueue ("ceph-msgr" ,WQ_NON_REENTRANT ,0 ); + ceph_msgr_wq =alloc_workqueue ("ceph-msgr" , +WQ_NON_REENTRANT |WQ_MEM_RECLAIM ,0 );if (ceph_msgr_wq)return 0 ;
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
As an early heads up, I see some builds failing in 3.10 and 3.14 with
drivers/of/selftest.c: In function 'of_selftest':drivers/of/selftest.c:224:2: error: implicit declaration of function 'of_selftest_property_match_string' [-Werror=implicit-function-declaration]
of_selftest_property_match_string();
^drivers/of/selftest.c: At top level:drivers/of/selftest.c:129:20: warning: 'of_selftest_property_string' defined but not used [-Wunused-function]
static void __init of_selftest_property_string(void)
^
Not surprising, since commit 'of: Fix overflow bug in string property parsing functions' replaces the now missing function with the defined but unused function, apparently without changing the caller. Oddly enough, the referenced upstream commit _does_ replace the function name for both caller and callee.
Guenter
Greg Kroah-Hartman
maintainerQuoted 19 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
As an early heads up, I see some builds failing in 3.10 and 3.14 with
drivers/of/selftest.c: In function 'of_selftest':drivers/of/selftest.c:224:2: error: implicit declaration of function 'of_selftest_property_match_string' [-Werror=implicit-function-declaration]
of_selftest_property_match_string();
^drivers/of/selftest.c: At top level:drivers/of/selftest.c:129:20: warning: 'of_selftest_property_string' defined but not used [-Wunused-function]
static void__initof_selftest_property_string(void)
Quoted 7 lines
^Not surprising, since commit 'of: Fix overflow bug in string property parsing functions' replaces the now missing function with the defined but unused function, apparently without changing the caller. Oddly enough, the referenced upstream commit _does_ replace the function name for both caller and callee.
Crap, I took the "ignore the rejects" too literally when applying that patch, let me go rework it and see if I can fix it up.
thanks for letting me know.
greg k-h
Greg Kroah-Hartman
maintainerQuoted 22 lines · Greg Kroah-Hartman
Quoted 21 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
As an early heads up, I see some builds failing in 3.10 and 3.14 with
drivers/of/selftest.c: In function 'of_selftest':drivers/of/selftest.c:224:2: error: implicit declaration of function 'of_selftest_property_match_string' [-Werror=implicit-function-declaration]
of_selftest_property_match_string();
^drivers/of/selftest.c: At top level:drivers/of/selftest.c:129:20: warning: 'of_selftest_property_string' defined but not used [-Wunused-function]
static void__initof_selftest_property_string(void)^
Quoted 8 lines
Quoted 5 lines
Not surprising, since commit 'of: Fix overflow bug in string property parsing functions' replaces the now missing function with the defined but unused function, apparently without changing the caller. Oddly enough, the referenced upstream commit _does_ replace the function name for both caller and callee.
Crap, I took the "ignore the rejects" too literally when applying that patch, let me go rework it and see if I can fix it up.
And I've fixed it now. I doubt it's worth rolling a new -rc release for this, given the low number of builds that are failing.
thanks,
greg k-h
Quoted 29 lines · Greg Kroah-Hartman
Quoted 28 lines · Greg Kroah-Hartman
Quoted 26 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
As an early heads up, I see some builds failing in 3.10 and 3.14 with
drivers/of/selftest.c: In function 'of_selftest':drivers/of/selftest.c:224:2: error: implicit declaration of function 'of_selftest_property_match_string' [-Werror=implicit-function-declaration]
of_selftest_property_match_string();
^drivers/of/selftest.c: At top level:drivers/of/selftest.c:129:20: warning: 'of_selftest_property_string' defined but not used [-Wunused-function]
static void__initof_selftest_property_string(void)^Not surprising, since commit 'of: Fix overflow bug in string property parsing functions' replaces the now missing function with the defined but unused function, apparently without changing the caller. Oddly enough, the referenced upstream commit _does_ replace the function name for both caller and callee.
Quoted 6 lines
Quoted 2 lines
Crap, I took the "ignore the rejects" too literally when applying that patch, let me go rework it and see if I can fix it up.
And I've fixed it now. I doubt it's worth rolling a new -rc release for this, given the low number of builds that are failing.
Confirmed to be fixed.
Thanks,
Guenter
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
Build results:
total: 137 pass: 133 fail: 4
Failed builds:
powerpc:allmodconfig (binutils 2.23)
powerpc:allmodconfig (binutils 2.24)
sparc64:allmodconfig
xtensa:allmodconfig
Qemu tests:
total: 27 pass: 27 fail: 0
Same build failures as with 3.14.
Details are available at http://server.roeck-us.net:8010/builders.
Guenter
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
Quoted 8 lines
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.60-rc1.gzand the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
-- Shuah
Signature · 4 lines
Shuah Khan Sr. Linux Kernel Developer Samsung Research America (Silicon Valley) [email protected] | (970) 217-8978
Greg Kroah-Hartman
maintainerQuoted 13 lines · Shuah Khan
Quoted 12 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.60 release. There are 123 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 Nov 14 01:17:00 UTC 2014. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.60-rc1.gzand the diffstat can be found below.
Quoted 6 lines
Quoted 4 lines
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
Thanks for testing all 3 of these and letting me know.
greg k-h