3.2.93-rc1 review
Subsystems (2)
cover 3.2.93-rc1 review
This is the start of the stable review cycle for the 3.2.93 release. There are 106 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Tue Sep 12 12:00:00 UTC 2017. Anything received after that time might be too late.
A combined patch relative to 3.2.92 will be posted as an additional response to this. A shortlog and diffstat can be found below.
Ben.
-------------
Al Viro (4):
excessive checks in ufs_write_failed() and ufs_evict_inode()
[babef37dccbaa49249a22bae9150686815d7be71]
fix ufs_isblockset()
[414cf7186dbec29bd946c138d6b5c09da5955a08]
osf_wait4(): fix infoleak
[a8c39544a6eb2093c04afd5005b6192bd0e880c6]
ufs: set correct ->s_maxsize
[6b0d144fa758869bdd652c50aa41aaf601232550]Alan Stern (2):
USB: ene_usb6250: fix DMA to the stack
[628c2893d44876ddd11602400c70606ade62e129]
USB: xhci: fix lock-inversion problem
[63aea0dbab90a2461faaae357cbc8cfd6c8de9fe]
Alex Deucher (1):
drm/radeon: add a quirk for Toshiba Satellite L20-183
[acfd6ee4fa7ebeee75511825fe02be3f7ac1d668]
Alexander Sverdlin (1):
dmaengine: ep93xx: Always start from BASE0
[0037ae47812b1f431cc602100d1d51f37d77b61e]
Alexander Tsoy (1):
ALSA: hda - apply STAC_9200_DELL_M22 quirk for Dell Latitude D430
[1fc2e41f7af4572b07190f9dec28396b418e9a36]
Andrew Lunn (1):
net: phy: marvell: Limit errata to 88m1101
[f2899788353c13891412b273fdff5f02d49aa40f]
Anthony Mallet (1):
USB: serial: ftdi_sio: fix setting latency for unprivileged users
[bb246681b3ed0967489a7401ad528c1aaa1a4c2e]
Ben Hutchings (2):
ipv6: xfrm: Handle errors reported by xfrm6_find_1stfragopt()
[6e80ac5cc992ab6256c3dae87f7e57db15e1a58c]
net: add kfree_skb_list()
[bd8a7036c06cf15779b31a5397d4afcb12be81ea]
Chris Brandt (2):
usb: r8a66597-hcd: decrease timeout
[dd14a3e9b92ac6f0918054f9e3477438760a4fa6]
usb: r8a66597-hcd: select a different endpoint on timeout
[1f873d857b6c2fefb4dada952674aa01bcfb92bd]Christoph Lameter (1):
mm: fix move/migrate_pages() race on task struct
[3268c63eded4612a3d07b56d1e02ce7731e6608e]
Christophe JAILLET (1):
[media] vb2: Fix an off by one error in 'vb2_plane_vaddr'
[5ebb6dd36c9f5fb37b1077b393c254d70a14cb46]
Corentin Labbe (1):
usb: xhci: ASMedia ASM1042A chipset need shorts TX quirk
[d2f48f05cd2a2a0a708fbfa45f1a00a87660d937]
Dan Carpenter (5):
block: fix an error code in add_partition()
[7bd897cfce1eb373892d35d7f73201b0f9b221c4]
drm/vmwgfx: Handle vmalloc() failure in vmw_local_fifo_reserve()
[f0c62e9878024300319ba2438adc7b06c6b9c448]
libceph: NULL deref on crush_decode() error path
[293dffaad8d500e1a5336eeb90d544cf40d4fbd8]
xfrm: NULL dereference on allocation failure
[e747f64336fc15e1c823344942923195b800aa1e]
xfrm: Oops on error in pfkey_msg2xfrm_state()
[1e3d0c2c70cd3edb5deed186c5f5c75f2b84a633]
Daniel Drake (1):
Input: i8042 - add Fujitsu Lifebook AH544 to notimeout list
[817ae460c784f32cd45e60b2b1b21378c3c6a847]
David S. Miller (1):
ipv6: Fix leak in ipv6_gso_segment().
[e3e86b5119f81e5e2499bea7ea1ebe8ac6aab789]
Eric Biggers (1):
KEYS: fix dereferencing NULL payload with nonzero length
[5649645d725c73df4302428ee4e02c869248b4c5]
Eric Dumazet (2):
net: ping: do not abuse udp_poll()
[77d4b1d36926a9b8387c6b53eeba42bcaaffcea3]
net: prevent sign extension in dev_get_stats()
[6f64ec74515925cced6df4571638b5a099a49aae]
Eric W. Biederman (1):
signal: Only reschedule timers on signals timers have sent
[57db7e4a2d92c2d3dfbca4ef8057849b2682436b]
Felipe Balbi (1):
usb: host: xhci: simplify irq handler return
[76a35293b901915c5dcb4a87a4a0da8d7caf39fe]
Gilad Ben-Yossef (1):
crypto: gcm - wait for crypto op not signal safe
[f3ad587070d6bd961ab942b3fd7a85d00dfc934b]
Gleb Natapov (1):
KVM: x86: fix use of uninitialized memory as segment descriptor in emulator.
[378a8b099fc207ddcb91b19a8c1457667e0af398]
Ilya Matveychikov (1):
lib/cmdline.c: fix get_options() overflow while parsing ranges
[a91e0f680bcd9e10c253ae8b62462a38bd48f09f]
Jan Kara (2):
ext4: fix data corruption for mmap writes
[a056bdaae7a181f7dcc876cfab2f94538e508709]
ext4: fix fdatasync(2) after extent manipulation operations
[67a7d5f561f469ad2fa5154d2888258ab8e6df7c]
Jann Horn (1):
ptrace: use fsuid, fsgid, effective creds for fs access checks
[caaee6234d05a58c5b4d05e7bf766131b810a657]
Johan Hovold (13):
USB: gadget: dummy_hcd: fix hub-descriptor removable fields
[d81182ce30dbd497a1e7047d7fda2af040347790]
USB: hub: fix SS hub-descriptor handling
[2c25a2c818023df64463aac3288a9f969491e507]
USB: hub: fix SS max number of ports
[93491ced3c87c94b12220dbac0527e1356702179]
USB: hub: fix non-SS hub-descriptor handling
[bec444cd1c94c48df409a35ad4e5b143c245c3f7]
USB: iowarrior: fix info ioctl on big-endian hosts
[dd5ca753fa92fb736b1395db892bd29f78e6d408]
USB: serial: io_ti: fix div-by-zero in set_termios
[6aeb75e6adfaed16e58780309613a578fe1ee90b]
USB: serial: ir-usb: fix big-endian baud-rate debug printk
[ad0ccac76dcc92c3331f4c94c9fc54f8bf1ab20c]
USB: serial: mct_u232: fix big-endian baud-rate handling
[26cede343656c0bc2c33cdc783771282405c7fb2]
USB: usbip: fix nonconforming hub descriptor
[ec963b412a54aac8e527708ecad06a6988a86fb4]
net: irda: irda-usb: fix firmware name on big-endian hosts
[75cf067953d5ee543b3bda90bbfcbee5e1f94ae8]
of: fdt: add missing allocation-failure check
[49e67dd17649b60b4d54966e18ec9c80198227f0]
uwb: fix device quirk on big-endian hosts
[41318a2b82f5d5fe1fb408f6d6e0b22aa557111d]
watchdog: pcwd_usb: fix NULL-deref at probe
[46c319b848268dab3f0e7c4a5b6e9146d3bca8a4]
Johannes Thumshirn (1):
scsi: qla2xxx: don't disable a not previously enabled PCI device
[ddff7ed45edce4a4c92949d3c61cd25d229c4a14]
Julius Werner (2):
drivers: char: mem: Check for address space wraparound with mmap()
[b299cde245b0b76c977f4291162cf668e087b408]
drivers: char: mem: Fix wraparound check to allow mappings up to the end
[32829da54d9368103a2f03269a5120aa9ee4d5da]
Konstantin Khlebnikov (1):
ext4: keep existing extra fields when inode expands
[887a9730614727c4fff7cb756711b190593fc1df]
Linus Torvalds (1):
Sanitize 'move_pages()' permission checks
[197e7e521384a23b9e585178f3f11c9fa08274b9]
Liping Zhang (1):
netfilter: ctnetlink: fix incorrect nf_ct_put during hash resize
[fefa92679dbe0c613e62b6c27235dcfbe9640ad1]
Marcin Nowakowski (1):
MIPS: kprobes: flush_insn_slot should flush only if probe initialised
[698b851073ddf5a894910d63ca04605e0473414e]
Mathias Nyman (2):
xhci: apply PME_STUCK_QUIRK and MISSING_CAS quirk for Denverton
[a0c16630d35a874e82bdf2088f58ecaca1024315]
xhci: workaround for hosts missing CAS bit
[346e99736c3ce328fd42d678343b70243aca5f36]
Max Filippov (1):
net: ethoc: enable NAPI before poll may be scheduled
[d220b942a4b6a0640aee78841608f4aa5e8e185e]
Michael Ellerman (1):
powerpc/mm: Fix virt_addr_valid() etc. on 64-bit hash
[e41e53cd4fe331d0d1f06f8e4ed7e2cc63ee2c34]
Naveen N. Rao (1):
powerpc/kprobes: Pause function_graph tracing during jprobes handling
[a9f8553e935f26cb5447f67e280946b0923cd2dc]
NeilBrown (1):
autofs: sanity check status reported with AUTOFS_DEV_IOCTL_FAIL
[9fa4eb8e490a28de40964b1b0e583d8db4c7e57c]
Nicholas Bellinger (1):
configfs: Fix race between create_link and configfs_rmdir
[ba80aa909c99802c428682c352b0ee0baac0acd3]
Nicholas Piggin (1):
powerpc/64: Initialise thread_info for emergency stacks
[34f19ff1b5a0d11e46df479623d6936460105c9f]
Patrik Jakobsson (1):
drm/gma500/psb: Actually use VBT mode when it is found
[82bc9a42cf854fdf63155759c0aa790bd1f361b0]
Paul Burton (1):
MIPS: Fix IRQ tracing & lockdep when rescheduling
[d8550860d910c6b7b70f830f59003b33daaa52c9]
Paul Moore (1):
selinux: fix double free in selinux_parse_opts_str()
[023f108dcc187e34ef864bf10ed966cf25e14e2a]
Peter Chen (1):
usb: host: xhci-mem: allocate zeroed Scratchpad Buffer
[7480d912d549f414e0ce39331870899e89a5598c]
Peter Ujfalusi (1):
usb: musb: tusb6010_omap: Do not reset the other direction's packet size
[6df2b42f7c040d57d9ecb67244e04e905ab87ac6]
Radim Krčmář (1):
KVM: x86: zero base3 of unusable segments
[f0367ee1d64d27fa08be2407df5c125442e885e3]
Rajkumar Manoharan (1):
mac80211: strictly check mesh address extension mode
[5667c86acf021e6dcf02584408b4484a273ac68f]
Roger Pau Monne (1):
xen: fix bio vec merging
[462cdace790ac2ed6aad1b19c9c0af0143b6aab0]
Russell King (1):
net: phy: fix marvell phy status reading
[898805e0cdf7fd860ec21bf661d3a0285a3defbd]
Sabrina Dubroca (2):
tracing/kprobes: Allow to create probe with a module name starting with a digit
[9e52b32567126fe146f198971364f68d3bc5233f]
xfrm: fix stack access out of bounds with CONFIG_XFRM_SUB_POLICY
[9b3eb54106cf6acd03f07cf0ab01c13676a226c2]
Sasha Levin (2):
mm: fix NULL ptr dereference in migrate_pages
[f2a9ef880763d7fbd657a3af646e132a90d70d34]
mm: fix NULL ptr dereference in move_pages
[6e8b09eaf268bceac0c62e389b4bc0cb83dfb8e5]
Sean Young (1):
[media] rc-core: race condition during ir_raw_event_register()
[963761a0b2e85663ee4a5630f72930885a06598a]
Sebastian Reichel (1):
i2c: i2c-tiny-usb: fix buffer not being DMA capable
[5165da5923d6c7df6f2927b0113b2e4d9288661e]
SeongJae Park (6):
perf probe: Fix examples section of documentation
[d89269a89ebb6a74512f3f40e89cd12017f60a75]
perf script python: Fix wrong code snippets in documentation
[26ddb8722df865aa67fbe459107d2f3f8e5c6829]
perf script python: Remove dups in documentation examples
[14fc42fa1b3e7ea5160c84d0e686a3a0c1ffe619]
perf script python: Updated trace_unhandled() signature
[1bf8d5a4a5da19b1f6e7958fe67db4118fa7a1c1]
perf script: Fix documentation errors
[34d4453dac257be53c21abf2f713c992fb692b5c]
perf script: Fix outdated comment for perf-trace-python
[c76132dc5182776b98e946d674cb41c421661ea9]
Serhey Popovych (1):
rtnetlink: add IFLA_GROUP to ifla_policy
[db833d40ad3263b2ee3b59a1ba168bb3cfed8137]
Soheil Hassas Yeganeh (1):
tcp: eliminate negative reordering in tcp_clean_rtx_queue
[bafbb9c73241760023d8981191ddd30bb1c6dbac]
Steffen Klassert (1):
af_key: Fix slab-out-of-bounds in pfkey_compile_policy.
[d90c902449a7561f1b1d58ba5a0d11728ce8b0b2]
Sui Chen (1):
ahci: Acer SA5-271 SSD Not Detected Fix
[8bfd174312629866efa535193d9e563768ff4307]
Takashi Iwai (1):
ASoC: Fix use-after-free at card unregistration
[4efda5f2130da033aeedc5b3205569893b910de2]
Thinh Nguyen (1):
usb: gadget: f_mass_storage: Serialize wake and sleep execution
[dc9217b69dd6089dcfeb86ed4b3c671504326087]
Thomas Gleixner (3):
alarmtimer: Prevent overflow of relative timers
[f4781e76f90df7aec400635d73ea4c35ee1d4765]
alarmtimer: Rate limit periodic intervals
[ff86bf0c65f14346bf2440534f9ba5ac232c39a0]
tracing/kprobes: Enforce kprobes teardown after testing
[30e7d894c1478c88d50ce94ddcdbd7f9763d9cdd]
Uwe Kleine-König (1):
net: ethernet: ax88796: don't call free_irq without request_irq first
[82533ad9a1ce3a7a6863849a552c2cc041b55e0d]
Vamsi Krishna Samavedam (1):
USB: core: replace %p with %pK
[2f964780c03b73de269b08d12aff96a9618d13f3]
Vladis Dronov (1):
xfrm: policy: check policy direction value
[7bab09631c2a303f87a7eb7e3d69e888673b9b7e]
WANG Cong (1):
ipv6: avoid unregistering inet6_dev for loopback
[60abc0be96e00ca71bac083215ac91ad2e575096]
Wan Ahmad Zainie (1):
usb: xhci: apply XHCI_PME_STUCK_QUIRK to Intel Apollo Lake
[6c97cfc1a097b1e0786c836e92b7a72b4d031e25]
Wanpeng Li (3):
KVM: X86: Fix read out-of-bounds vulnerability in kvm pio emulation
[cbfc6c9184ce71b52df4b1d82af5afc81a709178]
KVM: async_pf: avoid async pf injection when in guest mode
[9bc1f09f6fa76fdf31eb7d6a4a4df43574725f93]
KVM: cpuid: Fix read/write out-of-bounds vulnerability in cpuid emulation
[a3641631d14571242eec0d30c9faa786cbf52d44]
Wei Wang (1):
tcp: initialize rcv_mss to TCP_MIN_MSS instead of 0
[499350a5a6e7512d9ed369ed63a4244b6536f4f8]
Yu Zhao (1):
swap: cond_resched in swap_cgroup_prepare()
[ef70762948dde012146926720b70e79736336764]
Yuchung Cheng (1):
tcp: avoid fragmenting peculiar skbs in SACK
[b451e5d24ba6687c6f0e7319c727a709a1846c06]
Zhaowei Yuan (1):
[media] vb2: fix plane index sanity check in vb2_plane_cookie()
[a9ae4692eda4b99f85757b15d60971ff78a0a0e2]
Makefile | 4 +- arch/alpha/kernel/osf_sys.c | 6 +- arch/mips/include/asm/kprobes.h | 3 +- arch/mips/kernel/entry.S | 3 + arch/powerpc/include/asm/page.h | 12 +++ arch/powerpc/kernel/kprobes.c | 12 +++ arch/powerpc/kernel/setup_64.c | 25 ++++++ arch/x86/kvm/mmu.c | 7 +- arch/x86/kvm/mmu.h | 1 + arch/x86/kvm/x86.c | 53 ++++++++----- crypto/gcm.c | 6 +- drivers/ata/ahci.c | 38 +++++++++ drivers/char/mem.c | 5 ++ drivers/dma/ep93xx_dma.c | 2 + drivers/gpu/drm/radeon/radeon_combios.c | 7 ++ drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 2 + drivers/i2c/busses/i2c-tiny-usb.c | 25 +++++- drivers/input/serio/i8042-x86ia64io.h | 7 ++ drivers/media/rc/ir-raw.c | 13 ++-- drivers/media/video/videobuf2-core.c | 4 +- drivers/net/ethernet/8390/ax88796.c | 7 +- drivers/net/ethernet/ethoc.c | 3 +- drivers/net/irda/irda-usb.c | 2 +- drivers/net/phy/marvell.c | 68 ++++++++-------- drivers/of/fdt.c | 2 + drivers/scsi/qla2xxx/qla_os.c | 8 +- drivers/staging/gma500/psb_intel_lvds.c | 18 +++-- drivers/staging/usbip/vhci_hcd.c | 11 ++- drivers/usb/core/devio.c | 4 +- drivers/usb/core/hcd.c | 4 +- drivers/usb/core/hub.c | 28 +++++-- drivers/usb/gadget/dummy_hcd.c | 6 +- drivers/usb/gadget/f_mass_storage.c | 13 +++- drivers/usb/host/r8a66597-hcd.c | 6 +- drivers/usb/host/xhci-hub.c | 37 +++++++++ drivers/usb/host/xhci-mem.c | 2 +- drivers/usb/host/xhci-pci.c | 16 +++- drivers/usb/host/xhci-ring.c | 37 +++++---- drivers/usb/host/xhci.h | 3 + drivers/usb/misc/iowarrior.c | 2 +- drivers/usb/musb/tusb6010_omap.c | 13 +++- drivers/usb/serial/ftdi_sio.c | 2 +- drivers/usb/serial/io_ti.c | 5 +- drivers/usb/serial/ir-usb.c | 21 ++--- drivers/usb/serial/mct_u232.c | 2 +- drivers/usb/storage/ene_ub6250.c | 90 +++++++++++++--------- drivers/uwb/i1480/dfu/usb.c | 5 +- drivers/watchdog/pcwd_usb.c | 3 + drivers/xen/biomerge.c | 3 +- fs/autofs4/dev-ioctl.c | 2 +- fs/configfs/symlink.c | 3 +- fs/ext4/extents.c | 2 + fs/ext4/inode.c | 31 ++++++-- fs/partitions/check.c | 4 +- fs/proc/array.c | 2 +- fs/proc/base.c | 12 +-- fs/proc/namespaces.c | 4 +- fs/ufs/inode.c | 5 +- fs/ufs/super.c | 18 +++++ fs/ufs/truncate.c | 6 -- fs/ufs/util.h | 10 ++- include/linux/kprobes.h | 4 +- include/linux/ptrace.h | 24 +++++- include/linux/skbuff.h | 1 + include/linux/usb/ch11.h | 3 + include/net/xfrm.h | 10 --- kernel/events/core.c | 2 +- kernel/futex.c | 2 +- kernel/futex_compat.c | 2 +- kernel/kprobes.c | 2 +- kernel/ptrace.c | 39 ++++++++-- kernel/signal.c | 20 +++-- kernel/time/alarmtimer.c | 12 ++- kernel/trace/trace_kprobe.c | 18 +++-- lib/cmdline.c | 6 +- mm/mempolicy.c | 29 ++++--- mm/migrate.c | 45 +++++------ mm/page_cgroup.c | 3 + mm/process_vm_access.c | 2 +- net/ceph/osdmap.c | 1 + net/core/dev.c | 2 +- net/core/rtnetlink.c | 2 + net/core/skbuff.c | 20 +++-- net/ipv4/af_inet.c | 2 +- net/ipv4/tcp.c | 4 + net/ipv4/tcp_input.c | 11 +-- net/ipv6/addrconf.c | 5 +- net/ipv6/af_inet6.c | 4 +- net/ipv6/xfrm6_mode_ro.c | 2 + net/ipv6/xfrm6_mode_transport.c | 2 + net/key/af_key.c | 19 +++-- net/mac80211/rx.c | 3 +- net/netfilter/nf_conntrack_netlink.c | 7 +- net/wireless/util.c | 14 +++- net/xfrm/xfrm_policy.c | 51 ++---------- security/commoncap.c | 7 +- security/keys/keyctl.c | 4 +- security/selinux/hooks.c | 5 +- sound/pci/hda/patch_sigmatel.c | 2 + sound/soc/soc-core.c | 5 +- tools/perf/Documentation/perf-probe.txt | 8 +- tools/perf/Documentation/perf-script-perl.txt | 2 +- tools/perf/Documentation/perf-script-python.txt | 23 +++--- .../util/scripting-engines/trace-event-python.c | 2 +- 104 files changed, 794 insertions(+), 392 deletions(-)
Signature · 3 lines
Ben Hutchings For every complex problem there is a solution that is simple, neat, and wrong.
PATCH 1/106 xfrm: fix stack access out of bounds with CONFIG_XFRM_SUB_POLICY
3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sabrina Dubroca <[email protected]>
commit 9b3eb54106cf6acd03f07cf0ab01c13676a226c2 upstream.
When CONFIG_XFRM_SUB_POLICY=y, xfrm_dst stores a copy of the flowi for that dst. Unfortunately, the code that allocates and fills this copy doesn't care about what type of flowi (flowi, flowi4, flowi6) gets passed. In multiple code paths (from raw_sendmsg, from TCP when replying to a FIN, in vxlan, geneve, and gre), the flowi that gets passed to xfrm is actually an on-stack flowi4, so we end up reading stuff from the stack past the end of the flowi4 struct.
Since xfrm_dst->origin isn't used anywhere following commit ca116922afa8 ("xfrm: Eliminate "fl" and "pol" args to xfrm_bundle_ok()."), just get rid of it. xfrm_dst->partner isn't used either, so get rid of that too.
---
include/net/xfrm.h +0 -10
@@ -925,10 +925,6 @@ struct xfrm_dst {struct flow_cache_object flo;struct xfrm_policy *pols[XFRM_POLICY_TYPE_MAX ];int num_pols, num_xfrms; -#ifdef CONFIG_XFRM_SUB_POLICY -struct flowi *origin; -struct xfrm_selector *partner; -#endif u32 xfrm_genid;u32 policy_genid;u32 route_mtu_cached;
@@ -944,12 +940,6 @@ static inline void xfrm_dst_destroy(strudst_release (xdst->route);if (likely (xdst->u.dst.xfrm)) xfrm_state_put(xdst->u.dst.xfrm); -#ifdef CONFIG_XFRM_SUB_POLICY -kfree (xdst->origin); - xdst->origin =NULL ; -kfree (xdst->partner); - xdst->partner =NULL ; -#endif }#endif
net/xfrm/xfrm_policy.c +0 -45
57 lines not on this page · raw message
PATCH 2/106 af_key: Fix slab-out-of-bounds in pfkey_compile_policy.
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Steffen Klassert <[email protected]>
commit d90c902449a7561f1b1d58ba5a0d11728ce8b0b2 upstream.
The sadb_x_sec_len is stored in the unit 'byte divided by eight'. So we have to multiply this value by eight before we can do size checks. Otherwise we may get a slab-out-of-bounds when we memcpy the user sec_ctx.
--- net/key/af_key.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/key/af_key.c +1 -1
@@ -3230,7 +3230,7 @@ static struct xfrm_policy *pfkey_compile p += pol->sadb_x_policy_len*8 ; sec_ctx = (struct sadb_x_sec_ctx *)p;if (len < pol->sadb_x_policy_len*8 + - sec_ctx->sadb_x_sec_len) { + sec_ctx->sadb_x_sec_len*8 ) { *dir = -EINVAL ; goto out; }
PATCH 3/106 tcp: avoid fragmenting peculiar skbs in SACK
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Yuchung Cheng <[email protected]>
commit b451e5d24ba6687c6f0e7319c727a709a1846c06 upstream.
This patch fixes a bug in splitting an SKB during SACK processing. Specifically if an skb contains multiple packets and is only partially sacked in the higher sequences, tcp_match_sack_to_skb() splits the skb and marks the second fragment as SACKed.
The current code further attempts rounding up the first fragment to MSS boundaries. But it misses a boundary condition when the rounded-up fragment size (pkt_len) is exactly skb size. Spliting such an skb is pointless and causses a kernel warning and aborts the SACK processing. This patch universally checks such over-split before calling tcp_fragment to prevent these unnecessary warnings.
--- net/ipv4/tcp_input.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
net/ipv4/tcp_input.c +5 -4
@@ -1303,13 +1303,14 @@ static int tcp_match_skb_to_sack(struct*/ if (pkt_len > mss) {unsigned int new_len = (pkt_len / mss) * mss; -if (!in_sack && new_len < pkt_len) { +if (!in_sack && new_len < pkt_len) new_len += mss; -if (new_len >= skb->len) -return 0 ; - } pkt_len = new_len; } + +if (pkt_len >= skb->len && !in_sack) +return 0 ; + err =tcp_fragment (sk, skb, pkt_len, mss);if (err <0 )return err;
PATCH 4/106 net: irda: irda-usb: fix firmware name on big-endian hosts
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 75cf067953d5ee543b3bda90bbfcbee5e1f94ae8 upstream.
Add missing endianness conversion when using the USB device-descriptor bcdDevice field to construct a firmware file name.
--- drivers/net/irda/irda-usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/irda/irda-usb.c +1 -1
@@ -1083,7 +1083,7 @@ static int stir421x_patch_device(struct* are "42101001.sb" or "42101002.sb" */ sprintf (stir421x_fw_name,"4210%4X.sb" , - self->usbdev->descriptor.bcdDevice); +le16_to_cpu (self->usbdev->descriptor.bcdDevice)); ret =request_firmware (&fw, stir421x_fw_name, &self->usbdev->dev);if (ret <0 )return ret;
PATCH 5/106 USB: serial: ftdi_sio: fix setting latency for unprivileged users
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Anthony Mallet <[email protected]>
commit bb246681b3ed0967489a7401ad528c1aaa1a4c2e upstream.
Commit 557aaa7ffab6 ("ft232: support the ASYNC_LOW_LATENCY flag") enables unprivileged users to set the FTDI latency timer, but there was a logic flaw that skipped sending the corresponding USB control message to the device.
Specifically, the device latency timer would not be updated until next open, something which was later also inadvertently broken by commit c19db4c9e49a ("USB: ftdi_sio: set device latency timeout at port probe").
A recent commit c6dce2626606 ("USB: serial: ftdi_sio: fix extreme low-latency setting") disabled the low-latency mode by default so we now need this fix to allow unprivileged users to again enable it.
--- drivers/usb/serial/ftdi_sio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/serial/ftdi_sio.c +1 -1
@@ -1543,9 +1543,9 @@ static int set_serial_info(struct tty_st (new_serial.flags & ASYNC_FLAGS)); priv->custom_divisor = new_serial.custom_divisor; +check_and_exit:write_latency_timer (port); -check_and_exit:if ((old_priv.flags &ASYNC_SPD_MASK ) != (priv->flags &ASYNC_SPD_MASK )) {if ((priv->flags &ASYNC_SPD_MASK ) ==ASYNC_SPD_HI )
PATCH 6/106 USB: serial: ir-usb: fix big-endian baud-rate debug printk
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit ad0ccac76dcc92c3331f4c94c9fc54f8bf1ab20c upstream.
Add missing endianness conversion when printing the supported baud rates.
Found using sparse:
warning: restricted __le16 degrades to integer
--- drivers/usb/serial/ir-usb.c | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)
drivers/usb/serial/ir-usb.c +12 -9
@@ -236,6 +236,7 @@ static u8 ir_xbof_change(u8 xbof)static int ir_startup (struct usb_serial *serial) {struct usb_irda_cs_descriptor *irda_desc; +int rates; irda_desc =irda_usb_find_class_desc (serial->dev,0 );if (!irda_desc) {
@@ -244,17 +245,19 @@ static int ir_startup(struct usb_serialreturn -ENODEV ; } + rates =le16_to_cpu (irda_desc->wBaudRate); +dbg ("%s - Baud rates supported:%s%s%s%s%s%s%s%s%s" , __func__, - (irda_desc->wBaudRate &USB_IRDA_BR_2400 ) ?" 2400" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_9600 ) ?" 9600" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_19200 ) ?" 19200" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_38400 ) ?" 38400" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_57600 ) ?" 57600" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_115200 ) ?" 115200" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_576000 ) ?" 576000" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_1152000 ) ?" 1152000" :"" , - (irda_desc->wBaudRate &USB_IRDA_BR_4000000 ) ?" 4000000" :"" ); + (rates &USB_IRDA_BR_2400 ) ?" 2400" :"" , + (rates &USB_IRDA_BR_9600 ) ?" 9600" :"" , + (rates &USB_IRDA_BR_19200 ) ?" 19200" :"" , + (rates &USB_IRDA_BR_38400 ) ?" 38400" :"" , + (rates &USB_IRDA_BR_57600 ) ?" 57600" :"" , + (rates &USB_IRDA_BR_115200 ) ?" 115200" :"" , + (rates &USB_IRDA_BR_576000 ) ?" 576000" :"" , + (rates &USB_IRDA_BR_1152000 ) ?" 1152000" :"" , + (rates &USB_IRDA_BR_4000000 ) ?" 4000000" :"" );switch (irda_desc->bmAdditionalBOFs) {case USB_IRDA_AB_48 :
PATCH 7/106 USB: serial: mct_u232: fix big-endian baud-rate handling
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 26cede343656c0bc2c33cdc783771282405c7fb2 upstream.
Drop erroneous cpu_to_le32 when setting the baud rate, something which corrupted the divisor on big-endian hosts.
Found using sparse:
warning: incorrect type in argument 1 (different base types)
expected unsigned int [unsigned] [usertype] val got restricted __le32 [usertype] <noident>
--- drivers/usb/serial/mct_u232.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/serial/mct_u232.c +1 -1
@@ -251,7 +251,7 @@ static int mct_u232_set_baud_rate(structreturn -ENOMEM ; divisor =mct_u232_calculate_baud_rate (serial, value, &speed); -put_unaligned_le32 (cpu_to_le32 (divisor), buf); +put_unaligned_le32 (divisor, buf); rc = usb_control_msg(serial->dev, usb_sndctrlpipe(serial->dev, 0), MCT_U232_SET_BAUD_RATE_REQUEST, MCT_U232_SET_REQUEST_TYPE,
PATCH 8/106 USB: serial: io_ti: fix div-by-zero in set_termios
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 6aeb75e6adfaed16e58780309613a578fe1ee90b upstream.
Fix a division-by-zero in set_termios when debugging is enabled and a high-enough speed has been requested so that the divisor value becomes zero.
Instead of just fixing the offending debug statement, cap the baud rate at the base as a zero divisor value also appears to crash the firmware.
--- drivers/usb/serial/io_ti.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/usb/serial/io_ti.c +4 -1
@@ -2412,8 +2412,11 @@ static void change_port_settings(structif (!baud) {/* pick a default, any default... */ baud =9600 ; - }else + }else { +/* Avoid a zero divisor. */ + baud =min (baud,461550 );tty_encode_baud_rate (tty, baud, baud); + } edge_port->baud_rate = baud; config->wBaudRate = (__u16)((461550L + baud/2 ) / baud);
PATCH 9/106 ahci: Acer SA5-271 SSD Not Detected Fix
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sui Chen <[email protected]>
commit 8bfd174312629866efa535193d9e563768ff4307 upstream.
(Correction in this resend: fixed function name acer_sa5_271_workaround; fixed
the always-true condition in the function; fixed description.)
On the Acer Switch Alpha 12 (model number: SA5-271), the internal SSD may not get detected because the port_map and CAP.nr_ports combination causes the driver to skip the port that is actually connected to the SSD. More specifically, either all SATA ports are identified as DUMMY, or all ports get ``link down'' and never get up again.
This problem occurs occasionally. When this problem occurs, CAP may hold a value of 0xC734FF00 or 0xC734FF01 and port_map may hold a value of 0x00 or 0x01. When this problem does not occur, CAP holds a value of 0xC734FF02 and port_map may hold a value of 0x07. Overriding the CAP value to 0xC734FF02 and port_map to 0x7 significantly reduces the occurrence of this problem.
--- drivers/ata/ahci.c | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+)
drivers/ata/ahci.c +38 -0
@@ -1268,6 +1268,40 @@ static inline void ahci_gtf_filter_worka {}#endif +/* +* On the Acer Aspire Switch Alpha 12, sometimes all SATA ports are detected +* as DUMMY, or detected but eventually get a "link down" and never get up +* again. When this happens, CAP.NP may hold a value of 0x00 or 0x01, and the +* port_map may hold a value of 0x00. +* +* Overriding CAP.NP to 0x02 and the port_map to 0x7 will reveal all 3 ports +* and can significantly reduce the occurrence of the problem. +* +* https://bugzilla.kernel.org/show_bug.cgi?id=189471 +*/ +static void acer_sa5_271_workaround (struct ahci_host_priv *hpriv, +struct pci_dev *pdev) +{ +static const struct dmi_system_id sysids[] = { + { + .ident ="Acer Switch Alpha 12" , + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"Acer" ), +DMI_MATCH (DMI_PRODUCT_NAME ,"Switch SA5-271" ) + }, + }, + { } + }; + +if (dmi_check_system (sysids)) { +dev_info (&pdev->dev,"enabling Acer Switch Alpha 12 workaround\n" ); +if ((hpriv->saved_cap &0xC734FF00 ) ==0xC734FF00 ) { + hpriv->port_map =0x7 ; + hpriv->cap =0xC734FF02 ; + } + } +} +static int ahci_init_one (struct pci_dev *pdev,const struct pci_device_id *ent) {unsigned int board_id = ent->driver_data;
@@ -1407,6 +1441,10 @@ static int ahci_init_one(struct pci_dev "online status unreliable, applying workaround\n"); } + +/* Acer SA5-271 workaround modifies private_data */ +acer_sa5_271_workaround (hpriv, pdev); +/* CAP.NP sometimes indicate the index of the last enabled * port, at other times, that of the last possible port, so * determining the maximum port number requires looking at
PATCH 10/106 tcp: eliminate negative reordering in tcp_clean_rtx_queue
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Soheil Hassas Yeganeh <[email protected]>
commit bafbb9c73241760023d8981191ddd30bb1c6dbac upstream.
tcp_ack() can call tcp_fragment() which may dededuct the value tp->fackets_out when MSS changes. When prior_fackets is larger than tp->fackets_out, tcp_clean_rtx_queue() can invoke tcp_update_reordering() with negative values. This results in absurd tp->reodering values higher than sysctl_tcp_max_reordering.
Note that tcp_update_reordering indeeds sets tp->reordering to min(sysctl_tcp_max_reordering, metric), but because the comparison is signed, a negative metric always wins.
--- net/ipv4/tcp_input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/tcp_input.c +1 -1
@@ -3425,7 +3425,7 @@ static int tcp_clean_rtx_queue(struct soint delta;/* Non-retransmitted hole got filled? That's reordering */ -if (reord < prior_fackets) +if (reord < prior_fackets && reord <= tp->fackets_out)tcp_update_reordering (sk, tp->fackets_out - reord,0 ); delta = tcp_is_fack(tp) ? pkts_acked :
PATCH 11/106 USB: ene_usb6250: fix DMA to the stack
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Alan Stern <[email protected]>
commit 628c2893d44876ddd11602400c70606ade62e129 upstream.
The ene_usb6250 sub-driver in usb-storage does USB I/O to buffers on the stack, which doesn't work with vmapped stacks. This patch fixes the problem by allocating a separate 512-byte buffer at probe time and using it for all of the offending I/O operations.
--- drivers/usb/storage/ene_ub6250.c | 90 ++++++++++++++++++++++++---------------- 1 file changed, 55 insertions(+), 35 deletions(-)
drivers/usb/storage/ene_ub6250.c +55 -35
@@ -431,6 +431,10 @@ struct ms_lib_ctrl {#define SD_BLOCK_LEN 9struct ene_ub6250_info { + +/* I/O bounce buffer */ +u8 *bbuf; +/* for 6250 code */ struct SD_STATUS SD_Status;struct MS_STATUS MS_Status;
@@ -478,8 +482,11 @@ static int ene_load_bincode(struct us_dastatic void ene_ub6250_info_destructor (void *extra) { +struct ene_ub6250_info *info = (struct ene_ub6250_info *) extra; +if (!extra)return ; +kfree (info->bbuf); }static int ene_send_scsi_cmd (struct us_data *us,u8 fDir,void *buf,int use_sg)
@@ -843,8 +850,9 @@ static int ms_read_readpage(struct us_da u8 PageNum, u32 *PageBuf, struct ms_lib_type_extdat *ExtraDat) { struct bulk_cb_wrap *bcb = (struct bulk_cb_wrap *) us->iobuf; +struct ene_ub6250_info *info = (struct ene_ub6250_info *) us->extra; +u8 *bbuf = info->bbuf;int result; -u8 ExtBuf[4 ];u32 bn = PhyBlockAddr *0x20 + PageNum;/* printk(KERN_INFO "MS --- MS_ReaderReadPage,
@@ -887,7 +895,7 @@ static int ms_read_readpage(struct us_da bcb->CDB[2 ] = (unsigned char )(PhyBlockAddr>>16 ); bcb->CDB[6 ] =0x01 ; - result =ene_send_scsi_cmd (us,FDIR_READ , &ExtBuf,0 ); + result =ene_send_scsi_cmd (us,FDIR_READ , bbuf,0 );if (result !=USB_STOR_XFER_GOOD )return USB_STOR_TRANSPORT_ERROR ;
@@ -896,9 +904,9 @@ static int ms_read_readpage(struct us_da ExtraDat->status0 =0x10 ;/* Not yet,fireware support */ ExtraDat->status1 =0x00 ;/* Not yet,fireware support */ - ExtraDat->ovrflg = ExtBuf[0 ]; - ExtraDat->mngflg = ExtBuf[1 ]; - ExtraDat->logadr =memstick_logaddr (ExtBuf[2 ], ExtBuf[3 ]); + ExtraDat->ovrflg = bbuf[0 ]; + ExtraDat->mngflg = bbuf[1 ]; + ExtraDat->logadr =memstick_logaddr (bbuf[2 ], bbuf[3 ]);return USB_STOR_TRANSPORT_GOOD ; }
@@ -1324,8 +1332,9 @@ static int ms_lib_read_extra(struct us_d u8 PageNum, struct ms_lib_type_extdat *ExtraDat) { struct bulk_cb_wrap *bcb = (struct bulk_cb_wrap *) us->iobuf; +struct ene_ub6250_info *info = (struct ene_ub6250_info *) us->extra; +u8 *bbuf = info->bbuf;int result; -u8 ExtBuf[4 ];/* printk("MS_LibReadExtra --- PhyBlock = %x, PageNum = %x\n", PhyBlock, PageNum); */ memset (bcb,0 ,sizeof (struct bulk_cb_wrap ));
@@ -1340,7 +1349,7 @@ static int ms_lib_read_extra(struct us_d bcb->CDB[2 ] = (unsigned char )(PhyBlock>>16 ); bcb->CDB[6 ] =0x01 ; - result =ene_send_scsi_cmd (us,FDIR_READ , &ExtBuf,0 ); + result =ene_send_scsi_cmd (us,FDIR_READ , bbuf,0 );if (result !=USB_STOR_XFER_GOOD )return USB_STOR_TRANSPORT_ERROR ;
@@ -1348,9 +1357,9 @@ static int ms_lib_read_extra(struct us_d ExtraDat->intr =0x80 ;/* Not yet, waiting for fireware support */ ExtraDat->status0 =0x10 ;/* Not yet, waiting for fireware support */ ExtraDat->status1 =0x00 ;/* Not yet, waiting for fireware support */ - ExtraDat->ovrflg = ExtBuf[0 ]; - ExtraDat->mngflg = ExtBuf[1 ]; - ExtraDat->logadr =memstick_logaddr (ExtBuf[2 ], ExtBuf[3 ]); + ExtraDat->ovrflg = bbuf[0 ]; + ExtraDat->mngflg = bbuf[1 ]; + ExtraDat->logadr =memstick_logaddr (bbuf[2 ], bbuf[3 ]);return USB_STOR_TRANSPORT_GOOD ; }
@@ -1554,9 +1563,9 @@ static int ms_lib_scan_logicalblocknumbeu16 PhyBlock, newblk, i;u16 LogStart, LogEnde;struct ms_lib_type_extdat extdat; -u8 buf[0x200 ];u32 count =0 , index =0 ;struct ene_ub6250_info *info = (struct ene_ub6250_info *) us->extra; +u8 *bbuf = info->bbuf;for (PhyBlock =0 ; PhyBlock < info->MS_Lib.NumberOfPhyBlock;) {ms_lib_phy_to_log_range (PhyBlock, &LogStart, &LogEnde);
@@ -1570,14 +1579,16 @@ static int ms_lib_scan_logicalblocknumbe }if (count == PhyBlock) { -ms_lib_read_extrablock (us, PhyBlock,0 ,0x80 , &buf); +ms_lib_read_extrablock (us, PhyBlock,0 ,0x80 , + bbuf); count +=0x80 ; } index = (PhyBlock %0x80 ) *4 ; - extdat.ovrflg = buf[index]; - extdat.mngflg = buf[index+1 ]; - extdat.logadr =memstick_logaddr (buf[index+2 ], buf[index+3 ]); + extdat.ovrflg = bbuf[index]; + extdat.mngflg = bbuf[index+1 ]; + extdat.logadr =memstick_logaddr (bbuf[index+2 ], + bbuf[index+3 ]);if ((extdat.ovrflg &MS_REG_OVR_BKST ) !=MS_REG_OVR_BKST_OK ) {ms_lib_setacquired_errorblock (us, PhyBlock);
@@ -2066,9 +2077,9 @@ static int ene_ms_init(struct us_data *u {struct bulk_cb_wrap *bcb = (struct bulk_cb_wrap *) us->iobuf;int result; -u8 buf[0x200 ];u16 MSP_BlockSize, MSP_UserAreaBlocks;struct ene_ub6250_info *info = (struct ene_ub6250_info *) us->extra; +u8 *bbuf = info->bbuf;printk (KERN_INFO "transport --- ENE_MSInit\n" );
@@ -2087,13 +2098,13 @@ static int ene_ms_init(struct us_data *u bcb->CDB[0 ] =0xF1 ; bcb->CDB[1 ] =0x01 ; - result =ene_send_scsi_cmd (us,FDIR_READ , &buf,0 ); + result =ene_send_scsi_cmd (us,FDIR_READ , bbuf,0 );if (result !=USB_STOR_XFER_GOOD ) {printk (KERN_ERR "Execution MS Init Code Fail !!\n" );return USB_STOR_TRANSPORT_ERROR ; }/* the same part to test ENE */ - info->MS_Status = *(struct MS_STATUS *)&buf[0 ]; + info->MS_Status = *(struct MS_STATUS *) bbuf;if (info->MS_Status.Insert && info->MS_Status.Ready) {printk (KERN_INFO "Insert = %x\n" , info->MS_Status.Insert);
@@ -2102,15 +2113,15 @@ static int ene_ms_init(struct us_data *uprintk (KERN_INFO "IsMSPHG = %x\n" , info->MS_Status.IsMSPHG);printk (KERN_INFO "WtP= %x\n" , info->MS_Status.WtP);if (info->MS_Status.IsMSPro) { - MSP_BlockSize = (buf[6 ] <<8 ) | buf[7 ]; - MSP_UserAreaBlocks = (buf[10 ] <<8 ) | buf[11 ]; + MSP_BlockSize = (bbuf[6 ] <<8 ) | bbuf[7 ]; + MSP_UserAreaBlocks = (bbuf[10 ] <<8 ) | bbuf[11 ]; info->MSP_TotalBlock = MSP_BlockSize * MSP_UserAreaBlocks; }else {ms_card_init (us);/* Card is MS (to ms.c)*/ }US_DEBUGP ("MS Init Code OK !!\n" ); }else { -US_DEBUGP ("MS Card Not Ready --- %x\n" , buf[0 ]); +US_DEBUGP ("MS Card Not Ready --- %x\n" , bbuf[0 ]);return USB_STOR_TRANSPORT_ERROR ; }
@@ -2120,9 +2131,9 @@ static int ene_ms_init(struct us_data *ustatic int ene_sd_init (struct us_data *us) {int result; -u8 buf[0x200 ];struct bulk_cb_wrap *bcb = (struct bulk_cb_wrap *) us->iobuf;struct ene_ub6250_info *info = (struct ene_ub6250_info *) us->extra; +u8 *bbuf = info->bbuf;US_DEBUGP ("transport --- ENE_SDInit\n" );/* SD Init Part-1 */
@@ -2156,15 +2167,15 @@ static int ene_sd_init(struct us_data *u bcb->Flags =0x80 ; bcb->CDB[0 ] =0xF1 ; - result =ene_send_scsi_cmd (us,FDIR_READ , &buf,0 ); + result =ene_send_scsi_cmd (us,FDIR_READ , bbuf,0 );if (result !=USB_STOR_XFER_GOOD ) {US_DEBUGP ("Execution SD Init Code Fail !!\n" );return USB_STOR_TRANSPORT_ERROR ; } - info->SD_Status = *(struct SD_STATUS *)&buf[0 ]; + info->SD_Status = *(struct SD_STATUS *) bbuf;if (info->SD_Status.Insert && info->SD_Status.Ready) { -ene_get_card_status (us, (unsigned char *)&buf); +ene_get_card_status (us, bbuf);US_DEBUGP ("Insert = %x\n" , info->SD_Status.Insert);US_DEBUGP ("Ready = %x\n" , info->SD_Status.Ready);US_DEBUGP ("IsMMC = %x\n" , info->SD_Status.IsMMC);
@@ -2172,7 +2183,7 @@ static int ene_sd_init(struct us_data *uUS_DEBUGP ("HiSpeed = %x\n" , info->SD_Status.HiSpeed);US_DEBUGP ("WtP = %x\n" , info->SD_Status.WtP); }else { -US_DEBUGP ("SD Card Not Ready --- %x\n" , buf[0 ]); +US_DEBUGP ("SD Card Not Ready --- %x\n" , bbuf[0 ]);return USB_STOR_TRANSPORT_ERROR ; }return USB_STOR_TRANSPORT_GOOD ;
@@ -2182,13 +2193,15 @@ static int ene_sd_init(struct us_data *ustatic int ene_init (struct us_data *us) {int result; -u8 misc_reg03 =0 ; +u8 misc_reg03;struct ene_ub6250_info *info = (struct ene_ub6250_info *)(us->extra); +u8 *bbuf = info->bbuf; - result =ene_get_card_type (us,REG_CARD_STATUS , &misc_reg03); + result =ene_get_card_type (us,REG_CARD_STATUS , bbuf);if (result !=USB_STOR_XFER_GOOD )return USB_STOR_TRANSPORT_ERROR ; + misc_reg03 = bbuf[0 ];if (misc_reg03 &0x01 ) {if (!info->SD_Status.Ready) { result =ene_sd_init (us);
@@ -2304,8 +2317,9 @@ static int ene_ub6250_probe(struct usb_i const struct usb_device_id *id) {int result; -u8 misc_reg03 =0 ; +u8 misc_reg03;struct us_data *us; +struct ene_ub6250_info *info; result =usb_stor_probe1 (&us, intf, id, (id - ene_ub6250_usb_ids) + ene_ub6250_unusual_dev_list);
@@ -2313,11 +2327,16 @@ static int ene_ub6250_probe(struct usb_ireturn result;/* FIXME: where should the code alloc extra buf ? */ -if (!us->extra) { - us->extra =kzalloc (sizeof (struct ene_ub6250_info ),GFP_KERNEL ); -if (!us->extra) -return -ENOMEM ; - us->extra_destructor = ene_ub6250_info_destructor; + us->extra =kzalloc (sizeof (struct ene_ub6250_info ),GFP_KERNEL ); +if (!us->extra) +return -ENOMEM ; + us->extra_destructor = ene_ub6250_info_destructor; + + info = (struct ene_ub6250_info *)(us->extra); + info->bbuf =kmalloc (512 ,GFP_KERNEL ); +if (!info->bbuf) { +kfree (us->extra); +return -ENOMEM ; } us->transport_name ="ene_ub6250" ;
@@ -2329,12 +2348,13 @@ static int ene_ub6250_probe(struct usb_ireturn result;/* probe card type */ - result =ene_get_card_type (us,REG_CARD_STATUS , &misc_reg03); + result =ene_get_card_type (us,REG_CARD_STATUS , info->bbuf);if (result !=USB_STOR_XFER_GOOD ) {usb_stor_disconnect (intf);return USB_STOR_TRANSPORT_ERROR ; } + misc_reg03 = info->bbuf[0 ];if (!(misc_reg03 &0x01 )) {pr_info ("ums_eneub6250: The driver only supports SD/MS card. " "To use SM card, please build driver/staging/keucr\n" );
PATCH 12/106 USB: core: replace %p with %pK
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Vamsi Krishna Samavedam <[email protected]>
commit 2f964780c03b73de269b08d12aff96a9618d13f3 upstream.
Format specifier %p can leak kernel addresses while not valuing the kptr_restrict system settings. When kptr_restrict is set to (1), kernel pointers printed using the %pK format specifier will be replaced with Zeros. Debugging Note : &pK prints only Zeros as address. If you need actual address information, write 0 to kptr_restrict.
echo 0 > /proc/sys/kernel/kptr_restrict
[Found by poking around in a random vendor kernel tree, it would be nice if someone would actually send these types of patches upstream - gkh]
[bwh: Backported to 3.2: drop changes in proc_reapurb*(), usbdev_do_ioctl(),
usb_submit_urb()]
---
drivers/usb/core/devio.c +2 -2
@@ -325,11 +325,11 @@ static void snoop_urb(struct usb_deviceif (userurb) {/* Async */ if (when ==SUBMIT ) -dev_info (&udev->dev,"userurb %p, ep%d %s-%s, " +dev_info (&udev->dev,"userurb %pK, ep%d %s-%s, " "length %u\n" , userurb, ep, t, d, length);else -dev_info (&udev->dev,"userurb %p, ep%d %s-%s, " +dev_info (&udev->dev,"userurb %pK, ep%d %s-%s, " "actual_length %u status %d\n" , userurb, ep, t, d, length, timeout_or_status);
drivers/usb/core/hcd.c +2 -2
@@ -1563,7 +1563,7 @@ int usb_hcd_unlink_urb (struct urb *urb,if (retval ==0 ) retval = -EINPROGRESS ;else if (retval != -EIDRM && retval != -EBUSY ) -dev_dbg (&udev->dev,"hcd_unlink_urb %p fail %d\n" , +dev_dbg (&udev->dev,"hcd_unlink_urb %pK fail %d\n" , urb, retval);usb_put_dev (udev); }
@@ -1645,7 +1645,7 @@ rescan:/* kick hcd */ unlink1 (hcd, urb, -ESHUTDOWN ); dev_dbg (hcd->self.controller, - "shutdown urb %p ep%d%s%s\n", + "shutdown urb %pK ep%d%s%s\n", urb, usb_endpoint_num(&ep->desc), is_in ? "in" : "out", ({ char *s;
PATCH 13/106 uwb: fix device quirk on big-endian hosts
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 41318a2b82f5d5fe1fb408f6d6e0b22aa557111d upstream.
Add missing endianness conversion when using the USB device-descriptor idProduct field to apply a hardware quirk.
--- drivers/uwb/i1480/dfu/usb.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/uwb/i1480/dfu/usb.c +3 -2
@@ -341,6 +341,7 @@ error_submit_ep1:static int i1480_usb_probe (struct usb_interface *iface,const struct usb_device_id *id) { +struct usb_device *udev =interface_to_usbdev (iface);struct i1480_usb *i1480_usb;struct i1480 *i1480;struct device *dev = &iface->dev;
@@ -352,8 +353,8 @@ int i1480_usb_probe(struct usb_interface iface->cur_altsetting->desc.bInterfaceNumber); goto error; } -if (iface->num_altsetting >1 - &&interface_to_usbdev (iface)->descriptor.idProduct ==0xbabe ) { +if (iface->num_altsetting >1 && +le16_to_cpu (udev->descriptor.idProduct) ==0xbabe ) {/* Need altsetting #1 [HW QUIRK] or EP1 won't work */ result =usb_set_interface (interface_to_usbdev (iface),0 ,1 );if (result <0 )
PATCH 14/106 USB: iowarrior: fix info ioctl on big-endian hosts
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit dd5ca753fa92fb736b1395db892bd29f78e6d408 upstream.
Drop erroneous le16_to_cpu when returning the USB device speed which is already in host byte order.
Found using sparse:
warning: cast to restricted __le16
--- drivers/usb/misc/iowarrior.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/misc/iowarrior.c +1 -1
@@ -560,7 +560,7 @@ static long iowarrior_ioctl(struct file info.revision =le16_to_cpu (dev->udev->descriptor.bcdDevice);/* 0==UNKNOWN, 1==LOW(usb1.1) ,2=FULL(usb1.1), 3=HIGH(usb2.0) */ - info.speed =le16_to_cpu (dev->udev->speed); + info.speed = dev->udev->speed; info.if_num = dev->interface->cur_altsetting->desc.bInterfaceNumber; info.report_size = dev->report_size;
PATCH 15/106 usb: r8a66597-hcd: decrease timeout
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Chris Brandt <[email protected]>
commit dd14a3e9b92ac6f0918054f9e3477438760a4fa6 upstream.
The timeout for BULK packets was 300ms which is a long time if other endpoints or devices are waiting for their turn. Changing it to 50ms greatly increased the overall performance for multi-endpoint devices.
--- drivers/usb/host/r8a66597-hcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/host/r8a66597-hcd.c +1 -1
@@ -1274,7 +1274,7 @@ static void set_td_timer(struct r8a66597 time =30 ;break ;default : - time =300 ; + time =50 ;break ; }
PATCH 16/106 usb: r8a66597-hcd: select a different endpoint on timeout
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Chris Brandt <[email protected]>
commit 1f873d857b6c2fefb4dada952674aa01bcfb92bd upstream.
If multiple endpoints on a single device have pending IN URBs and one endpoint times out due to NAKs (perfectly legal), select a different endpoint URB to try.
The existing code only checked to see another device address has pending URBs and ignores other IN endpoints on the current device address. This leads to endpoints never getting serviced if one endpoint is using NAK as a flow control method.
--- drivers/usb/host/r8a66597-hcd.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/usb/host/r8a66597-hcd.c +3 -1
@@ -1790,6 +1790,7 @@ static void r8a66597_td_timer(unsigned l pipe = td->pipe;pipe_stop (r8a66597, pipe); +/* Select a different address or endpoint */ new_td = td; do { list_move_tail(&new_td->queue,
@@ -1799,7 +1800,8 @@ static void r8a66597_td_timer(unsigned l new_td = td;break ; } - }while (td != new_td && td->address == new_td->address); + }while (td != new_td && td->address == new_td->address && + td->pipe->info.epnum == new_td->pipe->info.epnum);start_transfer (r8a66597, new_td);
PATCH 17/106 USB: gadget: dummy_hcd: fix hub-descriptor removable fields
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit d81182ce30dbd497a1e7047d7fda2af040347790 upstream.
Flag the first and only port as removable while also leaving the remaining bits (including the reserved bit zero) unset in accordance with the specifications:
"Within a byte, if no port exists for a given location, the bit field representing the port characteristics shall be 0."
Also add a comment marking the legacy PortPwrCtrlMask field.
--- drivers/usb/gadget/dummy_hcd.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/usb/gadget/dummy_hcd.c +3 -3
@@ -1770,7 +1770,7 @@ ss_hub_descriptor(struct usb_hub_descrip desc->wHubCharacteristics =cpu_to_le16 (0x0001 ); desc->bNbrPorts =1 ; desc->u.ss.bHubHdrDecLat =0x04 ;/* Worst case: 0.4 micro sec*/ - desc->u.ss.DeviceRemovable =0xffff ; + desc->u.ss.DeviceRemovable =0 ; } static inline void
@@ -1781,8 +1781,8 @@ hub_descriptor (struct usb_hub_descripto desc->bDescLength =9 ; desc->wHubCharacteristics =cpu_to_le16 (0x0001 ); desc->bNbrPorts =1 ; - desc->u.hs.DeviceRemovable[0 ] =0xff ; - desc->u.hs.DeviceRemovable[1 ] =0xff ; + desc->u.hs.DeviceRemovable[0 ] =0 ; + desc->u.hs.DeviceRemovable[1 ] =0xff ;/* PortPwrCtrlMask */ } static int dummy_hub_control (
PATCH 18/106 USB: usbip: fix nonconforming hub descriptor
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit ec963b412a54aac8e527708ecad06a6988a86fb4 upstream.
Fix up the root-hub descriptor to accommodate the variable-length DeviceRemovable and PortPwrCtrlMask fields, while marking all ports as removable (and leaving the reserved bit zero unset).
Also add a build-time constraint on VHCI_HC_PORTS which must never be greater than USB_MAXCHILDREN (but this was only enforced through a KConfig constant).
This specifically fixes the descriptor layout whenever VHCI_HC_PORTS is greater than seven (default is 8).
[bwh: Backported to 3.2:
- s/VHCI_HC_PORTS/VHCI_NPORTS/
- Adjust filename, context]
--- drivers/staging/usbip/vhci_hcd.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
drivers/staging/usbip/vhci_hcd.c +8 -3
@@ -248,14 +248,19 @@ done:/* See hub_configure in hub.c */ static inline void hub_descriptor (struct usb_hub_descriptor *desc) { +int width; +memset (desc,0 ,sizeof (*desc)); desc->bDescriptorType =0x29 ; - desc->bDescLength =9 ; desc->wHubCharacteristics = (__force __u16) (__constant_cpu_to_le16 (0x0001 )); + desc->bNbrPorts =VHCI_NPORTS ; - desc->u.hs.DeviceRemovable[0 ] =0xff ; - desc->u.hs.DeviceRemovable[1 ] =0xff ; +BUILD_BUG_ON (VHCI_NPORTS >USB_MAXCHILDREN ); + width = desc->bNbrPorts /8 +1 ; + desc->bDescLength =USB_DT_HUB_NONVAR_SIZE +2 * width; +memset (&desc->u.hs.DeviceRemovable[0 ],0 , width); +memset (&desc->u.hs.DeviceRemovable[width],0xff , width); } static int vhci_hub_control(struct usb_hcd *hcd, u16 typeReq, u16 wValue,
PATCH 19/106 USB: hub: fix SS hub-descriptor handling
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 2c25a2c818023df64463aac3288a9f969491e507 upstream.
A SuperSpeed hub descriptor does not have any variable-length fields so bail out when reading a short descriptor.
This avoids parsing and leaking two bytes of uninitialised slab data through sysfs removable-attributes.
--- drivers/usb/core/hub.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
drivers/usb/core/hub.c +6 -2
@@ -195,8 +195,12 @@ static int get_hub_descriptor(struct usbUSB_REQ_GET_DESCRIPTOR ,USB_DIR_IN |USB_RT_HUB , dtype <<8 ,0 , data, size, USB_CTRL_GET_TIMEOUT); -if (ret >= (USB_DT_HUB_NONVAR_SIZE +2 )) +if (hub_is_superspeed (hdev)) { +if (ret == size) +return ret; + }else if (ret >= (USB_DT_HUB_NONVAR_SIZE +2 )) {return ret; + } }return -EINVAL ; }
@@ -1121,7 +1125,7 @@ static int hub_configure(struct usb_hub/* Request the entire hub descriptor. * hub->descriptor can handle USB_MAXCHILDREN ports, -* but the hub can/will return fewer bytes here. +* but a (non-SS) hub can/will return fewer bytes here. */ ret =get_hub_descriptor (hdev, hub->descriptor);if (ret <0 ) {
PATCH 20/106 USB: hub: fix non-SS hub-descriptor handling
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit bec444cd1c94c48df409a35ad4e5b143c245c3f7 upstream.
Add missing sanity check on the non-SuperSpeed hub-descriptor length in order to avoid parsing and leaking two bytes of uninitialised slab data through sysfs removable-attributes (or a compound-device debug statement).
Note that we only make sure that the DeviceRemovable field is always present (and specifically ignore the unused PortPwrCtrlMask field) in order to continue support any hubs with non-compliant descriptors. As a further safeguard, the descriptor buffer is also cleared.
--- drivers/usb/core/hub.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-)
drivers/usb/core/hub.c +9 -4
@@ -177,7 +177,8 @@ static struct usb_hub *hdev_to_hub(struc }/* USB 2.0 spec Section 11.24.4.5 */ -static int get_hub_descriptor (struct usb_device *hdev,void *data) +static int get_hub_descriptor (struct usb_device *hdev, +struct usb_hub_descriptor *desc) {int i, ret, size;unsigned dtype;
@@ -193,12 +194,16 @@ static int get_hub_descriptor(struct usbfor (i =0 ; i <3 ; i++) { ret =usb_control_msg (hdev,usb_rcvctrlpipe (hdev,0 ),USB_REQ_GET_DESCRIPTOR ,USB_DIR_IN |USB_RT_HUB , - dtype <<8 ,0 , data, size, + dtype <<8 ,0 , desc, size,USB_CTRL_GET_TIMEOUT );if (hub_is_superspeed (hdev)) {if (ret == size)return ret; - }else if (ret >= (USB_DT_HUB_NONVAR_SIZE +2 )) { + }else if (ret >=USB_DT_HUB_NONVAR_SIZE +2 ) { +/* Make sure we have the DeviceRemovable field. */ + size =USB_DT_HUB_NONVAR_SIZE + desc->bNbrPorts /8 +1 ; +if (ret < size) +return -EMSGSIZE ;return ret; } }
@@ -1117,7 +1122,7 @@ static int hub_configure(struct usb_hub }mutex_init (&hub->status_mutex); - hub->descriptor =kmalloc (sizeof (*hub->descriptor),GFP_KERNEL ); + hub->descriptor =kzalloc (sizeof (*hub->descriptor),GFP_KERNEL );if (!hub->descriptor) { ret = -ENOMEM ; goto fail;
PATCH 21/106 USB: hub: fix SS max number of ports
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 93491ced3c87c94b12220dbac0527e1356702179 upstream.
Add define for the maximum number of ports on a SuperSpeed hub as per USB 3.1 spec Table 10-5, and use it when verifying the retrieved hub descriptor.
This specifically avoids benign attempts to update the DeviceRemovable mask for non-existing ports (should we get that far).
[bwh: Backported to 3.2:
- Add maxchild variable in hub_configure(), which was added separately upstream
- Adjust filename]
--- drivers/usb/core/hub.c | 8 +++++++- include/linux/usb/ch11.h | 3 +++ 2 files changed, 10 insertions(+), 1 deletion(-)
drivers/usb/core/hub.c +8 -1
@@ -1108,6 +1108,7 @@ static int hub_configure(struct usb_hubunsigned int pipe;int maxp, ret;char *message ="out of memory" ; +unsigned maxchild; hub->buffer =kmalloc (sizeof (*hub->buffer),GFP_KERNEL );if (!hub->buffer) {
@@ -1136,7 +1137,13 @@ static int hub_configure(struct usb_hubif (ret <0 ) { message ="can't read hub descriptor" ; goto fail; - }else if (hub->descriptor->bNbrPorts >USB_MAXCHILDREN ) { + } + + maxchild =USB_MAXCHILDREN ; +if (hub_is_superspeed (hdev)) + maxchild =min_t (unsigned, maxchild,USB_SS_MAXPORTS ); + +if (hub->descriptor->bNbrPorts > maxchild) { message ="hub has too many ports!" ; ret = -ENODEV ; goto fail;
include/linux/usb/ch11.h +3 -0
@@ -11,6 +11,9 @@#include <linux/types.h> /* __u8 etc */ +/* See USB 3.1 spec Table 10-5 */ +#define USB_SS_MAXPORTS 15 +/* * Hub request types */
PATCH 22/106 mac80211: strictly check mesh address extension mode
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Rajkumar Manoharan <[email protected]>
commit 5667c86acf021e6dcf02584408b4484a273ac68f upstream.
Mesh forwarding path checks for address extension mode to fetch appropriate proxied address and MPP address. Existing condition that looks for 6 address format is not strict enough so that frames with improper values are processed and invalid entries are added into MPP table. Fix that by adding a stricter check before processing the packet.
Per IEEE Std 802.11s-2011 spec. Table 7-6g1 lists address extension mode 0x3 as reserved one. And also Table Table 9-13 does not specify 0x3 as valid address field.
[bwh: Backported to 3.2: add mesh_flags variable in ieee80211_data_to_8023(),
added separately upstream]
--- net/mac80211/rx.c | 3 ++- net/wireless/util.c | 10 ++++++---- 2 files changed, 8 insertions(+), 5 deletions(-)
net/mac80211/rx.c +2 -1
@@ -1959,7 +1959,8 @@ ieee80211_rx_h_mesh_fwding(struct ieee80if (is_multicast_ether_addr (hdr->addr1)) { mpp_addr = hdr->addr3; proxied_addr = mesh_hdr->eaddr1; - }else if (mesh_hdr->flags &MESH_FLAGS_AE_A5_A6 ) { + }else if ((mesh_hdr->flags &MESH_FLAGS_AE ) == +MESH_FLAGS_AE_A5_A6 ) {/* has_a4 already checked in ieee80211_rx_mesh_check */ mpp_addr = hdr->addr4; proxied_addr = mesh_hdr->eaddr2;
net/wireless/util.c +10 -4
@@ -360,12 +360,15 @@ int ieee80211_data_to_8023(struct sk_bufif (iftype ==NL80211_IFTYPE_MESH_POINT ) {struct ieee80211s_hdr *meshdr = (struct ieee80211s_hdr *) (skb->data + hdrlen); +u8 mesh_flags; +/* make sure meshdr->flags is on the linear part */ if (!pskb_may_pull (skb, hdrlen +1 ))return -1 ; -if (meshdr->flags &MESH_FLAGS_AE_A4 ) + mesh_flags = meshdr->flags &MESH_FLAGS_AE ; +if (mesh_flags ==MESH_FLAGS_AE_A4 )return -1 ; -if (meshdr->flags &MESH_FLAGS_AE_A5_A6 ) { +if (mesh_flags ==MESH_FLAGS_AE_A5_A6 ) {skb_copy_bits (skb, hdrlen + offsetof(struct ieee80211s_hdr , eaddr1), dst,ETH_ALEN );
@@ -386,12 +389,15 @@ int ieee80211_data_to_8023(struct sk_bufif (iftype ==NL80211_IFTYPE_MESH_POINT ) {struct ieee80211s_hdr *meshdr = (struct ieee80211s_hdr *) (skb->data + hdrlen); +u8 mesh_flags; +/* make sure meshdr->flags is on the linear part */ if (!pskb_may_pull (skb, hdrlen +1 ))return -1 ; -if (meshdr->flags &MESH_FLAGS_AE_A5_A6 ) + mesh_flags = meshdr->flags &MESH_FLAGS_AE ; +if (mesh_flags ==MESH_FLAGS_AE_A5_A6 )return -1 ; -if (meshdr->flags &MESH_FLAGS_AE_A4 ) +if (mesh_flags ==MESH_FLAGS_AE_A4 )skb_copy_bits (skb, hdrlen + offsetof(struct ieee80211s_hdr , eaddr1), src,ETH_ALEN );
PATCH 23/106 of: fdt: add missing allocation-failure check
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 49e67dd17649b60b4d54966e18ec9c80198227f0 upstream.
The memory allocator passed to __unflatten_device_tree() (e.g. a wrapped kzalloc) can fail so add the missing sanity check to avoid dereferencing a NULL pointer.
---
drivers/of/fdt.c +2 -0
@@ -388,6 +388,8 @@ static void __unflatten_device_tree(stru/* Allocate memory for the expanded device tree */ mem = (unsigned long )dt_alloc (size +4 , __alignof__(struct device_node )); +if (!mem) +return NULL ;memset ((void *)mem,0 , size);
PATCH 24/106 tracing/kprobes: Enforce kprobes teardown after testing
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Gleixner <[email protected]>
commit 30e7d894c1478c88d50ce94ddcdbd7f9763d9cdd upstream.
Enabling the tracer selftest triggers occasionally the warning in text_poke(), which warns when the to be modified page is not marked reserved.
The reason is that the tracer selftest installs kprobes on functions marked __init for testing. These probes are removed after the tests, but that removal schedules the delayed kprobes_optimizer work, which will do the actual text poke. If the work is executed after the init text is freed, then the warning triggers. The bug can be reproduced reliably when the work delay is increased.
Flush the optimizer work and wait for the optimizing/unoptimizing lists to become empty before returning from the kprobes tracer selftest. That ensures that all operations which were queued due to the probes removal have completed.
---
include/linux/kprobes.h +3 -1
@@ -292,7 +292,9 @@ extern int proc_kprobes_optimization_han int write, void __user *buffer, size_t *length, loff_t *ppos);#endif - +extern void wait_for_kprobe_optimizer (void ); +#else +static inline void wait_for_kprobe_optimizer (void ) { }#endif /* CONFIG_OPTPROBES */ /* Get the kprobe at this addr (if any) - called with preemption disabled */
kernel/kprobes.c +1 -1
@@ -598,7 +598,7 @@ static __kprobes void kprobe_optimizer(s }/* Wait for completing optimization and unoptimization */ -static __kprobes void wait_for_kprobe_optimizer (void ) +__kprobes void wait_for_kprobe_optimizer (void ) {if (delayed_work_pending (&optimizing_work))wait_for_completion (&optimizer_comp);
kernel/trace/trace_kprobe.c +5 -0
@@ -2109,6 +2109,11 @@ static __init int kprobe_trace_self_test end:release_all_trace_probes (); +/* +* Wait for the optimizer work to finish. Otherwise it might fiddle +* with probes in already freed __init text. +*/ +wait_for_kprobe_optimizer ();if (warn)pr_cont ("NG: Some tests are failed. Please check them.\n" );else
PATCH 25/106 xhci: workaround for hosts missing CAS bit
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Mathias Nyman <[email protected]>
commit 346e99736c3ce328fd42d678343b70243aca5f36 upstream.
If a device is unplugged and replugged during Sx system suspend some Intel xHC hosts will overwrite the CAS (Cold attach status) flag and no device connection is noticed in resume.
A device in this state can be identified in resume if its link state is in polling or compliance mode, and the current connect status is 0. A device in this state needs to be warm reset.
Intel 100/c230 series PCH specification update Doc #332692-006 Errata #8
Observed on Cherryview and Apollolake as they go into compliance mode if LFPS times out during polling, and re-plugged devices are not discovered at resume.
--- drivers/usb/host/xhci-hub.c | 37 +++++++++++++++++++++++++++++++++++++ drivers/usb/host/xhci-pci.c | 6 ++++++ drivers/usb/host/xhci.h | 3 +++ 3 files changed, 46 insertions(+)
drivers/usb/host/xhci-hub.c +37 -0
@@ -1036,6 +1036,35 @@ int xhci_bus_suspend(struct usb_hcd *hcdreturn 0 ; } +/* +* Workaround for missing Cold Attach Status (CAS) if device re-plugged in S3. +* warm reset a USB3 device stuck in polling or compliance mode after resume. +* See Intel 100/c230 series PCH specification update Doc #332692-006 Errata #8 +*/ +static bool xhci_port_missing_cas_quirk (int port_index, +__le32 __iomem **port_array) +{ +u32 portsc; + + portsc =readl (port_array[port_index]); + +/* if any of these are set we are not stuck */ +if (portsc & (PORT_CONNECT |PORT_CAS )) +return false; + +if (((portsc &PORT_PLS_MASK ) !=XDEV_POLLING ) && + ((portsc &PORT_PLS_MASK ) !=XDEV_COMP_MODE )) +return false; + +/* clear wakeup/change bits, and do a warm port reset */ + portsc &= ~(PORT_RWC_BITS |PORT_CEC |PORT_WAKE_BITS ); + portsc |=PORT_WR ; +writel (portsc, port_array[port_index]); +/* flush write */ +readl (port_array[port_index]); +return true; +} +int xhci_bus_resume (struct usb_hcd *hcd) {struct xhci_hcd *xhci =hcd_to_xhci (hcd);
@@ -1070,6 +1099,14 @@ int xhci_bus_resume(struct usb_hcd *hcd)int slot_id; temp =xhci_readl (xhci, port_array[port_index]); + +/* warm reset CAS limited ports stuck in polling/compliance */ +if ((xhci->quirks &XHCI_MISSING_CAS ) && + (hcd->speed >=HCD_USB3 ) && +xhci_port_missing_cas_quirk (port_index, port_array)) { +xhci_dbg (xhci,"reset stuck port %d\n" , port_index); +continue ; + }if (DEV_SUPERSPEED (temp)) temp &= ~(PORT_RWC_BITS |PORT_CEC |PORT_WAKE_BITS );else
drivers/usb/host/xhci-pci.c +6 -0
@@ -42,6 +42,7 @@#define PCI_DEVICE_ID_INTEL_SUNRISEPOINT_LP_XHCI 0x9d2f#define PCI_DEVICE_ID_INTEL_BROXTON_M_XHCI 0x0aa8#define PCI_DEVICE_ID_INTEL_BROXTON_B_XHCI 0x1aa8 +#define PCI_DEVICE_ID_INTEL_APL_XHCI 0x5aa8static const char hcd_name[] ="xhci_hcd" ;
@@ -141,6 +142,11 @@ static void xhci_pci_quirks(struct devic pdev->device == PCI_DEVICE_ID_INTEL_BROXTON_B_XHCI)) { xhci->quirks |=XHCI_PME_STUCK_QUIRK ; } +if (pdev->vendor ==PCI_VENDOR_ID_INTEL && + (pdev->device ==PCI_DEVICE_ID_INTEL_CHERRYVIEW_XHCI || + pdev->device ==PCI_DEVICE_ID_INTEL_APL_XHCI )) + xhci->quirks |=XHCI_MISSING_CAS ; +if (pdev->vendor ==PCI_VENDOR_ID_ETRON && pdev->device ==PCI_DEVICE_ID_ASROCK_P67 ) { xhci->quirks |=XHCI_RESET_ON_RESUME ;
drivers/usb/host/xhci.h +3 -0
@@ -280,6 +280,8 @@ struct xhci_op_regs {#define XDEV_U0 (0x0 << 5)#define XDEV_U2 (0x2 << 5)#define XDEV_U3 (0x3 << 5) +#define XDEV_POLLING (0x7 << 5) +#define XDEV_COMP_MODE (0xa << 5)#define XDEV_RESUME (0xf << 5)/* true: port has power (see HCC_PPC) */ #define PORT_POWER (1 << 9)
@@ -1499,6 +1501,7 @@ struct xhci_hcd {#define XHCI_SLOW_SUSPEND (1 << 17)#define XHCI_SPURIOUS_WAKEUP (1 << 18)#define XHCI_PME_STUCK_QUIRK (1 << 20) +#define XHCI_MISSING_CAS (1 << 24)unsigned int num_active_eps;unsigned int limit_active_eps;/* There are two roothubs to keep track of bus suspend info for */
PATCH 26/106 usb: xhci: apply XHCI_PME_STUCK_QUIRK to Intel Apollo Lake
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Wan Ahmad Zainie <[email protected]>
commit 6c97cfc1a097b1e0786c836e92b7a72b4d031e25 upstream.
Intel Apollo Lake also requires XHCI_PME_STUCK_QUIRK. Adding its PCI ID to quirk.
--- drivers/usb/host/xhci-pci.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/usb/host/xhci-pci.c +2 -1
@@ -139,7 +139,8 @@ static void xhci_pci_quirks(struct devic pdev->device ==PCI_DEVICE_ID_INTEL_SUNRISEPOINT_H_XHCI || pdev->device ==PCI_DEVICE_ID_INTEL_CHERRYVIEW_XHCI || pdev->device ==PCI_DEVICE_ID_INTEL_BROXTON_M_XHCI || - pdev->device == PCI_DEVICE_ID_INTEL_BROXTON_B_XHCI)) { + pdev->device ==PCI_DEVICE_ID_INTEL_BROXTON_B_XHCI || + pdev->device == PCI_DEVICE_ID_INTEL_APL_XHCI)) { xhci->quirks |= XHCI_PME_STUCK_QUIRK; } if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
PATCH 27/106 xhci: apply PME_STUCK_QUIRK and MISSING_CAS quirk for Denverton
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Mathias Nyman <[email protected]>
commit a0c16630d35a874e82bdf2088f58ecaca1024315 upstream.
Intel Denverton microserver is Atom based and need the PME and CAS quirks as well.
--- drivers/usb/host/xhci-pci.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/usb/host/xhci-pci.c +5 -2
@@ -43,6 +43,7 @@#define PCI_DEVICE_ID_INTEL_BROXTON_M_XHCI 0x0aa8#define PCI_DEVICE_ID_INTEL_BROXTON_B_XHCI 0x1aa8#define PCI_DEVICE_ID_INTEL_APL_XHCI 0x5aa8 +#define PCI_DEVICE_ID_INTEL_DNV_XHCI 0x19d0static const char hcd_name[] ="xhci_hcd" ;
@@ -140,12 +141,14 @@ static void xhci_pci_quirks(struct devic pdev->device ==PCI_DEVICE_ID_INTEL_CHERRYVIEW_XHCI || pdev->device ==PCI_DEVICE_ID_INTEL_BROXTON_M_XHCI || pdev->device ==PCI_DEVICE_ID_INTEL_BROXTON_B_XHCI || - pdev->device == PCI_DEVICE_ID_INTEL_APL_XHCI)) { + pdev->device ==PCI_DEVICE_ID_INTEL_APL_XHCI || + pdev->device == PCI_DEVICE_ID_INTEL_DNV_XHCI)) { xhci->quirks |= XHCI_PME_STUCK_QUIRK; }if (pdev->vendor ==PCI_VENDOR_ID_INTEL && (pdev->device ==PCI_DEVICE_ID_INTEL_CHERRYVIEW_XHCI || - pdev->device ==PCI_DEVICE_ID_INTEL_APL_XHCI )) + pdev->device ==PCI_DEVICE_ID_INTEL_APL_XHCI || + pdev->device ==PCI_DEVICE_ID_INTEL_DNV_XHCI )) xhci->quirks |=XHCI_MISSING_CAS ; if (pdev->vendor == PCI_VENDOR_ID_ETRON &&
PATCH 28/106 usb: host: xhci-mem: allocate zeroed Scratchpad Buffer
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Peter Chen <[email protected]>
commit 7480d912d549f414e0ce39331870899e89a5598c upstream.
According to xHCI ch4.20 Scratchpad Buffers, the Scratchpad Buffer needs to be zeroed.
...
The following operations take place to allocate Scratchpad Buffers to the xHC:
...
b. Software clears the Scratchpad Buffer to '0'
--- drivers/usb/host/xhci-mem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/host/xhci-mem.c +1 -1
@@ -1591,7 +1591,7 @@ static int scratchpad_alloc(struct xhci_if (!xhci->scratchpad) goto fail_sp; - xhci->scratchpad->sp_array =dma_alloc_coherent (dev, + xhci->scratchpad->sp_array =dma_zalloc_coherent (dev, num_sp *sizeof (u64), &xhci->scratchpad->sp_dma, flags);if (!xhci->scratchpad->sp_array)
PATCH 29/106 usb: host: xhci: simplify irq handler return
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Felipe Balbi <[email protected]>
commit 76a35293b901915c5dcb4a87a4a0da8d7caf39fe upstream.
Instead of having several return points, let's use a local variable and a single place to return. This makes the code slightly easier to read.
--- drivers/usb/host/xhci-ring.c | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-)
drivers/usb/host/xhci-ring.c +17 -15
@@ -2642,29 +2642,30 @@ static int xhci_handle_event(struct xhciirqreturn_t xhci_irq (struct usb_hcd *hcd) {struct xhci_hcd *xhci =hcd_to_xhci (hcd); -u32 status;union xhci_trb *trb; -u64 temp_64;union xhci_trb *event_ring_deq; +irqreturn_t ret =IRQ_NONE ;dma_addr_t deq; +u64 temp_64; +u32 status;spin_lock (&xhci->lock); trb = xhci->event_ring->dequeue;/* Check if the xHC generated the interrupt, or the irq is shared */ status =xhci_readl (xhci, &xhci->op_regs->status); -if (status ==0xffffffff ) - goto hw_died; - -if (!(status &STS_EINT )) { -spin_unlock (&xhci->lock); -return IRQ_NONE ; +if (status ==0xffffffff ) { + ret =IRQ_HANDLED ; + goto out; } + +if (!(status &STS_EINT )) + goto out; +if (status &STS_FATAL ) {xhci_warn (xhci,"WARNING: Host System Error\n" );xhci_halt (xhci); -hw_died: -spin_unlock (&xhci->lock); -return IRQ_HANDLED ; + ret =IRQ_HANDLED ; + goto out; }/*
@@ -2694,9 +2695,8 @@ hw_died: temp_64 =xhci_read_64 (xhci, &xhci->ir_set->erst_dequeue);xhci_write_64 (xhci, temp_64 |ERST_EHB , &xhci->ir_set->erst_dequeue); -spin_unlock (&xhci->lock); - -return IRQ_HANDLED ; + ret =IRQ_HANDLED ; + goto out; } event_ring_deq = xhci->event_ring->dequeue;
@@ -2721,10 +2721,12 @@ hw_died:/* Clear the event handler busy flag (RW1C); event ring is empty. */ temp_64 |=ERST_EHB ;xhci_write_64 (xhci, temp_64, &xhci->ir_set->erst_dequeue); + ret =IRQ_HANDLED ; +out:spin_unlock (&xhci->lock); -return IRQ_HANDLED ; +return ret; }irqreturn_t xhci_msi_irq (int irq,struct usb_hcd *hcd)
PATCH 30/106 USB: xhci: fix lock-inversion problem
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Alan Stern <[email protected]>
commit 63aea0dbab90a2461faaae357cbc8cfd6c8de9fe upstream.
With threaded interrupts, bottom-half handlers are called with interrupts enabled. Therefore they can't safely use spin_lock(); they have to use spin_lock_irqsave(). Lockdep warns about a violation occurring in xhci_irq():
=========================================================
[ INFO: possible irq lock inversion dependency detected ] 4.11.0-rc8-dbg+ #1 Not tainted
---------------------------------------------------------
swapper/7/0 just changed the state of lock:
(&(&ehci->lock)->rlock){-.-...}, at: [<ffffffffa0130a69>]ehci_hrtimer_func+0x29/0xc0 [ehci_hcd]
but this lock took another, HARDIRQ-unsafe lock in the past:
(hcd_urb_list_lock){+.....}
and interrupts could create inverse lock ordering between them.
other info that might help us debug this:
Possible interrupt unsafe locking scenario:
CPU0 CPU1
---- ----
lock(hcd_urb_list_lock);
local_irq_disable();
lock(&(&ehci->lock)->rlock);
lock(hcd_urb_list_lock);
<Interrupt>
lock(&(&ehci->lock)->rlock);*** DEADLOCK ***
no locks held by swapper/7/0.
the shortest dependencies between 2nd lock and 1st lock:
-> (hcd_urb_list_lock){+.....} ops: 252 {
HARDIRQ-ON-W at:
__lock_acquire+0x602/0x1280
lock_acquire+0xd5/0x1c0
_raw_spin_lock+0x2f/0x40
usb_hcd_unlink_urb_from_ep+0x1b/0x60 [usbcore]
xhci_giveback_urb_in_irq.isra.45+0x70/0x1b0 [xhci_hcd]
finish_td.constprop.60+0x1d8/0x2e0 [xhci_hcd]
xhci_irq+0xdd6/0x1fa0 [xhci_hcd]
usb_hcd_irq+0x26/0x40 [usbcore]
irq_forced_thread_fn+0x2f/0x70
irq_thread+0x149/0x1d0
kthread+0x113/0x150
ret_from_fork+0x2e/0x40This patch fixes the problem.
--- drivers/usb/host/xhci-ring.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/usb/host/xhci-ring.c +3 -2
@@ -2645,11 +2645,12 @@ irqreturn_t xhci_irq(struct usb_hcd *hcdunion xhci_trb *trb;union xhci_trb *event_ring_deq;irqreturn_t ret =IRQ_NONE ; +unsigned long flags;dma_addr_t deq;u64 temp_64;u32 status; -spin_lock (&xhci->lock); +spin_lock_irqsave (&xhci->lock, flags); trb = xhci->event_ring->dequeue;/* Check if the xHC generated the interrupt, or the irq is shared */ status =xhci_readl (xhci, &xhci->op_regs->status);
@@ -2724,7 +2725,7 @@ irqreturn_t xhci_irq(struct usb_hcd *hcd ret =IRQ_HANDLED ; out: -spin_unlock (&xhci->lock); +spin_unlock_irqrestore (&xhci->lock, flags);return ret; }
PATCH 31/106 usb: musb: tusb6010_omap: Do not reset the other direction's packet size
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Peter Ujfalusi <[email protected]>
commit 6df2b42f7c040d57d9ecb67244e04e905ab87ac6 upstream.
We have one register for each EP to set the maximum packet size for both TX and RX.
If for example an RX programming would happen before the previous TX transfer finishes we would reset the TX packet side.
To fix this issue, only modify the TX or RX part of the register.
--- drivers/usb/musb/tusb6010_omap.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-)
drivers/usb/musb/tusb6010_omap.c +9 -4
@@ -237,6 +237,7 @@ static int tusb_omap_dma_program(structu32 dma_remaining;int src_burst, dst_burst;u16 csr; +u32 psize;int ch;s8 dmareq;s8 sync_dev;
@@ -408,15 +409,19 @@ static int tusb_omap_dma_program(structif (chdat->tx) {/* Send transfer_packet_sz packets at a time */ -musb_writel (ep_conf,TUSB_EP_MAX_PACKET_SIZE_OFFSET , - chdat->transfer_packet_sz); + psize =musb_readl (ep_conf,TUSB_EP_MAX_PACKET_SIZE_OFFSET ); + psize &= ~0x7ff ; + psize |= chdat->transfer_packet_sz; +musb_writel (ep_conf,TUSB_EP_MAX_PACKET_SIZE_OFFSET , psize);musb_writel (ep_conf,TUSB_EP_TX_OFFSET ,TUSB_EP_CONFIG_XFR_SIZE (chdat->transfer_len)); }else {/* Receive transfer_packet_sz packets at a time */ -musb_writel (ep_conf,TUSB_EP_MAX_PACKET_SIZE_OFFSET , - chdat->transfer_packet_sz <<16 ); + psize =musb_readl (ep_conf,TUSB_EP_MAX_PACKET_SIZE_OFFSET ); + psize &= ~(0x7ff <<16 ); + psize |= (chdat->transfer_packet_sz <<16 ); +musb_writel (ep_conf,TUSB_EP_MAX_PACKET_SIZE_OFFSET , psize);musb_writel (ep_conf,TUSB_EP_RX_OFFSET ,TUSB_EP_CONFIG_XFR_SIZE (chdat->transfer_len));
PATCH 32/106 drivers: char: mem: Check for address space wraparound with mmap()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Julius Werner <[email protected]>
commit b299cde245b0b76c977f4291162cf668e087b408 upstream.
/dev/mem currently allows mmap() mappings that wrap around the end of the physical address space, which should probably be illegal. It circumvents the existing STRICT_DEVMEM permission check because the loop immediately terminates (as the start address is already higher than the end address). On the x86_64 architecture it will then cause a panic (from the BUG(start >= end) in arch/x86/mm/pat.c:reserve_memtype()).
This patch adds an explicit check to make sure offset + size will not wrap around in the physical address type.
--- drivers/char/mem.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/char/mem.c +5 -0
@@ -322,6 +322,11 @@ static const struct vm_operations_structstatic int mmap_mem (struct file *file,struct vm_area_struct *vma) {size_t size = vma->vm_end - vma->vm_start; +phys_addr_t offset = (phys_addr_t )vma->vm_pgoff <<PAGE_SHIFT ; + +/* It's illegal to wrap around the end of the physical address space. */ +if (offset + (phys_addr_t )size < offset) +return -EINVAL ;if (!valid_mmap_phys_addr_range (vma->vm_pgoff, size))return -EINVAL ;
PATCH 33/106 watchdog: pcwd_usb: fix NULL-deref at probe
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit 46c319b848268dab3f0e7c4a5b6e9146d3bca8a4 upstream.
Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious device lack endpoints.
--- drivers/watchdog/pcwd_usb.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/watchdog/pcwd_usb.c +3 -0
@@ -641,6 +641,9 @@ static int usb_pcwd_probe(struct usb_intreturn -ENODEV ; } +if (iface_desc->desc.bNumEndpoints <1 ) +return -ENODEV ; +/* check out the endpoint: it has to be Interrupt & IN */ endpoint = &iface_desc->endpoint[0 ].desc;
PATCH 34/106 powerpc/mm: Fix virt_addr_valid() etc. on 64-bit hash
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Michael Ellerman <[email protected]>
commit e41e53cd4fe331d0d1f06f8e4ed7e2cc63ee2c34 upstream.
virt_addr_valid() is supposed to tell you if it's OK to call virt_to_page() on an address. What this means in practice is that it should only return true for addresses in the linear mapping which are backed by a valid PFN.
We are failing to properly check that the address is in the linear mapping, because virt_to_pfn() will return a valid looking PFN for more or less any address. That bug is actually caused by __pa(), used in virt_to_pfn().
eg: __pa(0xc000000000010000) = 0x10000 # Good
__pa(0xd000000000010000) = 0x10000 # Bad!
__pa(0x0000000000010000) = 0x10000 # Bad!This started happening after commit bdbc29c19b26 ("powerpc: Work around gcc miscompilation of __pa() on 64-bit") (Aug 2013), where we changed the definition of __pa() to work around a GCC bug. Prior to that we subtracted PAGE_OFFSET from the value passed to __pa(), meaning __pa() of a 0xd or 0x0 address would give you something bogus back.
Until we can verify if that GCC bug is no longer an issue, or come up with another solution, this commit does the minimal fix to make virt_addr_valid() work, by explicitly checking that the address is in the linear mapping region.
--- arch/powerpc/include/asm/page.h | 12 ++++++++++++ 1 file changed, 12 insertions(+)
arch/powerpc/include/asm/page.h +12 -0
@@ -118,7 +118,19 @@ extern phys_addr_t kernstart_addr;#define virt_to_page (kaddr) pfn_to_page(__pa(kaddr) >> PAGE_SHIFT)#define pfn_to_kaddr (pfn) __va((pfn) << PAGE_SHIFT) + +#ifdef CONFIG_PPC_BOOK3S_64 +/* +* On hash the vmalloc and other regions alias to the kernel region when passed +* through __pa(), which virt_to_pfn() uses. That means virt_addr_valid() can +* return true for some vmalloc addresses, which is incorrect. So explicitly +* check that the address is in the kernel region. +*/ +#define virt_addr_valid (kaddr) (REGION_ID(kaddr) == KERNEL_REGION_ID && \ + pfn_valid(__pa(kaddr) >> PAGE_SHIFT)) +#else #define virt_addr_valid (kaddr) pfn_valid(__pa(kaddr) >> PAGE_SHIFT) +#endif /* * On Book-E parts we need __va to parse the device tree and we can't
PATCH 35/106 KVM: X86: Fix read out-of-bounds vulnerability in kvm pio emulation
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Wanpeng Li <[email protected]>
commit cbfc6c9184ce71b52df4b1d82af5afc81a709178 upstream.
Huawei folks reported a read out-of-bounds vulnerability in kvm pio emulation.
- "inb" instruction to access PIT Mod/Command register (ioport 0x43, write only, a read should be ignored) in guest can get a random number.
- "rep insb" instruction to access PIT register port 0x43 can control memcpy() in emulator_pio_in_emulated() to copy max 0x400 bytes but only read 1 bytes, which will disclose the unimportant kernel memory in host but no crash.
The similar test program below can reproduce the read out-of-bounds vulnerability:
void hexdump(void *mem, unsigned int len)
{
unsigned int i, j;
for(i = 0; i < len + ((len % HEXDUMP_COLS) ? (HEXDUMP_COLS - len % HEXDUMP_COLS) : 0); i++)
{
/* print offset */
if(i % HEXDUMP_COLS == 0)
{
printf("0x%06x: ", i);
}
/* print hex data */
if(i < len)
{
printf("%02x ", 0xFF & ((char*)mem)[i]);
}
else /* end of block, just aligning for ASCII dump */
{
printf(" ");
}
/* print ASCII dump */
if(i % HEXDUMP_COLS == (HEXDUMP_COLS - 1))
{
for(j = i - (HEXDUMP_COLS - 1); j <= i; j++)
{
if(j >= len) /* end of block, not really printing */
{
putchar(' ');
}
else if(isprint(((char*)mem)[j])) /* printable char */
{
putchar(0xFF & ((char*)mem)[j]);
}
else /* other char */
{
putchar('.');
}
}
putchar('\n');
}
}
}int main(void)
{
int i;
if (iopl(3))
{
err(1, "set iopl unsuccessfully\n");
return -1;
}
static char buf[0x40];
/* test ioport 0x40,0x41,0x42,0x43,0x44,0x45 */
memset(buf, 0xab, sizeof(buf));
asm volatile("push %rdi;");
asm volatile("mov %0, %%rdi;"::"q"(buf));
asm volatile ("mov $0x40, %rdx;");
asm volatile ("in %dx,%al;");
asm volatile ("stosb;");
asm volatile ("mov $0x41, %rdx;");
asm volatile ("in %dx,%al;");
asm volatile ("stosb;");
asm volatile ("mov $0x42, %rdx;");
asm volatile ("in %dx,%al;");
asm volatile ("stosb;");
asm volatile ("mov $0x43, %rdx;");
asm volatile ("in %dx,%al;");
asm volatile ("stosb;");
asm volatile ("mov $0x44, %rdx;");
asm volatile ("in %dx,%al;");
asm volatile ("stosb;");
asm volatile ("mov $0x45, %rdx;");
asm volatile ("in %dx,%al;");
asm volatile ("stosb;");
asm volatile ("pop %rdi;");
hexdump(buf, 0x40);
printf("\n");
/* ins port 0x40 */
memset(buf, 0xab, sizeof(buf));
asm volatile("push %rdi;");
asm volatile("mov %0, %%rdi;"::"q"(buf));
asm volatile ("mov $0x20, %rcx;");
asm volatile ("mov $0x40, %rdx;");
asm volatile ("rep insb;");
asm volatile ("pop %rdi;");
hexdump(buf, 0x40);
printf("\n");
/* ins port 0x43 */
memset(buf, 0xab, sizeof(buf));
asm volatile("push %rdi;");
asm volatile("mov %0, %%rdi;"::"q"(buf));
asm volatile ("mov $0x20, %rcx;");
asm volatile ("mov $0x43, %rdx;");
asm volatile ("rep insb;");
asm volatile ("pop %rdi;");
hexdump(buf, 0x40);
printf("\n");
return 0;
}The vcpu->arch.pio_data buffer is used by both in/out instrutions emulation w/o clear after using which results in some random datas are left over in the buffer. Guest reads port 0x43 will be ignored since it is write only, however, the function kernel_pio() can't distigush this ignore from successfully reads data from device's ioport. There is no new data fill the buffer from port 0x43, however, emulator_pio_in_emulated() will copy the stale data in the buffer to the guest unconditionally. This patch fixes it by clearing the buffer before in instruction emulation to avoid to grant guest the stale data in the buffer.
In addition, string I/O is not supported for in kernel device. So there is no iteration to read ioport %RCX times for string I/O. The function kernel_pio() just reads one round, and then copy the io size * %RCX to the guest unconditionally, actually it copies the one round ioport data w/ other random datas which are left over in the vcpu->arch.pio_data buffer to the guest. This patch fixes it by introducing the string I/O support for in kernel device in order to grant the right ioport datas to the guest.
Before the patch:
0x000000: fe 38 93 93 ff ff ab ab .8......0x000008: ab ab ab ab ab ab ab ab ........0x000010: ab ab ab ab ab ab ab ab ........0x000018: ab ab ab ab ab ab ab ab ........0x000020: ab ab ab ab ab ab ab ab ........0x000028: ab ab ab ab ab ab ab ab ........0x000030: ab ab ab ab ab ab ab ab ........0x000038: ab ab ab ab ab ab ab ab ........
0x000000: f6 00 00 00 00 00 00 00 ........0x000008: 00 00 00 00 00 00 00 00 ........0x000010: 00 00 00 00 4d 51 30 30 ....MQ000x000018: 30 30 20 33 20 20 20 20 00 30x000020: ab ab ab ab ab ab ab ab ........0x000028: ab ab ab ab ab ab ab ab ........0x000030: ab ab ab ab ab ab ab ab ........0x000038: ab ab ab ab ab ab ab ab ........
0x000000: f6 00 00 00 00 00 00 00 ........0x000008: 00 00 00 00 00 00 00 00 ........0x000010: 00 00 00 00 4d 51 30 30 ....MQ000x000018: 30 30 20 33 20 20 20 20 00 30x000020: ab ab ab ab ab ab ab ab ........0x000028: ab ab ab ab ab ab ab ab ........0x000030: ab ab ab ab ab ab ab ab ........0x000038: ab ab ab ab ab ab ab ab ........
After the patch:
0x000000: 1e 02 f8 00 ff ff ab ab ........0x000008: ab ab ab ab ab ab ab ab ........0x000010: ab ab ab ab ab ab ab ab ........0x000018: ab ab ab ab ab ab ab ab ........0x000020: ab ab ab ab ab ab ab ab ........0x000028: ab ab ab ab ab ab ab ab ........0x000030: ab ab ab ab ab ab ab ab ........0x000038: ab ab ab ab ab ab ab ab ........
0x000000: d2 e2 d2 df d2 db d2 d7 ........0x000008: d2 d3 d2 cf d2 cb d2 c7 ........0x000010: d2 c4 d2 c0 d2 bc d2 b8 ........0x000018: d2 b4 d2 b0 d2 ac d2 a8 ........0x000020: ab ab ab ab ab ab ab ab ........0x000028: ab ab ab ab ab ab ab ab ........0x000030: ab ab ab ab ab ab ab ab ........0x000038: ab ab ab ab ab ab ab ab ........
0x000000: 00 00 00 00 00 00 00 00 ........0x000008: 00 00 00 00 00 00 00 00 ........0x000010: 00 00 00 00 00 00 00 00 ........0x000018: 00 00 00 00 00 00 00 00 ........0x000020: ab ab ab ab ab ab ab ab ........0x000028: ab ab ab ab ab ab ab ab ........0x000030: ab ab ab ab ab ab ab ab ........0x000038: ab ab ab ab ab ab ab ab ........
--- arch/x86/kvm/x86.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-)
arch/x86/kvm/x86.c +15 -9
@@ -4380,16 +4380,20 @@ emul_write:static int kernel_pio (struct kvm_vcpu *vcpu,void *pd) { -/* TODO: String I/O for in kernel device */ -int r; +int r =0 , i; -if (vcpu->arch.pio.in) - r =kvm_io_bus_read (vcpu->kvm,KVM_PIO_BUS , vcpu->arch.pio.port, - vcpu->arch.pio.size, pd); -else - r =kvm_io_bus_write (vcpu->kvm,KVM_PIO_BUS , - vcpu->arch.pio.port, vcpu->arch.pio.size, - pd); +for (i =0 ; i < vcpu->arch.pio.count; i++) { +if (vcpu->arch.pio.in) + r =kvm_io_bus_read (vcpu->kvm,KVM_PIO_BUS , vcpu->arch.pio.port, + vcpu->arch.pio.size, pd); +else + r =kvm_io_bus_write (vcpu->kvm,KVM_PIO_BUS , + vcpu->arch.pio.port, vcpu->arch.pio.size, + pd); +if (r) +break ; + pd += vcpu->arch.pio.size; + }return r; }
@@ -4403,6 +4407,8 @@ static int emulator_pio_in_emulated(struif (vcpu->arch.pio.count) goto data_avail; +memset (vcpu->arch.pio_data,0 , size * count); +trace_kvm_pio (0 , port, size, count); vcpu->arch.pio.port = port;
PATCH 36/106 KVM: x86: fix use of uninitialized memory as segment descriptor in emulator.
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Gleb Natapov <[email protected]>
commit 378a8b099fc207ddcb91b19a8c1457667e0af398 upstream.
If VMX reports segment as unusable, zero descriptor passed by the emulator before returning. Such descriptor will be considered not present by the emulator.
--- arch/x86/kvm/x86.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/x86/kvm/x86.c +3 -1
@@ -4611,8 +4611,10 @@ static bool emulator_get_segment(structkvm_get_segment (emul_to_vcpu (ctxt), &var, seg); *selector = var.selector; -if (var.unusable) +if (var.unusable) { +memset (desc,0 ,sizeof (*desc));return false; + }if (var.g) var.limit >>=12 ;
PATCH 37/106 KVM: x86: zero base3 of unusable segments
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Radim Krčmář <[email protected]>
commit f0367ee1d64d27fa08be2407df5c125442e885e3 upstream.
Static checker noticed that base3 could be used uninitialized if the segment was not present (useable). Random stack values probably would not pass VMCS entry checks.
--- arch/x86/kvm/x86.c | 2 ++ 1 file changed, 2 insertions(+)
arch/x86/kvm/x86.c +2 -0
@@ -4613,6 +4613,8 @@ static bool emulator_get_segment(structif (var.unusable) {memset (desc,0 ,sizeof (*desc)); +if (base3) + *base3 =0 ;return false; }
PATCH 38/106 osf_wait4(): fix infoleak
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
commit a8c39544a6eb2093c04afd5005b6192bd0e880c6 upstream.
failing sys_wait4() won't fill struct rusage...
--- arch/alpha/kernel/osf_sys.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
arch/alpha/kernel/osf_sys.c +4 -2
@@ -1026,8 +1026,10 @@ SYSCALL_DEFINE4(osf_wait4, pid_t, pid, iif (!access_ok (VERIFY_WRITE , ur,sizeof (*ur)))return -EFAULT ; - err =0 ; - err |=put_user (status, ustatus); + err =put_user (status, ustatus); +if (ret <0 ) +return err ? err : ret; + err |=__put_user (r.ru_utime.tv_sec, &ur->ru_utime.tv_sec); err |=__put_user (r.ru_utime.tv_usec, &ur->ru_utime.tv_usec); err |=__put_user (r.ru_stime.tv_sec, &ur->ru_stime.tv_sec);
PATCH 39/106 ext4: keep existing extra fields when inode expands
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Konstantin Khlebnikov <[email protected]>
commit 887a9730614727c4fff7cb756711b190593fc1df upstream.
ext4_expand_extra_isize() should clear only space between old and new size.
--- fs/ext4/inode.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
fs/ext4/inode.c +3 -2
@@ -4637,8 +4637,9 @@ static int ext4_expand_extra_isize(struc/* No extended attributes present */ if (!ext4_test_inode_state (inode,EXT4_STATE_XATTR ) || header->h_magic !=cpu_to_le32 (EXT4_XATTR_MAGIC )) { -memset ((void *)raw_inode +EXT4_GOOD_OLD_INODE_SIZE ,0 , - new_extra_isize); +memset ((void *)raw_inode +EXT4_GOOD_OLD_INODE_SIZE + +EXT4_I (inode)->i_extra_isize,0 , + new_extra_isize -EXT4_I (inode)->i_extra_isize);EXT4_I (inode)->i_extra_isize = new_extra_isize;return 0 ; }
PATCH 40/106 i2c: i2c-tiny-usb: fix buffer not being DMA capable
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sebastian Reichel <[email protected]>
commit 5165da5923d6c7df6f2927b0113b2e4d9288661e upstream.
Since v4.9 i2c-tiny-usb generates the below call trace and longer works, since it can't communicate with the USB device. The reason is, that since v4.9 the USB stack checks, that the buffer it should transfer is DMA capable. This was a requirement since v2.2 days, but it usually worked nevertheless.
[ 17.504959] ------------[ cut here ]------------ [ 17.505488] WARNING: CPU: 0 PID: 93 at drivers/usb/core/hcd.c:1587 usb_hcd_map_urb_for_dma+0x37c/0x570 [ 17.506545] transfer buffer not dma capable [ 17.507022] Modules linked in: [ 17.507370] CPU: 0 PID: 93 Comm: i2cdetect Not tainted 4.11.0-rc8+ #10 [ 17.508103] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014 [ 17.509039] Call Trace: [ 17.509320] ? dump_stack+0x5c/0x78 [ 17.509714] ? __warn+0xbe/0xe0 [ 17.510073] ? warn_slowpath_fmt+0x5a/0x80 [ 17.510532] ? nommu_map_sg+0xb0/0xb0 [ 17.510949] ? usb_hcd_map_urb_for_dma+0x37c/0x570 [ 17.511482] ? usb_hcd_submit_urb+0x336/0xab0 [ 17.511976] ? wait_for_completion_timeout+0x12f/0x1a0 [ 17.512549] ? wait_for_completion_timeout+0x65/0x1a0 [ 17.513125] ? usb_start_wait_urb+0x65/0x160 [ 17.513604] ? usb_control_msg+0xdc/0x130 [ 17.514061] ? usb_xfer+0xa4/0x2a0 [ 17.514445] ? __i2c_transfer+0x108/0x3c0 [ 17.514899] ? i2c_transfer+0x57/0xb0 [ 17.515310] ? i2c_smbus_xfer_emulated+0x12f/0x590 [ 17.515851] ? _raw_spin_unlock_irqrestore+0x11/0x20 [ 17.516408] ? i2c_smbus_xfer+0x125/0x330 [ 17.516876] ? i2c_smbus_xfer+0x125/0x330 [ 17.517329] ? i2cdev_ioctl_smbus+0x1c1/0x2b0 [ 17.517824] ? i2cdev_ioctl+0x75/0x1c0 [ 17.518248] ? do_vfs_ioctl+0x9f/0x600 [ 17.518671] ? vfs_write+0x144/0x190 [ 17.519078] ? SyS_ioctl+0x74/0x80 [ 17.519463] ? entry_SYSCALL_64_fastpath+0x1e/0xad [ 17.519959] ---[ end trace d047c04982f5ac50 ]---
--- drivers/i2c/busses/i2c-tiny-usb.c | 25 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-)
drivers/i2c/busses/i2c-tiny-usb.c +21 -4
@@ -159,22 +159,39 @@ static int usb_read(struct i2c_adapter * int value, int index, void *data, int len) { struct i2c_tiny_usb *dev = (struct i2c_tiny_usb *)adapter->algo_data; +void *dmadata =kmalloc (len,GFP_KERNEL ); +int ret; + +if (!dmadata) +return -ENOMEM ;/* do control transfer */ -return usb_control_msg (dev->usb_dev,usb_rcvctrlpipe (dev->usb_dev,0 ), + ret =usb_control_msg (dev->usb_dev,usb_rcvctrlpipe (dev->usb_dev,0 ), cmd,USB_TYPE_VENDOR |USB_RECIP_INTERFACE | -USB_DIR_IN , value, index, data, len,2000 ); +USB_DIR_IN , value, index, dmadata, len,2000 ); + +memcpy (data, dmadata, len); +kfree (dmadata); +return ret; }static int usb_write (struct i2c_adapter *adapter,int cmd,int value,int index,void *data,int len) {struct i2c_tiny_usb *dev = (struct i2c_tiny_usb *)adapter->algo_data; +void *dmadata =kmemdup (data, len,GFP_KERNEL ); +int ret; + +if (!dmadata) +return -ENOMEM ;/* do control transfer */ -return usb_control_msg (dev->usb_dev,usb_sndctrlpipe (dev->usb_dev,0 ), + ret =usb_control_msg (dev->usb_dev,usb_sndctrlpipe (dev->usb_dev,0 ), cmd,USB_TYPE_VENDOR |USB_RECIP_INTERFACE , - value, index, data, len,2000 ); + value, index, dmadata, len,2000 ); + +kfree (dmadata); +return ret; }static void i2c_tiny_usb_free (struct i2c_tiny_usb *dev)
PATCH 41/106 crypto: gcm - wait for crypto op not signal safe
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Gilad Ben-Yossef <[email protected]>
commit f3ad587070d6bd961ab942b3fd7a85d00dfc934b upstream.
crypto_gcm_setkey() was using wait_for_completion_interruptible() to wait for completion of async crypto op but if a signal occurs it may return before DMA ops of HW crypto provider finish, thus corrupting the data buffer that is kfree'ed in this case.
Resolve this by using wait_for_completion() instead.
--- crypto/gcm.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
crypto/gcm.c +2 -4
@@ -140,10 +140,8 @@ static int crypto_gcm_setkey(struct cryp err =crypto_ablkcipher_encrypt (&data->req);if (err == -EINPROGRESS || err == -EBUSY ) { - err =wait_for_completion_interruptible ( - &data->result.completion); -if (!err) - err = data->result.err; +wait_for_completion (&data->result.completion); + err = data->result.err; }if (err)
PATCH 42/106 ALSA: hda - apply STAC_9200_DELL_M22 quirk for Dell Latitude D430
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Tsoy <[email protected]>
commit 1fc2e41f7af4572b07190f9dec28396b418e9a36 upstream.
This model is actually called 92XXM2-8 in Windows driver. But since pin configs for M22 and M28 are identical, just reuse M22 quirk.
Fixes external microphone (tested) and probably docking station ports (not tested).
--- sound/pci/hda/patch_sigmatel.c | 2 ++ 1 file changed, 2 insertions(+)
sound/pci/hda/patch_sigmatel.c +2 -0
@@ -1448,6 +1448,8 @@ static const struct snd_pci_quirk stac92 "Dell Inspiron 1501", STAC_9200_DELL_M26),SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x01f6 ,"unknown Dell" ,STAC_9200_DELL_M26 ), +SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x0201 , +"Dell Latitude D430" ,STAC_9200_DELL_M22 ),/* Panasonic */ SND_PCI_QUIRK(0x10f7, 0x8338, "Panasonic CF-74", STAC_9200_PANASONIC),/* Gateway machines needs EAPD to be set on resume */
PATCH 43/106 block: fix an error code in add_partition()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 7bd897cfce1eb373892d35d7f73201b0f9b221c4 upstream.
We don't set an error code on this path. It means that we return NULL instead of an error pointer and the caller does a NULL dereference.
--- fs/partitions/check.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
fs/partitions/check.c +3 -1
@@ -457,8 +457,10 @@ struct hd_struct *add_partition(struct gif (info) {struct partition_meta_info *pinfo =alloc_part_info (disk); -if (!pinfo) +if (!pinfo) { + err = -ENOMEM ; goto out_free_stats; + }memcpy (pinfo, info,sizeof (*info)); p->info = pinfo; }
PATCH 44/106 libceph: NULL deref on crush_decode() error path
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 293dffaad8d500e1a5336eeb90d544cf40d4fbd8 upstream.
If there is not enough space then ceph_decode_32_safe() does a goto bad. We need to return an error code in that situation. The current code returns ERR_PTR(0) which is NULL. The callers are not expecting that and it results in a NULL dereference.
--- net/ceph/osdmap.c | 1 + 1 file changed, 1 insertion(+)
net/ceph/osdmap.c +1 -0
@@ -268,6 +268,7 @@ static struct crush_map *crush_decode(vou32 yes;struct crush_rule *r; + err = -EINVAL ;ceph_decode_32_safe (p, end, yes, bad);if (!yes) { dout("crush_decode NO rule %d off %x %p to %p\n",
PATCH 45/106 drm/gma500/psb: Actually use VBT mode when it is found
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Patrik Jakobsson <[email protected]>
commit 82bc9a42cf854fdf63155759c0aa790bd1f361b0 upstream.
With LVDS we were incorrectly picking the pre-programmed mode instead of the prefered mode provided by VBT. Make sure we pick the VBT mode if one is provided. It is likely that the mode read-out code is still wrong but this patch fixes the immediate problem on most machines.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=78562
--- drivers/staging/gma500/psb_intel_lvds.c | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-)
drivers/staging/gma500/psb_intel_lvds.c +11 -7
@@ -792,20 +792,23 @@ void psb_intel_lvds_init(struct drm_deviif (scan->type &DRM_MODE_TYPE_PREFERRED ) { mode_dev->panel_fixed_mode =drm_mode_duplicate (dev, scan); +DRM_DEBUG_KMS ("Using mode from DDC\n" ); goto out;/* FIXME: check for quirks */ } }/* Failed to get EDID, what about VBT? do we need this? */ -if (mode_dev->vbt_mode) +if (dev_priv->lfp_lvds_vbt_mode) { mode_dev->panel_fixed_mode = -drm_mode_duplicate (dev, mode_dev->vbt_mode); +drm_mode_duplicate (dev, dev_priv->lfp_lvds_vbt_mode); -if (!mode_dev->panel_fixed_mode) -if (dev_priv->lfp_lvds_vbt_mode) - mode_dev->panel_fixed_mode = -drm_mode_duplicate (dev, - dev_priv->lfp_lvds_vbt_mode); +if (mode_dev->panel_fixed_mode) { + mode_dev->panel_fixed_mode->type |= +DRM_MODE_TYPE_PREFERRED ; +DRM_DEBUG_KMS ("Using mode from VBT\n" ); + goto out; + } + }/* * If we didn't get EDID, try checking if the panel is already turned
@@ -822,6 +825,7 @@ void psb_intel_lvds_init(struct drm_deviif (mode_dev->panel_fixed_mode) { mode_dev->panel_fixed_mode->type |=DRM_MODE_TYPE_PREFERRED ; +DRM_DEBUG_KMS ("Using pre-programmed mode\n" ); goto out;/* FIXME: check for quirks */ } }
PATCH 46/106 dmaengine: ep93xx: Always start from BASE0
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Sverdlin <[email protected]>
commit 0037ae47812b1f431cc602100d1d51f37d77b61e upstream.
The current buffer is being reset to zero on device_free_chan_resources() but not on device_terminate_all(). It could happen that HW is restarted and expects BASE0 to be used, but the driver is not synchronized and will start from BASE1. One solution is to reset the buffer explicitly in m2p_hw_setup().
--- drivers/dma/ep93xx_dma.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/dma/ep93xx_dma.c +2 -0
@@ -300,6 +300,8 @@ static int m2p_hw_setup(struct ep93xx_dm | M2P_CONTROL_ENABLE;m2p_set_control (edmac, control); + edmac->buffer =0 ; +return 0 ; }
PATCH 47/106 netfilter: ctnetlink: fix incorrect nf_ct_put during hash resize
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Liping Zhang <[email protected]>
commit fefa92679dbe0c613e62b6c27235dcfbe9640ad1 upstream.
If nf_conntrack_htable_size was adjusted by the user during the ct dump operation, we may invoke nf_ct_put twice for the same ct, i.e. the "last" ct. This will cause the ct will be freed but still linked in hash buckets.
It's very easy to reproduce the problem by the following commands:
# while : ; do echo $RANDOM > /proc/sys/net/netfilter/nf_conntrack_buckets done # while : ; do conntrack -L done # iperf -s 127.0.0.1 & # iperf -c 127.0.0.1 -P 60 -t 36000
After a while, the system will hang like this:
NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bash:20184] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [iperf:20382]
...
So at last if we find cb->args[1] is equal to "last", this means hash resize happened, then we can set cb->args[1] to 0 to fix the above issue.
--- net/netfilter/nf_conntrack_netlink.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
net/netfilter/nf_conntrack_netlink.c +6 -1
@@ -731,8 +731,13 @@ restart: } out:spin_unlock_bh (&nf_conntrack_lock); -if (last) +if (last) { +/* nf ct hash resize happened, now clear the leftover. */ +if ((struct nf_conn *)cb->args[1 ] == last) + cb->args[1 ] =0 ; +nf_ct_put (last); + }return skb->len; }
PATCH 48/106 ASoC: Fix use-after-free at card unregistration
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 4efda5f2130da033aeedc5b3205569893b910de2 upstream.
soc_cleanup_card_resources() call snd_card_free() at the last of its procedure. This turned out to lead to a use-after-free. PCM runtimes have been already removed via soc_remove_pcm_runtimes(), while it's dereferenced later in soc_pcm_free() called via snd_card_free().
The fix is simple: just move the snd_card_free() call to the beginning of the whole procedure. This also gives another benefit: it guarantees that all operations have been shut down before actually releasing the resources, which was racy until now.
--- sound/soc/soc-core.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
sound/soc/soc-core.c +3 -2
@@ -1574,6 +1574,9 @@ static int soc_cleanup_card_resources(stflush_delayed_work_sync (&rtd->delayed_work); } +/* free the ALSA card at first; this syncs with pending operations */ +snd_card_free (card->snd_card); +/* remove auxiliary devices */ for (i =0 ; i < card->num_aux_devs; i++)soc_remove_aux_dev (card, i);
@@ -1590,9 +1593,7 @@ static int soc_cleanup_card_resources(stsnd_soc_dapm_free (&card->dapm);kfree (card->rtd); -snd_card_free (card->snd_card);return 0 ; - }/* removes a socdev */
PATCH 49/106 scsi: qla2xxx: don't disable a not previously enabled PCI device
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Johannes Thumshirn <[email protected]>
commit ddff7ed45edce4a4c92949d3c61cd25d229c4a14 upstream.
When pci_enable_device() or pci_enable_device_mem() fail in qla2x00_probe_one() we bail out but do a call to pci_disable_device(). This causes the dev_WARN_ON() in pci_disable_device() to trigger, as the device wasn't enabled previously.
So instead of taking the 'probe_out' error path we can directly return *iff* one of the pci_enable_device() calls fails.
Additionally rename the 'probe_out' goto label's name to the more descriptive 'disable_device'.
--- drivers/scsi/qla2xxx/qla_os.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/scsi/qla2xxx/qla_os.c +4 -4
@@ -1999,10 +1999,10 @@ qla2x00_probe_one(struct pci_dev *pdev,if (mem_only) {if (pci_enable_device_mem (pdev)) - goto probe_out; +return ret; }else {if (pci_enable_device (pdev)) - goto probe_out; +return ret; }/* This may fail but that's ok */
@@ -2012,7 +2012,7 @@ qla2x00_probe_one(struct pci_dev *pdev,if (!ha) {ql_log_pci (ql_log_fatal, pdev,0x0009 ,"Unable to allocate memory for ha.\n" ); - goto probe_out; + goto disable_device; }ql_dbg_pci (ql_dbg_init, pdev,0x000a ,"Memory allocated for ha=%p.\n" , ha);
@@ -2433,7 +2433,7 @@ probe_hw_failed:kfree (ha); ha =NULL ; -probe_out: +disable_device:pci_disable_device (pdev);return ret; }
PATCH 50/106 net: ethernet: ax88796: don't call free_irq without request_irq first
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Uwe Kleine-König <[email protected]>
commit 82533ad9a1ce3a7a6863849a552c2cc041b55e0d upstream.
The function ax_init_dev (which is called only from the driver's .probe function) calls free_irq in the error path without having requested the irq in the first place. So drop the free_irq call in the error path.
--- drivers/net/ethernet/8390/ax88796.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)
drivers/net/ethernet/8390/ax88796.c +2 -5
@@ -769,13 +769,13 @@ static int ax_init_dev(struct net_device ret =ax_mii_init (dev);if (ret) - goto out_irq; + goto err_out;ax_NS8390_init (dev,0 ); ret =register_netdev (dev);if (ret) - goto out_irq; + goto err_out; netdev_info(dev, "%dbit, irq %d, %lx, MAC: %pM\n", ei_local->word16 ? 16 : 8, dev->irq, dev->base_addr,
@@ -783,9 +783,6 @@ static int ax_init_dev(struct net_devicereturn 0 ; - out_irq: -/* cleanup irq */ -free_irq (dev->irq, dev); err_out:return ret; }
PATCH 51/106 ext4: fix data corruption for mmap writes
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit a056bdaae7a181f7dcc876cfab2f94538e508709 upstream.
mpage_submit_page() can race with another process growing i_size and writing data via mmap to the written-back page. As mpage_submit_page() samples i_size too early, it may happen that ext4_bio_write_page() zeroes out too large tail of the page and thus corrupts user data.
Fix the problem by sampling i_size only after the page has been write-protected in page tables by clear_page_dirty_for_io() call.
[bwh: Backported to 3.2: The writeback path is very different here and
it needs to read i_size long before calling clear_page_dirty_for_io(). So read it twice and skip the page if it changed.]
--- fs/ext4/inode.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
fs/ext4/inode.c +23 -3
@@ -1344,7 +1344,6 @@ static int mpage_da_submit_io(struct mpaint ret =0 , err, nr_pages, i;struct inode *inode = mpd->inode;struct address_space *mapping = inode->i_mapping; -loff_t size =i_size_read (inode);unsigned int len, block_start;struct buffer_head *bh, *page_bufs =NULL ;int journal_data =ext4_should_journal_data (inode);
@@ -1370,6 +1369,7 @@ static int mpage_da_submit_io(struct mpafor (i =0 ; i < nr_pages; i++) {int commit_write =0 , skip_page =0 ;struct page *page = pvec.pages[i]; +loff_t size =i_size_read (inode); index = page->index;if (index > end)
@@ -1443,11 +1443,31 @@ static int mpage_da_submit_io(struct mpaif (skip_page) goto skip_page; +clear_page_dirty_for_io (page); +/* +* We have to be very careful here! Nothing protects +* writeback path against i_size changes and the page +* can be writeably mapped into page tables. So an +* application can be growing i_size and writing data +* through mmap while writeback runs. +* clear_page_dirty_for_io() write-protects our page in +* page tables and the page cannot get written to again +* until we release page lock. So only after +* clear_page_dirty_for_io() we are safe to sample +* i_size for ext4_bio_write_page() to zero-out tail of +* the written page. We rely on the barrier provided by +* TestClearPageDirty in clear_page_dirty_for_io() to +* make sure i_size is really sampled only after page +* tables are updated. +*/ +if (size !=i_size_read (inode)) { +set_page_dirty (page); + goto skip_page; + } +if (commit_write)/* mark the buffer_heads as dirty & uptodate */ block_commit_write (page,0 , len); - -clear_page_dirty_for_io (page);/* * Delalloc doesn't support data journalling, * but eventually maybe we'll lift this
PATCH 52/106 ext4: fix fdatasync(2) after extent manipulation operations
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Jan Kara <[email protected]>
commit 67a7d5f561f469ad2fa5154d2888258ab8e6df7c upstream.
Currently, extent manipulation operations such as hole punch, range zeroing, or extent shifting do not record the fact that file data has changed and thus fdatasync(2) has a work to do. As a result if we crash e.g. after a punch hole and fdatasync, user can still possibly see the punched out data after journal replay. Test generic/392 fails due to these problems.
Fix the problem by properly marking that file data has changed in these operations.
[bwh: Backported to 3.2: Only the punch-hole operation is supported, and
it's in extents.c.]
---
fs/ext4/extents.c +2 -0
@@ -5023,6 +5023,8 @@ out:ext4_orphan_del (handle, inode); inode->i_mtime = inode->i_ctime =ext4_current_time (inode);ext4_mark_inode_dirty (handle, inode); +if (err >=0 ) +ext4_update_inode_fsync_trans (handle, inode,1 );ext4_journal_stop (handle);return err; }
PATCH 53/106 net: phy: fix marvell phy status reading
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Russell King <[email protected]>
commit 898805e0cdf7fd860ec21bf661d3a0285a3defbd upstream.
The Marvell driver incorrectly provides phydev->lp_advertising as the logical and of the link partner's advert and our advert. This is incorrect - this field is supposed to store the link parter's unmodified advertisment.
This allows ethtool to report the correct link partner auto-negotiation status.
--- drivers/net/phy/marvell.c | 2 -- 1 file changed, 2 deletions(-)
drivers/net/phy/marvell.c +0 -2
@@ -653,8 +653,6 @@ static int marvell_read_status(struct phif (adv <0 )return adv; - lpa &= adv; -if (status &MII_M1011_PHY_STATUS_FULLDUPLEX ) phydev->duplex =DUPLEX_FULL ;else
PATCH 54/106 usb: gadget: f_mass_storage: Serialize wake and sleep execution
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Thinh Nguyen <[email protected]>
commit dc9217b69dd6089dcfeb86ed4b3c671504326087 upstream.
f_mass_storage has a memorry barrier issue with the sleep and wake functions that can cause a deadlock. This results in intermittent hangs during MSC file transfer. The host will reset the device after receiving no response to resume the transfer. This issue is seen when dwc3 is processing 2 transfer-in-progress events at the same time, invoking completion handlers for CSW and CBW. Also this issue occurs depending on the system timing and latency.
To increase the chance to hit this issue, you can force dwc3 driver to wait and process those 2 events at once by adding a small delay (~100us) in dwc3_check_event_buf() whenever the request is for CSW and read the event count again. Avoid debugging with printk and ftrace as extra delays and memory barrier will mask this issue.
Scenario which can lead to failure:
-----------------------------------
1) The main thread sleeps and waits for the next command in get_next_command().
2) bulk_in_complete() wakes up main thread for CSW.
3) bulk_out_complete() tries to wake up the running main thread for CBW.
4) thread_wakeup_needed is not loaded with correct value in sleep_thread().
5) Main thread goes to sleep again.
The pattern is shown below. Note the 2 critical variables.
* common->thread_wakeup_needed
* bh->state
CPU 0 (sleep_thread) CPU 1 (wakeup_thread) ============================== =============================== bh->state = BH_STATE_FULL; smp_wmb(); thread_wakeup_needed = 0; thread_wakeup_needed = 1; smp_rmb(); if (bh->state != BH_STATE_FULL) sleep again ...
As pointed out by Alan Stern, this is an R-pattern issue. The issue can be seen when there are two wakeups in quick succession. The thread_wakeup_needed can be overwritten in sleep_thread, and the read of the bh->state maybe reordered before the write to thread_wakeup_needed.
This patch applies full memory barrier smp_mb() in both sleep_thread() and wakeup_thread() to ensure the order which the thread_wakeup_needed and bh->state are written and loaded.
However, a better solution in the future would be to use wait_queue method that takes care of managing memory barrier between waker and waiter.
--- drivers/usb/gadget/f_mass_storage.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
drivers/usb/gadget/f_mass_storage.c +11 -2
@@ -512,7 +512,11 @@ static int fsg_set_halt(struct fsg_dev */* Caller must hold fsg->lock */ static void wakeup_thread (struct fsg_common *common) { -smp_wmb ();/* ensure the write of bh->state is complete */ +/* +* Ensure the reading of thread_wakeup_needed +* and the writing of bh->state are completed +*/ +smp_mb ();/* Tell the main thread that something has happened */ common->thread_wakeup_needed =1 ;if (common->thread_task)
@@ -732,7 +736,12 @@ static int sleep_thread(struct fsg_commo }__set_current_state (TASK_RUNNING ); common->thread_wakeup_needed =0 ; -smp_rmb ();/* ensure the latest bh->state is visible */ + +/* +* Ensure the writing of thread_wakeup_needed +* and the reading of bh->state are completed +*/ +smp_mb ();return rc; }
PATCH 55/106 ipv6: xfrm: Handle errors reported by xfrm6_find_1stfragopt()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
commit 6e80ac5cc992ab6256c3dae87f7e57db15e1a58c upstream.
xfrm6_find_1stfragopt() may now return an error code and we must not treat it as a length.
--- net/ipv6/xfrm6_mode_ro.c | 2 ++ net/ipv6/xfrm6_mode_transport.c | 2 ++ 2 files changed, 4 insertions(+)
net/ipv6/xfrm6_mode_ro.c +2 -0
@@ -48,6 +48,8 @@ static int xfrm6_ro_output(struct xfrm_s iph =ipv6_hdr (skb); hdr_len = x->type->hdr_offset (x, skb, &prevhdr); +if (hdr_len <0 ) +return hdr_len;skb_set_mac_header (skb, (prevhdr - x->props.header_len) - skb->data);skb_set_network_header (skb, -x->props.header_len); skb->transport_header = skb->network_header + hdr_len;
net/ipv6/xfrm6_mode_transport.c +2 -0
@@ -28,6 +28,8 @@ static int xfrm6_transport_output(struct iph =ipv6_hdr (skb); hdr_len = x->type->hdr_offset (x, skb, &prevhdr); +if (hdr_len <0 ) +return hdr_len;skb_set_mac_header (skb, (prevhdr - x->props.header_len) - skb->data);skb_set_network_header (skb, -x->props.header_len); skb->transport_header = skb->network_header + hdr_len;
PATCH 56/106 drivers: char: mem: Fix wraparound check to allow mappings up to the end
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Julius Werner <[email protected]>
commit 32829da54d9368103a2f03269a5120aa9ee4d5da upstream.
A recent fix to /dev/mem prevents mappings from wrapping around the end of physical address space. However, the check was written in a way that also prevents a mapping reaching just up to the end of physical address space, which may be a valid use case (especially on 32-bit systems). This patch fixes it by checking the last mapped address (instead of the first address behind that) for overflow.
--- drivers/char/mem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/char/mem.c +1 -1
@@ -325,7 +325,7 @@ static int mmap_mem(struct file *file, sphys_addr_t offset = (phys_addr_t )vma->vm_pgoff <<PAGE_SHIFT ;/* It's illegal to wrap around the end of the physical address space. */ -if (offset + (phys_addr_t )size < offset) +if (offset + (phys_addr_t )size -1 < offset)return -EINVAL ;if (!valid_mmap_phys_addr_range (vma->vm_pgoff, size))
PATCH 57/106 alarmtimer: Prevent overflow of relative timers
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Gleixner <[email protected]>
commit f4781e76f90df7aec400635d73ea4c35ee1d4765 upstream.
Andrey reported a alartimer related RCU stall while fuzzing the kernel with syzkaller.
The reason for this is an overflow in ktime_add() which brings the resulting time into negative space and causes immediate expiry of the timer. The following rearm with a small interval does not bring the timer back into positive space due to the same issue.
This results in a permanent firing alarmtimer which hogs the CPU.
Use ktime_add_safe() instead which detects the overflow and clamps the result to KTIME_SEC_MAX.
---
kernel/time/alarmtimer.c +2 -2
@@ -419,7 +419,7 @@ u64 alarm_forward(struct alarm *alarm, k overrun++; } - alarm->node.expires =ktime_add (alarm->node.expires, interval); + alarm->node.expires =ktime_add_safe (alarm->node.expires, interval);return overrun; }
@@ -604,7 +604,7 @@ static int alarm_timer_set(struct k_itimktime_t now; now = alarm_bases[timr->it.alarm.alarmtimer.type].gettime (); - exp =ktime_add (now, exp); + exp =ktime_add_safe (now, exp); }alarm_start (&timr->it.alarm.alarmtimer, exp);
PATCH 58/106 alarmtimer: Rate limit periodic intervals
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Gleixner <[email protected]>
commit ff86bf0c65f14346bf2440534f9ba5ac232c39a0 upstream.
The alarmtimer code has another source of potentially rearming itself too fast. Interval timers with a very samll interval have a similar CPU hog effect as the previously fixed overflow issue.
The reason is that alarmtimers do not implement the normal protection against this kind of problem which the other posix timer use:
timer expires -> queue signal -> deliver signal -> rearm timer
This scheme brings the rearming under scheduler control and prevents permanently firing timers which hog the CPU.
Bringing this scheme to the alarm timer code is a major overhaul because it lacks all the necessary mechanisms completely.
So for a quick fix limit the interval to one jiffie. This is not problematic in practice as alarmtimers are usually backed by an RTC for suspend which have 1 second resolution. It could be therefor argued that the resolution of this clock should be set to 1 second in general, but that's outside the scope of this fix.
[bwh: Backported to 3.2:
- Use ktime_to_ns()/ktime_set() as ktime_t is not scalar
- Adjust context]
--- kernel/time/alarmtimer.c | 8 ++++++++ 1 file changed, 8 insertions(+)
kernel/time/alarmtimer.c +8 -0
@@ -598,6 +598,14 @@ static int alarm_timer_set(struct k_itim/* start the timer */ timr->it.alarm.interval =timespec_to_ktime (new_setting->it_interval); + +/* +* Rate limit to the tick as a hot fix to prevent DOS. Will be +* mopped up later. +*/ +if (ktime_to_ns (timr->it.alarm.interval) <TICK_NSEC ) + timr->it.alarm.interval =ktime_set (1 ,0 ); + exp =timespec_to_ktime (new_setting->it_value);/* Convert (if necessary) to absolute time */ if (flags !=TIMER_ABSTIME ) {
PATCH 59/106 rc-core: race condition during ir_raw_event_register()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sean Young <[email protected]>
commit 963761a0b2e85663ee4a5630f72930885a06598a upstream.
A rc device can call ir_raw_event_handle() after rc_allocate_device(), but before rc_register_device() has completed. This is racey because rcdev->raw is set before rcdev->raw->thread has a valid value.
--- drivers/media/rc/ir-raw.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
drivers/media/rc/ir-raw.c +8 -5
@@ -225,7 +225,7 @@ void ir_raw_event_handle(struct rc_dev * {unsigned long flags; -if (!dev->raw) +if (!dev->raw || !dev->raw->thread)return ;spin_lock_irqsave (&dev->raw->lock, flags);
@@ -252,6 +252,7 @@ int ir_raw_event_register(struct rc_dev {int rc;struct ir_raw_handler *handler; +struct task_struct *thread;if (!dev)return -EINVAL ;
@@ -269,14 +270,16 @@ int ir_raw_event_register(struct rc_dev goto out;spin_lock_init (&dev->raw->lock); - dev->raw->thread =kthread_run (ir_raw_event_thread, dev->raw, -"rc%ld" , dev->devno); + thread =kthread_run (ir_raw_event_thread, dev->raw,"rc%ld" , + dev->devno); -if (IS_ERR (dev->raw->thread)) { - rc =PTR_ERR (dev->raw->thread); +if (IS_ERR (thread)) { + rc =PTR_ERR (thread); goto out; } + dev->raw->thread = thread; +mutex_lock (&ir_raw_handler_lock);list_add_tail (&dev->raw->list, &ir_raw_client_list);list_for_each_entry (handler, &ir_raw_handler_list, list)
PATCH 60/106 net: add kfree_skb_list()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
Extracted from upstream commit bd8a7036c06c "gre: fix a possible skb leak".
This patch adds a kfree_skb_list() helper.
---
include/linux/skbuff.h +1 -0
@@ -534,6 +534,7 @@ static inline struct rtable *skb_rtable( }extern void kfree_skb (struct sk_buff *skb); +extern void kfree_skb_list (struct sk_buff *segs);extern void consume_skb (struct sk_buff *skb);extern void __kfree_skb (struct sk_buff *skb); extern struct sk_buff *__alloc_skb(unsigned int size,
net/core/skbuff.c +12 -8
@@ -277,15 +277,8 @@ EXPORT_SYMBOL(dev_alloc_skb);static void skb_drop_list (struct sk_buff **listp) { -struct sk_buff *list = *listp; - +kfree_skb_list (*listp); *listp =NULL ; - -do { -struct sk_buff *this = list; - list = list->next; -kfree_skb (this); - }while (list); }static inline void skb_drop_fraglist (struct sk_buff *skb)
@@ -436,6 +429,17 @@ void kfree_skb(struct sk_buff *skb) }EXPORT_SYMBOL (kfree_skb); +void kfree_skb_list (struct sk_buff *segs) +{ +while (segs) { +struct sk_buff *next = segs->next; + +kfree_skb (segs); + segs = next; + } +} +EXPORT_SYMBOL (kfree_skb_list); +/** * consume_skb - free an skbuff * @skb: buffer to free
PATCH 61/106 ipv6: Fix leak in ipv6_gso_segment().
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: "David S. Miller" <[email protected]>
commit e3e86b5119f81e5e2499bea7ea1ebe8ac6aab789 upstream.
If ip6_find_1stfragopt() fails and we return an error we have to free up 'segs' because nobody else is going to.
--- net/ipv6/af_inet6.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/ipv6/af_inet6.c +3 -1
@@ -824,8 +824,10 @@ static struct sk_buff *ipv6_gso_segment( sizeof(*ipv6h));if (proto ==IPPROTO_UDP ) {int err =ip6_find_1stfragopt (skb, &prevhdr); -if (err <0 ) +if (err <0 ) { +kfree_skb_list (segs);return ERR_PTR (err); + } fptr = (struct frag_hdr *)(skb_network_header (skb) + err); fptr->frag_off =htons (offset);
PATCH 62/106 net: ping: do not abuse udp_poll()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
commit 77d4b1d36926a9b8387c6b53eeba42bcaaffcea3 upstream.
Alexander reported various KASAN messages triggered in recent kernels
The problem is that ping sockets should not use udp_poll() in the first place, and recent changes in UDP stack finally exposed this old bug.
[bwh: Backported to 3.2:
- Drop IPv6 bits
- Adjust context]
---
net/ipv4/af_inet.c +1 -1
@@ -1032,7 +1032,7 @@ static struct inet_protosw inetsw_array[ .type = SOCK_DGRAM, .protocol = IPPROTO_ICMP, .prot = &ping_prot, - .ops = &inet_dgram_ops, + .ops = &inet_sockraw_ops, .no_check = UDP_CSUM_DEFAULT, .flags = INET_PROTOSW_REUSE, },
PATCH 63/106 vb2: fix plane index sanity check in vb2_plane_cookie()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Zhaowei Yuan <[email protected]>
commit a9ae4692eda4b99f85757b15d60971ff78a0a0e2 upstream.
It's also invalid when plane_no is equal to vb->num_planes
--- drivers/media/video/videobuf2-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/video/videobuf2-core.c +1 -1
@@ -754,7 +754,7 @@ void *vb2_plane_cookie(struct vb2_buffer {struct vb2_queue *q = vb->vb2_queue; -if (plane_no > vb->num_planes) +if (plane_no >= vb->num_planes)return NULL ;return call_memop (q, plane_no, cookie, vb->planes[plane_no].mem_priv);
PATCH 64/106 vb2: Fix an off by one error in 'vb2_plane_vaddr'
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Christophe JAILLET <[email protected]>
commit 5ebb6dd36c9f5fb37b1077b393c254d70a14cb46 upstream.
We should ensure that 'plane_no' is '< vb->num_planes' as done in 'vb2_plane_cookie' just a few lines below.
--- drivers/media/video/videobuf2-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/video/videobuf2-core.c +1 -1
@@ -731,7 +731,7 @@ void *vb2_plane_vaddr(struct vb2_buffer {struct vb2_queue *q = vb->vb2_queue; -if (plane_no > vb->num_planes) +if (plane_no >= vb->num_planes)return NULL ;return call_memop (q, plane_no, vaddr, vb->planes[plane_no].mem_priv);
PATCH 65/106 net: ethoc: enable NAPI before poll may be scheduled
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Max Filippov <[email protected]>
commit d220b942a4b6a0640aee78841608f4aa5e8e185e upstream.
ethoc_reset enables device interrupts, ethoc_interrupt may schedule a NAPI poll before NAPI is enabled in the ethoc_open, which results in device being unable to send or receive anything until it's closed and reopened. In case the device is flooded with ingress packets it may be unable to recover at all.
Move napi_enable above ethoc_reset in the ethoc_open to fix that.
--- drivers/net/ethernet/ethoc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/ethoc.c +2 -1
@@ -703,6 +703,8 @@ static int ethoc_open(struct net_deviceif (ret)return ret; +napi_enable (&priv->napi); +ethoc_init_ring (priv, dev->mem_start);ethoc_reset (priv);
@@ -715,7 +717,6 @@ static int ethoc_open(struct net_device }phy_start (priv->phy); -napi_enable (&priv->napi);if (netif_msg_ifup (priv)) { dev_info(&dev->dev, "I/O: %08lx Memory: %08lx-%08lx\n",
PATCH 66/106 drm/vmwgfx: Handle vmalloc() failure in vmw_local_fifo_reserve()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit f0c62e9878024300319ba2438adc7b06c6b9c448 upstream.
If vmalloc() fails then we need to a bit of cleanup before returning.
--- drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c +2 -0
@@ -368,6 +368,8 @@ void *vmw_fifo_reserve(struct vmw_privatreturn fifo_state->static_buffer; else { fifo_state->dynamic_buffer =vmalloc (bytes); +if (!fifo_state->dynamic_buffer) + goto out_err;return fifo_state->dynamic_buffer; } }
PATCH 67/106 perf probe: Fix examples section of documentation
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: SeongJae Park <[email protected]>
commit d89269a89ebb6a74512f3f40e89cd12017f60a75 upstream.
An example in perf-probe documentation for pattern of function name based probe addition is not providing example command for that case.
This commit fixes the example to give appropriate example command.
--- tools/perf/Documentation/perf-probe.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
tools/perf/Documentation/perf-probe.txt +6 -2
@@ -170,9 +170,13 @@ Add a probe on schedule() function 12th or ./perf probe --add='schedule:12 cpu' - this will add one or more probes which has the name start with "schedule". +Add one or more probes which has the name start with "schedule". - Add probes on lines in schedule() function which calls update_rq_clock(). + ./perf probe schedule* + or + ./perf probe --add='schedule*' + +Add probes on lines in schedule() function which calls update_rq_clock(). ./perf probe 'schedule;update_rq_clock*' or
PATCH 68/106 perf script: Fix outdated comment for perf-trace-python
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: SeongJae Park <[email protected]>
commit c76132dc5182776b98e946d674cb41c421661ea9 upstream.
Script generated by the '--gen-script' option contains an outdated comment. It mentions a 'perf-trace-python' document while it has been renamed to 'perf-script-python'. Fix it.
--- tools/perf/util/scripting-engines/trace-event-python.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/perf/util/scripting-engines/trace-event-python.c +1 -1
@@ -465,7 +465,7 @@ static int python_generate_script(constfprintf (ofp,"# be retrieved using Python functions of the form " "common_*(context).\n" ); -fprintf (ofp,"# See the perf-trace-python Documentation for the list " +fprintf (ofp,"# See the perf-script-python Documentation for the list " "of available functions.\n\n" );fprintf (ofp,"import os\n" );
PATCH 69/106 perf script: Fix documentation errors
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: SeongJae Park <[email protected]>
commit 34d4453dac257be53c21abf2f713c992fb692b5c upstream.
This commit fixes two errors in documents for perf-script-python and perf-script-perl as below:
- /sys/kernel/debug/tracing events -> /sys/kernel/debug/tracing/events/
- trace_handled -> trace_unhandled
--- tools/perf/Documentation/perf-script-perl.txt | 2 +- tools/perf/Documentation/perf-script-python.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
tools/perf/Documentation/perf-script-perl.txt +1 -1
@@ -39,7 +39,7 @@ EVENT HANDLERS When perf script is invoked using a trace script, a user-defined 'handler function' is called for each event in the trace. If there's no handler function defined for a given event type, the event is -ignored (or passed to a 'trace_handled' function, see below) and the +ignored (or passed to a 'trace_unhandled' function, see below) and the next event is processed. Most of the event's field values are passed as arguments to the
tools/perf/Documentation/perf-script-python.txt +2 -2
@@ -321,7 +321,7 @@ So those are the essential steps in writ process can be generalized to any tracepoint or set of tracepoints you're interested in - basically find the tracepoint(s) you're interested in by looking at the list of available events shown by -'perf list' and/or look in /sys/kernel/debug/tracing events for +'perf list' and/or look in /sys/kernel/debug/tracing/events/ for detailed event and field info, record the corresponding trace data using 'perf record', passing it the list of interesting events, generate a skeleton script using 'perf script -g python' and modify the
@@ -439,7 +439,7 @@ EVENT HANDLERS When perf script is invoked using a trace script, a user-defined 'handler function' is called for each event in the trace. If there's no handler function defined for a given event type, the event is -ignored (or passed to a 'trace_handled' function, see below) and the +ignored (or passed to a 'trace_unhandled' function, see below) and the next event is processed. Most of the event's field values are passed as arguments to the
PATCH 70/106 perf script python: Fix wrong code snippets in documentation
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: SeongJae Park <[email protected]>
commit 26ddb8722df865aa67fbe459107d2f3f8e5c6829 upstream.
This commit fixes wrong code snippets for trace_begin() and trace_end() function example definition.
--- tools/perf/Documentation/perf-script-python.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/perf/Documentation/perf-script-python.txt +2 -2
@@ -534,7 +534,7 @@ can implement a set of optional function gives scripts a chance to do setup tasks: ---- -def trace_begin: +def trace_begin(): pass ----
@@ -543,7 +543,7 @@ def trace_begin: as display results: ---- -def trace_end: +def trace_end(): pass ----
PATCH 71/106 perf script python: Updated trace_unhandled() signature
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: SeongJae Park <[email protected]>
commit 1bf8d5a4a5da19b1f6e7958fe67db4118fa7a1c1 upstream.
Default function signature of trace_unhandled() got changed to include a field dict, but its documentation, perf-script-python.txt has not been updated. Fix it.
--- tools/perf/Documentation/perf-script-python.txt | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-)
tools/perf/Documentation/perf-script-python.txt +3 -6
@@ -149,10 +149,8 @@ def raw_syscalls__sys_enter(event_name, print "id=%d, args=%s\n" % \ (id, args), -def trace_unhandled(event_name, context, common_cpu, common_secs, common_nsecs, - common_pid, common_comm): - print_header(event_name, common_cpu, common_secs, common_nsecs, - common_pid, common_comm) +def trace_unhandled(event_name, context, event_fields_dict): + print ' '.join(['%s=%s'%(k,str(v))for k,v in sorted(event_fields_dict.items())]) def print_header(event_name, cpu, secs, nsecs, pid, comm): print "%-20s %5u %05u.%09u %8u %-20s " % \
@@ -552,8 +550,7 @@ def trace_end(): of common arguments are passed into it: ---- -def trace_unhandled(event_name, context, common_cpu, common_secs, - common_nsecs, common_pid, common_comm): +def trace_unhandled(event_name, context, event_fields_dict): pass ----
PATCH 72/106 perf script python: Remove dups in documentation examples
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: SeongJae Park <[email protected]>
commit 14fc42fa1b3e7ea5160c84d0e686a3a0c1ffe619 upstream.
Few shell command examples in perf-script-python.txt has few nitpicks include:
- tools/perf/scripts/python directory listing command is unnecessarily repeated.
- few examples contain additional information in command prompt unnecessarily and inconsistently.
This commit fixes them to enhance readability of the document.
--- tools/perf/Documentation/perf-script-python.txt | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
tools/perf/Documentation/perf-script-python.txt +2 -4
@@ -332,7 +332,7 @@ right place, you can have your script li scripts listed by the 'perf script -l' command e.g.: ---- -root@tropicana:~# perf script -l +# perf script -l List of available trace scripts: workqueue-stats workqueue stats (ins/exe/create/destroy) wakeup-latency system-wide min/max/avg wakeup latency
@@ -382,8 +382,6 @@ source tree: ---- # ls -al kernel-source/tools/perf/scripts/python - -root@tropicana:/home/trz/src/tip# ls -al tools/perf/scripts/python total 32 drwxr-xr-x 4 trz trz 4096 2010-01-26 22:30 . drwxr-xr-x 4 trz trz 4096 2010-01-26 22:29 ..
@@ -398,7 +396,7 @@ otherwise your script won't show up at r should show a new entry for your script: ---- -root@tropicana:~# perf script -l +# perf script -l List of available trace scripts: workqueue-stats workqueue stats (ins/exe/create/destroy) wakeup-latency system-wide min/max/avg wakeup latency
PATCH 73/106 KVM: cpuid: Fix read/write out-of-bounds vulnerability in cpuid emulation
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Wanpeng Li <[email protected]>
commit a3641631d14571242eec0d30c9faa786cbf52d44 upstream.
If "i" is the last element in the vcpu->arch.cpuid_entries[] array, it potentially can be exploited the vulnerability. this will out-of-bounds read and write. Luckily, the effect is small:
/* when no next entry is found, the current entry[i] is reselected */
for (j = i + 1; ; j = (j + 1) % nent) {
struct kvm_cpuid_entry2 *ej = &vcpu->arch.cpuid_entries[j];
if (ej->function == e->function) {It reads ej->maxphyaddr, which is user controlled. However...
ej->flags |= KVM_CPUID_FLAG_STATE_READ_NEXT;
After cpuid_entries there is
int maxphyaddr; struct x86_emulate_ctxt emulate_ctxt; /* 16-byte aligned */
So we have:
- cpuid_entries at offset 1B50 (6992)
- maxphyaddr at offset 27D0 (6992 + 3200 = 10192)
- padding at 27D4...27DF
- emulate_ctxt at 27E0
And it writes in the padding. Pfew, writing the ops field of emulate_ctxt would have been much worse.
This patch fixes it by modding the index to avoid the out-of-bounds access. Worst case, i == j and ej->function == e->function, the loop can bail out.
--- arch/x86/kvm/x86.c | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-)
arch/x86/kvm/x86.c +11 -9
@@ -5450,18 +5450,20 @@ int emulator_fix_hypercall(struct x86_emstatic int move_to_next_stateful_cpuid_entry (struct kvm_vcpu *vcpu,int i) {struct kvm_cpuid_entry2 *e = &vcpu->arch.cpuid_entries[i]; -int j, nent = vcpu->arch.cpuid_nent; +struct kvm_cpuid_entry2 *ej; +int j = i; +int nent = vcpu->arch.cpuid_nent; e->flags &= ~KVM_CPUID_FLAG_STATE_READ_NEXT ;/* when no next entry is found, the current entry[i] is reselected */ -for (j = i +1 ; ; j = (j +1 ) % nent) { -struct kvm_cpuid_entry2 *ej = &vcpu->arch.cpuid_entries[j]; -if (ej->function == e->function) { - ej->flags |=KVM_CPUID_FLAG_STATE_READ_NEXT ; -return j; - } - } -return 0 ;/* silence gcc, even though control never reaches here */ +do { + j = (j +1 ) % nent; + ej = &vcpu->arch.cpuid_entries[j]; + }while (ej->function != e->function); + + ej->flags |=KVM_CPUID_FLAG_STATE_READ_NEXT ; + +return j; }/* find an entry with matching function, matching index (if needed), and that
PATCH 74/106 MIPS: kprobes: flush_insn_slot should flush only if probe initialised
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Marcin Nowakowski <[email protected]>
commit 698b851073ddf5a894910d63ca04605e0473414e upstream.
When ftrace is used with kprobes, it is possible for a kprobe to contain an invalid location (ie. only initialised to 0 and not to a specific location in the code). Trying to perform a cache flush on such location leads to a crash r4k_flush_icache_range().
Patchwork: https://patchwork.linux-mips.org/patch/16296/
--- arch/mips/include/asm/kprobes.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/mips/include/asm/kprobes.h +2 -1
@@ -40,7 +40,8 @@ typedef union mips_instruction kprobe_op#define flush_insn_slot (p) \ do { \ - flush_icache_range((unsigned long)p->addr, \ + if (p->addr) \ + flush_icache_range((unsigned long)p->addr, \ (unsigned long)p->addr + \ (MAX_INSN_SIZE * sizeof(kprobe_opcode_t))); \ } while (0)
PATCH 75/106 KEYS: fix dereferencing NULL payload with nonzero length
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Eric Biggers <[email protected]>
commit 5649645d725c73df4302428ee4e02c869248b4c5 upstream.
sys_add_key() and the KEYCTL_UPDATE operation of sys_keyctl() allowed a NULL payload with nonzero length to be passed to the key type's ->preparse(), ->instantiate(), and/or ->update() methods. Various key types including asymmetric, cifs.idmap, cifs.spnego, and pkcs7_test did not handle this case, allowing an unprivileged user to trivially cause a NULL pointer dereference (kernel oops) if one of these key types was present. Fix it by doing the copy_from_user() when 'plen' is nonzero rather than when '_payload' is non-NULL, causing the syscall to fail with EFAULT as expected when an invalid buffer is specified.
--- security/keys/keyctl.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
security/keys/keyctl.c +2 -2
@@ -85,7 +85,7 @@ SYSCALL_DEFINE5(add_key, const char __us payload =NULL ; vm = false; -if (_payload) { +if (plen) { ret = -ENOMEM ; payload =kmalloc (plen,GFP_KERNEL );if (!payload) {
@@ -319,7 +319,7 @@ long keyctl_update_key(key_serial_t id,/* pull the payload in if one was supplied */ payload =NULL ; -if (_payload) { +if (plen) { ret = -ENOMEM ; payload =kmalloc (plen,GFP_KERNEL );if (!payload)
PATCH 76/106 fix ufs_isblockset()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
commit 414cf7186dbec29bd946c138d6b5c09da5955a08 upstream.
--- fs/ufs/util.h | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
fs/ufs/util.h +7 -3
@@ -473,15 +473,19 @@ static inline unsigned _ubh_find_last_zestatic inline int _ubh_isblockset_ (struct ufs_sb_private_info * uspi,struct ufs_buffer_head * ubh,unsigned begin,unsigned block) { +u8 mask;switch (uspi->s_fpb) {case 8 :return (*ubh_get_addr (ubh, begin + block) ==0xff );case 4 : -return (*ubh_get_addr (ubh, begin + (block >>1 )) == (0x0f << ((block &0x01 ) <<2 ))); + mask =0x0f << ((block &0x01 ) <<2 ); +return (*ubh_get_addr (ubh, begin + (block >>1 )) & mask) == mask;case 2 : -return (*ubh_get_addr (ubh, begin + (block >>2 )) == (0x03 << ((block &0x03 ) <<1 ))); + mask =0x03 << ((block &0x03 ) <<1 ); +return (*ubh_get_addr (ubh, begin + (block >>2 )) & mask) == mask;case 1 : -return (*ubh_get_addr (ubh, begin + (block >>3 )) == (0x01 << (block &0x07 ))); + mask =0x01 << (block &0x07 ); +return (*ubh_get_addr (ubh, begin + (block >>3 )) & mask) == mask; }return 0 ; }
PATCH 77/106 ufs: set correct ->s_maxsize
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
commit 6b0d144fa758869bdd652c50aa41aaf601232550 upstream.
--- fs/ufs/super.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
fs/ufs/super.c +18 -0
@@ -695,6 +695,23 @@ static void ufs_put_super_internal(strucUFSD ("EXIT\n" ); } +static u64 ufs_max_bytes (struct super_block *sb) +{ +struct ufs_sb_private_info *uspi =UFS_SB (sb)->s_uspi; +int bits = uspi->s_apbshift; +u64 res; + +if (bits >21 ) + res = ~0ULL ; +else + res =UFS_NDADDR + (1LL << bits) + (1LL << (2 *bits)) + + (1LL << (3 *bits)); + +if (res >= (MAX_LFS_FILESIZE >> uspi->s_bshift)) +return MAX_LFS_FILESIZE ; +return res << uspi->s_bshift; +} +static int ufs_fill_super (struct super_block *sb,void *data,int silent) {struct ufs_sb_info * sbi;
@@ -1157,6 +1174,7 @@ magic_found: "fast symlink size (%u)\n", uspi->s_maxsymlinklen); uspi->s_maxsymlinklen = maxsymlen; } + sb->s_maxbytes =ufs_max_bytes (sb); inode =ufs_iget (sb,UFS_ROOTINO );if (IS_ERR (inode)) {
PATCH 78/106 excessive checks in ufs_write_failed() and ufs_evict_inode()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
commit babef37dccbaa49249a22bae9150686815d7be71 upstream.
As it is, short copy in write() to append-only file will fail to truncate the excessive allocated blocks. As the matter of fact, all checks in ufs_truncate_blocks() are either redundant or wrong for that caller. As for the only other caller (ufs_evict_inode()), we only need the file type checks there.
[bwh: Backported to 3.2:
- No functions need to be renamed
- Adjust filenames, context]
---
fs/ufs/inode.c +4 -1
@@ -890,7 +890,10 @@ void ufs_evict_inode(struct inode * inodufs_update_inode (inode,IS_SYNC (inode)); old_i_size = inode->i_size; inode->i_size =0 ; -if (inode->i_blocks &&ufs_truncate (inode, old_i_size)) +if (inode->i_blocks && + (S_ISREG (inode->i_mode) ||S_ISDIR (inode->i_mode) || +S_ISLNK (inode->i_mode)) && +ufs_truncate (inode, old_i_size))ufs_warning (inode->i_sb, __func__,"ufs_truncate failed\n" );unlock_ufs (inode->i_sb); }
fs/ufs/truncate.c +0 -6
@@ -451,12 +451,6 @@ int ufs_truncate(struct inode *inode, lo inode->i_ino, (unsigned long long )i_size_read (inode), (unsigned long long)old_i_size); -if (!(S_ISREG (inode->i_mode) ||S_ISDIR (inode->i_mode) || -S_ISLNK (inode->i_mode))) -return -EINVAL ; -if (IS_APPEND (inode) ||IS_IMMUTABLE (inode)) -return -EPERM ; - err =ufs_alloc_lastblock (inode);if (err) {
PATCH 79/106 KVM: async_pf: avoid async pf injection when in guest mode
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Wanpeng Li <[email protected]>
commit 9bc1f09f6fa76fdf31eb7d6a4a4df43574725f93 upstream.
INFO: task gnome-terminal-:1734 blocked for more than 120 seconds.
Not tainted 4.12.0-rc4+ #8
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
gnome-terminal- D 0 1734 1015 0x00000000
Call Trace:
__schedule+0x3cd/0xb30
schedule+0x40/0x90
kvm_async_pf_task_wait+0x1cc/0x270
? __vfs_read+0x37/0x150
? prepare_to_swait+0x22/0x70
do_async_page_fault+0x77/0xb0
? do_async_page_fault+0x77/0xb0
async_page_fault+0x28/0x30This is triggered by running both win7 and win2016 on L1 KVM simultaneously, and then gives stress to memory on L1, I can observed this hang on L1 when at least ~70% swap area is occupied on L0.
This is due to async pf was injected to L2 which should be injected to L1, L2 guest starts receiving pagefault w/ bogus %cr2(apf token from the host actually), and L1 guest starts accumulating tasks stuck in D state in kvm_async_pf_task_wait() since missing PAGE_READY async_pfs.
This patch fixes the hang by doing async pf when executing L1 guest.
--- arch/x86/kvm/mmu.c | 7 +++++-- arch/x86/kvm/mmu.h | 1 + arch/x86/kvm/x86.c | 3 +-- 3 files changed, 7 insertions(+), 4 deletions(-)
arch/x86/kvm/mmu.c +5 -2
@@ -3011,12 +3011,15 @@ static int kvm_arch_setup_async_pf(strucreturn kvm_setup_async_pf (vcpu, gva, gfn, &arch); } -static bool can_do_async_pf (struct kvm_vcpu *vcpu) +bool kvm_can_do_async_pf (struct kvm_vcpu *vcpu) {if (unlikely (!irqchip_in_kernel (vcpu->kvm) ||kvm_event_needs_reinjection (vcpu)))return false; +if (is_guest_mode (vcpu)) +return false; +return kvm_x86_ops->interrupt_allowed (vcpu); }
@@ -3032,7 +3035,7 @@ static bool try_async_pf(struct kvm_vcpuput_page (pfn_to_page (*pfn)); -if (!prefault &&can_do_async_pf (vcpu)) { +if (!prefault &&kvm_can_do_async_pf (vcpu)) {trace_kvm_try_async_get_page (gva, gfn);if (kvm_find_async_pf_gfn (vcpu, gfn)) {trace_kvm_async_pf_doublefault (gva, gfn);
arch/x86/kvm/mmu.h +1 -0
@@ -52,6 +52,7 @@ int kvm_mmu_get_spte_hierarchy(struct kvvoid kvm_mmu_set_mmio_spte_mask (u64 mmio_mask);int handle_mmio_page_fault_common (struct kvm_vcpu *vcpu,u64 addr,bool direct);int kvm_init_shadow_mmu (struct kvm_vcpu *vcpu,struct kvm_mmu *context); +bool kvm_can_do_async_pf (struct kvm_vcpu *vcpu);static inline unsigned int kvm_mmu_available_pages (struct kvm *kvm) {
arch/x86/kvm/x86.c +1 -2
@@ -6935,8 +6935,7 @@ bool kvm_arch_can_inject_async_page_presif (!(vcpu->arch.apf.msr_val &KVM_ASYNC_PF_ENABLED ))return true;else -return !kvm_event_needs_reinjection (vcpu) && - kvm_x86_ops->interrupt_allowed (vcpu); +return kvm_can_do_async_pf (vcpu); }EXPORT_TRACEPOINT_SYMBOL_GPL (kvm_exit);
PATCH 80/106 configfs: Fix race between create_link and configfs_rmdir
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Bellinger <[email protected]>
commit ba80aa909c99802c428682c352b0ee0baac0acd3 upstream.
This patch closes a long standing race in configfs between the creation of a new symlink in create_link(), while the symlink target's config_item is being concurrently removed via configfs_rmdir().
This can happen because the symlink target's reference is obtained by config_item_get() in create_link() before the CONFIGFS_USET_DROPPING bit set by configfs_detach_prep() during configfs_rmdir() shutdown is actually checked..
This originally manifested itself on ppc64 on v4.8.y under heavy load using ibmvscsi target ports with Novalink API:
[ 7877.289863] rpadlpar_io: slot U8247.22L.212A91A-V1-C8 added
[ 7879.893760] ------------[ cut here ]------------
[ 7879.893768] WARNING: CPU: 15 PID: 17585 at ./include/linux/kref.h:46 config_item_get+0x7c/0x90 [configfs]
[ 7879.893811] CPU: 15 PID: 17585 Comm: targetcli Tainted: G O 4.8.17-customv2.22 #12
[ 7879.893812] task: c00000018a0d3400 task.stack: c0000001f3b40000
[ 7879.893813] NIP: d000000002c664ec LR: d000000002c60980 CTR: c000000000b70870
[ 7879.893814] REGS: c0000001f3b43810 TRAP: 0700 Tainted: G O (4.8.17-customv2.22)
[ 7879.893815] MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 28222242 XER: 00000000
[ 7879.893820] CFAR: d000000002c664bc SOFTE: 1
GPR00: d000000002c60980 c0000001f3b43a90 d000000002c70908 c0000000fbc06820
GPR04: c0000001ef1bd900 0000000000000004 0000000000000001 0000000000000000
GPR08: 0000000000000000 0000000000000001 d000000002c69560 d000000002c66d80
GPR12: c000000000b70870 c00000000e798700 c0000001f3b43ca0 c0000001d4949d40
GPR16: c00000014637e1c0 0000000000000000 0000000000000000 c0000000f2392940
GPR20: c0000001f3b43b98 0000000000000041 0000000000600000 0000000000000000
GPR24: fffffffffffff000 0000000000000000 d000000002c60be0 c0000001f1dac490
GPR28: 0000000000000004 0000000000000000 c0000001ef1bd900 c0000000f2392940
[ 7879.893839] NIP [d000000002c664ec] config_item_get+0x7c/0x90 [configfs]
[ 7879.893841] LR [d000000002c60980] check_perm+0x80/0x2e0 [configfs]
[ 7879.893842] Call Trace:
[ 7879.893844] [c0000001f3b43ac0] [d000000002c60980] check_perm+0x80/0x2e0 [configfs]
[ 7879.893847] [c0000001f3b43b10] [c000000000329770] do_dentry_open+0x2c0/0x460
[ 7879.893849] [c0000001f3b43b70] [c000000000344480] path_openat+0x210/0x1490
[ 7879.893851] [c0000001f3b43c80] [c00000000034708c] do_filp_open+0xfc/0x170
[ 7879.893853] [c0000001f3b43db0] [c00000000032b5bc] do_sys_open+0x1cc/0x390
[ 7879.893856] [c0000001f3b43e30] [c000000000009584] system_call+0x38/0xec
[ 7879.893856] Instruction dump:
[ 7879.893858] 409d0014 38210030 e8010010 7c0803a6 4e800020 3d220000 e94981e0 892a0000
[ 7879.893861] 2f890000 409effe0 39200001 992a0000 <0fe00000> 4bffffd0 60000000 60000000
[ 7879.893866] ---[ end trace 14078f0b3b5ad0aa ]---To close this race, go ahead and obtain the symlink's target config_item reference only after the existing CONFIGFS_USET_DROPPING check succeeds.
This way, if configfs_rmdir() wins create_link() will return -ENONET, and if create_link() wins configfs_rmdir() will return -EBUSY.
--- fs/configfs/symlink.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
fs/configfs/symlink.c +1 -2
@@ -83,14 +83,13 @@ static int create_link(struct config_ite ret = -ENOMEM ; sl =kmalloc (sizeof (struct configfs_symlink ),GFP_KERNEL );if (sl) { - sl->sl_target =config_item_get (item);spin_lock (&configfs_dirent_lock);if (target_sd->s_type &CONFIGFS_USET_DROPPING ) {spin_unlock (&configfs_dirent_lock); -config_item_put (item);kfree (sl);return -ENOENT ; } + sl->sl_target =config_item_get (item);list_add (&sl->sl_list, &target_sd->s_links);spin_unlock (&configfs_dirent_lock); ret = configfs_create_link(sl, parent_item->ci_dentry,
PATCH 81/106 usb: xhci: ASMedia ASM1042A chipset need shorts TX quirk
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Corentin Labbe <[email protected]>
commit d2f48f05cd2a2a0a708fbfa45f1a00a87660d937 upstream.
When plugging an USB webcam I see the following message:
[106385.615559] xhci_hcd 0000:04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [106390.583860] handle_tx_event: 913 callbacks suppressed
With this patch applied, I get no more printing of this message.
---
drivers/usb/host/xhci-pci.c +4 -0
@@ -159,6 +159,10 @@ static void xhci_pci_quirks(struct devic }if (pdev->vendor ==PCI_VENDOR_ID_VIA ) xhci->quirks |=XHCI_RESET_ON_RESUME ; + +if (pdev->vendor ==PCI_VENDOR_ID_ASMEDIA && + pdev->device ==0x1142 ) + xhci->quirks |=XHCI_TRUST_TX_LENGTH ; }/*
PATCH 82/106 selinux: fix double free in selinux_parse_opts_str()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Paul Moore <[email protected]>
commit 023f108dcc187e34ef864bf10ed966cf25e14e2a upstream.
This patch is based on a discussion generated by an earlier patch from Tetsuo Handa:
* https://marc.info/?t=149035659300001&r=1&w=2
The double free problem involves the mnt_opts field of the security_mnt_opts struct, selinux_parse_opts_str() frees the memory on error, but doesn't set the field to NULL so if the caller later attempts to call security_free_mnt_opts() we trigger the problem.
In order to play it safe we change selinux_parse_opts_str() to call security_free_mnt_opts() on error instead of free'ing the memory directly. This should ensure that everything is handled correctly, regardless of what the caller may do.
--- security/selinux/hooks.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
security/selinux/hooks.c +2 -3
@@ -911,10 +911,8 @@ static int selinux_parse_opts_str(char * goto out_err; opts->mnt_opts_flags =kcalloc (NUM_SEL_MNT_OPTS ,sizeof (int ),GFP_ATOMIC ); -if (!opts->mnt_opts_flags) { -kfree (opts->mnt_opts); +if (!opts->mnt_opts_flags) goto out_err; - }if (fscontext) { opts->mnt_opts[num_mnt_opts] = fscontext;
@@ -937,6 +935,7 @@ static int selinux_parse_opts_str(char *return 0 ; out_err: +security_free_mnt_opts (opts);kfree (context);kfree (defcontext);kfree (fscontext);
PATCH 83/106 xfrm: Oops on error in pfkey_msg2xfrm_state()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 1e3d0c2c70cd3edb5deed186c5f5c75f2b84a633 upstream.
There are some missing error codes here so we accidentally return NULL instead of an error pointer. It results in a NULL pointer dereference.
--- net/key/af_key.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
net/key/af_key.c +12 -4
@@ -1163,8 +1163,10 @@ static struct xfrm_state * pfkey_msg2xfrif (key) keysize = (key->sadb_key_bits +7 ) /8 ; x->aalg =kmalloc (sizeof (*x->aalg) + keysize,GFP_KERNEL ); -if (!x->aalg) +if (!x->aalg) { + err = -ENOMEM ; goto out; + }strcpy (x->aalg->alg_name, a->name); x->aalg->alg_key_len =0 ;if (key) {
@@ -1183,8 +1185,10 @@ static struct xfrm_state * pfkey_msg2xfr goto out; } x->calg =kmalloc (sizeof (*x->calg),GFP_KERNEL ); -if (!x->calg) +if (!x->calg) { + err = -ENOMEM ; goto out; + }strcpy (x->calg->alg_name, a->name); x->props.calgo = sa->sadb_sa_encrypt; }else {
@@ -1198,8 +1202,10 @@ static struct xfrm_state * pfkey_msg2xfrif (key) keysize = (key->sadb_key_bits +7 ) /8 ; x->ealg =kmalloc (sizeof (*x->ealg) + keysize,GFP_KERNEL ); -if (!x->ealg) +if (!x->ealg) { + err = -ENOMEM ; goto out; + }strcpy (x->ealg->alg_name, a->name); x->ealg->alg_key_len =0 ;if (key) {
@@ -1247,8 +1253,10 @@ static struct xfrm_state * pfkey_msg2xfrstruct xfrm_encap_tmpl *natt; x->encap =kmalloc (sizeof (*x->encap),GFP_KERNEL ); -if (!x->encap) +if (!x->encap) { + err = -ENOMEM ; goto out; + } natt = x->encap; n_type = ext_hdrs[SADB_X_EXT_NAT_T_TYPE -1 ];
PATCH 84/106 xfrm: NULL dereference on allocation failure
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit e747f64336fc15e1c823344942923195b800aa1e upstream.
The default error code in pfkey_msg2xfrm_state() is -ENOBUFS. We added a new call to security_xfrm_state_alloc() which sets "err" to zero so there several places where we can return ERR_PTR(0) if kmalloc() fails. The caller is expecting error pointers so it leads to a NULL dereference.
--- net/key/af_key.c | 1 + 1 file changed, 1 insertion(+)
net/key/af_key.c +1 -0
@@ -1152,6 +1152,7 @@ static struct xfrm_state * pfkey_msg2xfr goto out; } + err = -ENOBUFS ; key = ext_hdrs[SADB_EXT_KEY_AUTH -1 ];if (sa->sadb_sa_auth) {int keysize =0 ;
PATCH 85/106 powerpc/kprobes: Pause function_graph tracing during jprobes handling
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: "Naveen N. Rao" <[email protected]>
commit a9f8553e935f26cb5447f67e280946b0923cd2dc upstream.
This fixes a crash when function_graph and jprobes are used together. This is essentially commit 237d28db036e ("ftrace/jprobes/x86: Fix conflict between jprobes and function graph tracing"), but for powerpc.
Jprobes breaks function_graph tracing since the jprobe hook needs to use jprobe_return(), which never returns back to the hook, but instead to the original jprobe'd function. The solution is to momentarily pause function_graph tracing before invoking the jprobe hook and re-enable it when returning back to the original jprobe'd function.
[bwh: Backported to 3.2: include <linux/ftrace.h>, which apparently gets
included indirectly upstream]
---
arch/powerpc/kernel/kprobes.c +12 -0
@@ -32,6 +32,7 @@#include <linux/module.h> #include <linux/kdebug.h> #include <linux/slab.h> +#include <linux/ftrace.h> #include <asm/cacheflush.h> #include <asm/sstep.h> #include <asm/uaccess.h>
@@ -530,6 +531,15 @@ int __kprobes setjmp_pre_handler(struct regs->gpr[2 ] = (unsigned long )(((func_descr_t *)jp->entry)->toc);#endif +/* +* jprobes use jprobe_return() which skips the normal return +* path of the function, and this messes up the accounting of the +* function graph tracer. +* +* Pause function graph tracing while performing the jprobe function. +*/ +pause_graph_tracing (); +return 1 ; }
@@ -552,6 +562,8 @@ int __kprobes longjmp_break_handler(stru* saved regs... */ memcpy (regs, &kcb->jprobe_saved_regs,sizeof (struct pt_regs )); +/* It's OK to start function graph tracing again */ +unpause_graph_tracing ();preempt_enable_no_resched ();return 1 ; }
PATCH 86/106 swap: cond_resched in swap_cgroup_prepare()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Yu Zhao <[email protected]>
commit ef70762948dde012146926720b70e79736336764 upstream.
I saw need_resched() warnings when swapping on large swapfile (TBs) because continuously allocating many pages in swap_cgroup_prepare() took too long.
We already cond_resched when freeing page in swap_cgroup_swapoff(). Do the same for the page allocation.
--- mm/page_cgroup.c | 3 +++ 1 file changed, 3 insertions(+)
mm/page_cgroup.c +3 -0
@@ -399,6 +399,9 @@ static int swap_cgroup_prepare(int type)if (!page) goto not_enough_page; ctrl->map[idx] = page; + +if (!(idx %SWAP_CLUSTER_MAX )) +cond_resched (); }return 0 ; not_enough_page:
PATCH 87/106 signal: Only reschedule timers on signals timers have sent
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: "Eric W. Biederman" <[email protected]>
commit 57db7e4a2d92c2d3dfbca4ef8057849b2682436b upstream.
Quoted 37 lines · Thomas Gleixner
The CRIU support added a 'feature' which allows a user space task to send arbitrary (kernel) signals to itself. The changelog says:
The kernel prevents sending of siginfo with positive
si_code, because these codes are reserved for kernel. I think we can allow a task to send such a siginfo to itself. This operation should not be dangerous.Quite contrary to that claim, it turns out that it is outright dangerous for signals with
info->si_code==SI_TIMER. The following code sequence in a user space task allows to crash the kernel:id = timer_create(CLOCK_XXX, ..... signo = SIGX); timer_set(id, ....); info->si_signo = SIGX; info->si_code = SI_TIMER: info->_sifields._timer._tid = id; info->_sifields._timer._sys_private = 2; rt_[tg]sigqueueinfo(..., SIGX, info); sigemptyset(&sigset); sigaddset(&sigset, SIGX); rt_sigtimedwait(sigset, info);For timers based on
CLOCK_PROCESS_CPUTIME_ID,CLOCK_THREAD_CPUTIME_IDthis results in a kernel crash becausesigwait()dequeues the signal and the dequeue code observes:info->si_code == SI_TIMER && info->_sifields._timer._sys_private != 0which triggers the following callchain:
do_schedule_next_timer()->posix_cpu_timer_schedule()->arm_timer()
arm_timer()executes alist_add()on the timer, which is already armed via thetimer_set()syscall. That's a double list add which corrupts the posix cpu timer list. As a consequence the kernel crashes on the next operation touching the posix cpu timer list.
Quoted 5 lines
Posix clocks which are internally implemented based on hrtimers are not affected by this because
hrtimer_start()can handle already armed timers nicely, but it's a reliable way to trigger theWARN_ON()inhrtimer_forward(), which complains about calling that function on an already armed timer.
This problem has existed since the posix timer code was merged into 2.5.63. A few releases earlier in 2.5.60 ptrace gained the ability to inject not just a signal (which linux has supported since 1.0) but the full siginfo of a signal.
The core problem is that the code will reschedule in response to signals getting dequeued not just for signals the timers sent but for other signals that happen to a si_code of SI_TIMER.
Avoid this confusion by testing to see if the queued signal was preallocated as all timer signals are preallocated, and so far only the timer code preallocates signals.
Move the check for if a timer needs to be rescheduled up into collect_signal where the preallocation check must be performed, and pass the result back to dequeue_signal where the code reschedules
timers. This makes it clear why the code cares about preallocated
timers.
History Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
Reference: 66dd34ad31e5 ("signal: allow to send any siginfo to itself")
Reference: 1669ce53e2ff ("Add PTRACE_GETSIGINFO and PTRACE_SETSIGINFO")
--- kernel/signal.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-)
kernel/signal.c +14 -6
@@ -535,7 +535,8 @@ unblock_all_signals(void)spin_unlock_irqrestore (¤t->sighand->siglock, flags); } -static void collect_signal (int sig,struct sigpending *list,siginfo_t *info) +static void collect_signal (int sig,struct sigpending *list,siginfo_t *info, +bool *resched_timer) {struct sigqueue *q, *first =NULL ;
@@ -557,6 +558,12 @@ static void collect_signal(int sig, stru still_pending:list_del_init (&first->list);copy_siginfo (info, &first->info); + + *resched_timer = + (first->flags &SIGQUEUE_PREALLOC ) && + (info->si_code ==SI_TIMER ) && + (info->si_sys_private); +__sigqueue_free (first); }else {/*
@@ -573,7 +580,7 @@ still_pending: }static int __dequeue_signal (struct sigpending *pending,sigset_t *mask, -siginfo_t *info) +siginfo_t *info,bool *resched_timer) {int sig =next_signal (pending, mask);
@@ -587,7 +594,7 @@ static int __dequeue_signal(struct sigpe } } -collect_signal (sig, pending, info); +collect_signal (sig, pending, info, resched_timer); }return sig;
@@ -601,15 +608,16 @@ static int __dequeue_signal(struct sigpe*/ int dequeue_signal (struct task_struct *tsk,sigset_t *mask,siginfo_t *info) { +bool resched_timer = false;int signr;/* We only dequeue private signals from ourselves, we don't let * signalfd steal them */ - signr =__dequeue_signal (&tsk->pending, mask, info); + signr =__dequeue_signal (&tsk->pending, mask, info, &resched_timer);if (!signr) { signr =__dequeue_signal (&tsk->signal->shared_pending, - mask, info); + mask, info, &resched_timer);/* * itimer signal ? *
@@ -654,7 +662,7 @@ int dequeue_signal(struct task_struct *t*/ current->jobctl |=JOBCTL_STOP_DEQUEUED ; } -if ((info->si_code & __SI_MASK) == __SI_TIMER && info->si_sys_private) { +if (resched_timer) {/* * Release the siglock to ensure proper locking order * of timer locks outside of siglocks. Note, we leave
PATCH 88/106 Input: i8042 - add Fujitsu Lifebook AH544 to notimeout list
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Drake <[email protected]>
commit 817ae460c784f32cd45e60b2b1b21378c3c6a847 upstream.
Without this quirk, the touchpad is not responsive on this product, with the following message repeated in the logs:
psmouse serio1: bad data from KBC - timeout
Add it to the notimeout list alongside other similar Fujitsu laptops.
--- drivers/input/serio/i8042-x86ia64io.h | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/input/serio/i8042-x86ia64io.h +7 -0
@@ -673,6 +673,13 @@ static const struct dmi_system_id __init DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK U574"), }, }, + { + /* Fujitsu UH554 laptop */ + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"), + DMI_MATCH(DMI_PRODUCT_NAME, "LIFEBOOK UH544"), + }, + }, { } };
PATCH 89/106 drm/radeon: add a quirk for Toshiba Satellite L20-183
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit acfd6ee4fa7ebeee75511825fe02be3f7ac1d668 upstream.
Fixes resume from suspend.
--- drivers/gpu/drm/radeon/radeon_combios.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/gpu/drm/radeon/radeon_combios.c +7 -0
@@ -3406,6 +3406,13 @@ void radeon_combios_asic_init(struct drm rdev->pdev->subsystem_vendor ==0x103c && rdev->pdev->subsystem_device == 0x280a) return; +/* quirk for rs4xx Toshiba Sattellite L20-183 latop to make it resume +* - it hangs on resume inside the dynclk 1 table. +*/ +if (rdev->family ==CHIP_RS400 && + rdev->pdev->subsystem_vendor ==0x1179 && + rdev->pdev->subsystem_device ==0xff31 ) +return ;/* DYN CLK 1 */ table =combios_get_table_offset (dev,COMBIOS_DYN_CLK_1_TABLE );
PATCH 90/106 rtnetlink: add IFLA_GROUP to ifla_policy
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Serhey Popovych <[email protected]>
commit db833d40ad3263b2ee3b59a1ba168bb3cfed8137 upstream.
Network interface groups support added while ago, however there is no IFLA_GROUP attribute description in policy and netlink message size calculations until now.
Add IFLA_GROUP attribute to the policy.
--- net/core/rtnetlink.c | 2 ++ 1 file changed, 2 insertions(+)
net/core/rtnetlink.c +2 -0
@@ -791,6 +791,7 @@ static noinline size_t if_nlmsg_size(con +nla_total_size (4 )/* IFLA_MASTER */ +nla_total_size (1 )/* IFLA_OPERSTATE */ +nla_total_size (1 )/* IFLA_LINKMODE */ + +nla_total_size (4 )/* IFLA_GROUP */ +nla_total_size (ext_filter_mask &RTEXT_FILTER_VF ?4 :0 )/* IFLA_NUM_VF */ +rtnl_vfinfo_size (dev, ext_filter_mask)/* IFLA_VFINFO_LIST */
@@ -1142,6 +1143,7 @@ const struct nla_policy ifla_policy[IFLA [IFLA_PORT_SELF] = { .type = NLA_NESTED }, [IFLA_AF_SPEC] = { .type = NLA_NESTED }, [IFLA_EXT_MASK] = { .type = NLA_U32 }, + [IFLA_GROUP ] = { .type =NLA_U32 }, };EXPORT_SYMBOL (ifla_policy );
PATCH 91/106 ipv6: avoid unregistering inet6_dev for loopback
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: WANG Cong <[email protected]>
commit 60abc0be96e00ca71bac083215ac91ad2e575096 upstream.
The per netns loopback_dev->ip6_ptr is unregistered and set to NULL when its mtu is set to smaller than IPV6_MIN_MTU, this leads to that we could set rt->rt6i_idev NULL after a rt6_uncached_list_flush_dev() and then crash after another call.
In this case we should just bring its inet6_dev down, rather than unregistering it, at least prior to commit 176c39af29bc ("netns: fix addrconf_ifdown kernel panic") we always override the case for loopback.
Thanks a lot to Andrey for finding a reliable reproducer.
[bwh: Backported to 3.2: the NETDEV_CHANGEMTU case used to fall-through to the
NETDEV_DOWN case here, so replace that with a separate call to addrconf_ifdown()]
---
net/ipv6/addrconf.c +4 -1
@@ -2633,6 +2633,7 @@ static int addrconf_notify(struct notifi {struct net_device *dev = (struct net_device *) data;struct inet6_dev *idev =__in6_dev_get (dev); +struct net *net =dev_net (dev);int run_pending =0 ;int err;
@@ -2733,7 +2734,7 @@ static int addrconf_notify(struct notifi* IPV6_MIN_MTU stop IPv6 on this interface. */ if (dev->mtu <IPV6_MIN_MTU ) -addrconf_ifdown (dev,1 ); +addrconf_ifdown (dev, dev != net->loopback_dev); }break ;
@@ -2754,6 +2755,8 @@ static int addrconf_notify(struct notifi* MTU falled under IPV6_MIN_MTU. * Stop IPv6 on this interface. */ +addrconf_ifdown (dev, dev != net->loopback_dev); +break ;case NETDEV_DOWN :case NETDEV_UNREGISTER :
PATCH 92/106 powerpc/64: Initialise thread_info for emergency stacks
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Piggin <[email protected]>
commit 34f19ff1b5a0d11e46df479623d6936460105c9f upstream.
Emergency stacks have their thread_info mostly uninitialised, which in particular means garbage preempt_count values.
Emergency stack code runs with interrupts disabled entirely, and is used very rarely, so this has been unnoticed so far. It was found by a proposed new powerpc watchdog that takes a soft-NMI directly from the masked_interrupt handler and using the emergency stack. That crashed at BUG_ON(in_nmi()) in nmi_enter(). preempt_count()s were found to be garbage.
To fix this, zero the entire THREAD_SIZE allocation, and initialize the thread_info.
[mpe: Move it all into setup_64.c, use a function not a macro. Fix
crashes on Cell by setting preempt_count to 0 not HARDIRQ_OFFSET]
[bwh: Backported to 3.2:
- There's only one emergency stack
- No need to call klp_init_thread_info()
- Add the ti variable in emergency_stack_init()]
--- arch/powerpc/kernel/setup_64.c | 31 ++++++++++++++++++++++++++++--- 1 file changed, 28 insertions(+), 3 deletions(-)
arch/powerpc/kernel/setup_64.c +25 -0
@@ -509,6 +509,23 @@ static void __init exc_lvl_early_init(vo#endif /* +* Emergency stacks are used for a range of things, from asynchronous +* NMIs (system reset, machine check) to synchronous, process context. +* We set preempt_count to zero, even though that isn't necessarily correct. To +* get the right value we'd need to copy it from the previous thread_info, but +* doing that might fault causing more problems. +* TODO: what to do with accounting? +*/ +static void emerg_stack_init_thread_info (struct thread_info *ti,int cpu) +{ + ti->task =NULL ; + ti->cpu = cpu; + ti->preempt_count =0 ; + ti->local_flags =0 ; + ti->flags =0 ; +} + +/* * Stack space used when we detect a bad kernel stack pointer, and * early in SMP boots before relocation is enabled. */
@@ -525,12 +542,20 @@ static void __init emergency_stack_init(* Since we use these as temporary stacks during secondary CPU * bringup, we need to get at them in real mode. This means they * must also be within the RMO region. +* +* The IRQ stacks allocated elsewhere in this file are zeroed and +* initialized in kernel/irq.c. These are initialized here in order +* to have emergency stacks available as early as possible. */ limit =min (safe_stack_limit (), ppc64_rma_size);for_each_possible_cpu (i) {unsigned long sp; +struct thread_info *ti; sp =memblock_alloc_base (THREAD_SIZE ,THREAD_SIZE , limit); + ti =__va (sp); +memset (ti,0 ,THREAD_SIZE ); +emerg_stack_init_thread_info (ti, i); sp +=THREAD_SIZE ; paca[i].emergency_sp =__va (sp); }
PATCH 93/106 autofs: sanity check status reported with AUTOFS_DEV_IOCTL_FAIL
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: NeilBrown <[email protected]>
commit 9fa4eb8e490a28de40964b1b0e583d8db4c7e57c upstream.
If a positive status is passed with the AUTOFS_DEV_IOCTL_FAIL ioctl, autofs4_d_automount() will return
ERR_PTR(status)
with that status to follow_automount(), which will then dereference an invalid pointer.
So treat a positive status the same as zero, and map to ENOENT.
See comment in systemd src/core/automount.c::automount_send_ready().
--- fs/autofs4/dev-ioctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/autofs4/dev-ioctl.c +1 -1
@@ -345,7 +345,7 @@ static int autofs_dev_ioctl_fail(structint status; token = (autofs_wqt_t ) param->fail.token; - status = param->fail.status ? param->fail.status : -ENOENT ; + status = param->fail.status <0 ? param->fail.status : -ENOENT ;return autofs4_wait_release (sbi, token, status); }
PATCH 94/106 lib/cmdline.c: fix get_options() overflow while parsing ranges
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Ilya Matveychikov <[email protected]>
commit a91e0f680bcd9e10c253ae8b62462a38bd48f09f upstream.
When using get_options() it's possible to specify a range of numbers, like 1-100500. The problem is that it doesn't track array size while calling internally to get_range() which iterates over the range and fills the memory with numbers.
--- lib/cmdline.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
lib/cmdline.c +3 -3
@@ -22,14 +22,14 @@* the values[M, M+1, ..., N] into the ints array in get_options. */ -static int get_range (char **str,int *pint) +static int get_range (char **str,int *pint,int n) {int x, inc_counter, upper_range; (*str)++; upper_range =simple_strtol ((*str),NULL ,0 ); inc_counter = upper_range - *pint; -for (x = *pint; x < upper_range; x++) +for (x = *pint; n && x < upper_range; x++, n--) *pint++ = x;return inc_counter; }
@@ -95,7 +95,7 @@ char *get_options(const char *str, int nbreak ;if (res ==3 ) {int range_nums; - range_nums =get_range ((char **)&str, ints + i); + range_nums =get_range ((char **)&str, ints + i, nints - i);if (range_nums <0 )break ;/*
PATCH 95/106 net: prevent sign extension in dev_get_stats()
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
commit 6f64ec74515925cced6df4571638b5a099a49aae upstream.
Similar to the fix provided by Dominik Heidler in commit 9b3dc0a17d73 ("l2tp: cast l2tp traffic counter to unsigned") we need to take care of 32bit kernels in dev_get_stats().
When using atomic_long_read(), we add a 'long' to u64 and might misinterpret high order bit, unless we cast to unsigned.
---
net/core/dev.c +1 -1
@@ -5942,7 +5942,7 @@ struct rtnl_link_stats64 *dev_get_stats( }else {netdev_stats_to_stats64 (storage, &dev->stats); } - storage->rx_dropped +=atomic_long_read (&dev->rx_dropped); + storage->rx_dropped += (unsigned long )atomic_long_read (&dev->rx_dropped);return storage; }EXPORT_SYMBOL (dev_get_stats);
PATCH 96/106 MIPS: Fix IRQ tracing & lockdep when rescheduling
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Paul Burton <[email protected]>
commit d8550860d910c6b7b70f830f59003b33daaa52c9 upstream.
When the scheduler sets TIF_NEED_RESCHED & we call into the scheduler from arch/mips/kernel/entry.S we disable interrupts. This is true regardless of whether we reach work_resched from syscall_exit_work, resume_userspace or by looping after calling schedule(). Although we disable interrupts in these paths we don't call trace_hardirqs_off() before calling into C code which may acquire locks, and we therefore leave lockdep with an inconsistent view of whether interrupts are disabled or not when CONFIG_PROVE_LOCKING & CONFIG_DEBUG_LOCKDEP are both enabled.
Without tracing this interrupt state lockdep will print warnings such as the following once a task returns from a syscall via syscall_exit_partial with TIF_NEED_RESCHED set:
[ 49.927678] ------------[ cut here ]------------ [ 49.934445] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3687 check_flags.part.41+0x1dc/0x1e8 [ 49.946031] DEBUG_LOCKS_WARN_ON(current->hardirqs_enabled) [ 49.946355] CPU: 0 PID: 1 Comm: init Not tainted 4.10.0-00439-gc9fd5d362289-dirty #197 [ 49.963505] Stack : 0000000000000000 ffffffff81bb5d6a 0000000000000006 ffffffff801ce9c4 [ 49.974431] 0000000000000000 0000000000000000 0000000000000000 000000000000004a [ 49.985300] ffffffff80b7e487 ffffffff80a24498 a8000000ff160000 ffffffff80ede8b8 [ 49.996194] 0000000000000001 0000000000000000 0000000000000000 0000000077c8030c [ 50.007063] 000000007fd8a510 ffffffff801cd45c 0000000000000000 a8000000ff127c88 [ 50.017945] 0000000000000000 ffffffff801cf928 0000000000000001 ffffffff80a24498 [ 50.028827] 0000000000000000 0000000000000001 0000000000000000 0000000000000000 [ 50.039688] 0000000000000000 a8000000ff127bd0 0000000000000000 ffffffff805509bc [ 50.050575] 00000000140084e0 0000000000000000 0000000000000000 0000000000040a00 [ 50.061448] 0000000000000000 ffffffff8010e1b0 0000000000000000 ffffffff805509bc [ 50.072327] ... [ 50.076087] Call Trace: [ 50.079869] [<ffffffff8010e1b0>] show_stack+0x80/0xa8 [ 50.086577] [<ffffffff805509bc>] dump_stack+0x10c/0x190 [ 50.093498] [<ffffffff8015dde0>] __warn+0xf0/0x108 [ 50.099889] [<ffffffff8015de34>] warn_slowpath_fmt+0x3c/0x48 [ 50.107241] [<ffffffff801c15b4>] check_flags.part.41+0x1dc/0x1e8 [ 50.114961] [<ffffffff801c239c>] lock_is_held_type+0x8c/0xb0 [ 50.122291] [<ffffffff809461b8>] __schedule+0x8c0/0x10f8 [ 50.129221] [<ffffffff80946a60>] schedule+0x30/0x98 [ 50.135659] [<ffffffff80106278>] work_resched+0x8/0x34 [ 50.142397] ---[ end trace 0cb4f6ef5b99fe21 ]--- [ 50.148405] possible reason: unannotated irqs-off. [ 50.154600] irq event stamp: 400463 [ 50.159566] hardirqs last enabled at (400463): [<ffffffff8094edc8>] _raw_spin_unlock_irqrestore+0x40/0xa8 [ 50.171981] hardirqs last disabled at (400462): [<ffffffff8094eb98>] _raw_spin_lock_irqsave+0x30/0xb0 [ 50.183897] softirqs last enabled at (400450): [<ffffffff8016580c>] __do_softirq+0x4ac/0x6a8 [ 50.195015] softirqs last disabled at (400425): [<ffffffff80165e78>] irq_exit+0x110/0x128
Fix this by using the TRACE_IRQS_OFF macro to call trace_hardirqs_off() when CONFIG_TRACE_IRQFLAGS is enabled. This is done before invoking schedule() following the work_resched label because:
1) Interrupts are disabled regardless of the path we take to reach work_resched() & schedule().
2) Performing the tracing here avoids the need to do it in paths which disable interrupts but don't call out to C code before hitting a path which uses the RESTORE_SOME macro that will call trace_hardirqs_on() or trace_hardirqs_off() as appropriate.
We call trace_hardirqs_on() using the TRACE_IRQS_ON macro before calling syscall_trace_leave() for similar reasons, ensuring that lockdep has a consistent view of state after we re-enable interrupts.
Patchwork: https://patchwork.linux-mips.org/patch/15385/
--- arch/mips/kernel/entry.S | 3 +++ 1 file changed, 3 insertions(+)
arch/mips/kernel/entry.S +3 -0
@@ -10,6 +10,7 @@ #include <asm/asm.h> #include <asm/asmmacro.h> +#include <asm/irqflags.h> #include <asm/regdef.h> #include <asm/mipsregs.h> #include <asm/stackframe.h>
@@ -145,6 +146,7 @@ work_pending: andi t0, a2, _TIF_NEED_RESCHED # a2 is preloaded with TI_FLAGS beqz t0, work_notifysig work_resched: + TRACE_IRQS_OFF jal schedule local_irq_disable # make sure need_resched and
@@ -172,6 +174,7 @@ syscall_exit_work: beqz t0, work_pending # trace bit set? local_irq_enable # could let syscall_trace_leave() # call schedule() instead + TRACE_IRQS_ON move a0, sp jal syscall_trace_leave b resume_userspace
PATCH 97/106 tracing/kprobes: Allow to create probe with a module name starting with a digit
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sabrina Dubroca <[email protected]>
commit 9e52b32567126fe146f198971364f68d3bc5233f upstream.
Always try to parse an address, since kstrtoul() will safely fail when given a symbol as input. If that fails (which will be the case for a symbol), try to parse a symbol instead.
This allows creating a probe such as:
p:probe/vlan_gro_receive 8021q:vlan_gro_receive+0
Which is necessary for this command to work:
perf probe -m 8021q -a vlan_gro_receive
[bwh: Backported to 3.2: preserve the check that an addresses isn't used for
a kretprobe]
--- kernel/trace/trace_kprobe.c | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-)
kernel/trace/trace_kprobe.c +5 -8
@@ -1225,24 +1225,21 @@ static int create_trace_probe(int argc,pr_info ("Probe point is not specified.\n" );return -EINVAL ; } -if (isdigit (argv[1 ][0 ])) { + +/* try to parse an address. if that fails, try to read the +* input as a symbol. */ +if (!strict_strtoul (argv[1 ],0 , (unsigned long *)&addr)) {if (is_return) {pr_info ("Return probe point must be a symbol.\n" );return -EINVAL ; } -/* an address specified */ - ret =strict_strtoul (&argv[1 ][0 ],0 , (unsigned long *)&addr); -if (ret) { -pr_info ("Failed to parse address.\n" ); -return ret; - } }else {/* a symbol specified */ symbol = argv[1 ];/* TODO: support .init module functions */ ret =split_symbol_offset (symbol, &offset);if (ret) { -pr_info ("Failed to parse symbol.\n" ); +pr_info ("Failed to parse either an address or a symbol.\n" );return ret; }if (offset && is_return) {
PATCH 98/106 tcp: initialize rcv_mss to TCP_MIN_MSS instead of 0
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Wei Wang <[email protected]>
commit 499350a5a6e7512d9ed369ed63a4244b6536f4f8 upstream.
When tcp_disconnect() is called, inet_csk_delack_init() sets icsk->icsk_ack.rcv_mss to 0.
This could potentially cause tcp_recvmsg() => tcp_cleanup_rbuf() => __tcp_select_window() call path to have division by 0 issue. So this patch initializes rcv_mss to TCP_MIN_MSS instead of 0.
--- net/ipv4/tcp.c | 4 ++++ 1 file changed, 4 insertions(+)
net/ipv4/tcp.c +4 -0
@@ -2106,6 +2106,10 @@ int tcp_disconnect(struct sock *sk, inttcp_set_ca_state (sk, TCP_CA_Open);tcp_clear_retrans (tp);inet_csk_delack_init (sk); +/* Initialize rcv_mss to TCP_MIN_MSS to avoid division by 0 +* issue in __tcp_select_window() +*/ + icsk->icsk_ack.rcv_mss =TCP_MIN_MSS ;tcp_init_send_head (sk);memset (&tp->rx_opt,0 ,sizeof (tp->rx_opt));__sk_dst_reset (sk);
PATCH 99/106 xfrm: policy: check policy direction value
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Vladis Dronov <[email protected]>
commit 7bab09631c2a303f87a7eb7e3d69e888673b9b7e upstream.
The 'dir' parameter in xfrm_migrate() is a user-controlled byte which is used as an array index. This can lead to an out-of-bound access, kernel lockup and DoS. Add a check for the 'dir' value.
This fixes CVE-2017-11600.
References: https://bugzilla.redhat.com/show_bug.cgi?id=1474928
--- net/xfrm/xfrm_policy.c | 6 ++++++ 1 file changed, 6 insertions(+)
net/xfrm/xfrm_policy.c +6 -0
@@ -2897,9 +2897,15 @@ int xfrm_migrate(const struct xfrm_selecstruct xfrm_state *x_new[XFRM_MAX_DEPTH ];struct xfrm_migrate *mp; +/* Stage 0 - sanity checks */ if ((err =xfrm_migrate_check (m, num_migrate)) <0 ) goto out; +if (dir >=XFRM_POLICY_MAX ) { + err = -EINVAL ; + goto out; + } +/* Stage 1 - find policy */ if ((pol =xfrm_migrate_policy_find (sel, dir, type)) ==NULL ) { err = -ENOENT ;
PATCH 100/106 xen: fix bio vec merging
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Roger Pau Monne <[email protected]>
commit 462cdace790ac2ed6aad1b19c9c0af0143b6aab0 upstream.
The current test for bio vec merging is not fully accurate and can be tricked into merging bios when certain grant combinations are used. The result of these malicious bio merges is a bio that extends past the memory page used by any of the originating bios.
Take into account the following scenario, where a guest creates two grant references that point to the same mfn, ie: grant 1 -> mfn A, grant 2 -> mfn A.
These references are then used in a PV block request, and mapped by the backend domain, thus obtaining two different pfns that point to the same mfn, pfn B -> mfn A, pfn C -> mfn A.
If those grants happen to be used in two consecutive sectors of a disk IO operation becoming two different bios in the backend domain, the checks in xen_biovec_phys_mergeable will succeed, because bfn1 == bfn2 (they both point to the same mfn). However due to the bio merging, the backend domain will end up with a bio that expands past mfn A into mfn A + 1.
Fix this by making sure the check in xen_biovec_phys_mergeable takes into account the offset and the length of the bio, this basically replicates whats done in __BIOVEC_PHYS_MERGEABLE using mfns (bus addresses). While there also remove the usage of __BIOVEC_PHYS_MERGEABLE, since that's already checked by the callers of xen_biovec_phys_mergeable.
[bwh: Backported to 3.2:
- s/bfn/mfn/g
- Adjust context]
--- drivers/xen/biomerge.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/xen/biomerge.c +1 -2
@@ -8,6 +8,5 @@ bool xen_biovec_phys_mergeable(const strunsigned long mfn1 =pfn_to_mfn (page_to_pfn (vec1->bv_page));unsigned long mfn2 =pfn_to_mfn (page_to_pfn (vec2->bv_page)); -return __BIOVEC_PHYS_MERGEABLE (vec1, vec2) && - ((mfn1 == mfn2) || ((mfn1+1 ) == mfn2)); +return mfn1 +PFN_DOWN (vec1->bv_offset + vec1->bv_len) == mfn2; }
PATCH 101/106 ptrace: use fsuid, fsgid, effective creds for fs access checks
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Jann Horn <[email protected]>
commit caaee6234d05a58c5b4d05e7bf766131b810a657 upstream.
By checking the effective credentials instead of the real UID / permitted capabilities, ensure that the calling process actually intended to use its credentials.
To ensure that all ptrace checks use the correct caller credentials (e.g. in case out-of-tree code or newly added code omits the PTRACE_MODE_*CREDS flag), use two new flags and require one of them to be set.
The problem was that when a privileged task had temporarily dropped its privileges, e.g. by calling setreuid(0, user_uid), with the intent to perform following syscalls with the credentials of a user, it still passed ptrace access checks that the user would not be able to pass.
While an attacker should not be able to convince the privileged task to perform a ptrace() syscall, this is a problem because the ptrace access check is reused for things in procfs.
In particular, the following somewhat interesting procfs entries only rely on ptrace access checks:
/proc/$pid/stat - uses the check for determining whether pointers
should be visible, useful for bypassing ASLR
/proc/$pid/maps - also useful for bypassing ASLR /proc/$pid/cwd - useful for gaining access to restricted
directories that contain files with lax permissions, e.g. in this scenario:
lrwxrwxrwx root root /proc/13020/cwd -> /root/foobar drwx------ root root /root
drwxr-xr-x root root /root/foobar
-rw-r--r-- root root /root/foobar/secret
Therefore, on a system where a root-owned mode 6755 binary changes its effective credentials as described and then dumps a user-specified file, this could be used by an attacker to reveal the memory layout of root's processes or reveal the contents of files he is not allowed to access (through /proc/$pid/cwd).
[bwh: Backported to 3.2:
- Drop changes to kcmp, procfs map_files, procfs has_pid_permissions()
- Keep using uid_t, gid_t and == operator for IDs
- Adjust context]
---
fs/proc/array.c +1 -1
@@ -380,7 +380,7 @@ static int do_task_stat(struct seq_file state = *get_task_state (task); vsize = eip = esp =0 ; - permitted =ptrace_may_access (task,PTRACE_MODE_READ ); + permitted =ptrace_may_access (task,PTRACE_MODE_READ_FSCREDS ); mm =get_task_mm (task);if (mm) { vsize =task_vsize (mm);
fs/proc/base.c +6 -6
@@ -216,7 +216,7 @@ static struct mm_struct *mm_access(strucstruct mm_struct *mm_for_maps (struct task_struct *task) { -return mm_access (task,PTRACE_MODE_READ ); +return mm_access (task,PTRACE_MODE_READ_FSCREDS ); }static int proc_pid_cmdline (struct task_struct *task,char * buffer)
@@ -288,7 +288,7 @@ static int proc_pid_wchan(struct task_st wchan =get_wchan (task);if (lookup_symbol_name (wchan, symname) <0 ) -if (!ptrace_may_access (task,PTRACE_MODE_READ )) +if (!ptrace_may_access (task,PTRACE_MODE_READ_FSCREDS ))return 0 ;else return sprintf (buffer,"%lu" , wchan);
@@ -302,7 +302,7 @@ static int lock_trace(struct task_structint err =mutex_lock_killable (&task->signal->cred_guard_mutex);if (err)return err; -if (!ptrace_may_access (task,PTRACE_MODE_ATTACH )) { +if (!ptrace_may_access (task,PTRACE_MODE_ATTACH_FSCREDS )) {mutex_unlock (&task->signal->cred_guard_mutex);return -EPERM ; }
@@ -544,7 +544,7 @@ static int proc_fd_access_allowed(struct*/ task =get_proc_task (inode);if (task) { - allowed =ptrace_may_access (task,PTRACE_MODE_READ ); + allowed =ptrace_may_access (task,PTRACE_MODE_READ_FSCREDS );put_task_struct (task); }return allowed;
@@ -769,7 +769,7 @@ static int mem_open(struct inode* inode,if (!task)return -ESRCH ; - mm =mm_access (task,PTRACE_MODE_ATTACH ); + mm =mm_access (task,PTRACE_MODE_ATTACH |PTRACE_MODE_FSCREDS );put_task_struct (task);if (IS_ERR (mm))
@@ -2627,7 +2627,7 @@ static int do_io_accounting(struct task_if (result)return result; -if (!ptrace_may_access (task,PTRACE_MODE_READ )) { +if (!ptrace_may_access (task,PTRACE_MODE_READ_FSCREDS )) { result = -EACCES ; goto out_unlock; }
fs/proc/namespaces.c +2 -2
@@ -91,7 +91,7 @@ static int proc_ns_dir_readdir(struct fi goto out_no_task; ret = -EPERM ; -if (!ptrace_may_access (task,PTRACE_MODE_READ )) +if (!ptrace_may_access (task,PTRACE_MODE_READ_FSCREDS )) goto out; ret =0 ;
@@ -154,7 +154,7 @@ static struct dentry *proc_ns_dir_lookup goto out_no_task; error =ERR_PTR (-EPERM ); -if (!ptrace_may_access (task,PTRACE_MODE_READ )) +if (!ptrace_may_access (task,PTRACE_MODE_READ_FSCREDS )) goto out; last = &ns_entries[ARRAY_SIZE (ns_entries) -1 ];
include/linux/ptrace.h +23 -1
@@ -130,9 +130,31 @@ extern void __ptrace_unlink(struct task_extern void exit_ptrace (struct task_struct *tracer);#define PTRACE_MODE_READ 1#define PTRACE_MODE_ATTACH 2 +#define PTRACE_MODE_FSCREDS 0x08 +#define PTRACE_MODE_REALCREDS 0x10 + +/* shorthands for READ/ATTACH and FSCREDS/REALCREDS combinations */ +#define PTRACE_MODE_READ_FSCREDS (PTRACE_MODE_READ | PTRACE_MODE_FSCREDS) +#define PTRACE_MODE_READ_REALCREDS (PTRACE_MODE_READ | PTRACE_MODE_REALCREDS) +#define PTRACE_MODE_ATTACH_FSCREDS (PTRACE_MODE_ATTACH | PTRACE_MODE_FSCREDS) +#define PTRACE_MODE_ATTACH_REALCREDS (PTRACE_MODE_ATTACH | PTRACE_MODE_REALCREDS) +/* Returns 0 on success, -errno on denial. */ extern int __ptrace_may_access (struct task_struct *task,unsigned int mode); -/* Returns true on success, false on denial. */ +/** +* ptrace_may_access - check whether the caller is permitted to access +* a target task. +* @task: target task +* @mode: selects type of access and caller credentials +* +* Returns true on success, false on denial. +* +* One of the flags PTRACE_MODE_FSCREDS and PTRACE_MODE_REALCREDS must +* be set in @mode to specify whether the access was requested through +* a filesystem syscall (should use effective capabilities and fsuid +* of the caller) or through an explicit syscall such as +* process_vm_writev or ptrace (and should use the real credentials). +*/ extern bool ptrace_may_access (struct task_struct *task,unsigned int mode);static inline int ptrace_reparented (struct task_struct *child)
kernel/events/core.c +1 -1
@@ -3004,7 +3004,7 @@ find_lively_task_by_vpid(pid_t vpid)/* Reuse ptrace permission checks for now. */ err = -EACCES ; -if (!ptrace_may_access (task,PTRACE_MODE_READ )) +if (!ptrace_may_access (task,PTRACE_MODE_READ_REALCREDS )) goto errout;return task;
kernel/futex.c +1 -1
@@ -2627,7 +2627,7 @@ SYSCALL_DEFINE3(get_robust_list, int, pi } ret = -EPERM ; -if (!ptrace_may_access (p,PTRACE_MODE_READ )) +if (!ptrace_may_access (p,PTRACE_MODE_READ_REALCREDS )) goto err_unlock; head = p->robust_list;
kernel/futex_compat.c +1 -1
@@ -154,7 +154,7 @@ compat_sys_get_robust_list(int pid, comp } ret = -EPERM ; -if (!ptrace_may_access (p,PTRACE_MODE_READ )) +if (!ptrace_may_access (p,PTRACE_MODE_READ_REALCREDS )) goto err_unlock; head = p->compat_robust_list;
kernel/ptrace.c +31 -8
@@ -220,6 +220,14 @@ int ptrace_check_attach(struct task_struint __ptrace_may_access (struct task_struct *task,unsigned int mode) {const struct cred *cred =current_cred (), *tcred; +int dumpable =0 ; +uid_t caller_uid; +gid_t caller_gid; + +if (!(mode &PTRACE_MODE_FSCREDS ) == !(mode &PTRACE_MODE_REALCREDS )) { +WARN (1 ,"denying ptrace access check without PTRACE_MODE_*CREDS\n" ); +return -EPERM ; + }/* May we inspect the given task? * This check is used both for attaching with ptrace
@@ -229,19 +237,34 @@ int __ptrace_may_access(struct task_stru* because setting up the necessary parent/child relationship * or halting the specified task is impossible. */ -int dumpable =0 ; +/* Don't let security modules deny introspection */ if (same_thread_group (task, current))return 0 ;rcu_read_lock (); +if (mode &PTRACE_MODE_FSCREDS ) { + caller_uid = cred->fsuid; + caller_gid = cred->fsgid; + }else { +/* +* Using the euid would make more sense here, but something +* in userland might rely on the old behavior, and this +* shouldn't be a security problem since +* PTRACE_MODE_REALCREDS implies that the caller explicitly +* used a syscall that requests access to another process +* (and not a filesystem syscall to procfs). +*/ + caller_uid = cred->uid; + caller_gid = cred->gid; + } tcred =__task_cred (task);if (cred->user->user_ns == tcred->user->user_ns && - (cred->uid == tcred->euid && - cred->uid == tcred->suid && - cred->uid == tcred->uid && - cred->gid == tcred->egid && - cred->gid == tcred->sgid && - cred->gid == tcred->gid)) + (caller_uid == tcred->euid && + caller_uid == tcred->suid && + caller_uid == tcred->uid && + caller_gid == tcred->egid && + caller_gid == tcred->sgid && + caller_gid == tcred->gid)) goto ok;if (ns_capable (tcred->user->user_ns,CAP_SYS_PTRACE )) goto ok;
@@ -308,7 +331,7 @@ static int ptrace_attach(struct task_str goto out;task_lock (task); - retval =__ptrace_may_access (task,PTRACE_MODE_ATTACH ); + retval =__ptrace_may_access (task,PTRACE_MODE_ATTACH_REALCREDS );task_unlock (task);if (retval) goto unlock_creds;
mm/process_vm_access.c +1 -1
@@ -299,7 +299,7 @@ static ssize_t process_vm_rw_core(pid_t }task_lock (task); -if (__ptrace_may_access (task,PTRACE_MODE_ATTACH )) { +if (__ptrace_may_access (task,PTRACE_MODE_ATTACH_REALCREDS )) {task_unlock (task); rc = -EPERM ; goto put_task_struct;
security/commoncap.c +6 -1
@@ -141,12 +141,17 @@ int cap_ptrace_access_check(struct task_ {int ret =0 ;const struct cred *cred, *child_cred; +const kernel_cap_t *caller_caps;rcu_read_lock (); cred =current_cred (); child_cred =__task_cred (child); +if (mode &PTRACE_MODE_FSCREDS ) + caller_caps = &cred->cap_effective; +else + caller_caps = &cred->cap_permitted;if (cred->user->user_ns == child_cred->user->user_ns && -cap_issubset (child_cred->cap_permitted, cred->cap_permitted)) +cap_issubset (child_cred->cap_permitted, *caller_caps)) goto out;if (ns_capable (child_cred->user->user_ns,CAP_SYS_PTRACE )) goto out;
PATCH 102/106 mm: fix move/migrate_pages() race on task struct
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Lameter <[email protected]>
commit 3268c63eded4612a3d07b56d1e02ce7731e6608e upstream.
Migration functions perform the rcu_read_unlock too early. As a result the task pointed to may change from under us. This can result in an oops, as reported by Dave Hansen in https://lkml.org/lkml/2012/2/23/302.
The following patch extend the period of the rcu_read_lock until after the permissions checks are done. We also take a refcount so that the task reference is stable when calling security check functions and performing cpuset node validation (which takes a mutex).
The refcount is dropped before actual page migration occurs so there is no change to the refcounts held during page migration.
Also move the determination of the mm of the task struct to immediately before the do_migrate*() calls so that it is clear that we switch from handling the task during permission checks to the mm for the actual migration. Since the determination is only done once and we then no longer use the task_struct we can be sure that we operate on a specific address space that will not change from under us.
--- mm/mempolicy.c | 32 +++++++++++++++++++------------- mm/migrate.c | 36 +++++++++++++++++++----------------- 2 files changed, 38 insertions(+), 30 deletions(-)
mm/mempolicy.c +19 -13
@@ -1334,12 +1334,9 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pi err = -ESRCH ; goto out; } - mm =get_task_mm (task); -rcu_read_unlock (); +get_task_struct (task); err = -EINVAL ; -if (!mm) - goto out;/* * Check if this process has the right to modify the specified
@@ -1347,14 +1344,13 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pi* capabilities, superuser privileges or the same * userid as the target process. */ -rcu_read_lock (); tcred =__task_cred (task);if (cred->euid != tcred->suid && cred->euid != tcred->uid && cred->uid != tcred->suid && cred->uid != tcred->uid && !capable (CAP_SYS_NICE )) {rcu_read_unlock (); err = -EPERM ; - goto out; + goto out_put; }rcu_read_unlock ();
@@ -1362,26 +1358,36 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pi/* Is the user allowed to access the target nodes? */ if (!nodes_subset (*new, task_nodes) && !capable (CAP_SYS_NICE )) { err = -EPERM ; - goto out; + goto out_put; }if (!nodes_subset (*new, node_states[N_HIGH_MEMORY ])) { err = -EINVAL ; - goto out; + goto out_put; } err =security_task_movememory (task);if (err) - goto out; + goto out_put; - err =do_migrate_pages (mm, old, new, -capable (CAP_SYS_NICE ) ?MPOL_MF_MOVE_ALL :MPOL_MF_MOVE ); -out: + mm =get_task_mm (task); +put_task_struct (task);if (mm) -mmput (mm); + err =do_migrate_pages (mm, old, new, +capable (CAP_SYS_NICE ) ?MPOL_MF_MOVE_ALL :MPOL_MF_MOVE ); +else + err = -EINVAL ; + +mmput (mm); +out:NODEMASK_SCRATCH_FREE (scratch);return err; + +out_put: +put_task_struct (task); + goto out; + }
mm/migrate.c +19 -17
@@ -1198,20 +1198,17 @@ set_status:* Migrate an array of page address onto an array of nodes and fill * the corresponding array of status. */ -static int do_pages_move (struct mm_struct *mm,struct task_struct *task, +static int do_pages_move (struct mm_struct *mm,nodemask_t task_nodes,unsigned long nr_pages,const void __user *__user *pages,const int __user *nodes,int __user *status,int flags) {struct page_to_node *pm; -nodemask_t task_nodes;unsigned long chunk_nr_pages;unsigned long chunk_start;int err; - task_nodes =cpuset_mems_allowed (task); - err = -ENOMEM ; pm = (struct page_to_node *)__get_free_page (GFP_KERNEL );if (!pm)
@@ -1373,6 +1370,7 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid,struct task_struct *task;struct mm_struct *mm;int err; +nodemask_t task_nodes;/* Check flags */ if (flags & ~(MPOL_MF_MOVE |MPOL_MF_MOVE_ALL ))
@@ -1388,11 +1386,7 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid,rcu_read_unlock ();return -ESRCH ; } - mm =get_task_mm (task); -rcu_read_unlock (); - -if (!mm) -return -EINVAL ; +get_task_struct (task);/* * Check if this process has the right to modify the specified
@@ -1400,7 +1394,6 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid,* capabilities, superuser privileges or the same * userid as the target process. */ -rcu_read_lock (); tcred =__task_cred (task); if (cred->euid != tcred->suid && cred->euid != tcred->uid && cred->uid != tcred->suid && cred->uid != tcred->uid &&
@@ -1415,16 +1408,25 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid,if (err) goto out; -if (nodes) { - err =do_pages_move (mm, task, nr_pages, pages, nodes, status, - flags); - }else { - err =do_pages_stat (mm, nr_pages, pages, status); - } + task_nodes =cpuset_mems_allowed (task); + mm =get_task_mm (task); +put_task_struct (task); + +if (mm) { +if (nodes) + err =do_pages_move (mm, task_nodes, nr_pages, pages, + nodes, status, flags); +else + err =do_pages_stat (mm, nr_pages, pages, status); + }else + err = -EINVAL ; -out:mmput (mm);return err; + +out: +put_task_struct (task); +return err; }/*
PATCH 103/106 mm: fix NULL ptr dereference in migrate_pages
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sasha Levin <[email protected]>
commit f2a9ef880763d7fbd657a3af646e132a90d70d34 upstream.
Commit 3268c63 ("mm: fix move/migrate_pages() race on task struct") has added an odd construct where 'mm' is checked for being NULL, and if it is, it would get dereferenced anyways by mput()ing it.
This would lead to the following NULL ptr deref and BUG() when calling migrate_pages() with a pid that has no mm struct:
[25904.193704] BUG: unable to handle kernel NULL pointer dereference at 0000000000000050 [25904.194235] IP: [<ffffffff810b0de7>] mmput+0x27/0xf0 [25904.194235] PGD 773e6067 PUD 77da0067 PMD 0 [25904.194235] Oops: 0002 [#1] PREEMPT SMP [25904.194235] CPU 2 [25904.194235] Pid: 31608, comm: trinity Tainted: G W 3.4.0-rc2-next-20120412-sasha #69 [25904.194235] RIP: 0010:[<ffffffff810b0de7>] [<ffffffff810b0de7>] mmput+0x27/0xf0 [25904.194235] RSP: 0018:ffff880077d49e08 EFLAGS: 00010202 [25904.194235] RAX: 0000000000000286 RBX: 0000000000000000 RCX: 0000000000000000 [25904.194235] RDX: ffff880075ef8000 RSI: 000000000000023d RDI: 0000000000000286 [25904.194235] RBP: ffff880077d49e18 R08: 0000000000000001 R09: 0000000000000001 [25904.194235] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [25904.194235] R13: 00000000ffffffea R14: ffff880034287740 R15: ffff8800218d3010 [25904.194235] FS: 00007fc8b244c700(0000) GS:ffff880029800000(0000) knlGS:0000000000000000 [25904.194235] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [25904.194235] CR2: 0000000000000050 CR3: 00000000767c6000 CR4: 00000000000406e0 [25904.194235] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [25904.194235] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [25904.194235] Process trinity (pid: 31608, threadinfo ffff880077d48000, task ffff880075ef8000) [25904.194235] Stack: [25904.194235] ffff8800342876c0 0000000000000000 ffff880077d49f78 ffffffff811b8020 [25904.194235] ffffffff811b7d91 ffff880075ef8000 ffff88002256d200 0000000000000000 [25904.194235] 00000000000003ff 0000000000000000 0000000000000000 0000000000000000 [25904.194235] Call Trace: [25904.194235] [<ffffffff811b8020>] sys_migrate_pages+0x340/0x3a0 [25904.194235] [<ffffffff811b7d91>] ? sys_migrate_pages+0xb1/0x3a0 [25904.194235] [<ffffffff8266cbb9>] system_call_fastpath+0x16/0x1b [25904.194235] Code: c9 c3 66 90 55 31 d2 48 89 e5 be 3d 02 00 00 48 83 ec 10 48 89 1c 24 4c 89 64 24 08 48 89 fb 48 c7 c7 cf 0e e1 82 e8 69 18 03 00 <f0> ff 4b 50 0f 94 c0 84 c0 0f 84 aa 00 00 00 48 89 df e8 72 f1 [25904.194235] RIP [<ffffffff810b0de7>] mmput+0x27/0xf0 [25904.194235] RSP <ffff880077d49e08> [25904.194235] CR2: 0000000000000050 [25904.348999] ---[ end trace a307b3ed40206b4b ]---
--- mm/mempolicy.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
mm/mempolicy.c +7 -4
@@ -1372,11 +1372,14 @@ SYSCALL_DEFINE4(migrate_pages, pid_t, pi mm =get_task_mm (task);put_task_struct (task); -if (mm) - err =do_migrate_pages (mm, old, new, -capable (CAP_SYS_NICE ) ?MPOL_MF_MOVE_ALL :MPOL_MF_MOVE ); -else + +if (!mm) { err = -EINVAL ; + goto out; + } + + err =do_migrate_pages (mm, old, new, +capable (CAP_SYS_NICE ) ?MPOL_MF_MOVE_ALL :MPOL_MF_MOVE );mmput (mm); out:
PATCH 104/106 mm: fix NULL ptr dereference in move_pages
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Sasha Levin <[email protected]>
commit 6e8b09eaf268bceac0c62e389b4bc0cb83dfb8e5 upstream.
Commit 3268c63 ("mm: fix move/migrate_pages() race on task struct") has added an odd construct where 'mm' is checked for being NULL, and if it is, it would get dereferenced anyways by mput()ing it.
--- mm/migrate.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
mm/migrate.c +8 -8
@@ -1412,14 +1412,14 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid, mm =get_task_mm (task);put_task_struct (task); -if (mm) { -if (nodes) - err =do_pages_move (mm, task_nodes, nr_pages, pages, - nodes, status, flags); -else - err =do_pages_stat (mm, nr_pages, pages, status); - }else - err = -EINVAL ; +if (!mm) +return -EINVAL ; + +if (nodes) + err =do_pages_move (mm, task_nodes, nr_pages, pages, + nodes, status, flags); +else + err =do_pages_stat (mm, nr_pages, pages, status);mmput (mm);return err;
PATCH 105/106 Sanitize 'move_pages()' permission checks
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Linus Torvalds <[email protected]>
commit 197e7e521384a23b9e585178f3f11c9fa08274b9 upstream.
The 'move_paghes()' system call was introduced long long ago with the same permission checks as for sending a signal (except using CAP_SYS_NICE instead of CAP_SYS_KILL for the overriding capability).
That turns out to not be a great choice - while the system call really only moves physical page allocations around (and you need other capabilities to do a lot of it), you can check the return value to map out some the virtual address choices and defeat ASLR of a binary that still shares your uid.
So change the access checks to the more common 'ptrace_may_access()' model instead.
This tightens the access checks for the uid, and also effectively changes the CAP_SYS_NICE check to CAP_SYS_PTRACE, but it's unlikely that anybody really _uses_ this legacy system call any more (we hav ebetter NUMA placement models these days), so I expect nobody to notice.
Famous last words.
--- mm/migrate.c | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-)
mm/migrate.c +3 -8
@@ -34,6 +34,7 @@#include <linux/syscalls.h> #include <linux/hugetlb.h> #include <linux/gfp.h> +#include <linux/ptrace.h> #include <asm/tlbflush.h>
@@ -1366,7 +1367,6 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid, const int __user *, nodes, int __user *, status, int, flags) { - const struct cred *cred = current_cred(), *tcred; struct task_struct *task;struct mm_struct *mm;int err;
@@ -1390,14 +1390,9 @@ SYSCALL_DEFINE6(move_pages, pid_t, pid,/* * Check if this process has the right to modify the specified -* process. The right exists if the process has administrative -* capabilities, superuser privileges or the same -* userid as the target process. +* process. Use the regular "ptrace_may_access()" checks. */ - tcred =__task_cred (task); -if (cred->euid != tcred->suid && cred->euid != tcred->uid && - cred->uid != tcred->suid && cred->uid != tcred->uid && - !capable (CAP_SYS_NICE )) { +if (!ptrace_may_access (task,PTRACE_MODE_READ_REALCREDS )) {rcu_read_unlock (); err = -EPERM ; goto out;
PATCH 106/106 net: phy: marvell: Limit errata to 88m1101
In reply to Ben Hutchings3.2.93-rc1 review patch. If anyone has any objections, please let me know.
------------------
From: Andrew Lunn <[email protected]>
commit f2899788353c13891412b273fdff5f02d49aa40f upstream.
The 88m1101 has an errata when configuring autoneg. However, it was being applied to many other Marvell PHYs as well. Limit its scope to just the 88m1101.
--- drivers/net/phy/marvell.c | 66 ++++++++++++++++++++++++++--------------------- 1 file changed, 37 insertions(+), 29 deletions(-)
drivers/net/phy/marvell.c +37 -29
@@ -126,34 +126,6 @@ static int marvell_config_aneg(struct ph {int err; -/* The Marvell PHY has an errata which requires -* that certain registers get written in order -* to restart autonegotiation */ - err =phy_write (phydev,MII_BMCR ,BMCR_RESET ); - -if (err <0 ) -return err; - - err =phy_write (phydev,0x1d ,0x1f ); -if (err <0 ) -return err; - - err =phy_write (phydev,0x1e ,0x200c ); -if (err <0 ) -return err; - - err =phy_write (phydev,0x1d ,0x5 ); -if (err <0 ) -return err; - - err =phy_write (phydev,0x1e ,0 ); -if (err <0 ) -return err; - - err =phy_write (phydev,0x1e ,0x100 ); -if (err <0 ) -return err; - err =phy_write (phydev,MII_M1011_PHY_SCR ,MII_M1011_PHY_SCR_AUTO_CROSS );if (err <0 )
@@ -188,6 +160,42 @@ static int marvell_config_aneg(struct phreturn 0 ; } +static int m88e1101_config_aneg (struct phy_device *phydev) +{ +int err; + +/* This Marvell PHY has an errata which requires +* that certain registers get written in order +* to restart autonegotiation +*/ + err =phy_write (phydev,MII_BMCR ,BMCR_RESET ); + +if (err <0 ) +return err; + + err =phy_write (phydev,0x1d ,0x1f ); +if (err <0 ) +return err; + + err =phy_write (phydev,0x1e ,0x200c ); +if (err <0 ) +return err; + + err =phy_write (phydev,0x1d ,0x5 ); +if (err <0 ) +return err; + + err =phy_write (phydev,0x1e ,0 ); +if (err <0 ) +return err; + + err =phy_write (phydev,0x1e ,0x100 ); +if (err <0 ) +return err; + +return marvell_config_aneg (phydev); +} +#ifdef CONFIG_OF_MDIO /* * Set and/or override some configuration registers based on the
@@ -722,7 +730,7 @@ static struct phy_driver marvell_drivers .name = "Marvell 88E1101", .features = PHY_GBIT_FEATURES, .flags = PHY_HAS_INTERRUPT, - .config_aneg = &marvell_config_aneg, + .config_aneg = &m88e1101_config_aneg, .read_status = &genphy_read_status, .ack_interrupt = &marvell_ack_interrupt, .config_intr = &marvell_config_intr,
Quoted 8 lines · Ben Hutchings
This is the start of the stable review cycle for the 3.2.93 release. There are 106 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Tue Sep 12 12:00:00 UTC 2017. Anything received after that time might be too late.
Build results:
total: 86 pass: 86 fail: 0 Qemu test results: total: 69 pass: 69 fail: 0
Details are available at http://kerneltests.org/builders.
Guenter
Quoted 13 lines · Guenter Roeck
Quoted 11 lines · Ben Hutchings
This is the start of the stable review cycle for the 3.2.93 release.
There are 106 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.Responses should be made by Tue Sep 12 12:00:00 UTC 2017. Anything received after that time might be too late.
Quoted 6 lines
Build results:
total: 86 pass: 86 fail: 0 Qemu test results: total: 69 pass: 69 fail: 0Details are available at http://kerneltests.org/builders.
Thanks for checking!
Ben.
Signature · 4 lines
Ben Hutchings [W]e found...that it wasn't as easy to get programs right as we had thought. ... I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs. - Maurice Wilkes, 1949