3.12.46-stable review
Subsystems (3)
cover 3.12.46-stable review
This is the start of the stable review cycle for the 3.12.46 release. There are 123 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu Aug 6 16:39:14 CEST 2015. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
http://kernel.org/pub/linux/kernel/people/jirislaby/stable-review/patch-3.12.46-rc1.xz
and the diffstat can be found below.
thanks,
js
===============
AMAN DEEP (1):
usb: xhci: Bugfix for NULL pointer deference in xhci_endpoint_init()
function
Al Viro (3):
9p: forgetting to cancel request on interrupted zero-copy RPC 9p: don't leave a half-initialized inode sitting around sg_start_req(): make sure that there's not too many elements in iovec
Alan Cox (1):
i2c: i801: Add PCI ID for Intel Braswell
Alan Stern (1):
USB: usbfs: allow URBs to be reaped after disconnection
Aleksei Mamlin (1):
libata: add ATA_HORKAGE_BROKEN_FPDMA_AA quirk for HP 250GB SATA disk
VB0250EAVER
Alex Deucher (2):
drm/radeon: take the mode_config mutex when dealing with hpds (v2) drm/radeon: add a dpm quirk for Sapphire Radeon R9 270X 2GB GDDR5
Arnd Bergmann (1):
ideapad: fix software rfkill setting
Arne Fitzenreiter (2):
libata: add ATA_HORKAGE_NOTRIM
libata: force disable trim for SuperSSpeed S238
Axel Lin (3):
ASoC: wm8737: Fixup setting VMID Impedance control register
ASoC: wm8955: Fix setting wrong register for WM8955_K_8_0_MASK bits
ASoC: wm8903: Fix define for WM8903_VMID_RES_250K
Bill Richardson (1):
mfd: cros_ec: cleanup: cros_ec.c is GPL licensed, like all the others.
Bob Moore (1):
ACPICA: Add "Windows 2013" string to _OSI support.
Boris BREZILLON (1):
mtd: nand: fix erroneous read_buf call in nand_write_page_raw_syndrome
Chad Dupuis (1):
qla2xxx: Mark port lost when we receive an RSCN for it.
Chris Metcalf (1):
__bitmap_parselist: fix bug in empty string handling
Chris Wilson (1):
agp/intel: Fix typo in needs_ilk_vtd_wa()
Christoffer Dall (1):
arm64: Don't report clear pmds and puds as huge
Chuck Lever (1):
NFS: Fix size of NFSACL SETACL operations
Claudio Cappelli (1):
USB: option: add 2020:4000 ID
Cyrille Pitchen (1):
i2c: at91: fix a race condition when using the DMA controller
Damian Eppel (1):
clocksource: exynos_mct: Avoid blocking calls in the cpu hotplug
notifier
Dan Carpenter (3):
drivers/mailbox/omap: make mbox->irq signed for error handling
ASoC: imx-wm8962: Add a missing error check
USB: devio: fix a condition in async_completed()
Darrick J. Wong (1):
ext4: don't retry file block mapping on bigalloc fs with non-extent
file
Dennis Yang (1):
dm btree remove: fix bug in redistribute3
Devin Ryles (2):
ALSA: hda_intel: Add DeviceIDs for Sunrise Point-LP
i2c: i801: Add DeviceIDs for SunrisePoint LP
Ding Wang (1):
mmc: card: Fixup request missing in mmc_blk_issue_rw_rq
Dmitry Monakhov (1):
jbd2: use GFP_NOFS in jbd2_cleanup_journal_tail()
Eric Sandeen (1):
xfs: fix remote symlinks on V5/CRC filesystems
Eryu Guan (2):
ext4: be more strict when migrating to non-extent based file
ext4: correctly migrate a file with a hole at the beginning
Fabio Estevam (3):
iio: light: hid-sensor-als.c: Fix memory leak in probe()
iio: gyro: hid-sensor-gyro-3d: Fix memory leak in probe()
iio: accel: hid-sensor-accel-3d: Fix memory leak in probe()
Felipe Balbi (1):
usb: musb: host: rely on port_mode to call musb_start()
Felix Fietkau (1):
ath9k: fix DMA stop sequence for AR9003+
Filipe Manana (2):
Btrfs: use kmem_cache_free when freeing entry in inode cache
Btrfs: fix memory leak in the extent_same ioctl
Firo Yang (1):
md: fix a build warning
Frediano Ziglio (2):
drm/qxl: Do not cause spice-server to clean our objects drm/qxl: Do not leak memory if qxl_release_list_add fails
Haggai Eran (1):
staging: rtl8712: prevent buffer overrun in recvbuf2recvframe
Hon Ching \\(Vicky\\) Lo (1):
vTPM: set virtual device before passing to ibmvtpm_reset_crq
Ilya Dryomov (2):
crush: fix a bug in tree bucket decode
rbd: use GFP_NOIO in rbd_obj_request_create()
JM Friedt (1):
iio: DAC: ad5624r_spi: fix bit shift of output data value
James Ralston (1):
ALSA: hda_intel: Add Device IDs for Intel Sunrise Point PCH
Jan Kara (1):
reiserfs: Fix use after free in journal teardown
Jan Leupold (1):
iio: adc: at91_adc: allow to use full range of startup time
Jean Delvare (2):
i2c: i801: Fix the alignment of the device table
i2c: i801: Add device ID for Intel Wildcat Point PCH
Jeff Layton (1):
nfs: increase size of EXCHANGE_ID name string buffer
Joe Perches (1):
hpfs: hpfs_error: Remove static buffer, use vsprintf extension %pV
instead
Joe Thornber (2):
dm space map metadata: fix occasional leak of a metadata block on
resize
dm btree: silence lockdep lock inversion in dm_btree_del()
Johannes Thumshirn (1):
USB: serial: Destroy serial_minors IDR on module exit
John Youn (1):
usb: dwc3: Reset the transfer resource index on SET_INTERFACE
Joseph Qi (1):
jbd2: fix ocfs2 corrupt when updating journal superblock fails
Jérôme Glisse (2):
drm/radeon: compute ring fix hibernation (CI GPU family) v2. drm/radeon: SDMA fix hibernation (CI GPU family).
Len Brown (2):
intel_idle: Broadwell support
intel_idle: support additional Broadwell model
Libin Yang (5):
ALSA: hda_intel: apply the Seperate stream_tag for Skylake
ALSA: hda_intel: apply the Seperate stream_tag for Sunrise Point
ALSA: hda - add codec ID for Skylake display audio codec
ALSA: hda/hdmi - apply Haswell fix-ups to Skylake display codec
ALSA: hda_intel: add AZX_DCAPS_I915_POWERWELL for SKL and BSW
Linus Torvalds (1):
Fix firmware loader uevent buffer NULL pointer dereference
Lior Amsalem (1):
dmaengine: mv_xor: bug fix for racing condition in descriptors cleanup
Lukas Czerner (1):
ext4: fix reservation release on invalidatepage for delalloc fs
Lv Zheng (1):
ACPICA: Tables: Fix an issue that FACS initialization is performed
twice
Marcel Holtmann (1):
Bluetooth: btusb: Fix memory leak in Intel setup routine
Martin K. Petersen (1):
libata: Do not blacklist Micron M500DC
Martin Schwidefsky (1):
kexec: allocate the kexec control page with KEXEC_CONTROL_MEMORY_GFP
Mauro Carvalho Chehab (3):
af9013: Don't accept invalid bandwidth
s5h1420: fix a buffer overflow when checking userspace params
cx24116: fix a buffer overflow when checking userspace params
Mengdong Lin (1):
ALSA: hda - verify pin:cvt connection on preparing a stream for Intel
HDMI codec
Michal Hocko (1):
ext4: replace open coded nofail allocation in ext4_free_blocks()
Michal Kazior (1):
mac80211: prevent possible crypto tx tailroom corruption
Michel Dänzer (1):
drm/radeon: Don't flush the GART TLB if rdev->gart.ptr == NULL
Mika Westerberg (2):
gpio/lynxpoint: add new ACPI ID
i2c: designware: add new ACPI IDs
Mike Christie (1):
[SCSI] be2iscsi: fix bad if expression
Miklos Szeredi (1):
fuse: initialize fc->release before calling it
Mikulas Patocka (2):
libata: increase the timeout when setting transfer mode dm stats: fix divide by zero if 'number_of_areas' arg is zero
Nicholas Bellinger (1):
iscsi-target: Convert iscsi_thread_set usage to kthread.h
Olga Kornievskaia (1):
fixing infinite OPEN loop in 4.0 stateid recovery
Pali Rohár (1):
dell-laptop: Fix allocating & freeing SMI buffer page
Paolo Bonzini (1):
kvm: x86: fix kvm_apic_has_events to check for NULL pointer
Peter Sanford (1):
USB: cp210x: add ID for Aruba Networks controllers
Rafal Redzimski (1):
ALSA: hda_controller: Separate stream_tag for input and output
streams.
Richard Fitzgerald (1):
ASoC: arizona: Fix noise generator gain TLV
Sagi Grimberg (2):
iser-target: Fix possible deadlock in RDMA_CM connection error
iser-target: release stale iser connections
Steven Rostedt (Red Hat) (3):
tracing/filter: Do not WARN on operand count going below zero tracing/filter: Do not allow infix to exceed end of string
tracing: Have branch tracer use recursive field of task struct
Stevens, Nick (1):
hwmon: (mcp3021) Fix broken output scaling
Subbaraya Sundeep Bhatta (2):
usb: dwc3: gadget: return error if command sent to DGCMD register
fails
usb: dwc3: gadget: return error if command sent to DEPCMD register
fails
Takashi Iwai (5):
ALSA: hda - Add dock pin setups for Thinkpad T440
ALSA: hda - Treat zero connection as non-error
ALSA: usb-audio: Resume mixer values properly
ALSA: usb-audio: Save mixer status only once at suspend
ALSA: usb-audio: Fix deadlocks at resuming
Theodore Ts'o (2):
ext4: fix race between truncate and __ext4_journalled_writepage()
ext4: call sync_blockdev() before invalidate_bdev() in put_super()
Tomas Winkler (1):
mmc: block: Add missing mmc_blk_put() in power_ro_lock_show()
Trond Myklebust (1):
SUNRPC: Fix a memory leak in the backchannel code
Uwe Kleine-König (1):
watchdog: omap: assert the counter being stopped before reprogramming
Vasily Averin (1):
security_syslog() should be called once only
Zhao Junwang (1):
drm: add a check for x/y in drm_mode_setcrtc
Zidan Wang (1):
ASoC: wm8960: the enum of "DAC Polarity" should be wm8960_enum[1]
[email protected] (1):
i2c: i801: Add Device IDs for Intel Sunrise Point PCH
Documentation/i2c/busses/i2c-i801 | 3 + arch/arm64/mm/hugetlbpage.c | 4 +- arch/s390/include/asm/kexec.h | 3 + arch/x86/kvm/lapic.h | 2 +- drivers/acpi/acpica/utosi.c | 1 + drivers/acpi/acpica/utxfinit.c | 10 +- drivers/ata/libata-core.c | 11 +- drivers/ata/libata-scsi.c | 3 +- drivers/base/firmware_class.c | 16 ++- drivers/block/rbd.c | 4 +- drivers/bluetooth/btusb.c | 2 + drivers/char/agp/intel-gtt.c | 2 +- drivers/char/tpm/tpm_ibmvtpm.c | 5 +- drivers/clocksource/exynos_mct.c | 43 ++++-- drivers/dma/mv_xor.c | 72 ++++++---- drivers/dma/mv_xor.h | 1 + drivers/gpio/gpio-lynxpoint.c | 1 + drivers/gpu/drm/drm_crtc.c | 7 +- drivers/gpu/drm/qxl/qxl_cmd.c | 1 + drivers/gpu/drm/qxl/qxl_ioctl.c | 4 +- drivers/gpu/drm/radeon/cik.c | 34 +++++ drivers/gpu/drm/radeon/cik_sdma.c | 11 ++ drivers/gpu/drm/radeon/radeon_gart.c | 12 +- drivers/gpu/drm/radeon/radeon_irq_kms.c | 2 + drivers/gpu/drm/radeon/si_dpm.c | 1 + drivers/hwmon/mcp3021.c | 14 +- drivers/i2c/busses/Kconfig | 3 + drivers/i2c/busses/i2c-at91.c | 70 +++++++--- drivers/i2c/busses/i2c-designware-platdrv.c | 2 + drivers/i2c/busses/i2c-i801.c | 147 +++++++++++---------- drivers/idle/intel_idle.c | 71 +++++++++- drivers/iio/accel/hid-sensor-accel-3d.c | 13 +- drivers/iio/adc/at91_adc.c | 2 +- drivers/iio/dac/ad5624r_spi.c | 4 +- drivers/iio/gyro/hid-sensor-gyro-3d.c | 13 +- drivers/iio/light/hid-sensor-als.c | 12 +- drivers/infiniband/ulp/isert/ib_isert.c | 32 ++++- drivers/mailbox/omap-mbox.h | 2 +- drivers/md/dm-stats.c | 2 + drivers/md/md.c | 2 +- drivers/md/persistent-data/dm-btree-remove.c | 6 +- drivers/md/persistent-data/dm-btree.c | 2 +- drivers/md/persistent-data/dm-space-map-metadata.c | 50 ++++--- drivers/media/dvb-frontends/af9013.c | 4 + drivers/media/dvb-frontends/cx24116.c | 8 +- drivers/media/dvb-frontends/s5h1420.c | 2 +- drivers/mfd/cros_ec.c | 3 + drivers/mmc/card/block.c | 10 +- drivers/mtd/nand/nand_base.c | 2 +- drivers/net/wireless/ath/ath9k/main.c | 12 +- drivers/platform/x86/dell-laptop.c | 8 +- drivers/platform/x86/ideapad-laptop.c | 2 +- drivers/scsi/be2iscsi/be_main.c | 2 +- drivers/scsi/qla2xxx/qla_isr.c | 17 ++- drivers/scsi/sg.c | 3 + drivers/staging/rtl8712/rtl8712_recv.c | 3 +- drivers/target/iscsi/iscsi_target.c | 104 +++++++-------- drivers/target/iscsi/iscsi_target_core.h | 7 + drivers/target/iscsi/iscsi_target_erl0.c | 13 +- drivers/target/iscsi/iscsi_target_login.c | 59 ++++++++- drivers/usb/core/devio.c | 65 +++++---- drivers/usb/dwc3/ep0.c | 4 + drivers/usb/dwc3/gadget.c | 4 + drivers/usb/host/xhci-mem.c | 2 +- drivers/usb/musb/musb_virthub.c | 4 +- drivers/usb/serial/cp210x.c | 1 + drivers/usb/serial/option.c | 1 + drivers/usb/serial/usb-serial.c | 1 + drivers/watchdog/omap_wdt.c | 7 + fs/9p/vfs_inode.c | 3 +- fs/9p/vfs_inode_dotl.c | 3 +- fs/btrfs/inode-map.c | 2 +- fs/btrfs/ioctl.c | 3 +- fs/ext4/indirect.c | 2 +- fs/ext4/inode.c | 38 +++++- fs/ext4/mballoc.c | 16 +-- fs/ext4/migrate.c | 17 ++- fs/ext4/super.c | 1 + fs/fuse/inode.c | 2 +- fs/hpfs/super.c | 11 +- fs/jbd2/checkpoint.c | 7 +- fs/jbd2/journal.c | 38 +++++- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4state.c | 2 + fs/reiserfs/journal.c | 21 ++- fs/reiserfs/super.c | 6 +- fs/xfs/xfs_symlink.c | 2 +- include/acpi/actypes.h | 1 + include/linux/jbd2.h | 4 +- include/linux/kexec.h | 4 + include/linux/libata.h | 1 + include/linux/nfs_xdr.h | 2 +- include/uapi/linux/usbdevice_fs.h | 3 +- kernel/kexec.c | 2 +- kernel/printk/printk.c | 11 +- kernel/trace/trace.h | 1 + kernel/trace/trace_branch.c | 17 ++- kernel/trace/trace_events_filter.c | 10 +- lib/bitmap.c | 17 +-- net/9p/client.c | 3 +- net/ceph/osdmap.c | 2 +- net/mac80211/main.c | 3 + net/sunrpc/backchannel_rqst.c | 2 +- sound/pci/hda/hda_codec.c | 2 +- sound/pci/hda/hda_intel.c | 42 +++++- sound/pci/hda/patch_hdmi.c | 38 +++++- sound/pci/hda/patch_realtek.c | 15 ++- sound/soc/codecs/wm5102.c | 2 +- sound/soc/codecs/wm5110.c | 2 +- sound/soc/codecs/wm8737.c | 6 +- sound/soc/codecs/wm8903.h | 2 +- sound/soc/codecs/wm8955.c | 2 +- sound/soc/codecs/wm8960.c | 2 +- sound/soc/codecs/wm8997.c | 2 +- sound/soc/fsl/imx-wm8962.c | 2 +- sound/usb/card.c | 28 +++- sound/usb/mixer.c | 99 +++++++++++--- sound/usb/mixer.h | 7 +- sound/usb/usbaudio.h | 1 + 119 files changed, 1098 insertions(+), 463 deletions(-)
Signature · 1 line
2.5.0
PATCH 1/123 mfd: cros_ec: cleanup: cros_ec.c is GPL licensed, like all the others.
From: Bill Richardson <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit a865a589144da6dbf26750b7193a9748da159305 upstream.
This module has always been GPL licensed. It was just missing the explicit declaration to avoid tainting the kernel.
--- drivers/mfd/cros_ec.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/mfd/cros_ec.c +3 -0
@@ -184,3 +184,6 @@ int cros_ec_resume(struct cros_ec_device *ec_dev)EXPORT_SYMBOL (cros_ec_resume);#endif + +MODULE_LICENSE ("GPL" ); +MODULE_DESCRIPTION ("ChromeOS EC core driver" );
Signature · 1 line
2.5.0
PATCH 2/123 drivers/mailbox/omap: make mbox->irq signed for error handling
From: Dan Carpenter <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4a102b4d144f0422eb8b0a59c7cb194bf12163a9 upstream.
There is a bug in omap2_mbox_probe() where we try do:
mbox->irq = platform_get_irq(pdev, info->irq_id);
if (mbox->irq < 0) {The problem is that mbox->irq is unsigned so the error handling doesn't work. I've changed it to a signed integer.
--- drivers/mailbox/omap-mbox.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mailbox/omap-mbox.h +1 -1
@@ -52,7 +52,7 @@ struct omap_mbox_queue {struct omap_mbox {const char *name; -unsigned int irq; +int irq;struct omap_mbox_queue *txq, *rxq;struct omap_mbox_ops *ops;struct device *dev;
Signature · 1 line
2.5.0
PATCH 3/123 iio: light: hid-sensor-als.c: Fix memory leak in probe()
In reply to Jiri SlabyFrom: Fabio Estevam <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 9ecdbed7903921f29adae63a3155814b453e7186 upstream.
'channels' is allocated via kmemdup and it is never freed in the subsequent error paths.
Use 'indio_dev->channels' directly instead, so that we avoid such memory leak problem.
--- drivers/iio/light/hid-sensor-als.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/iio/light/hid-sensor-als.c +6 -6
@@ -239,7 +239,6 @@ static int hid_als_probe(struct platform_device *pdev)struct iio_dev *indio_dev;struct als_state *als_state;struct hid_sensor_hub_device *hsdev = pdev->dev.platform_data; -struct iio_chan_spec *channels; indio_dev =devm_iio_device_alloc (&pdev->dev,sizeof (struct als_state ));if (!indio_dev)
@@ -257,20 +256,21 @@ static int hid_als_probe(struct platform_device *pdev)return ret; } - channels =kmemdup (als_channels,sizeof (als_channels),GFP_KERNEL ); -if (!channels) { + indio_dev->channels =kmemdup (als_channels, +sizeof (als_channels),GFP_KERNEL ); +if (!indio_dev->channels) {dev_err (&pdev->dev,"failed to duplicate channels\n" );return -ENOMEM ; } - ret =als_parse_report (pdev, hsdev, channels, -HID_USAGE_SENSOR_ALS , als_state); + ret =als_parse_report (pdev, hsdev, + (struct iio_chan_spec *)indio_dev->channels, +HID_USAGE_SENSOR_ALS , als_state);if (ret) {dev_err (&pdev->dev,"failed to setup attributes\n" ); goto error_free_dev_mem; } - indio_dev->channels = channels; indio_dev->num_channels =ARRAY_SIZE (als_channels); indio_dev->dev.parent = &pdev->dev;
Signature · 1 line
2.5.0
PATCH 4/123 iio: gyro: hid-sensor-gyro-3d: Fix memory leak in probe()
In reply to Jiri SlabyFrom: Fabio Estevam <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d8c9d23e29e3d758ea477adaa95e28cbf3556518 upstream.
'channels' is allocated via kmemdup and it is never freed in the subsequent error paths.
Use 'indio_dev->channels' directly instead, so that we avoid such memory leak problem.
--- drivers/iio/gyro/hid-sensor-gyro-3d.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
drivers/iio/gyro/hid-sensor-gyro-3d.c +6 -7
@@ -272,7 +272,6 @@ static int hid_gyro_3d_probe(struct platform_device *pdev)struct iio_dev *indio_dev;struct gyro_3d_state *gyro_state;struct hid_sensor_hub_device *hsdev = pdev->dev.platform_data; -struct iio_chan_spec *channels; indio_dev =devm_iio_device_alloc (&pdev->dev,sizeof (*gyro_state));if (!indio_dev)
@@ -291,21 +290,21 @@ static int hid_gyro_3d_probe(struct platform_device *pdev)return ret; } - channels =kmemdup (gyro_3d_channels,sizeof (gyro_3d_channels), -GFP_KERNEL ); -if (!channels) { + indio_dev->channels =kmemdup (gyro_3d_channels, +sizeof (gyro_3d_channels),GFP_KERNEL ); +if (!indio_dev->channels) {dev_err (&pdev->dev,"failed to duplicate channels\n" );return -ENOMEM ; } - ret =gyro_3d_parse_report (pdev, hsdev, channels, -HID_USAGE_SENSOR_GYRO_3D , gyro_state); + ret =gyro_3d_parse_report (pdev, hsdev, + (struct iio_chan_spec *)indio_dev->channels, +HID_USAGE_SENSOR_GYRO_3D , gyro_state);if (ret) {dev_err (&pdev->dev,"failed to setup attributes\n" ); goto error_free_dev_mem; } - indio_dev->channels = channels; indio_dev->num_channels =ARRAY_SIZE (gyro_3d_channels); indio_dev->dev.parent = &pdev->dev; indio_dev->info = &gyro_3d_info;
Signature · 1 line
2.5.0
PATCH 5/123 iio: accel: hid-sensor-accel-3d: Fix memory leak in probe()
In reply to Jiri SlabyFrom: Fabio Estevam <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit b136faff9bc2f4adea050ed2119c01199f9a86a5 upstream.
'channels' is allocated via kmemdup and it is never freed in the subsequent error paths.
Use 'indio_dev->channels' directly instead, so that we avoid such memory leak problem.
--- drivers/iio/accel/hid-sensor-accel-3d.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
drivers/iio/accel/hid-sensor-accel-3d.c +6 -7
@@ -272,7 +272,6 @@ static int hid_accel_3d_probe(struct platform_device *pdev)struct iio_dev *indio_dev;struct accel_3d_state *accel_state;struct hid_sensor_hub_device *hsdev = pdev->dev.platform_data; -struct iio_chan_spec *channels; indio_dev =devm_iio_device_alloc (&pdev->dev,sizeof (struct accel_3d_state ));
@@ -293,21 +292,21 @@ static int hid_accel_3d_probe(struct platform_device *pdev)return ret; } - channels =kmemdup (accel_3d_channels,sizeof (accel_3d_channels), -GFP_KERNEL ); -if (!channels) { + indio_dev->channels =kmemdup (accel_3d_channels, +sizeof (accel_3d_channels),GFP_KERNEL ); +if (!indio_dev->channels) {dev_err (&pdev->dev,"failed to duplicate channels\n" );return -ENOMEM ; } - ret =accel_3d_parse_report (pdev, hsdev, channels, -HID_USAGE_SENSOR_ACCEL_3D , accel_state); + ret =accel_3d_parse_report (pdev, hsdev, + (struct iio_chan_spec *)indio_dev->channels, +HID_USAGE_SENSOR_ACCEL_3D , accel_state);if (ret) {dev_err (&pdev->dev,"failed to setup attributes\n" ); goto error_free_dev_mem; } - indio_dev->channels = channels; indio_dev->num_channels =ARRAY_SIZE (accel_3d_channels); indio_dev->dev.parent = &pdev->dev; indio_dev->info = &accel_3d_info;
Signature · 1 line
2.5.0
PATCH 6/123 kvm: x86: fix kvm_apic_has_events to check for NULL pointer
In reply to Jiri SlabyFrom: Paolo Bonzini <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit ce40cd3fc7fa40a6119e5fe6c0f2bc0eb4541009 upstream.
Malicious (or egregiously buggy) userspace can trigger it, but it should never happen in normal operation.
--- arch/x86/kvm/lapic.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/lapic.h +1 -1
@@ -165,7 +165,7 @@ static inline u16 apic_logical_id(struct kvm_apic_map *map, u32 ldr)static inline bool kvm_apic_has_events (struct kvm_vcpu *vcpu) { -return vcpu->arch.apic->pending_events; +return kvm_vcpu_has_lapic (vcpu) && vcpu->arch.apic->pending_events; }bool kvm_apic_pending_eoi (struct kvm_vcpu *vcpu,int vector);
Signature · 1 line
2.5.0
PATCH 7/123 ALSA: hda - Add dock pin setups for Thinkpad T440
In reply to Jiri SlabyFrom: Takashi Iwai <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 1c37c22332a2d2c1b4ab32177a4f847c7fe06e38 upstream.
The headphone and mic jacks on Thinkpad T440 are assigned to pins NID 0x16 and 0x19, respectively. These need to be set up manually by a fixup.
--- sound/pci/hda/patch_realtek.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-)
sound/pci/hda/patch_realtek.c +14 -1
@@ -3745,6 +3745,7 @@ enum {ALC282_FIXUP_ASUS_TX300 ,ALC283_FIXUP_INT_MIC ,ALC290_FIXUP_MONO_SPEAKERS , + ALC292_FIXUP_TPT440_DOCK, }; static const struct hda_fixup alc269_fixups[] = {
@@ -4079,6 +4080,16 @@ static const struct hda_fixup alc269_fixups[] = { .chained = true, .chain_id = ALC269_FIXUP_DELL3_MIC_NO_PRESENCE, }, + [ALC292_FIXUP_TPT440_DOCK] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x16 ,0x21211010 },/* dock headphone */ + {0x19 ,0x21a11010 },/* dock mic */ + { } + }, + .chained = true, + .chain_id =ALC269_FIXUP_LIMIT_INT_MIC_BOOST + }, };static const struct snd_pci_quirk alc269_fixup_tbl[] = {
@@ -4174,7 +4185,8 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {SND_PCI_QUIRK (0x17aa ,0x21fb ,"Thinkpad T430s" ,ALC269_FIXUP_LENOVO_DOCK ),SND_PCI_QUIRK (0x17aa ,0x2203 ,"Thinkpad X230 Tablet" ,ALC269_FIXUP_LENOVO_DOCK ),SND_PCI_QUIRK (0x17aa ,0x2208 ,"Thinkpad T431s" ,ALC269_FIXUP_LENOVO_DOCK ), -SND_PCI_QUIRK (0x17aa ,0x220c ,"Thinkpad" ,ALC269_FIXUP_LIMIT_INT_MIC_BOOST ), +SND_PCI_QUIRK (0x17aa ,0x220c ,"Thinkpad T440s" ,ALC292_FIXUP_TPT440_DOCK ), +SND_PCI_QUIRK (0x17aa ,0x220e ,"Thinkpad T440p" ,ALC292_FIXUP_TPT440_DOCK ),SND_PCI_QUIRK (0x17aa ,0x2212 ,"Thinkpad" ,ALC269_FIXUP_LIMIT_INT_MIC_BOOST ),SND_PCI_QUIRK (0x17aa ,0x2214 ,"Thinkpad" ,ALC269_FIXUP_LIMIT_INT_MIC_BOOST ), SND_PCI_QUIRK(0x17aa, 0x2215, "Thinkpad", ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
@@ -4250,6 +4262,7 @@ static const struct hda_model_fixup alc269_fixup_models[] = { {.id = ALC269_FIXUP_HP_GPIO_LED, .name = "hp-gpio-led"}, {.id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, .name = "dell-headset-multi"}, {.id = ALC269_FIXUP_DELL2_MIC_NO_PRESENCE, .name = "dell-headset-dock"}, + {.id = ALC292_FIXUP_TPT440_DOCK, .name = "tpt440-dock"}, {} };
Signature · 1 line
2.5.0
PATCH 8/123 ALSA: hda - Treat zero connection as non-error
In reply to Jiri SlabyFrom: Takashi Iwai <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4758fed912d7cd0ba53d2694e89b884114de6580 upstream.
The zero-length connection list happens so often on Haswell HDMI, and it results in warning messages like
ALSA: hda_codec: invalid CONNECT_LIST verb 5[1]:0
at each time the codec resumes from the power-save, which is fairly annoying.
Since this is no real error, make it shown only in the verbose debug mode.
--- sound/pci/hda/hda_codec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/pci/hda/hda_codec.c +1 -1
@@ -567,7 +567,7 @@ int snd_hda_get_raw_connections(struct hda_codec *codec, hda_nid_t nid, range_val = !!(parm & (1 << (shift-1 )));/* ranges */ val = parm & mask;if (val ==0 && null_count++) {/* no second chance */ -snd_printk (KERN_WARNING "hda_codec: " +snd_printdd ("hda_codec: " "invalid CONNECT_LIST verb %x[%i]:%x\n" , nid, i, parm);return 0 ;
Signature · 1 line
2.5.0
PATCH 9/123 ALSA: hda_intel: Add Device IDs for Intel Sunrise Point PCH
In reply to Jiri SlabyFrom: James Ralston <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit c8b00fd2f4c504a564adcad5b8bd6952ab850b02 upstream.
This patch adds the HD Audio Device IDs for the Intel Sunrise Point PCH.
[the item position rearranged by tiwai]
--- sound/pci/hda/hda_intel.c | 4 ++++ 1 file changed, 4 insertions(+)
sound/pci/hda/hda_intel.c +4 -0
@@ -170,6 +170,7 @@ MODULE_SUPPORTED_DEVICE("{{Intel, ICH6},""{Intel, LPT}," "{Intel, LPT_LP}," "{Intel, WPT_LP}," +"{Intel, SPT}," "{Intel, HPT}," "{Intel, PBG}," "{Intel, SCH},"
@@ -4063,6 +4064,9 @@ static DEFINE_PCI_DEVICE_TABLE(azx_ids) = {/* Wildcat Point-LP */ { PCI_DEVICE(0x8086, 0x9ca0), .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, + /* Sunrise Point */ + { PCI_DEVICE(0x8086, 0xa170), + .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, /* Haswell */ { PCI_DEVICE(0x8086, 0x0a0c), .driver_data = AZX_DRIVER_HDMI | AZX_DCAPS_INTEL_HASWELL },
Signature · 1 line
2.5.0
PATCH 10/123 ALSA: hda_intel: Add DeviceIDs for Sunrise Point-LP
In reply to Jiri SlabyFrom: Devin Ryles <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit b4565913460cbd7d86c6bd52913dfaa07fa384aa upstream.
This patch adds DeviceIDs for Sunrise Point-LP
--- sound/pci/hda/hda_intel.c | 4 ++++ 1 file changed, 4 insertions(+)
sound/pci/hda/hda_intel.c +4 -0
@@ -171,6 +171,7 @@ MODULE_SUPPORTED_DEVICE("{{Intel, ICH6},""{Intel, LPT_LP}," "{Intel, WPT_LP}," "{Intel, SPT}," +"{Intel, SPT_LP}," "{Intel, HPT}," "{Intel, PBG}," "{Intel, SCH},"
@@ -4067,6 +4068,9 @@ static DEFINE_PCI_DEVICE_TABLE(azx_ids) = {/* Sunrise Point */ { PCI_DEVICE(0x8086, 0xa170), .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, + /* Sunrise Point-LP */ + { PCI_DEVICE(0x8086, 0x9d70), + .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, /* Haswell */ { PCI_DEVICE(0x8086, 0x0a0c), .driver_data = AZX_DRIVER_HDMI | AZX_DCAPS_INTEL_HASWELL },
Signature · 1 line
2.5.0
PATCH 11/123 ALSA: hda - verify pin:cvt connection on preparing a stream for Intel HDMI codec
In reply to Jiri SlabyFrom: Mengdong Lin <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2df6742f613840a0b0a1590fb28f7af5b058a673 upstream.
This is a temporary fix for some Intel HDMI codecs to avoid no sound output for a resuming playback after S3.
After S3, the audio driver restores pin:cvt connection selections by snd_hda_codec_resume_cache(). However this can happen before the gfx side is ready and such connect selection is overlooked by HW. After gfx is ready, the pins make the default selection again. And this will cause multiple pins share a same convertor and mute control will affect each other. Thus a resumed audio playback become silent after S3.
This patch verifies pin:cvt connection on preparing a stream, to assure the pin selects the right convetor and an assigned convertor is not shared by other unused pins. Apply this fix-up on Haswell, Broadwell and Valleyview (Baytrail).
We need this temporary fix before a reliable software communication channel is established between audio and gfx, to sync audio/gfx operations.
--- sound/pci/hda/patch_hdmi.c | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)
sound/pci/hda/patch_hdmi.c +32 -0
@@ -67,6 +67,7 @@ struct hdmi_spec_per_pin {hda_nid_t pin_nid;int num_mux_nids;hda_nid_t mux_nids[HDA_MAX_CONNECTIONS ]; +int mux_idx;hda_nid_t cvt_nid;struct hda_codec *codec;
@@ -1266,6 +1267,8 @@ static int hdmi_choose_cvt(struct hda_codec *codec,if (cvt_idx == spec->num_cvts)return -ENODEV ; + per_pin->mux_idx = mux_idx; +if (cvt_id) *cvt_id = cvt_idx;if (mux_id)
@@ -1274,6 +1277,22 @@ static int hdmi_choose_cvt(struct hda_codec *codec,return 0 ; } +/* Assure the pin select the right convetor */ +static void intel_verify_pin_cvt_connect (struct hda_codec *codec, +struct hdmi_spec_per_pin *per_pin) +{ +hda_nid_t pin_nid = per_pin->pin_nid; +int mux_idx, curr; + + mux_idx = per_pin->mux_idx; + curr =snd_hda_codec_read (codec, pin_nid,0 , +AC_VERB_GET_CONNECT_SEL ,0 ); +if (curr != mux_idx) +snd_hda_codec_write_cache (codec, pin_nid,0 , +AC_VERB_SET_CONNECT_SEL , + mux_idx); +} +/* Intel HDMI workaround to fix audio routing issue: * For some Intel display codecs, pins share the same connection list. * So a conveter can be selected by multiple pins and playback on any of these
@@ -1689,6 +1708,19 @@ static int generic_hdmi_playback_pcm_prepare(struct hda_pcm_stream *hinfo,bool non_pcm;int pinctl; +if (is_haswell_plus (codec) ||is_valleyview (codec)) { +/* Verify pin:cvt selections to avoid silent audio after S3. +* After S3, the audio driver restores pin:cvt selections +* but this can happen before gfx is ready and such selection +* is overlooked by HW. Thus multiple pins can share a same +* default convertor and mute control will affect each other, +* which can cause a resumed audio playback become silent +* after S3. +*/ +intel_verify_pin_cvt_connect (codec, per_pin); +intel_not_share_assigned_cvt (codec, pin_nid, per_pin->mux_idx); + } + non_pcm =check_non_pcm_per_cvt (codec, cvt_nid);mutex_lock (&per_pin->lock); per_pin->channels = substream->runtime->channels;
Signature · 1 line
2.5.0
PATCH 12/123 ALSA: hda_controller: Separate stream_tag for input and output streams.
In reply to Jiri SlabyFrom: Rafal Redzimski <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 93e3423e6ba4b0ddaf056ecbdf5bc46f18f41deb upstream.
Implemented separate stream_tag assignment for input and output streams. According to hda specification stream tag must be unique throughout the input streams group, however an output stream might use a stream tag which is already in use by an input stream. This change is necessary to support HW which provides a total of more than 15 stream DMA engines which with legacy implementation causes an overflow on SDxCTL.STRM field (and the whole SDxCTL register) and as a result usage of Reserved value 0 in the SDxCTL.STRM field which confuses HDA controller.
--- sound/pci/hda/hda_intel.c | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-)
sound/pci/hda/hda_intel.c +23 -2
@@ -607,6 +607,7 @@ enum {#define AZX_DCAPS_COUNT_LPIB_DELAY (1 << 25)/* Take LPIB as delay */ #define AZX_DCAPS_PM_RUNTIME (1 << 26)/* runtime PM support */ #define AZX_DCAPS_I915_POWERWELL (1 << 27)/* HSW i915 power well support */ +#define AZX_DCAPS_SEPARATE_STREAM_TAG (1 << 30)/* capture and playback use separate stream tag */ /* quirks for Intel PCH */ #define AZX_DCAPS_INTEL_PCH_NOPM \
@@ -2717,12 +2718,20 @@ static int azx_mixer_create(struct azx *chip) } +static bool is_input_stream (struct azx *chip,unsigned char index) +{ +return (index >= chip->capture_index_offset && + index < chip->capture_index_offset + chip->capture_streams); +} +/* * initialize SD streams */ static int azx_init_stream (struct azx *chip) {int i; +int in_stream_tag =0 ; +int out_stream_tag =0 ;/* initialize each stream (aka device) * assign the starting bdl address to each stream (device)
@@ -2735,9 +2744,21 @@ static int azx_init_stream(struct azx *chip) azx_dev->sd_addr = chip->remap_addr + (0x20 * i +0x80 );/* int mask: SDI0=0x01, SDI1=0x02, ... SDO3=0x80 */ azx_dev->sd_int_sta_mask =1 << i; -/* stream tag: must be non-zero and unique */ azx_dev->index = i; - azx_dev->stream_tag = i +1 ; + +/* stream tag must be unique throughout +* the stream direction group, +* valid values 1...15 +* use separate stream tag if the flag +* AZX_DCAPS_SEPARATE_STREAM_TAG is used +*/ +if (chip->driver_caps &AZX_DCAPS_SEPARATE_STREAM_TAG ) + azx_dev->stream_tag = +is_input_stream (chip, i) ? + ++in_stream_tag : + ++out_stream_tag; +else + azx_dev->stream_tag = i +1 ; }return 0 ;
Signature · 1 line
2.5.0
PATCH 13/123 ALSA: hda_intel: apply the Seperate stream_tag for Skylake
In reply to Jiri SlabyFrom: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d6795827bd79b28fef1abdaf7e525fcca506b831 upstream.
The total stream number of Skylake's input and output stream exceeds 15, which will cause some streams do not work because of the overflow on SDxCTL.STRM field if using the legacy stream tag allocation method.
This patch uses the new stream tag allocation method by add the flag AZX_DCAPS_SEPARATE_STREAM_TAG for Skylake platform.
--- sound/pci/hda/hda_intel.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
sound/pci/hda/hda_intel.c +4 -1
@@ -622,6 +622,9 @@ enum { AZX_DCAPS_COUNT_LPIB_DELAY | AZX_DCAPS_PM_RUNTIME | \ AZX_DCAPS_I915_POWERWELL) +#define AZX_DCAPS_INTEL_SKYLAKE \ + (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_SEPARATE_STREAM_TAG) +/* quirks for ATI SB / AMD Hudson */ #define AZX_DCAPS_PRESET_ATI_SB \ (AZX_DCAPS_ATI_SNOOP | AZX_DCAPS_NO_TCSEL | \
@@ -4091,7 +4094,7 @@ static DEFINE_PCI_DEVICE_TABLE(azx_ids) = { .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH },/* Sunrise Point-LP */ { PCI_DEVICE(0x8086, 0x9d70), - .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, + .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_SKYLAKE }, /* Haswell */ { PCI_DEVICE(0x8086, 0x0a0c), .driver_data = AZX_DRIVER_HDMI | AZX_DCAPS_INTEL_HASWELL },
Signature · 1 line
2.5.0
PATCH 14/123 ALSA: hda_intel: apply the Seperate stream_tag for Sunrise Point
In reply to Jiri SlabyFrom: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit db48abf4367cb1f9e118defee0a37238638c2752 upstream.
The total stream number of Sunrise Point's input and output stream exceeds 15, which will cause some streams do not work because of the overflow on SDxCTL.STRM field if using the legacy stream tag allocation method.
This patch uses the new stream tag allocation method by add the flag AZX_DCAPS_SEPARATE_STREAM_TAG for Skylake platform.
--- sound/pci/hda/hda_intel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/pci/hda/hda_intel.c +1 -1
@@ -4091,7 +4091,7 @@ static DEFINE_PCI_DEVICE_TABLE(azx_ids) = { .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH },/* Sunrise Point */ { PCI_DEVICE(0x8086, 0xa170), - .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, + .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_SKYLAKE }, /* Sunrise Point-LP */ { PCI_DEVICE(0x8086, 0x9d70), .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_SKYLAKE },
Signature · 1 line
2.5.0
PATCH 15/123 ALSA: hda - add codec ID for Skylake display audio codec
In reply to Jiri SlabyFrom: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 99fcb3778b0ec12a8fa8b58435d75e9203bb430d upstream.
This patch adds codec ID (0x80862809) and module alias for Skylake display codec.
--- sound/pci/hda/patch_hdmi.c | 2 ++ 1 file changed, 2 insertions(+)
sound/pci/hda/patch_hdmi.c +2 -0
@@ -2887,6 +2887,7 @@ static const struct hda_codec_preset snd_hda_preset_hdmi[] = { { .id = 0x80862806, .name = "PantherPoint HDMI", .patch = patch_generic_hdmi }, { .id = 0x80862807, .name = "Haswell HDMI", .patch = patch_generic_hdmi }, { .id = 0x80862808, .name = "Broadwell HDMI", .patch = patch_generic_hdmi }, +{ .id = 0x80862809, .name = "Skylake HDMI", .patch = patch_generic_hdmi }, { .id = 0x80862880, .name = "CedarTrail HDMI", .patch = patch_generic_hdmi }, { .id = 0x80862882, .name = "Valleyview2 HDMI", .patch = patch_generic_hdmi }, { .id = 0x80862883, .name = "Braswell HDMI", .patch = patch_generic_hdmi },
@@ -2944,6 +2945,7 @@ MODULE_ALIAS("snd-hda-codec-id:80862805");MODULE_ALIAS ("snd-hda-codec-id:80862806" );MODULE_ALIAS ("snd-hda-codec-id:80862807" );MODULE_ALIAS ("snd-hda-codec-id:80862808" ); +MODULE_ALIAS ("snd-hda-codec-id:80862809" );MODULE_ALIAS ("snd-hda-codec-id:80862880" );MODULE_ALIAS ("snd-hda-codec-id:80862882" );MODULE_ALIAS ("snd-hda-codec-id:80862883" );
Signature · 1 line
2.5.0
PATCH 16/123 ALSA: hda/hdmi - apply Haswell fix-ups to Skylake display codec
In reply to Jiri SlabyFrom: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 432ac1a2c028acb289d90f918e3a7b79e4ac8c07 upstream.
Skylake and Haswell have the same behavior on display audio. So this patch applys Haswell fix-ups to Skylake.
--- sound/pci/hda/patch_hdmi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
sound/pci/hda/patch_hdmi.c +3 -1
@@ -46,7 +46,9 @@ MODULE_PARM_DESC(static_hdmi_pcm, "Don't restrict PCM parameters per ELD info");#define is_haswell (codec) ((codec)->vendor_id == 0x80862807)#define is_broadwell (codec) ((codec)->vendor_id == 0x80862808) -#define is_haswell_plus (codec) (is_haswell(codec) || is_broadwell(codec)) +#define is_skylake (codec) ((codec)->vendor_id == 0x80862809) +#define is_haswell_plus (codec) (is_haswell(codec) || is_broadwell(codec) \ + || is_skylake(codec))#define is_valleyview (codec) ((codec)->vendor_id == 0x80862882)
Signature · 1 line
2.5.0
PATCH 17/123 ALSA: hda_intel: add AZX_DCAPS_I915_POWERWELL for SKL and BSW
In reply to Jiri SlabyFrom: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2d846c74027231264e57e4e34faf9576394e3ce0 upstream.
HDMI/DP codec on SKL/BSW is in the power well. The power well must be turned on before probing the HDMI/DP codec.
This is a temporary patch, which will power on the powerwell by adding AZX_DCAPS_I915_POWERWELL for SKL and BSW. After restructuring and new flag is added, this patch will be reverted.
--- sound/pci/hda/hda_intel.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
sound/pci/hda/hda_intel.c +6 -2
@@ -622,8 +622,12 @@ enum { AZX_DCAPS_COUNT_LPIB_DELAY | AZX_DCAPS_PM_RUNTIME | \ AZX_DCAPS_I915_POWERWELL) +#define AZX_DCAPS_INTEL_BRASWELL \ + (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_I915_POWERWELL) +#define AZX_DCAPS_INTEL_SKYLAKE \ - (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_SEPARATE_STREAM_TAG) + (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_SEPARATE_STREAM_TAG |\ + AZX_DCAPS_I915_POWERWELL)/* quirks for ATI SB / AMD Hudson */ #define AZX_DCAPS_PRESET_ATI_SB \
@@ -4119,7 +4123,7 @@ static DEFINE_PCI_DEVICE_TABLE(azx_ids) = { .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH_NOPM },/* Braswell */ { PCI_DEVICE(0x8086, 0x2284), - .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, + .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_BRASWELL }, /* ICH */ { PCI_DEVICE(0x8086, 0x2668), .driver_data = AZX_DRIVER_ICH | AZX_DCAPS_OLD_SSYNC |
Signature · 1 line
2.5.0
Re: [PATCH 3.12 017/123] ALSA: hda_intel: add AZX_DCAPS_I915_POWERWELL for SKL and BSW
Quoted 13 lines · Jiri Slaby
From: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit
2d846c74027231264e57e4e34faf9576394e3ce0upstream.HDMI/DP codec on SKL/BSW is in the power well. The power well must be turned on before probing the HDMI/DP codec.
Quoted 8 lines
This is a temporary patch, which will power on the powerwell by adding
AZX_DCAPS_I915_POWERWELLfor SKL and BSW. After restructuring and new flag is added, this patch will be reverted.Signed-off-by Libin Yang <[email protected]>Signed-off-by Takashi Iwai <[email protected]>Signed-off-by Jiri Slaby <[email protected]>
Since the i915 side hook for SKL/BSW is missing on 3.12, applying this blindly may be seen as a regression. So, please drop this for now.
(For SLE12, I'm going to provide an additional patch to paper over the
failure path.)
thanks,
Takashi
Quoted 34 lines
--- sound/pci/hda/hda_intel.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)sound/pci/hda/hda_intel.c +6
-2@@ -622,8 +622,12 @@ enum { AZX_DCAPS_COUNT_LPIB_DELAY | AZX_DCAPS_PM_RUNTIME | \ AZX_DCAPS_I915_POWERWELL) +#define AZX_DCAPS_INTEL_BRASWELL \ + (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_I915_POWERWELL) +#define AZX_DCAPS_INTEL_SKYLAKE \ - (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_SEPARATE_STREAM_TAG) + (AZX_DCAPS_INTEL_PCH | AZX_DCAPS_SEPARATE_STREAM_TAG |\ + AZX_DCAPS_I915_POWERWELL)/* quirks for ATI SB / AMD Hudson */ #define AZX_DCAPS_PRESET_ATI_SB \@@ -4119,7 +4123,7 @@ static DEFINE_PCI_DEVICE_TABLE(azx_ids) = { .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH_NOPM },/* Braswell */ { PCI_DEVICE(0x8086, 0x2284), - .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_PCH }, + .driver_data = AZX_DRIVER_PCH | AZX_DCAPS_INTEL_BRASWELL }, /* ICH */ { PCI_DEVICE(0x8086, 0x2668), .driver_data = AZX_DRIVER_ICH | AZX_DCAPS_OLD_SSYNC |Signature · 1 line
2.5.0
Re: [PATCH 3.12 017/123] ALSA: hda_intel: add AZX_DCAPS_I915_POWERWELL for SKL and BSW
Quoted 10 lines · Takashi Iwai
Quoted 8 lines · Jiri Slaby
From: Libin Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit
2d846c74027231264e57e4e34faf9576394e3ce0upstream.
...
Quoted 2 lines
Since the i915 side hook for SKL/BSW is missing on 3.12, applying this blindly may be seen as a regression. So, please drop this for now.
Dropped, thanks.
Signature · 2 lines
js suse labs
PATCH 18/123 ALSA: usb-audio: Resume mixer values properly
In reply to Jiri SlabyFrom: Takashi Iwai <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf upstream.
Implement reset_resume callback so that the mixer values are properly restored. Still no boot quirks are called, so it might not work well on some devices.
--- sound/usb/card.c | 18 ++++++++-- sound/usb/mixer.c | 99 ++++++++++++++++++++++++++++++++++++++++++++----------- sound/usb/mixer.h | 7 ++-- 3 files changed, 99 insertions(+), 25 deletions(-)
sound/usb/card.c +15 -3
@@ -706,12 +706,12 @@ static int usb_audio_suspend(struct usb_interface *intf, pm_message_t message) }list_for_each_entry (mixer, &chip->mixer_list, list) -snd_usb_mixer_inactivate (mixer); +snd_usb_mixer_suspend (mixer);return 0 ; } -static int usb_audio_resume (struct usb_interface *intf) +static int __usb_audio_resume (struct usb_interface *intf,bool reset_resume) {struct snd_usb_audio *chip =usb_get_intfdata (intf);struct usb_mixer_interface *mixer;
@@ -726,7 +726,7 @@ static int usb_audio_resume(struct usb_interface *intf)* we just notify and restart the mixers */ list_for_each_entry (mixer, &chip->mixer_list, list) { - err =snd_usb_mixer_activate (mixer); + err =snd_usb_mixer_resume (mixer, reset_resume);if (err <0 ) goto err_out; }
@@ -738,9 +738,20 @@ static int usb_audio_resume(struct usb_interface *intf) err_out:return err; } + +static int usb_audio_resume (struct usb_interface *intf) +{ +return __usb_audio_resume (intf, false); +} + +static int usb_audio_reset_resume (struct usb_interface *intf) +{ +return __usb_audio_resume (intf, true); +}#else #define usb_audio_suspend NULL#define usb_audio_resume NULL +#define usb_audio_reset_resume NULL#endif /* CONFIG_PM */ static struct usb_device_id usb_audio_ids [] = {
@@ -762,6 +773,7 @@ static struct usb_driver usb_audio_driver = { .disconnect = usb_audio_disconnect, .suspend = usb_audio_suspend, .resume = usb_audio_resume, + .reset_resume = usb_audio_reset_resume, .id_table = usb_audio_ids, .supports_autosuspend = 1, };
sound/usb/mixer.c +79 -20
108 lines not on this page · raw message
sound/usb/mixer.h +5 -2
@@ -63,8 +63,6 @@ void snd_usb_mixer_notify_id(struct usb_mixer_interface *mixer, int unitid);int snd_usb_mixer_set_ctl_value (struct usb_mixer_elem_info *cval,int request,int validx,int value_set); -void snd_usb_mixer_inactivate (struct usb_mixer_interface *mixer); -int snd_usb_mixer_activate (struct usb_mixer_interface *mixer);int snd_usb_mixer_add_control (struct usb_mixer_interface *mixer,struct snd_kcontrol *kctl);
@@ -72,4 +70,9 @@ int snd_usb_mixer_add_control(struct usb_mixer_interface *mixer,int snd_usb_mixer_vol_tlv (struct snd_kcontrol *kcontrol,int op_flag,unsigned int size,unsigned int __user *_tlv); +#ifdef CONFIG_PM +int snd_usb_mixer_suspend (struct usb_mixer_interface *mixer); +int snd_usb_mixer_resume (struct usb_mixer_interface *mixer,bool reset_resume); +#endif +#endif /* __USBMIXER_H */
Signature · 1 line
2.5.0
PATCH 19/123 ALSA: usb-audio: Save mixer status only once at suspend
In reply to Jiri SlabyFrom: Takashi Iwai <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 1c53e7253ed8769a00afa0f06777d731dbe1ba6f upstream.
The suspend callback of usb-audio driver may be called multiple times per suspend when multiple USB interfaces are bound to a single sound card instance. In such a case, it's superfluous to save the mixer values multiple times. This patch fixes it by checking the counter.
--- sound/usb/card.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
sound/usb/card.c +3 -2
@@ -705,8 +705,9 @@ static int usb_audio_suspend(struct usb_interface *intf, pm_message_t message) chip->autosuspended =1 ; } -list_for_each_entry (mixer, &chip->mixer_list, list) -snd_usb_mixer_suspend (mixer); +if (chip->num_suspended_intf ==1 ) +list_for_each_entry (mixer, &chip->mixer_list, list) +snd_usb_mixer_suspend (mixer);return 0 ; }
Signature · 1 line
2.5.0
PATCH 20/123 ALSA: usb-audio: Fix deadlocks at resuming
In reply to Jiri SlabyFrom: Takashi Iwai <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 1ee23fe07ee83a38ecee927e701f762888ada942 upstream.
The recent addition of the USB audio mixer suspend/resume may lead to deadlocks when the driver tries to call usb_autopm_get_interface() recursively, since the function tries to sync with the finish of the other calls. For avoiding it, introduce a flag indicating the resume operation and avoids the recursive usb_autopm_get_interface() calls during the resume.
--- sound/usb/card.c | 7 +++++-- sound/usb/usbaudio.h | 1 + 2 files changed, 6 insertions(+), 2 deletions(-)
sound/usb/card.c +5 -2
@@ -661,7 +661,7 @@ int snd_usb_autoresume(struct snd_usb_audio *chip)int err = -ENODEV ;down_read (&chip->shutdown_rwsem); -if (chip->probing) +if (chip->probing && chip->in_pm) err =0 ;else if (!chip->shutdown) err =usb_autopm_get_interface (chip->pm_intf);
@@ -673,7 +673,7 @@ int snd_usb_autoresume(struct snd_usb_audio *chip)void snd_usb_autosuspend (struct snd_usb_audio *chip) {down_read (&chip->shutdown_rwsem); -if (!chip->shutdown && !chip->probing) +if (!chip->shutdown && !chip->probing && !chip->in_pm)usb_autopm_put_interface (chip->pm_intf);up_read (&chip->shutdown_rwsem); }
@@ -722,6 +722,8 @@ static int __usb_audio_resume(struct usb_interface *intf, bool reset_resume)return 0 ;if (--chip->num_suspended_intf)return 0 ; + + chip->in_pm =1 ;/* * ALSA leaves material resumption to user space * we just notify and restart the mixers
@@ -737,6 +739,7 @@ static int __usb_audio_resume(struct usb_interface *intf, bool reset_resume) chip->autosuspended =0 ; err_out: + chip->in_pm =0 ;return err; }
sound/usb/usbaudio.h +1 -0
@@ -40,6 +40,7 @@ struct snd_usb_audio {struct rw_semaphore shutdown_rwsem; unsigned int shutdown:1; unsigned int probing:1; + unsigned int in_pm:1; unsigned int autosuspended:1; unsigned int txfr_quirk:1; /* Subframe boundaries on transfers */
Signature · 1 line
2.5.0
PATCH 21/123 reiserfs: Fix use after free in journal teardown
In reply to Jiri SlabyFrom: Jan Kara <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 01777836c87081e4f68c4a43c9abe6114805f91e upstream.
If do_journal_release() races with do_journal_end() which requeues delayed works for transaction flushing, we can leave work items for flushing outstanding transactions queued while freeing them. That results in use after free and possible crash in run_timers_softirq().
Fix the problem by not requeueing works if superblock is being shut down (MS_ACTIVE not set) and using cancel_delayed_work_sync() in do_journal_release().
--- fs/reiserfs/journal.c | 21 ++++++++++++++++----- fs/reiserfs/super.c | 6 +++++- 2 files changed, 21 insertions(+), 6 deletions(-)
fs/reiserfs/journal.c +16 -5
@@ -1883,8 +1883,6 @@ static int do_journal_release(struct reiserfs_transaction_handle *th, } reiserfs_mounted_fs_count--; -/* wait for all commits to finish */ -cancel_delayed_work (&SB_JOURNAL (sb)->j_work);/* * We must release the write lock here because
@@ -1892,8 +1890,14 @@ static int do_journal_release(struct reiserfs_transaction_handle *th,*/ reiserfs_write_unlock (sb); +/* +* Cancel flushing of old commits. Note that neither of these works +* will be requeued because superblock is being shutdown and doesn't +* have MS_ACTIVE set. +*/ cancel_delayed_work_sync (&REISERFS_SB (sb)->old_work); -flush_workqueue (commit_wq); +/* wait for all commits to finish */ +cancel_delayed_work_sync (&SB_JOURNAL (sb)->j_work);if (!reiserfs_mounted_fs_count) {destroy_workqueue (commit_wq);
@@ -4133,8 +4137,15 @@ static int do_journal_end(struct reiserfs_transaction_handle *th,if (flush) {flush_commit_list (sb, jl,1 );flush_journal_list (sb, jl,1 ); - }else if (!(jl->j_state &LIST_COMMIT_PENDING )) -queue_delayed_work (commit_wq, &journal->j_work,HZ /10 ); + }else if (!(jl->j_state &LIST_COMMIT_PENDING )) { +/* +* Avoid queueing work when sb is being shut down. Transaction +* will be flushed on journal shutdown. +*/ +if (sb->s_flags &MS_ACTIVE ) +queue_delayed_work (commit_wq, + &journal->j_work,HZ /10 ); + }/* if the next transaction has any chance of wrapping, flush ** transactions that might get overwritten. If any journal lists are very
fs/reiserfs/super.c +5 -1
@@ -101,7 +101,11 @@ void reiserfs_schedule_old_flush(struct super_block *s)struct reiserfs_sb_info *sbi =REISERFS_SB (s);unsigned long delay; -if (s->s_flags &MS_RDONLY ) +/* +* Avoid scheduling flush when sb is being shut down. It can race +* with journal shutdown and free still queued delayed work. +*/ +if (s->s_flags &MS_RDONLY || !(s->s_flags &MS_ACTIVE ))return ;spin_lock (&sbi->old_work_lock);
Signature · 1 line
2.5.0
PATCH 22/123 libata: Do not blacklist Micron M500DC
In reply to Jiri SlabyFrom: "Martin K. Petersen" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 243918be6393f643e513a26e7882e6ae06ff7717 upstream.
Queued TRIM got disabled on Micron M500DC drives thanks to the "Micron_M500*" pattern we had in place to accommodate the previous generation of this drive family. Tweak the blacklist entry slightly so we only disable queued TRIM for the non-DC variants of M500 drives.
--- drivers/ata/libata-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/ata/libata-core.c +1 -1
@@ -4224,7 +4224,7 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = { { "PIONEER DVD-RW DVR-216D", NULL, ATA_HORKAGE_NOSETXFER },/* devices that don't properly handle queued TRIM commands */ - { "Micron_M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM, }, + { "Micron_M500_*", NULL, ATA_HORKAGE_NO_NCQ_TRIM, }, { "Crucial_CT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM, }, { "Micron_M5[15]0*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM, }, { "Crucial_CT*M550*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM, },
Signature · 1 line
2.5.0
PATCH 23/123 be2iscsi: fix bad if expression
In reply to Jiri SlabyFrom: Mike Christie <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 126e964a444f125bd428757fb88c24c730f6fcf9 upstream.
https://bugzilla.kernel.org/show_bug.cgi?id=67091
--- drivers/scsi/be2iscsi/be_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/be2iscsi/be_main.c +1 -1
@@ -313,7 +313,7 @@ static int beiscsi_eh_device_reset(struct scsi_cmnd *sc)if (!abrt_task->sc || abrt_task->state ==ISCSI_TASK_FREE )continue ; -if (abrt_task->sc->device->lun != abrt_task->sc->device->lun) +if (sc->device->lun != abrt_task->sc->device->lun)continue ; inv_tbl->cid = cid;
Signature · 1 line
2.5.0
PATCH 24/123 gpio/lynxpoint: add new ACPI ID
In reply to Jiri SlabyFrom: Mika Westerberg <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4edd7901eee13f878e7b5fd5efba610e70b09313 upstream.
Newer Intel PCHs have the same GPIO controller than Haswell but the ACPI ID is different. Add this ID to the driver supported IDs list.
--- drivers/gpio/gpio-lynxpoint.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpio/gpio-lynxpoint.c +1 -0
@@ -437,6 +437,7 @@ static const struct dev_pm_ops lp_gpio_pm_ops = {static const struct acpi_device_id lynxpoint_gpio_acpi_match[] = { {"INT33C7" ,0 }, + {"INT3437" ,0 }, { } };MODULE_DEVICE_TABLE (acpi, lynxpoint_gpio_acpi_match);
Signature · 1 line
2.5.0
PATCH 25/123 i2c: designware: add new ACPI IDs
In reply to Jiri SlabyFrom: Mika Westerberg <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 25b3dfc87bff80317d67ddd2cd4cfb91e6fe7d79 upstream.
Newer Intel PCHs with LPSS have the same Designware I2C controllers than Haswell but the ACPI IDs differ. Add these IDs to the driver list.
--- drivers/i2c/busses/i2c-designware-platdrv.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/i2c/busses/i2c-designware-platdrv.c +2 -0
@@ -103,6 +103,8 @@ static int dw_i2c_acpi_configure(struct platform_device *pdev)static const struct acpi_device_id dw_i2c_acpi_match[] = { {"INT33C2" ,0 }, {"INT33C3" ,0 }, + {"INT3432" ,0 }, + {"INT3433" ,0 }, {"80860F41" ,0 }, { } };
Signature · 1 line
2.5.0
PATCH 26/123 ACPICA: Add "Windows 2013" string to _OSI support.
In reply to Jiri SlabyFrom: Bob Moore <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit faae404ebdc6bba744919d82e64c16448eb24a36 upstream.
This urgent patch is cherry picked from ACPICA upstream. It is reported that some platforms fail to boot without this new _OSI string.
This change adds this string for Windows 8.1 and Server 2012 R2.
--- drivers/acpi/acpica/utosi.c | 1 + 1 file changed, 1 insertion(+)
drivers/acpi/acpica/utosi.c +1 -0
@@ -74,6 +74,7 @@ static struct acpi_interface_info acpi_default_supported_interfaces[] = { {"Windows 2006 SP2", NULL, 0, ACPI_OSI_WIN_VISTA_SP2}, /* Windows Vista SP2 - Added 09/2010 */ {"Windows 2009", NULL, 0, ACPI_OSI_WIN_7}, /* Windows 7 and Server 2008 R2 - Added 09/2009 */ {"Windows 2012", NULL, 0, ACPI_OSI_WIN_8}, /* Windows 8 and Server 2012 - Added 08/2012 */ + {"Windows 2013", NULL, 0, ACPI_OSI_WIN_8}, /* Windows 8.1 and Server 2012 R2 - Added 01/2014 */ /* Feature Group Strings */
Signature · 1 line
2.5.0
PATCH 27/123 i2c: i801: Fix the alignment of the device table
In reply to Jiri SlabyFrom: Jean Delvare <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit ce3161106ab57afbfbe1c33d95bf4a569405983a upstream.
A long name broke the alignment, shift the columns a bit to fix it and make the table look nice again. While we're here, switch to the standard comment style to make checkpatch happy, and use tabs instead of spaces for column alignment.
--- drivers/i2c/busses/i2c-i801.c | 136 +++++++++++++++++++++--------------------- 1 file changed, 68 insertions(+), 68 deletions(-)
drivers/i2c/busses/i2c-i801.c +68 -68
@@ -22,57 +22,57 @@*/ /* -Supports the following Intel I/O Controller Hubs (ICH): - -I/O Block I2C -region SMBus Block proc. block -Chip name PCI ID size PEC buffer call read ----------------------------------------------------------------------- -82801AA (ICH) 0x2413 16 no no no no -82801AB (ICH0) 0x2423 16 no no no no -82801BA (ICH2) 0x2443 16 no no no no -82801CA (ICH3) 0x2483 32 soft no no no -82801DB (ICH4) 0x24c3 32 hard yes no no -82801E (ICH5) 0x24d3 32 hard yes yes yes -6300ESB 0x25a4 32 hard yes yes yes -82801F (ICH6) 0x266a 32 hard yes yes yes -6310ESB/6320ESB 0x269b 32 hard yes yes yes -82801G (ICH7) 0x27da 32 hard yes yes yes -82801H (ICH8) 0x283e 32 hard yes yes yes -82801I (ICH9) 0x2930 32 hard yes yes yes -EP80579 (Tolapai) 0x5032 32 hard yes yes yes -ICH10 0x3a30 32 hard yes yes yes -ICH10 0x3a60 32 hard yes yes yes -5/3400 Series (PCH) 0x3b30 32 hard yes yes yes -6 Series (PCH) 0x1c22 32 hard yes yes yes -Patsburg (PCH) 0x1d22 32 hard yes yes yes -Patsburg (PCH) IDF 0x1d70 32 hard yes yes yes -Patsburg (PCH) IDF 0x1d71 32 hard yes yes yes -Patsburg (PCH) IDF 0x1d72 32 hard yes yes yes -DH89xxCC (PCH) 0x2330 32 hard yes yes yes -Panther Point (PCH) 0x1e22 32 hard yes yes yes -Lynx Point (PCH) 0x8c22 32 hard yes yes yes -Lynx Point-LP (PCH) 0x9c22 32 hard yes yes yes -Avoton (SOC) 0x1f3c 32 hard yes yes yes -Wellsburg (PCH) 0x8d22 32 hard yes yes yes -Wellsburg (PCH) MS 0x8d7d 32 hard yes yes yes -Wellsburg (PCH) MS 0x8d7e 32 hard yes yes yes -Wellsburg (PCH) MS 0x8d7f 32 hard yes yes yes -Coleto Creek (PCH) 0x23b0 32 hard yes yes yes -Wildcat Point-LP (PCH) 0x9ca2 32 hard yes yes yes -BayTrail (SOC) 0x0f12 32 hard yes yes yes - -Features supported by this driver: -Software PEC no -Hardware PEC yes -Block buffer yes -Block process call transaction no -I2C block read transaction yes (doesn't use the block buffer) -Slave mode no -Interrupt processing yes - -See the file Documentation/i2c/busses/i2c-i801 for details. -*/ +* Supports the following Intel I/O Controller Hubs (ICH): +* +* I/O Block I2C +* region SMBus Block proc. block +* Chip name PCI ID size PEC buffer call read +* --------------------------------------------------------------------------- +* 82801AA (ICH) 0x2413 16 no no no no +* 82801AB (ICH0) 0x2423 16 no no no no +* 82801BA (ICH2) 0x2443 16 no no no no +* 82801CA (ICH3) 0x2483 32 soft no no no +* 82801DB (ICH4) 0x24c3 32 hard yes no no +* 82801E (ICH5) 0x24d3 32 hard yes yes yes +* 6300ESB 0x25a4 32 hard yes yes yes +* 82801F (ICH6) 0x266a 32 hard yes yes yes +* 6310ESB/6320ESB 0x269b 32 hard yes yes yes +* 82801G (ICH7) 0x27da 32 hard yes yes yes +* 82801H (ICH8) 0x283e 32 hard yes yes yes +* 82801I (ICH9) 0x2930 32 hard yes yes yes +* EP80579 (Tolapai) 0x5032 32 hard yes yes yes +* ICH10 0x3a30 32 hard yes yes yes +* ICH10 0x3a60 32 hard yes yes yes +* 5/3400 Series (PCH) 0x3b30 32 hard yes yes yes +* 6 Series (PCH) 0x1c22 32 hard yes yes yes +* Patsburg (PCH) 0x1d22 32 hard yes yes yes +* Patsburg (PCH) IDF 0x1d70 32 hard yes yes yes +* Patsburg (PCH) IDF 0x1d71 32 hard yes yes yes +* Patsburg (PCH) IDF 0x1d72 32 hard yes yes yes +* DH89xxCC (PCH) 0x2330 32 hard yes yes yes +* Panther Point (PCH) 0x1e22 32 hard yes yes yes +* Lynx Point (PCH) 0x8c22 32 hard yes yes yes +* Lynx Point-LP (PCH) 0x9c22 32 hard yes yes yes +* Avoton (SOC) 0x1f3c 32 hard yes yes yes +* Wellsburg (PCH) 0x8d22 32 hard yes yes yes +* Wellsburg (PCH) MS 0x8d7d 32 hard yes yes yes +* Wellsburg (PCH) MS 0x8d7e 32 hard yes yes yes +* Wellsburg (PCH) MS 0x8d7f 32 hard yes yes yes +* Coleto Creek (PCH) 0x23b0 32 hard yes yes yes +* Wildcat Point-LP (PCH) 0x9ca2 32 hard yes yes yes +* BayTrail (SOC) 0x0f12 32 hard yes yes yes +* +* Features supported by this driver: +* Software PEC no +* Hardware PEC yes +* Block buffer yes +* Block process call transaction no +* I2C block read transaction yes (doesn't use the block buffer) +* Slave mode no +* Interrupt processing yes +* +* See the file Documentation/i2c/busses/i2c-i801 for details. +*/ #include <linux/interrupt.h> #include <linux/module.h>
@@ -162,24 +162,24 @@ STATUS_ERROR_FLAGS)/* Older devices have their ID defined in <linux/pci_ids.h> */ -#define PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS 0x0f12 -#define PCI_DEVICE_ID_INTEL_COUGARPOINT_SMBUS 0x1c22 -#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS 0x1d22 +#define PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS 0x0f12 +#define PCI_DEVICE_ID_INTEL_COUGARPOINT_SMBUS 0x1c22 +#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS 0x1d22/* Patsburg also has three 'Integrated Device Function' SMBus controllers */ -#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS_IDF0 0x1d70 -#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS_IDF1 0x1d71 -#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS_IDF2 0x1d72 -#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_SMBUS 0x1e22 -#define PCI_DEVICE_ID_INTEL_AVOTON_SMBUS 0x1f3c -#define PCI_DEVICE_ID_INTEL_DH89XXCC_SMBUS 0x2330 -#define PCI_DEVICE_ID_INTEL_COLETOCREEK_SMBUS 0x23b0 -#define PCI_DEVICE_ID_INTEL_5_3400_SERIES_SMBUS 0x3b30 -#define PCI_DEVICE_ID_INTEL_LYNXPOINT_SMBUS 0x8c22 -#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS 0x8d22 -#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS0 0x8d7d -#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1 0x8d7e -#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS2 0x8d7f -#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS 0x9c22 +#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS_IDF0 0x1d70 +#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS_IDF1 0x1d71 +#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS_IDF2 0x1d72 +#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_SMBUS 0x1e22 +#define PCI_DEVICE_ID_INTEL_AVOTON_SMBUS 0x1f3c +#define PCI_DEVICE_ID_INTEL_DH89XXCC_SMBUS 0x2330 +#define PCI_DEVICE_ID_INTEL_COLETOCREEK_SMBUS 0x23b0 +#define PCI_DEVICE_ID_INTEL_5_3400_SERIES_SMBUS 0x3b30 +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_SMBUS 0x8c22 +#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS 0x8d22 +#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS0 0x8d7d +#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1 0x8d7e +#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS2 0x8d7f +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS 0x9c22#define PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS 0x9ca2struct i801_mux_config {
Signature · 1 line
2.5.0
PATCH 28/123 i2c: i801: Add device ID for Intel Wildcat Point PCH
In reply to Jiri SlabyFrom: Jean Delvare <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit b299de839157852c563b9f133c8b7e630545a9c3 upstream.
--- Documentation/i2c/busses/i2c-i801 | 1 + drivers/i2c/busses/Kconfig | 1 + drivers/i2c/busses/i2c-i801.c | 3 +++ 3 files changed, 5 insertions(+)
Documentation/i2c/busses/i2c-i801 +1 -0
@@ -25,6 +25,7 @@ Supported adapters: * Intel Avoton (SOC) * Intel Wellsburg (PCH) * Intel Coleto Creek (PCH) + * Intel Wildcat Point (PCH) * Intel Wildcat Point-LP (PCH) * Intel BayTrail (SOC) Datasheets: Publicly available at the Intel website
drivers/i2c/busses/Kconfig +1 -0
@@ -109,6 +109,7 @@ config I2C_I801 Avoton (SOC) Wellsburg (PCH) Coleto Creek (PCH) + Wildcat Point (PCH) Wildcat Point-LP (PCH) BayTrail (SOC)
drivers/i2c/busses/i2c-i801.c +3 -0
@@ -59,6 +59,7 @@* Wellsburg (PCH) MS 0x8d7e 32 hard yes yes yes * Wellsburg (PCH) MS 0x8d7f 32 hard yes yes yes * Coleto Creek (PCH) 0x23b0 32 hard yes yes yes +* Wildcat Point (PCH) 0x8ca2 32 hard yes yes yes * Wildcat Point-LP (PCH) 0x9ca2 32 hard yes yes yes * BayTrail (SOC) 0x0f12 32 hard yes yes yes *
@@ -175,6 +176,7 @@#define PCI_DEVICE_ID_INTEL_COLETOCREEK_SMBUS 0x23b0#define PCI_DEVICE_ID_INTEL_5_3400_SERIES_SMBUS 0x3b30#define PCI_DEVICE_ID_INTEL_LYNXPOINT_SMBUS 0x8c22 +#define PCI_DEVICE_ID_INTEL_WILDCATPOINT_SMBUS 0x8ca2#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS 0x8d22#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS0 0x8d7d#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1 0x8d7e
@@ -823,6 +825,7 @@ static DEFINE_PCI_DEVICE_TABLE(i801_ids) = { { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS1) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS2) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_COLETOCREEK_SMBUS) }, + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS) }, { 0, }
Signature · 1 line
2.5.0
PATCH 29/123 i2c: i801: Add PCI ID for Intel Braswell
In reply to Jiri SlabyFrom: Alan Cox <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 39e8e30ee544a62c148033d64a979028b958ca05 upstream.
The SMBus host controller is the same as used in Baytrail so add the new PCI ID to the driver's list of supported IDs.
--- drivers/i2c/busses/i2c-i801.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/i2c/busses/i2c-i801.c +2 -0
@@ -164,6 +164,7 @@/* Older devices have their ID defined in <linux/pci_ids.h> */ #define PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS 0x0f12 +#define PCI_DEVICE_ID_INTEL_BRASWELL_SMBUS 0x2292#define PCI_DEVICE_ID_INTEL_COUGARPOINT_SMBUS 0x1c22#define PCI_DEVICE_ID_INTEL_PATSBURG_SMBUS 0x1d22/* Patsburg also has three 'Integrated Device Function' SMBus controllers */
@@ -828,6 +829,7 @@ static DEFINE_PCI_DEVICE_TABLE(i801_ids) = { { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS) }, + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BRASWELL_SMBUS) }, { 0, } };
Signature · 1 line
2.5.0
PATCH 30/123 i2c: i801: Add Device IDs for Intel Sunrise Point PCH
In reply to Jiri SlabyFrom: "[email protected]" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 3e27a8445c21f8056517f188303827450590d868 upstream.
This patch adds the I2C/SMBus Device IDs for the Intel Sunrise Point PCH.
--- Documentation/i2c/busses/i2c-i801 | 1 + drivers/i2c/busses/Kconfig | 1 + drivers/i2c/busses/i2c-i801.c | 3 +++ 3 files changed, 5 insertions(+)
Documentation/i2c/busses/i2c-i801 +1 -0
@@ -28,6 +28,7 @@ Supported adapters: * Intel Wildcat Point (PCH) * Intel Wildcat Point-LP (PCH) * Intel BayTrail (SOC) + * Intel Sunrise Point-H (PCH) Datasheets: Publicly available at the Intel website On Intel Patsburg and later chipsets, both the normal host SMBus controller
drivers/i2c/busses/Kconfig +1 -0
@@ -112,6 +112,7 @@ config I2C_I801 Wildcat Point (PCH) Wildcat Point-LP (PCH) BayTrail (SOC) + Sunrise Point-H (PCH) This driver can also be built as a module. If so, the module will be called i2c-i801.
drivers/i2c/busses/i2c-i801.c +3 -0
@@ -62,6 +62,7 @@* Wildcat Point (PCH) 0x8ca2 32 hard yes yes yes * Wildcat Point-LP (PCH) 0x9ca2 32 hard yes yes yes * BayTrail (SOC) 0x0f12 32 hard yes yes yes +* Sunrise Point-H (PCH) 0xa123 32 hard yes yes yes * * Features supported by this driver: * Software PEC no
@@ -184,6 +185,7 @@#define PCI_DEVICE_ID_INTEL_WELLSBURG_SMBUS_MS2 0x8d7f#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS 0x9c22#define PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS 0x9ca2 +#define PCI_DEVICE_ID_INTEL_SUNRISEPOINT_H_SMBUS 0xa123struct i801_mux_config {char *gpio_chip;
@@ -830,6 +832,7 @@ static DEFINE_PCI_DEVICE_TABLE(i801_ids) = { { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BRASWELL_SMBUS) }, + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_SUNRISEPOINT_H_SMBUS) }, { 0, } };
Signature · 1 line
2.5.0
PATCH 31/123 i2c: i801: Add DeviceIDs for SunrisePoint LP
In reply to Jiri SlabyFrom: Devin Ryles <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 3eee1799aed90e990e02a73a89bfcff1982c74dd upstream.
--- Documentation/i2c/busses/i2c-i801 | 1 + drivers/i2c/busses/Kconfig | 1 + drivers/i2c/busses/i2c-i801.c | 3 +++ 3 files changed, 5 insertions(+)
Documentation/i2c/busses/i2c-i801 +1 -0
@@ -29,6 +29,7 @@ Supported adapters: * Intel Wildcat Point-LP (PCH) * Intel BayTrail (SOC) * Intel Sunrise Point-H (PCH) + * Intel Sunrise Point-LP (PCH) Datasheets: Publicly available at the Intel website On Intel Patsburg and later chipsets, both the normal host SMBus controller
drivers/i2c/busses/Kconfig +1 -0
@@ -113,6 +113,7 @@ config I2C_I801 Wildcat Point-LP (PCH) BayTrail (SOC) Sunrise Point-H (PCH) + Sunrise Point-LP (PCH) This driver can also be built as a module. If so, the module will be called i2c-i801.
drivers/i2c/busses/i2c-i801.c +3 -0
@@ -63,6 +63,7 @@* Wildcat Point-LP (PCH) 0x9ca2 32 hard yes yes yes * BayTrail (SOC) 0x0f12 32 hard yes yes yes * Sunrise Point-H (PCH) 0xa123 32 hard yes yes yes +* Sunrise Point-LP (PCH) 0x9d23 32 hard yes yes yes * * Features supported by this driver: * Software PEC no
@@ -186,6 +187,7 @@#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_SMBUS 0x9c22#define PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_SMBUS 0x9ca2#define PCI_DEVICE_ID_INTEL_SUNRISEPOINT_H_SMBUS 0xa123 +#define PCI_DEVICE_ID_INTEL_SUNRISEPOINT_LP_SMBUS 0x9d23struct i801_mux_config {char *gpio_chip;
@@ -833,6 +835,7 @@ static DEFINE_PCI_DEVICE_TABLE(i801_ids) = { { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BAYTRAIL_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_BRASWELL_SMBUS) }, { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_SUNRISEPOINT_H_SMBUS) }, + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_SUNRISEPOINT_LP_SMBUS) }, { 0, } };
Signature · 1 line
2.5.0
PATCH 32/123 kexec: allocate the kexec control page with KEXEC_CONTROL_MEMORY_GFP
In reply to Jiri SlabyFrom: Martin Schwidefsky <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 7e01b5acd88b3f3108d8c4ce44e3205d67437202 upstream.
Introduce KEXEC_CONTROL_MEMORY_GFP to allow the architecture code to override the gfp flags of the allocation for the kexec control page. The loop in kimage_alloc_normal_control_pages allocates pages with GFP_KERNEL until a page is found that happens to have an address smaller than the KEXEC_CONTROL_MEMORY_LIMIT. On systems with a large memory size but a small KEXEC_CONTROL_MEMORY_LIMIT the loop will keep allocating memory until the oom killer steps in.
--- arch/s390/include/asm/kexec.h | 3 +++ include/linux/kexec.h | 4 ++++ kernel/kexec.c | 2 +- 3 files changed, 8 insertions(+), 1 deletion(-)
arch/s390/include/asm/kexec.h +3 -0
@@ -26,6 +26,9 @@/* Not more than 2GB */ #define KEXEC_CONTROL_MEMORY_LIMIT (1UL<<31) +/* Allocate control page with GFP_DMA */ +#define KEXEC_CONTROL_MEMORY_GFP GFP_DMA +/* Maximum address we can use for the crash control pages */ #define KEXEC_CRASH_CONTROL_MEMORY_LIMIT (-1UL)
include/linux/kexec.h +4 -0
@@ -26,6 +26,10 @@#error KEXEC_CONTROL_MEMORY_LIMIT not defined#endif +#ifndef KEXEC_CONTROL_MEMORY_GFP +#define KEXEC_CONTROL_MEMORY_GFP GFP_KERNEL +#endif +#ifndef KEXEC_CONTROL_PAGE_SIZE #error KEXEC_CONTROL_PAGE_SIZE not defined#endif
kernel/kexec.c +1 -1
@@ -432,7 +432,7 @@ static struct page *kimage_alloc_normal_control_pages(struct kimage *image, do { unsigned long pfn, epfn, addr, eaddr; - pages = kimage_alloc_pages(GFP_KERNEL, order); + pages = kimage_alloc_pages(KEXEC_CONTROL_MEMORY_GFP, order); if (!pages) break; pfn = page_to_pfn(pages);
Signature · 1 line
2.5.0
PATCH 33/123 intel_idle: Broadwell support
In reply to Jiri SlabyFrom: Len Brown <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit a138b56800f4b83a7af69a9958d04f0f124eb37b upstream.
Broadwell (BDW) is similar to Haswell (HSW), the preceding processor generation.
Currently, the only difference in their C-state tables is that PC3 max exit latency is 33usec on HSW and 40usec on BDW.
--- drivers/idle/intel_idle.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 69 insertions(+), 1 deletion(-)
drivers/idle/intel_idle.c +69 -1
@@ -296,6 +296,66 @@ static struct cpuidle_state hsw_cstates[CPUIDLE_STATE_MAX] = { { .enter = NULL } }; +static struct cpuidle_state bdw_cstates[] = { + { + .name ="C1-BDW" , + .desc ="MWAIT 0x00" , + .flags =MWAIT2flg (0x00 ) |CPUIDLE_FLAG_TIME_VALID , + .exit_latency =2 , + .target_residency =2 , + .enter = &intel_idle }, + { + .name ="C1E-BDW" , + .desc ="MWAIT 0x01" , + .flags =MWAIT2flg (0x01 ) |CPUIDLE_FLAG_TIME_VALID , + .exit_latency =10 , + .target_residency =20 , + .enter = &intel_idle }, + { + .name ="C3-BDW" , + .desc ="MWAIT 0x10" , + .flags =MWAIT2flg (0x10 ) |CPUIDLE_FLAG_TIME_VALID |CPUIDLE_FLAG_TLB_FLUSHED , + .exit_latency =40 , + .target_residency =100 , + .enter = &intel_idle }, + { + .name ="C6-BDW" , + .desc ="MWAIT 0x20" , + .flags =MWAIT2flg (0x20 ) |CPUIDLE_FLAG_TIME_VALID |CPUIDLE_FLAG_TLB_FLUSHED , + .exit_latency =133 , + .target_residency =400 , + .enter = &intel_idle }, + { + .name ="C7s-BDW" , + .desc ="MWAIT 0x32" , + .flags =MWAIT2flg (0x32 ) |CPUIDLE_FLAG_TIME_VALID |CPUIDLE_FLAG_TLB_FLUSHED , + .exit_latency =166 , + .target_residency =500 , + .enter = &intel_idle }, + { + .name ="C8-BDW" , + .desc ="MWAIT 0x40" , + .flags =MWAIT2flg (0x40 ) |CPUIDLE_FLAG_TIME_VALID |CPUIDLE_FLAG_TLB_FLUSHED , + .exit_latency =300 , + .target_residency =900 , + .enter = &intel_idle }, + { + .name ="C9-BDW" , + .desc ="MWAIT 0x50" , + .flags =MWAIT2flg (0x50 ) |CPUIDLE_FLAG_TIME_VALID |CPUIDLE_FLAG_TLB_FLUSHED , + .exit_latency =600 , + .target_residency =1800 , + .enter = &intel_idle }, + { + .name ="C10-BDW" , + .desc ="MWAIT 0x60" , + .flags =MWAIT2flg (0x60 ) |CPUIDLE_FLAG_TIME_VALID |CPUIDLE_FLAG_TLB_FLUSHED , + .exit_latency =2600 , + .target_residency =7700 , + .enter = &intel_idle }, + { + .enter =NULL } +};static struct cpuidle_state atom_cstates[CPUIDLE_STATE_MAX ] = { {
@@ -483,6 +543,11 @@ static const struct idle_cpu idle_cpu_hsw = { .disable_promotion_to_c1e = true, }; +static const struct idle_cpu idle_cpu_bdw = { + .state_table = bdw_cstates, + .disable_promotion_to_c1e = true, +}; +static const struct idle_cpu idle_cpu_avn = { .state_table = avn_cstates, .disable_promotion_to_c1e = true,
@@ -510,7 +575,10 @@ static const struct x86_cpu_id intel_idle_ids[] = {ICPU (0x3f , idle_cpu_hsw),ICPU (0x45 , idle_cpu_hsw),ICPU (0x46 , idle_cpu_hsw), -ICPU (0x4D , idle_cpu_avn), +ICPU (0x4d , idle_cpu_avn), +ICPU (0x3d , idle_cpu_bdw), +ICPU (0x4f , idle_cpu_bdw), + ICPU(0x56, idle_cpu_bdw), {} };MODULE_DEVICE_TABLE (x86cpu, intel_idle_ids);
Signature · 1 line
2.5.0
PATCH 34/123 intel_idle: support additional Broadwell model
In reply to Jiri SlabyFrom: Len Brown <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit bea57077e44ec9c1e6d3a3c142c8a3c0289e290d upstream.
--- drivers/idle/intel_idle.c | 1 + 1 file changed, 1 insertion(+)
drivers/idle/intel_idle.c +1 -0
@@ -577,6 +577,7 @@ static const struct x86_cpu_id intel_idle_ids[] = {ICPU (0x46 , idle_cpu_hsw),ICPU (0x4d , idle_cpu_avn),ICPU (0x3d , idle_cpu_bdw), +ICPU (0x47 , idle_cpu_bdw),ICPU (0x4f , idle_cpu_bdw), ICPU(0x56, idle_cpu_bdw), {}
Signature · 1 line
2.5.0
PATCH 35/123 mtd: nand: fix erroneous read_buf call in nand_write_page_raw_syndrome
In reply to Jiri SlabyFrom: Boris BREZILLON <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 60c3bc1fd6f1fa40b415ef5b83e2948a89a3d79c upstream.
read_buf is called in place of write_buf in thenand_write_page_raw_syndrome function.
--- drivers/mtd/nand/nand_base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mtd/nand/nand_base.c +1 -1
@@ -1902,7 +1902,7 @@ static int nand_write_page_raw_syndrome(struct mtd_info *mtd, oob += chip->ecc.prepad; } - chip->read_buf (mtd, oob, eccbytes); + chip->write_buf (mtd, oob, eccbytes); oob += eccbytes;if (chip->ecc.postpad) {
Signature · 1 line
2.5.0
PATCH 36/123 Bluetooth: btusb: Fix memory leak in Intel setup routine
In reply to Jiri SlabyFrom: Marcel Holtmann <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit ecffc80478cdce122f0ecb6a4e4f909132dd5c47 upstream.
The SKB returned from the Intel specific version information command is missing a kfree_skb.
--- drivers/bluetooth/btusb.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/bluetooth/btusb.c +2 -0
@@ -1256,6 +1256,8 @@ static int btusb_setup_intel(struct hci_dev *hdev) } fw_ptr = fw->data; +kfree_skb (skb); +/* This Intel specific command enables the manufacturer mode of the * controller. *
Signature · 1 line
2.5.0
PATCH 37/123 ath9k: fix DMA stop sequence for AR9003+
In reply to Jiri SlabyFrom: Felix Fietkau <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 300f77c08ded96d33f492aaa02549103852f0c12 upstream.
AR93xx and newer needs to stop rx before tx to avoid getting the DMA engine or MAC into a stuck state.
This should reduce/fix the occurence of "Failed to stop Tx DMA" logspam.
--- drivers/net/wireless/ath/ath9k/main.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
drivers/net/wireless/ath/ath9k/main.c +7 -5
@@ -194,11 +194,13 @@ static bool ath_prepare_reset(struct ath_softc *sc)ath9k_hw_disable_interrupts (ah); -if (!ath_drain_all_txq (sc)) - ret = false; - -if (!ath_stoprecv (sc)) - ret = false; +if (AR_SREV_9300_20_OR_LATER (ah)) { + ret &=ath_stoprecv (sc); + ret &=ath_drain_all_txq (sc); + }else { + ret &=ath_drain_all_txq (sc); + ret &=ath_stoprecv (sc); + }return ret; }
Signature · 1 line
2.5.0
PATCH 38/123 staging: rtl8712: prevent buffer overrun in recvbuf2recvframe
In reply to Jiri SlabyFrom: Haggai Eran <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit cab462140f8a183e3cca0b51c8b59ef715cb6148 upstream.
With an RTL8191SU USB adaptor, sometimes the hints for a fragmented packet are set, but the packet length is too large. Allocate enough space to prevent memory corruption and a resulting kernel panic [1].
[1] http://www.spinics.net/lists/linux-wireless/msg136546.html
--- drivers/staging/rtl8712/rtl8712_recv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/staging/rtl8712/rtl8712_recv.c +2 -1
@@ -1075,7 +1075,8 @@ static int recvbuf2recvframe(struct _adapter *padapter, struct sk_buff *pskb)/* for first fragment packet, driver need allocate 1536 + * drvinfo_sz + RXDESC_SIZE to defrag packet. */ if ((mf ==1 ) && (frag ==0 )) - alloc_sz =1658 ;/*1658+6=1664, 1664 is 128 alignment.*/ +/*1658+6=1664, 1664 is 128 alignment.*/ + alloc_sz =max_t (u16, tmp_len,1658 );else alloc_sz = tmp_len;/* 2 is for IP header 4 bytes alignment in QoS packet case.
Signature · 1 line
2.5.0
PATCH 39/123 ext4: fix race between truncate and __ext4_journalled_writepage()
In reply to Jiri SlabyFrom: Theodore Ts'o <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit bdf96838aea6a265f2ae6cbcfb12a778c84a0b8e upstream.
The commit cf108bca465d: "ext4: Invert the locking order of page_lock and transaction start" caused __ext4_journalled_writepage() to drop the page lock before the page was written back, as part of changing the locking order to jbd2_journal_start -> page_lock. However, this introduced a potential race if there was a truncate racing with the data=journalled writeback mode.
Fix this by grabbing the page lock after starting the journal handle, and then checking to see if page had gotten truncated out from under us.
This fixes a number of different warnings or BUG_ON's when running xfstests generic/086 in data=journalled mode, including:
jbd2_journal_dirty_metadata: vdc-8: bad jh for block 115643: transaction (ee3fe7 c0, 164), jh->b_transaction ( (null), 0), jh->b_next_transaction ( (null), 0), jlist 0
- and -
kernel BUG at /usr/projects/linux/ext4/fs/jbd2/transaction.c:2200!
... Call Trace: [<c02b2ded>] ? __ext4_journalled_invalidatepage+0x117/0x117 [<c02b2de5>] __ext4_journalled_invalidatepage+0x10f/0x117 [<c02b2ded>] ? __ext4_journalled_invalidatepage+0x117/0x117 [<c027d883>] ? lock_buffer+0x36/0x36 [<c02b2dfa>] ext4_journalled_invalidatepage+0xd/0x22 [<c0229139>] do_invalidatepage+0x22/0x26 [<c0229198>] truncate_inode_page+0x5b/0x85 [<c022934b>] truncate_inode_pages_range+0x156/0x38c [<c0229592>] truncate_inode_pages+0x11/0x15 [<c022962d>] truncate_pagecache+0x55/0x71 [<c02b913b>] ext4_setattr+0x4a9/0x560 [<c01ca542>] ? current_kernel_time+0x10/0x44 [<c026c4d8>] notify_change+0x1c7/0x2be [<c0256a00>] do_truncate+0x65/0x85 [<c0226f31>] ? file_ra_state_init+0x12/0x29
- and -
WARNING: CPU: 1 PID: 1331 at /usr/projects/linux/ext4/fs/jbd2/transaction.c:1396
irty_metadata+0x14a/0x1ae()
...
Call Trace:
[<c01b879f>] ? console_unlock+0x3a1/0x3ce
[<c082cbb4>] dump_stack+0x48/0x60
[<c0178b65>] warn_slowpath_common+0x89/0xa0
[<c02ef2cf>] ? jbd2_journal_dirty_metadata+0x14a/0x1ae
[<c0178bef>] warn_slowpath_null+0x14/0x18
[<c02ef2cf>] jbd2_journal_dirty_metadata+0x14a/0x1ae
[<c02d8615>] __ext4_handle_dirty_metadata+0xd4/0x19d
[<c02b2f44>] write_end_fn+0x40/0x53
[<c02b4a16>] ext4_walk_page_buffers+0x4e/0x6a
[<c02b59e7>] ext4_writepage+0x354/0x3b8
[<c02b2f04>] ? mpage_release_unused_pages+0xd4/0xd4
[<c02b1b21>] ? wait_on_buffer+0x2c/0x2c
[<c02b5a4b>] ? ext4_writepage+0x3b8/0x3b8
[<c02b5a5b>] __writepage+0x10/0x2e
[<c0225956>] write_cache_pages+0x22d/0x32c
[<c02b5a4b>] ? ext4_writepage+0x3b8/0x3b8
[<c02b6ee8>] ext4_writepages+0x102/0x607
[<c019adfe>] ? sched_clock_local+0x10/0x10e
[<c01a8a7c>] ? __lock_is_held+0x2e/0x44
[<c01a8ad5>] ? lock_is_held+0x43/0x51
[<c0226dff>] do_writepages+0x1c/0x29
[<c0276bed>] __writeback_single_inode+0xc3/0x545
[<c0277c07>] writeback_sb_inodes+0x21f/0x36d
...--- fs/ext4/inode.c | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-)
fs/ext4/inode.c +19 -4
@@ -1744,19 +1744,32 @@ static int __ext4_journalled_writepage(struct page *page,ext4_walk_page_buffers (handle, page_bufs,0 , len,NULL , bget_one); } -/* As soon as we unlock the page, it can go away, but we have -* references to buffers so we are safe */ +/* +* We need to release the page lock before we start the +* journal, so grab a reference so the page won't disappear +* out from under us. +*/ +get_page (page);unlock_page (page); handle =ext4_journal_start (inode,EXT4_HT_WRITE_PAGE ,ext4_writepage_trans_blocks (inode));if (IS_ERR (handle)) { ret =PTR_ERR (handle); - goto out; +put_page (page); + goto out_no_pagelock; } -BUG_ON (!ext4_handle_valid (handle)); +lock_page (page); +put_page (page); +if (page->mapping != mapping) { +/* The page got truncated from under us */ +ext4_journal_stop (handle); + ret =0 ; + goto out; + } +if (inline_data) { ret =ext4_journal_get_write_access (handle, inode_bh);
@@ -1781,6 +1794,8 @@ static int __ext4_journalled_writepage(struct page *page, NULL, bput_one);ext4_set_inode_state (inode,EXT4_STATE_JDATA ); out: +unlock_page (page); +out_no_pagelock:brelse (inode_bh);return ret; }
Signature · 1 line
2.5.0
PATCH 40/123 ext4: call sync_blockdev() before invalidate_bdev() in put_super()
In reply to Jiri SlabyFrom: Theodore Ts'o <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 89d96a6f8e6491f24fc8f99fd6ae66820e85c6c1 upstream.
Normally all of the buffers will have been forced out to disk before we call invalidate_bdev(), but there will be some cases, where a file system operation was aborted due to an ext4_error(), where there may still be some dirty buffers in the buffer cache for the device. So try to force them out to memory before calling invalidate_bdev().
This fixes a warning triggered by generic/081:
WARNING: CPU: 1 PID: 3473 at /usr/projects/linux/ext4/fs/block_dev.c:56 __blkdev_put+0xb5/0x16f()
--- fs/ext4/super.c | 1 + 1 file changed, 1 insertion(+)
fs/ext4/super.c +1 -0
@@ -813,6 +813,7 @@ static void ext4_put_super(struct super_block *sb)dump_orphan_list (sb, sbi);J_ASSERT (list_empty (&sbi->s_orphan)); +sync_blockdev (sb->s_bdev);invalidate_bdev (sb->s_bdev);if (sbi->journal_bdev && sbi->journal_bdev != sb->s_bdev) {/*
Signature · 1 line
2.5.0
PATCH 41/123 ext4: don't retry file block mapping on bigalloc fs with non-extent file
In reply to Jiri SlabyFrom: "Darrick J. Wong" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 292db1bc6c105d86111e858859456bcb11f90f91 upstream.
ext4 isn't willing to map clusters to a non-extent file. Don't signal this with an out of space error, since the FS will retry the allocation (which didn't fail) forever. Instead, return EUCLEAN so that the operation will fail immediately all the way back to userspace.
(The fix is either to run e2fsck -E bmap2extent, or to chattr +e the file.)
--- fs/ext4/indirect.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/indirect.c +1 -1
@@ -576,7 +576,7 @@ int ext4_ind_map_blocks(handle_t *handle, struct inode *inode, EXT4_FEATURE_RO_COMPAT_BIGALLOC)) {EXT4_ERROR_INODE (inode,"Can't allocate blocks for " "non-extent mapped inodes with bigalloc" ); -return -ENOSPC ; +return -EUCLEAN ; } goal =ext4_find_goal (inode, map->m_lblk, partial);
Signature · 1 line
2.5.0
PATCH 42/123 ext4: fix reservation release on invalidatepage for delalloc fs
In reply to Jiri SlabyFrom: Lukas Czerner <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 9705acd63b125dee8b15c705216d7186daea4625 upstream.
On delalloc enabled file system on invalidatepage operation in ext4_da_page_release_reservation() we want to clear the delayed buffer and remove the extent covering the delayed buffer from the extent status tree.
However currently there is a bug where on the systems with page size > block size we will always remove extents from the start of the page regardless where the actual delayed buffers are positioned in the page. This leads to the errors like this:
EXT4-fs warning (device loop0): ext4_da_release_space:1225:ext4_da_release_space: ino 13, to_free 1 with only 0 reserved data blocks
This however can cause data loss on writeback time if the file system is in ENOSPC condition because we're releasing reservation for someones else delayed buffer.
Fix this by only removing extents that corresponds to the part of the page we want to invalidate.
This problem is reproducible by the following fio receipt (however I was only able to reproduce it with fio-2.1 or older.
[global]
bs=8k
iodepth=1024
iodepth_batch=60
randrepeat=1
size=1m
directory=/mnt/test
numjobs=20
[job1]
ioengine=sync
bs=1k
direct=1
rw=randread
filename=file1:file2
[job2]
ioengine=libaio
rw=randwrite
direct=1
filename=file1:file2
[job3]
bs=1k
ioengine=posixaio
rw=randwrite
direct=1
filename=file1:file2
[job5]
bs=1k
ioengine=sync
rw=randread
filename=file1:file2
[job7]
ioengine=libaio
rw=randwrite
filename=file1:file2
[job8]
ioengine=posixaio
rw=randwrite
filename=file1:file2
[job10]
ioengine=mmap
rw=randwrite
bs=1k
filename=file1:file2
[job11]
ioengine=mmap
rw=randwrite
direct=1
filename=file1:file2
--- fs/ext4/inode.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
fs/ext4/inode.c +12 -3
@@ -1357,7 +1357,7 @@ static void ext4_da_page_release_reservation(struct page *page,unsigned int offset, unsigned int length) { - int to_release = 0; + int to_release = 0, contiguous_blks = 0;struct buffer_head *head, *bh;unsigned int curr_off =0 ;struct inode *inode = page->mapping->host;
@@ -1378,14 +1378,23 @@ static void ext4_da_page_release_reservation(struct page *page,if ((offset <= curr_off) && (buffer_delay (bh))) { to_release++; + contiguous_blks++;clear_buffer_delay (bh); + }else if (contiguous_blks) { + lblk = page->index << + (PAGE_CACHE_SHIFT - inode->i_blkbits); + lblk += (curr_off >> inode->i_blkbits) - + contiguous_blks; +ext4_es_remove_extent (inode, lblk, contiguous_blks); + contiguous_blks =0 ; } curr_off = next_off; }while ((bh = bh->b_this_page) != head); -if (to_release) { +if (contiguous_blks) { lblk = page->index << (PAGE_CACHE_SHIFT - inode->i_blkbits); -ext4_es_remove_extent (inode, lblk, to_release); + lblk += (curr_off >> inode->i_blkbits) - contiguous_blks; +ext4_es_remove_extent (inode, lblk, contiguous_blks); }/* If we have released all the blocks belonging to a cluster, then we
Signature · 1 line
2.5.0
PATCH 43/123 ext4: be more strict when migrating to non-extent based file
In reply to Jiri SlabyFrom: Eryu Guan <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d6f123a9297496ad0b6335fe881504c4b5b2a5e5 upstream.
Currently the check in ext4_ind_migrate() is not enough before doing the real conversion:
a) delayed allocated extents could bypass the check on eh->eh_entries and eh->eh_depth
This can be demonstrated by this script
xfs_io -fc "pwrite 0 4k" -c "pwrite 8k 4k" /mnt/ext4/testfile chattr -e /mnt/ext4/testfile
where testfile has two extents but still be converted to non-extent based file format.
b) only extent length is checked but not the offset, which would result in data lose (delalloc) or fs corruption (nodelalloc), because non-extent based file only supports at most (12 + 2^10 + 2^20 + 2^30) blocks
This can be demostrated by
xfs_io -fc "pwrite 5T 4k" /mnt/ext4/testfile
chattr -e /mnt/ext4/testfile
sync
If delalloc is enabled, dmesg prints
EXT4-fs warning (device dm-4): ext4_block_to_path:105: block 1342177280 > max in inode 53
EXT4-fs (dm-4): Delayed block allocation failed for inode 53 at logical offset 1342177280 with max blocks 1 with error 5 EXT4-fs (dm-4): This should not happen!! Data will be lost
If delalloc is disabled, e2fsck -nf shows corruption
Inode 53, i_size is 5497558142976, should be 4096. Fix? no
Fix the two issues by
a) forcing all delayed allocation blocks to be allocated before checking eh->eh_depth and eh->eh_entries
b) limiting the last logical block of the extent is within direct map
--- fs/ext4/migrate.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-)
fs/ext4/migrate.c +11 -1
@@ -616,6 +616,7 @@ int ext4_ind_migrate(struct inode *inode)struct ext4_inode_info *ei =EXT4_I (inode);struct ext4_extent *ex;unsigned int i, len; +ext4_lblk_t end;ext4_fsblk_t blk;handle_t *handle;int ret;
@@ -629,6 +630,14 @@ int ext4_ind_migrate(struct inode *inode) EXT4_FEATURE_RO_COMPAT_BIGALLOC))return -EOPNOTSUPP ; +/* +* In order to get correct extent info, force all delayed allocation +* blocks to be allocated, otherwise delayed allocation blocks may not +* be reflected and bypass the checks on extent header. +*/ +if (test_opt (inode->i_sb,DELALLOC )) +ext4_alloc_da_blocks (inode); + handle =ext4_journal_start (inode,EXT4_HT_MIGRATE ,1 );if (IS_ERR (handle))return PTR_ERR (handle);
@@ -650,7 +659,8 @@ int ext4_ind_migrate(struct inode *inode)else { len =le16_to_cpu (ex->ee_len); blk =ext4_ext_pblock (ex); -if (len >EXT4_NDIR_BLOCKS ) { + end =le32_to_cpu (ex->ee_block) + len -1 ; +if (end >=EXT4_NDIR_BLOCKS ) { ret = -EOPNOTSUPP ; goto errout; }
Signature · 1 line
2.5.0
PATCH 44/123 ext4: correctly migrate a file with a hole at the beginning
In reply to Jiri SlabyFrom: Eryu Guan <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 8974fec7d72e3e02752fe0f27b4c3719c78d9a15 upstream.
Currently ext4_ind_migrate() doesn't correctly handle a file which contains a hole at the beginning of the file. This caused the migration to be done incorrectly, and then if there is a subsequent following delayed allocation write to the "hole", this would reclaim the same data blocks again and results in fs corruption.
# assmuing 4k block size ext4, with delalloc enabled # skip the first block and write to the second block xfs_io -fc "pwrite 4k 4k" -c "fsync" /mnt/ext4/testfile
# converting to indirect-mapped file, which would move the data blocks # to the beginning of the file, but extent status cache still marks # that region as a hole chattr -e /mnt/ext4/testfile
# delayed allocation writes to the "hole", reclaim the same data block # again, results in i_blocks corruption xfs_io -c "pwrite 0 4k" /mnt/ext4/testfile umount /mnt/ext4 e2fsck -nf /dev/sda6 ... Inode 53, i_blocks is 16, should be 8. Fix? no ...
--- fs/ext4/migrate.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
fs/ext4/migrate.c +5 -4
@@ -616,7 +616,7 @@ int ext4_ind_migrate(struct inode *inode)struct ext4_inode_info *ei =EXT4_I (inode);struct ext4_extent *ex;unsigned int i, len; -ext4_lblk_t end; +ext4_lblk_t start, end;ext4_fsblk_t blk;handle_t *handle;int ret;
@@ -655,11 +655,12 @@ int ext4_ind_migrate(struct inode *inode) goto errout; }if (eh->eh_entries ==0 ) - blk = len =0 ; + blk = len = start = end =0 ;else { len =le16_to_cpu (ex->ee_len); blk =ext4_ext_pblock (ex); - end =le32_to_cpu (ex->ee_block) + len -1 ; + start =le32_to_cpu (ex->ee_block); + end = start + len -1 ;if (end >=EXT4_NDIR_BLOCKS ) { ret = -EOPNOTSUPP ; goto errout;
@@ -668,7 +669,7 @@ int ext4_ind_migrate(struct inode *inode)ext4_clear_inode_flag (inode,EXT4_INODE_EXTENTS );memset (ei->i_data,0 ,sizeof (ei->i_data)); -for (i=0 ; i < len; i++) +for (i = start; i <= end; i++) ei->i_data[i] =cpu_to_le32 (blk++);ext4_mark_inode_dirty (handle, inode); errout:
Signature · 1 line
2.5.0
PATCH 45/123 ext4: replace open coded nofail allocation in ext4_free_blocks()
In reply to Jiri SlabyFrom: Michal Hocko <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 7444a072c387a93ebee7066e8aee776954ab0e41 upstream.
ext4_free_blocks is looping around the allocation request and mimics __GFP_NOFAIL behavior without any allocation fallback strategy. Let's remove the open coded loop and replace it with __GFP_NOFAIL. Without the flag the allocator has no way to find out never-fail requirement and cannot help in any way.
--- fs/ext4/mballoc.c | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-)
fs/ext4/mballoc.c +5 -11
@@ -4793,18 +4793,12 @@ do_more:/* * blocks being freed are metadata. these blocks shouldn't * be used until this transaction is committed +* +* We use __GFP_NOFAIL because ext4_free_blocks() is not allowed +* to fail. */ - retry: - new_entry =kmem_cache_alloc (ext4_free_data_cachep,GFP_NOFS ); -if (!new_entry) { -/* -* We use a retry loop because -* ext4_free_blocks() is not allowed to fail. -*/ -cond_resched (); -congestion_wait (BLK_RW_ASYNC ,HZ /50 ); - goto retry; - } + new_entry =kmem_cache_alloc (ext4_free_data_cachep, +GFP_NOFS |__GFP_NOFAIL); new_entry->efd_start_cluster = bit; new_entry->efd_group = block_group; new_entry->efd_count = count_clusters;
Signature · 1 line
2.5.0
PATCH 46/123 jbd2: use GFP_NOFS in jbd2_cleanup_journal_tail()
In reply to Jiri SlabyFrom: Dmitry Monakhov <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit b4f1afcd068f6e533230dfed00782cd8a907f96b upstream.
jbd2_cleanup_journal_tail() can be invoked by jbd2__journal_start() So allocations should be done with GFP_NOFS
[Full stack trace snipped from 3.10-rh7]
[<ffffffff815c4bd4>] dump_stack+0x19/0x1b [<ffffffff8105dba1>] warn_slowpath_common+0x61/0x80 [<ffffffff8105dcca>] warn_slowpath_null+0x1a/0x20 [<ffffffff815c2142>] slab_pre_alloc_hook.isra.31.part.32+0x15/0x17 [<ffffffff8119c045>] kmem_cache_alloc+0x55/0x210 [<ffffffff811477f5>] ? mempool_alloc_slab+0x15/0x20 [<ffffffff811477f5>] mempool_alloc_slab+0x15/0x20 [<ffffffff81147939>] mempool_alloc+0x69/0x170 [<ffffffff815cb69e>] ? _raw_spin_unlock_irq+0xe/0x20 [<ffffffff8109160d>] ? finish_task_switch+0x5d/0x150 [<ffffffff811f1a8e>] bio_alloc_bioset+0x1be/0x2e0 [<ffffffff8127ee49>] blkdev_issue_flush+0x99/0x120 [<ffffffffa019a733>] jbd2_cleanup_journal_tail+0x93/0xa0 [jbd2] -->GFP_KERNEL [<ffffffffa019aca1>] jbd2_log_do_checkpoint+0x221/0x4a0 [jbd2] [<ffffffffa019afc7>] __jbd2_log_wait_for_space+0xa7/0x1e0 [jbd2] [<ffffffffa01952d8>] start_this_handle+0x2d8/0x550 [jbd2] [<ffffffff811b02a9>] ? __memcg_kmem_put_cache+0x29/0x30 [<ffffffff8119c120>] ? kmem_cache_alloc+0x130/0x210 [<ffffffffa019573a>] jbd2__journal_start+0xba/0x190 [jbd2] [<ffffffff811532ce>] ? lru_cache_add+0xe/0x10 [<ffffffffa01c9549>] ? ext4_da_write_begin+0xf9/0x330 [ext4] [<ffffffffa01f2c77>] __ext4_journal_start_sb+0x77/0x160 [ext4] [<ffffffffa01c9549>] ext4_da_write_begin+0xf9/0x330 [ext4] [<ffffffff811446ec>] generic_file_buffered_write_iter+0x10c/0x270 [<ffffffff81146918>] __generic_file_write_iter+0x178/0x390 [<ffffffff81146c6b>] __generic_file_aio_write+0x8b/0xb0 [<ffffffff81146ced>] generic_file_aio_write+0x5d/0xc0 [<ffffffffa01bf289>] ext4_file_write+0xa9/0x450 [ext4] [<ffffffff811c31d9>] ? pipe_read+0x379/0x4f0 [<ffffffff811b93f0>] do_sync_write+0x90/0xe0 [<ffffffff811b9b6d>] vfs_write+0xbd/0x1e0 [<ffffffff811ba5b8>] SyS_write+0x58/0xb0 [<ffffffff815d4799>] system_call_fastpath+0x16/0x1b
--- fs/jbd2/checkpoint.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/jbd2/checkpoint.c +1 -1
@@ -463,7 +463,7 @@ int jbd2_cleanup_journal_tail(journal_t *journal)* jbd2_cleanup_journal_tail() doesn't get called all that often. */ if (journal->j_flags &JBD2_BARRIER ) -blkdev_issue_flush (journal->j_fs_dev,GFP_KERNEL ,NULL ); +blkdev_issue_flush (journal->j_fs_dev,GFP_NOFS ,NULL );__jbd2_update_log_tail (journal, first_tid, blocknr);return 0 ;
Signature · 1 line
2.5.0
PATCH 47/123 jbd2: fix ocfs2 corrupt when updating journal superblock fails
In reply to Jiri SlabyFrom: Joseph Qi <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 6f6a6fda294506dfe0e3e0a253bb2d2923f28f0a upstream.
If updating journal superblock fails after journal data has been flushed, the error is omitted and this will mislead the caller as a normal case. In ocfs2, the checkpoint will be treated successfully and the other node can get the lock to update. Since the sb_start is still pointing to the old log block, it will rewrite the journal data during journal recovery by the other node. Thus the new updates will be overwritten and ocfs2 corrupts. So in above case we have to return the error, and ocfs2_commit_cache will take care of the error and prevent the other node to do update first. And only after recovering journal it can do the new updates.
The issue discussion mail can be found at:
https://oss.oracle.com/pipermail/ocfs2-devel/2015-June/010856.html
http://comments.gmane.org/gmane.comp.file-systems.ext4/48841
[ Fixed bug in patch which allowed a non-negative error return from
jbd2_cleanup_journal_tail() to leak out of jbd2_fjournal_flush(); this was causing xfstests ext4/306 to fail. -- Ted ]
--- fs/jbd2/checkpoint.c | 5 ++--- fs/jbd2/journal.c | 38 +++++++++++++++++++++++++++++++------- include/linux/jbd2.h | 4 ++-- 3 files changed, 35 insertions(+), 12 deletions(-)
fs/jbd2/checkpoint.c +2 -3
@@ -448,7 +448,7 @@ int jbd2_cleanup_journal_tail(journal_t *journal)unsigned long blocknr;if (is_journal_aborted (journal)) -return 1 ; +return -EIO ;if (!jbd2_journal_get_log_tail (journal, &first_tid, &blocknr))return 1 ;
@@ -465,8 +465,7 @@ int jbd2_cleanup_journal_tail(journal_t *journal)if (journal->j_flags &JBD2_BARRIER )blkdev_issue_flush (journal->j_fs_dev,GFP_NOFS ,NULL ); -__jbd2_update_log_tail (journal, first_tid, blocknr); -return 0 ; +return __jbd2_update_log_tail (journal, first_tid, blocknr); }
fs/jbd2/journal.c +31 -7
@@ -887,9 +887,10 @@ int jbd2_journal_get_log_tail(journal_t *journal, tid_t *tid,* * Requires j_checkpoint_mutex */ -void __jbd2_update_log_tail (journal_t *journal,tid_t tid,unsigned long block) +int __jbd2_update_log_tail (journal_t *journal,tid_t tid,unsigned long block) {unsigned long freed; +int ret;BUG_ON (!mutex_is_locked (&journal->j_checkpoint_mutex));
@@ -899,7 +900,10 @@ void __jbd2_update_log_tail(journal_t *journal, tid_t tid, unsigned long block)* space and if we lose sb update during power failure we'd replay * old transaction with possibly newly overwritten data. */ -jbd2_journal_update_sb_log_tail (journal, tid, block,WRITE_FUA ); + ret =jbd2_journal_update_sb_log_tail (journal, tid, block,WRITE_FUA ); +if (ret) + goto out; +write_lock (&journal->j_state_lock); freed = block - journal->j_tail;if (block < journal->j_tail)
@@ -915,6 +919,9 @@ void __jbd2_update_log_tail(journal_t *journal, tid_t tid, unsigned long block) journal->j_tail_sequence = tid; journal->j_tail = block;write_unlock (&journal->j_state_lock); + +out: +return ret; }/*
@@ -1333,7 +1340,7 @@ static int journal_reset(journal_t *journal)return jbd2_journal_start_thread (journal); } -static void jbd2_write_superblock (journal_t *journal,int write_op) +static int jbd2_write_superblock (journal_t *journal,int write_op) {struct buffer_head *bh = journal->j_sb_buffer;journal_superblock_t *sb = journal->j_superblock;
@@ -1372,7 +1379,10 @@ static void jbd2_write_superblock(journal_t *journal, int write_op)printk (KERN_ERR "JBD2: Error %d detected when updating " "journal superblock for %s.\n" , ret, journal->j_devname); +jbd2_journal_abort (journal, ret); } + +return ret; }/**
@@ -1385,10 +1395,11 @@ static void jbd2_write_superblock(journal_t *journal, int write_op)* Update a journal's superblock information about log tail and write it to * disk, waiting for the IO to complete. */ -void jbd2_journal_update_sb_log_tail (journal_t *journal,tid_t tail_tid, +int jbd2_journal_update_sb_log_tail (journal_t *journal,tid_t tail_tid,unsigned long tail_block,int write_op) {journal_superblock_t *sb = journal->j_superblock; +int ret;BUG_ON (!mutex_is_locked (&journal->j_checkpoint_mutex)); jbd_debug(1, "JBD2: updating superblock (start %lu, seq %u)\n",
@@ -1397,13 +1408,18 @@ void jbd2_journal_update_sb_log_tail(journal_t *journal, tid_t tail_tid, sb->s_sequence =cpu_to_be32 (tail_tid); sb->s_start =cpu_to_be32 (tail_block); -jbd2_write_superblock (journal, write_op); + ret =jbd2_write_superblock (journal, write_op); +if (ret) + goto out;/* Log is no longer empty */ write_lock (&journal->j_state_lock);WARN_ON (!sb->s_sequence); journal->j_flags &= ~JBD2_FLUSHED ;write_unlock (&journal->j_state_lock); + +out: +return ret; }/**
@@ -1954,7 +1970,14 @@ int jbd2_journal_flush(journal_t *journal)return -EIO ;mutex_lock (&journal->j_checkpoint_mutex); -jbd2_cleanup_journal_tail (journal); +if (!err) { + err =jbd2_cleanup_journal_tail (journal); +if (err <0 ) { +mutex_unlock (&journal->j_checkpoint_mutex); + goto out; + } + err =0 ; + }/* Finally, mark the journal as really needing no recovery. * This sets s_start==0 in the underlying superblock, which is
@@ -1970,7 +1993,8 @@ int jbd2_journal_flush(journal_t *journal)J_ASSERT (journal->j_head == journal->j_tail);J_ASSERT (journal->j_tail_sequence == journal->j_transaction_sequence);write_unlock (&journal->j_state_lock); -return 0 ; +out: +return err; }/**
include/linux/jbd2.h +2 -2
@@ -1035,7 +1035,7 @@ struct buffer_head *jbd2_journal_get_descriptor_buffer(journal_t *journal);int jbd2_journal_next_log_block (journal_t *,unsigned long long *);int jbd2_journal_get_log_tail (journal_t *journal,tid_t *tid,unsigned long *block); -void __jbd2_update_log_tail (journal_t *journal,tid_t tid,unsigned long block); +int __jbd2_update_log_tail (journal_t *journal,tid_t tid,unsigned long block);void jbd2_update_log_tail (journal_t *journal,tid_t tid,unsigned long block);/* Commit management */
@@ -1157,7 +1157,7 @@ extern int jbd2_journal_recover (journal_t *journal);extern int jbd2_journal_wipe (journal_t *,int );extern int jbd2_journal_skip_recovery (journal_t *);extern void jbd2_journal_update_sb_errno (journal_t *); -extern void jbd2_journal_update_sb_log_tail (journal_t *,tid_t , +extern int jbd2_journal_update_sb_log_tail (journal_t *,tid_t ,unsigned long ,int );extern void __jbd2_journal_abort_hard (journal_t *);extern void jbd2_journal_abort (journal_t *,int );
Signature · 1 line
2.5.0
PATCH 48/123 i2c: at91: fix a race condition when using the DMA controller
In reply to Jiri SlabyFrom: Cyrille Pitchen <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 93563a6a71bb69dd324fc7354c60fb05f84aae6b upstream.
For TX transactions, the TXCOMP bit in the Status Register is cleared when the first data is written into the Transmit Holding Register.
In the lines from at91_do_twi_transfer():at91_twi_write_data_dma(dev); at91_twi_write(dev, AT91_TWI_IER, AT91_TWI_TXCOMP);
the TXCOMP interrupt may be enabled before the DMA controller has actually started to write into the THR. In such a case, the TXCOMP bit is still set into the Status Register so the interrupt is triggered immediately. The driver understands that a transaction completion has occurred but this transaction hasn't started yet. Hence the TXCOMP interrupt is no longer enabled by at91_do_twi_transfer() but instead by at91_twi_write_data_dma_callback().
Also, the TXCOMP bit in the Status Register in not a clear on read flag but a snapshot of the transmission state at the time the Status Register is read.
When a NACK error is dectected by the I2C controller, the TXCOMP, NACK and TXRDY bits are set together to 1 in the SR. If enabled, the TXCOMP interrupt is triggered at the same time. Also setting the TXRDY to 1 triggers the DMA controller to write the next data into the THR. Such a write resets the TXCOMP bit to 0 in the SR. So depending on when the interrupt handler reads the SR, it may fail to detect the NACK error if it relies on the TXCOMP bit. The NACK bit and its interrupt should be used instead.
For RX transactions, the TXCOMP bit in the Status Register is cleared when the START bit is set into the Control Register. However to unify the management of the TXCOMP bit when the DMA controller is used, the TXCOMP interrupt is now enabled by the DMA callbacks for both TX and RX transfers.
--- drivers/i2c/busses/i2c-at91.c | 70 ++++++++++++++++++++++++++++++++----------- 1 file changed, 53 insertions(+), 17 deletions(-)
drivers/i2c/busses/i2c-at91.c +53 -17
@@ -62,6 +62,9 @@#define AT91_TWI_UNRE 0x0080/* Underrun Error */ #define AT91_TWI_NACK 0x0100/* Not Acknowledged */ +#define AT91_TWI_INT_MASK \ + (AT91_TWI_TXCOMP | AT91_TWI_RXRDY | AT91_TWI_TXRDY | AT91_TWI_NACK) +#define AT91_TWI_IER 0x0024/* Interrupt Enable Register */ #define AT91_TWI_IDR 0x0028/* Interrupt Disable Register */ #define AT91_TWI_IMR 0x002c/* Interrupt Mask Register */
@@ -117,13 +120,12 @@ static void at91_twi_write(struct at91_twi_dev *dev, unsigned reg, unsigned val)static void at91_disable_twi_interrupts (struct at91_twi_dev *dev) { -at91_twi_write (dev,AT91_TWI_IDR , -AT91_TWI_TXCOMP |AT91_TWI_RXRDY |AT91_TWI_TXRDY ); +at91_twi_write (dev,AT91_TWI_IDR ,AT91_TWI_INT_MASK ); }static void at91_twi_irq_save (struct at91_twi_dev *dev) { - dev->imr =at91_twi_read (dev,AT91_TWI_IMR ) &0x7 ; + dev->imr =at91_twi_read (dev,AT91_TWI_IMR ) &AT91_TWI_INT_MASK ;at91_disable_twi_interrupts (dev); }
@@ -213,6 +215,14 @@ static void at91_twi_write_data_dma_callback(void *data)dma_unmap_single (dev->dev,sg_dma_address (&dev->dma.sg), dev->buf_len,DMA_TO_DEVICE ); +/* +* When this callback is called, THR/TX FIFO is likely not to be empty +* yet. So we have to wait for TXCOMP or NACK bits to be set into the +* Status Register to be sure that the STOP bit has been sent and the +* transfer is completed. The NACK interrupt has already been enabled, +* we just have to enable TXCOMP one. +*/ +at91_twi_write (dev,AT91_TWI_IER ,AT91_TWI_TXCOMP );at91_twi_write (dev,AT91_TWI_CR ,AT91_TWI_STOP ); }
@@ -307,7 +317,7 @@ static void at91_twi_read_data_dma_callback(void *data)/* The last two bytes have to be read without using dma */ dev->buf += dev->buf_len -2 ; dev->buf_len =2 ; -at91_twi_write (dev,AT91_TWI_IER ,AT91_TWI_RXRDY ); +at91_twi_write (dev,AT91_TWI_IER ,AT91_TWI_RXRDY |AT91_TWI_TXCOMP ); }static void at91_twi_read_data_dma (struct at91_twi_dev *dev)
@@ -368,7 +378,7 @@ static irqreturn_t atmel_twi_interrupt(int irq, void *dev_id)/* catch error flags */ dev->transfer_status |= status; -if (irqstatus &AT91_TWI_TXCOMP ) { +if (irqstatus & (AT91_TWI_TXCOMP |AT91_TWI_NACK )) {at91_disable_twi_interrupts (dev);complete (&dev->cmd_complete); }
@@ -381,6 +391,34 @@ static int at91_do_twi_transfer(struct at91_twi_dev *dev)int ret;bool has_unre_flag = dev->pdata->has_unre_flag; +/* +* WARNING: the TXCOMP bit in the Status Register is NOT a clear on +* read flag but shows the state of the transmission at the time the +* Status Register is read. According to the programmer datasheet, +* TXCOMP is set when both holding register and internal shifter are +* empty and STOP condition has been sent. +* Consequently, we should enable NACK interrupt rather than TXCOMP to +* detect transmission failure. +* +* Besides, the TXCOMP bit is already set before the i2c transaction +* has been started. For read transactions, this bit is cleared when +* writing the START bit into the Control Register. So the +* corresponding interrupt can safely be enabled just after. +* However for write transactions managed by the CPU, we first write +* into THR, so TXCOMP is cleared. Then we can safely enable TXCOMP +* interrupt. If TXCOMP interrupt were enabled before writing into THR, +* the interrupt handler would be called immediately and the i2c command +* would be reported as completed. +* Also when a write transaction is managed by the DMA controller, +* enabling the TXCOMP interrupt in this function may lead to a race +* condition since we don't know whether the TXCOMP interrupt is enabled +* before or after the DMA has started to write into THR. So the TXCOMP +* interrupt is enabled later by at91_twi_write_data_dma_callback(). +* Immediately after in that DMA callback, we still need to send the +* STOP condition manually writing the corresponding bit into the +* Control Register. +*/ +dev_dbg (dev->dev,"transfer: %s %d bytes.\n" , (dev->msg->flags &I2C_M_RD ) ?"read" :"write" , dev->buf_len);
@@ -411,26 +449,24 @@ static int at91_do_twi_transfer(struct at91_twi_dev *dev)* seems to be the best solution. */ if (dev->use_dma && (dev->buf_len >AT91_I2C_DMA_THRESHOLD )) { +at91_twi_write (dev,AT91_TWI_IER ,AT91_TWI_NACK );at91_twi_read_data_dma (dev); -/* -* It is important to enable TXCOMP irq here because -* doing it only when transferring the last two bytes -* will mask NACK errors since TXCOMP is set when a -* NACK occurs. -*/ -at91_twi_write (dev,AT91_TWI_IER , -AT91_TWI_TXCOMP ); - }else + }else {at91_twi_write (dev,AT91_TWI_IER , -AT91_TWI_TXCOMP |AT91_TWI_RXRDY ); +AT91_TWI_TXCOMP | +AT91_TWI_NACK | +AT91_TWI_RXRDY ); + } }else {if (dev->use_dma && (dev->buf_len >AT91_I2C_DMA_THRESHOLD )) { +at91_twi_write (dev,AT91_TWI_IER ,AT91_TWI_NACK );at91_twi_write_data_dma (dev); -at91_twi_write (dev,AT91_TWI_IER ,AT91_TWI_TXCOMP ); }else {at91_twi_write_next_byte (dev);at91_twi_write (dev,AT91_TWI_IER , -AT91_TWI_TXCOMP |AT91_TWI_TXRDY ); +AT91_TWI_TXCOMP | +AT91_TWI_NACK | +AT91_TWI_TXRDY ); } }
Signature · 1 line
2.5.0
PATCH 49/123 iio: DAC: ad5624r_spi: fix bit shift of output data value
In reply to Jiri SlabyFrom: JM Friedt <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit adfa969850ae93beca57f7527f0e4dc10cbe1309 upstream.
The value sent on the SPI bus is shifted by an erroneous number of bits. The shift value was already computed in the iio_chan_spec structure and hence subtracting this argument to 16 yields an erroneous data position in the SPI stream.
--- drivers/iio/dac/ad5624r_spi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/iio/dac/ad5624r_spi.c +2 -2
@@ -22,7 +22,7 @@#include "ad5624r.h" static int ad5624r_spi_write (struct spi_device *spi, -u8 cmd,u8 addr,u16 val,u8 len) +u8 cmd,u8 addr,u16 val,u8 shift) {u32 data;u8 msg[3 ];
@@ -35,7 +35,7 @@ static int ad5624r_spi_write(struct spi_device *spi,* 14-, 12-bit input code followed by 0, 2, or 4 don't care bits, * for the AD5664R, AD5644R, and AD5624R, respectively. */ - data = (0 <<22 ) | (cmd <<19 ) | (addr <<16 ) | (val << (16 - len)); + data = (0 <<22 ) | (cmd <<19 ) | (addr <<16 ) | (val << shift); msg[0 ] = data >>16 ; msg[1 ] = data >>8 ; msg[2 ] = data;
Signature · 1 line
2.5.0
PATCH 50/123 iio: adc: at91_adc: allow to use full range of startup time
In reply to Jiri SlabyFrom: Jan Leupold <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2ab5f39bc7825808e0fa1e7e5f0b23e174563467 upstream.
The DT-Property "atmel,adc-startup-time" is stored in an u8 for a microsecond value. When trying to increase the value of STARTUP in Register AT91_ADC_MR some higher values can't be reached.
Change the type in function parameter and private structure field from u8 to u32.
--- drivers/iio/adc/at91_adc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iio/adc/at91_adc.c +1 -1
@@ -55,7 +55,7 @@ struct at91_adc_state {u8 num_channels;void __iomem *reg_base;struct at91_adc_reg_desc *registers; -u8 startup_time; +u32 startup_time;u8 sample_hold_time;bool sleep_mode;struct iio_trigger **trig;
Signature · 1 line
2.5.0
PATCH 51/123 af9013: Don't accept invalid bandwidth
In reply to Jiri SlabyFrom: Mauro Carvalho Chehab <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d7b76c91f471413de9ded837bddeca2164786571 upstream.
If userspace sends an invalid bandwidth, it should either return EINVAL or switch to auto mode.
This driver will go past an array and program the hardware on a wrong way if this happens.
--- drivers/media/dvb-frontends/af9013.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/media/dvb-frontends/af9013.c +4 -0
@@ -606,6 +606,10 @@ static int af9013_set_frontend(struct dvb_frontend *fe) } } +/* Return an error if can't find bandwidth or the right clock */ +if (i ==ARRAY_SIZE (coeff_lut)) +return -EINVAL ; + ret =af9013_wr_regs (state,0xae00 , coeff_lut[i].val,sizeof (coeff_lut[i].val)); }
Signature · 1 line
2.5.0
PATCH 52/123 s5h1420: fix a buffer overflow when checking userspace params
In reply to Jiri SlabyFrom: Mauro Carvalho Chehab <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 12f4543f5d6811f864e6c4952eb27253c7466c02 upstream.
The maximum size for a DiSEqC command is 6, according to the userspace API. However, the code allows to write up to 7 values:
drivers/media/dvb-frontends/s5h1420.c:193 s5h1420_send_master_cmd() error: buffer overflow 'cmd->msg' 6 <= 7
--- drivers/media/dvb-frontends/s5h1420.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/dvb-frontends/s5h1420.c +1 -1
@@ -180,7 +180,7 @@ static int s5h1420_send_master_cmd (struct dvb_frontend* fe,int result =0 ;dprintk ("enter %s\n" , __func__); -if (cmd->msg_len >8 ) +if (cmd->msg_len >sizeof (cmd->msg))return -EINVAL ;/* setup for DISEQC */
Signature · 1 line
2.5.0
PATCH 53/123 cx24116: fix a buffer overflow when checking userspace params
In reply to Jiri SlabyFrom: Mauro Carvalho Chehab <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 1fa2337a315a2448c5434f41e00d56b01a22283c upstream.
The maximum size for a DiSEqC command is 6, according to the userspace API. However, the code allows to write up much more values:
drivers/media/dvb-frontends/cx24116.c:983 cx24116_send_diseqc_msg() error: buffer overflow 'd->msg' 6 <= 23
--- drivers/media/dvb-frontends/cx24116.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/media/dvb-frontends/cx24116.c +4 -4
@@ -963,6 +963,10 @@ static int cx24116_send_diseqc_msg(struct dvb_frontend *fe,struct cx24116_state *state = fe->demodulator_priv;int i, ret; +/* Validate length */ +if (d->msg_len >sizeof (d->msg)) +return -EINVAL ; +/* Dump DiSEqC message */ if (debug) {printk (KERN_INFO "cx24116: %s(" , __func__);
@@ -974,10 +978,6 @@ static int cx24116_send_diseqc_msg(struct dvb_frontend *fe,printk (") toneburst=%d\n" , toneburst); } -/* Validate length */ -if (d->msg_len > (CX24116_ARGLEN -CX24116_DISEQC_MSGOFS )) -return -EINVAL ; -/* DiSEqC message */ for (i =0 ; i < d->msg_len; i++) state->dsec_cmd.args[CX24116_DISEQC_MSGOFS + i] = d->msg[i];
Signature · 1 line
2.5.0
PATCH 54/123 ASoC: arizona: Fix noise generator gain TLV
In reply to Jiri SlabyFrom: Richard Fitzgerald <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 15575ed544910464715df5c45a44b9732e415b93 upstream.
The Arizona codec drivers had an incorrect dB scaling for the noise generator gain that started at 0dB and went upwards. Actually the highest setting is 0dB.
--- sound/soc/codecs/wm5102.c | 2 +- sound/soc/codecs/wm5110.c | 2 +- sound/soc/codecs/wm8997.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
sound/soc/codecs/wm5102.c +1 -1
@@ -41,7 +41,7 @@ struct wm5102_priv { static DECLARE_TLV_DB_SCALE(ana_tlv, 0, 100, 0); static DECLARE_TLV_DB_SCALE(eq_tlv, -1200, 100, 0); static DECLARE_TLV_DB_SCALE(digital_tlv, -6400, 50, 0); -static DECLARE_TLV_DB_SCALE(noise_tlv, 0, 600, 0); +static DECLARE_TLV_DB_SCALE(noise_tlv, -13200, 600, 0); static DECLARE_TLV_DB_SCALE(ng_tlv, -10200, 600, 0);static const struct wm_adsp_region wm5102_dsp1_regions[] = {
sound/soc/codecs/wm5110.c +1 -1
@@ -129,7 +129,7 @@ static int wm5110_sysclk_ev(struct snd_soc_dapm_widget *w, static DECLARE_TLV_DB_SCALE(ana_tlv, 0, 100, 0); static DECLARE_TLV_DB_SCALE(eq_tlv, -1200, 100, 0); static DECLARE_TLV_DB_SCALE(digital_tlv, -6400, 50, 0); -static DECLARE_TLV_DB_SCALE(noise_tlv, 0, 600, 0); +static DECLARE_TLV_DB_SCALE(noise_tlv, -13200, 600, 0); static DECLARE_TLV_DB_SCALE(ng_tlv, -10200, 600, 0);#define WM5110_NG_SRC (name, base) \
sound/soc/codecs/wm8997.c +1 -1
@@ -40,7 +40,7 @@ struct wm8997_priv { static DECLARE_TLV_DB_SCALE(ana_tlv, 0, 100, 0); static DECLARE_TLV_DB_SCALE(eq_tlv, -1200, 100, 0); static DECLARE_TLV_DB_SCALE(digital_tlv, -6400, 50, 0); -static DECLARE_TLV_DB_SCALE(noise_tlv, 0, 600, 0); +static DECLARE_TLV_DB_SCALE(noise_tlv, -13200, 600, 0); static DECLARE_TLV_DB_SCALE(ng_tlv, -10200, 600, 0);static const struct reg_default wm8997_sysclk_reva_patch[] = {
Signature · 1 line
2.5.0
PATCH 55/123 ASoC: imx-wm8962: Add a missing error check
In reply to Jiri SlabyFrom: Dan Carpenter <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 474ff0ae23b834e9fc18374d14bb5f3e7b3828b4 upstream.
My static checker complains that:
sound/soc/fsl/imx-wm8962.c:196 imx_wm8962_probe() warn: we tested 'ret' before and it was 'false'
The intent was that we use "ret" to check imx_audmux_v2_configure_port().
Otherwise, Acked-by: Nicolin Chen <[email protected]>
--- sound/soc/fsl/imx-wm8962.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/fsl/imx-wm8962.c +1 -1
@@ -192,7 +192,7 @@ static int imx_wm8962_probe(struct platform_device *pdev)dev_err (&pdev->dev,"audmux internal port setup failed\n" );return ret; } -imx_audmux_v2_configure_port (ext_port, + ret =imx_audmux_v2_configure_port (ext_port,IMX_AUDMUX_V2_PTCR_SYN ,IMX_AUDMUX_V2_PDCR_RXDSEL (int_port));if (ret) {
Signature · 1 line
2.5.0
PATCH 56/123 ASoC: wm8737: Fixup setting VMID Impedance control register
In reply to Jiri SlabyFrom: Axel Lin <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 14ba3ec1de043260cecd9e828ea2e3a0ad302893 upstream.
According to the datasheet:
R10 (0Ah) VMID Impedance Control
BIT 3:2 VMIDSEL DEFAULT 00
DESCRIPTION: VMID impedance selection control 00: 75kΩ output
01: 300kΩ output
10: 2.5kΩ output
WM8737_VMIDSEL_MASK is 0xC (VMIDSEL - [3:2]),
so it needs to left shift WM8737_VMIDSEL_SHIFT bits for setting these bits.
--- sound/soc/codecs/wm8737.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
sound/soc/codecs/wm8737.c +4 -2
@@ -494,7 +494,8 @@ static int wm8737_set_bias_level(struct snd_soc_codec *codec,/* Fast VMID ramp at 2*2.5k */ snd_soc_update_bits (codec,WM8737_MISC_BIAS_CONTROL , -WM8737_VMIDSEL_MASK ,0x4 ); +WM8737_VMIDSEL_MASK , +2 <<WM8737_VMIDSEL_SHIFT );/* Bring VMID up */ snd_soc_update_bits(codec, WM8737_POWER_MANAGEMENT,
@@ -508,7 +509,8 @@ static int wm8737_set_bias_level(struct snd_soc_codec *codec,/* VMID at 2*300k */ snd_soc_update_bits (codec,WM8737_MISC_BIAS_CONTROL , -WM8737_VMIDSEL_MASK ,2 ); +WM8737_VMIDSEL_MASK , +1 <<WM8737_VMIDSEL_SHIFT );break ;
Signature · 1 line
2.5.0
PATCH 57/123 ASoC: wm8955: Fix setting wrong register for WM8955_K_8_0_MASK bits
In reply to Jiri SlabyFrom: Axel Lin <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 12c350050538c7dc779c083b7342bfd20f74949c upstream.
WM8955_K_8_0_MASK bits is controlled by WM8955_PLL_CONTROL_3 rather than WM8955_PLL_CONTROL_2.
--- sound/soc/codecs/wm8955.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/wm8955.c +1 -1
@@ -298,7 +298,7 @@ static int wm8955_configure_clocking(struct snd_soc_codec *codec)snd_soc_update_bits (codec,WM8955_PLL_CONTROL_2 ,WM8955_K_17_9_MASK , (pll.k >>9 ) &WM8955_K_17_9_MASK ); -snd_soc_update_bits (codec,WM8955_PLL_CONTROL_2 , +snd_soc_update_bits (codec,WM8955_PLL_CONTROL_3 ,WM8955_K_8_0_MASK , pll.k &WM8955_K_8_0_MASK );if (pll.k)
Signature · 1 line
2.5.0
PATCH 58/123 ASoC: wm8903: Fix define for WM8903_VMID_RES_250K
In reply to Jiri SlabyFrom: Axel Lin <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit ebb6ad73e645b8f2d098dd3c41d2ff0da4146a02 upstream.
VMID Control 0 BIT[2:1] is VMID Divider Enable and Select
00 = VMID disabled (for OFF mode)
01 = 2 x 50kΩ divider (for normal operation) 10 = 2 x 250kΩ divider (for low power standby) 11 = 2 x 5kΩ divider (for fast start-up)
So WM8903_VMID_RES_250K should be 2 << 1, which is 4.
--- sound/soc/codecs/wm8903.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/wm8903.h +1 -1
@@ -172,7 +172,7 @@ extern int wm8903_mic_detect(struct snd_soc_codec *codec,#define WM8903_VMID_BUF_ENA_WIDTH 1/* VMID_BUF_ENA */ #define WM8903_VMID_RES_50K 2 -#define WM8903_VMID_RES_250K 3 +#define WM8903_VMID_RES_250K 4#define WM8903_VMID_RES_5K 6/*
Signature · 1 line
2.5.0
PATCH 59/123 ASoC: wm8960: the enum of "DAC Polarity" should be wm8960_enum[1]
In reply to Jiri SlabyFrom: Zidan Wang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit a077e81ec61e07a7f86997d045109f06719fbffe upstream.
the enum of "DAC Polarity" should be wm8960_enum[1].
--- sound/soc/codecs/wm8960.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/wm8960.c +1 -1
@@ -242,7 +242,7 @@ SOC_SINGLE("PCM Playback -6dB Switch", WM8960_DACCTL1, 7, 1, 0),SOC_ENUM ("ADC Polarity" , wm8960_enum[0 ]),SOC_SINGLE ("ADC High Pass Filter Switch" ,WM8960_DACCTL1 ,0 ,1 ,0 ), -SOC_ENUM ("DAC Polarity" , wm8960_enum[2 ]), +SOC_ENUM ("DAC Polarity" , wm8960_enum[1 ]),SOC_SINGLE_BOOL_EXT ("DAC Deemphasis Switch" ,0 , wm8960_get_deemph, wm8960_put_deemph),
Signature · 1 line
2.5.0
PATCH 60/123 libata: add ATA_HORKAGE_BROKEN_FPDMA_AA quirk for HP 250GB SATA disk VB0250EAVER
In reply to Jiri SlabyFrom: Aleksei Mamlin <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 08c85d2a599d967ede38a847f5594447b6100642 upstream.
Enabling AA on HP 250GB SATA disk VB0250EAVER causes errors:
[ 3.788362] ata3.00: failed to enable AA (error_mask=0x1) [ 3.789243] ata3.00: failed to enable AA (error_mask=0x1)
Add the ATA_HORKAGE_BROKEN_FPDMA_AA for this specific harddisk.
tj: Collected FPDMA_AA entries and updated comment.
--- drivers/ata/libata-core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/ata/libata-core.c +2 -1
@@ -4173,9 +4173,10 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = { {"ST3320[68]13AS" ,"SD1[5-9]" ,ATA_HORKAGE_NONCQ | ATA_HORKAGE_FIRMWARE_WARN }, -/* Seagate Momentus SpinPoint M8 seem to have FPMDA_AA issues */ +/* drives which fail FPDMA_AA activation (some may freeze afterwards) */ { "ST1000LM024 HN-M101MBB", "2AR10001", ATA_HORKAGE_BROKEN_FPDMA_AA }, { "ST1000LM024 HN-M101MBB", "2BA30001", ATA_HORKAGE_BROKEN_FPDMA_AA }, + { "VB0250EAVER", "HPG7", ATA_HORKAGE_BROKEN_FPDMA_AA },/* Blacklist entries taken from Silicon Image 3124/3132 Windows driver .inf file - also several Linux problem reports */
Signature · 1 line
2.5.0
PATCH 61/123 libata: increase the timeout when setting transfer mode
In reply to Jiri SlabyFrom: Mikulas Patocka <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d531be2ca2f27cca5f041b6a140504999144a617 upstream.
I have a ST4000DM000 disk. If Linux is booted while the disk is spun down, the command that sets transfer mode causes the disk to spin up. The spin-up takes longer than the default 5s timeout, so the command fails and timeout is reported.
Fix this by increasing the timeout to 15s, which is enough for the disk to spin up.
--- drivers/ata/libata-core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/ata/libata-core.c +2 -1
@@ -4536,7 +4536,8 @@ static unsigned int ata_dev_set_xfermode(struct ata_device *dev)else /* In the ancient relic department - skip all of this */ return 0 ; - err_mask =ata_exec_internal (dev, &tf,NULL ,DMA_NONE ,NULL ,0 ,0 ); +/* On some disks, this command causes spin-up, so we need longer timeout */ + err_mask =ata_exec_internal (dev, &tf,NULL ,DMA_NONE ,NULL ,0 ,15000 );DPRINTK ("EXIT, err_mask=%x\n" , err_mask);return err_mask;
Signature · 1 line
2.5.0
PATCH 62/123 usb: dwc3: gadget: return error if command sent to DGCMD register fails
In reply to Jiri SlabyFrom: Subbaraya Sundeep Bhatta <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 891b1dc022955d36cf4c0f42d383226a930db7ed upstream.
We need to return error to caller if command is not sent to controller succesfully.
--- drivers/usb/dwc3/gadget.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/dwc3/gadget.c +2 -0
@@ -299,6 +299,8 @@ int dwc3_send_gadget_generic_command(struct dwc3 *dwc, int cmd, u32 param)if (!(reg &DWC3_DGCMD_CMDACT )) {dev_vdbg (dwc->dev,"Command Complete --> %d\n" ,DWC3_DGCMD_STATUS (reg)); +if (DWC3_DGCMD_STATUS (reg)) +return -EINVAL ;return 0 ; }
Signature · 1 line
2.5.0
PATCH 63/123 usb: dwc3: gadget: return error if command sent to DEPCMD register fails
In reply to Jiri SlabyFrom: Subbaraya Sundeep Bhatta <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 76e838c9f7765f9a6205b4d558d75a66104bc60d upstream.
We need to return error to caller if command is not sent to controller succesfully.
--- drivers/usb/dwc3/gadget.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/dwc3/gadget.c +2 -0
@@ -337,6 +337,8 @@ int dwc3_send_gadget_ep_cmd(struct dwc3 *dwc, unsigned ep,if (!(reg &DWC3_DEPCMD_CMDACT )) {dev_vdbg (dwc->dev,"Command Complete --> %d\n" ,DWC3_DEPCMD_STATUS (reg)); +if (DWC3_DEPCMD_STATUS (reg)) +return -EINVAL ;return 0 ; }
Signature · 1 line
2.5.0
PATCH 64/123 usb: dwc3: Reset the transfer resource index on SET_INTERFACE
In reply to Jiri SlabyFrom: John Youn <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit aebda618718157a69c0dc0adb978d69bc2b8723c upstream.
This fixes an issue introduced in commit b23c843992b6 (usb: dwc3:
gadget: fix DEPSTARTCFG for non-EP0 EPs) that made sure we would only use DEPSTARTCFG once per SetConfig.
The trick is that we should use one DEPSTARTCFG per SetConfig *OR* SetInterface. SetInterface was completely missed from the original patch.
This problem became aparent after commit 76e838c9f776 (usb: dwc3:
gadget: return error if command sent to DEPCMD register fails) added checking of the return status of device endpoint commands.
'Set Endpoint Transfer Resource' command was caught failing occasionally. This is because the Transfer Resource Index was not getting reset during a SET_INTERFACE request.
Finally, to fix the issue, was we have to do is make sure that our start_config_issued flag gets reset whenever we receive a SetInterface request.
To verify the problem (and its fix), all we have to do is run test 9 from testusb with 'testusb -t 9 -s 2048 -a -c 5000'.
--- drivers/usb/dwc3/ep0.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/dwc3/ep0.c +4 -0
@@ -707,6 +707,10 @@ static int dwc3_ep0_std_request(struct dwc3 *dwc, struct usb_ctrlrequest *ctrl)dev_vdbg (dwc->dev,"USB_REQ_SET_ISOCH_DELAY\n" ); ret =dwc3_ep0_set_isoch_delay (dwc, ctrl);break ; +case USB_REQ_SET_INTERFACE : +dev_vdbg (dwc->dev,"USB_REQ_SET_INTERFACE\n" ); + dwc->start_config_issued = false; +/* Fall through */ default :dev_vdbg (dwc->dev,"Forwarding to gadget driver\n" ); ret =dwc3_ep0_delegate_req (dwc, ctrl);
Signature · 1 line
2.5.0
PATCH 65/123 USB: devio: fix a condition in async_completed()
In reply to Jiri SlabyFrom: Dan Carpenter <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 83ed07c5db71bc02bd646d6eb60b48908235cdf9 upstream.
Static checkers complain that the current condition is never true. It seems pretty likely that it's a typo and "URB" was intended instead of "USB".
--- drivers/usb/core/devio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/core/devio.c +1 -1
@@ -513,7 +513,7 @@ static void async_completed(struct urb *urb)snoop (&urb->dev->dev,"urb complete\n" );snoop_urb (urb->dev, as->userurb, urb->pipe, urb->actual_length, as->status,COMPLETE ,NULL ,0 ); -if ((urb->transfer_flags &URB_DIR_MASK ) ==USB_DIR_IN ) +if ((urb->transfer_flags &URB_DIR_MASK ) ==URB_DIR_IN )snoop_urb_data (urb, urb->actual_length); if (as->status < 0 && as->bulk_addr && as->status != -ECONNRESET &&
Signature · 1 line
2.5.0
PATCH 66/123 usb: musb: host: rely on port_mode to call musb_start()
In reply to Jiri SlabyFrom: Felipe Balbi <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit be9d39881fc4fa39a64b6eed6bab5d9ee5125344 upstream.
Currently, we're calling musb_start() twice for DRD ports in some situations. This has been observed to cause enumeration issues after suspend/resume cycles with AM335x.
In order to fix the problem, we just have to fix the check on musb_has_gadget() so that it only returns true if current mode is Host and ignore the fact that we have or not a gadget driver loaded.
--- drivers/usb/musb/musb_virthub.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/usb/musb/musb_virthub.c +1 -3
@@ -231,9 +231,7 @@ static int musb_has_gadget(struct musb *musb)#ifdef CONFIG_USB_MUSB_HOST return 1 ;#else -if (musb->port_mode ==MUSB_PORT_MODE_HOST ) -return 1 ; -return musb->g.dev.driver !=NULL ; +return musb->port_mode ==MUSB_PORT_MODE_HOST ;#endif }
Signature · 1 line
2.5.0
PATCH 67/123 USB: cp210x: add ID for Aruba Networks controllers
In reply to Jiri SlabyFrom: Peter Sanford <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit f98a7aa81eeeadcad25665c3501c236d531d4382 upstream.
Add the USB serial console device ID for Aruba Networks 7xxx series controllers which have a USB port for their serial console.
--- drivers/usb/serial/cp210x.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/cp210x.c +1 -0
@@ -187,6 +187,7 @@ static const struct usb_device_id id_table[] = { { USB_DEVICE(0x1FB9, 0x0602) }, /* Lake Shore Model 648 Magnet Power Supply */ { USB_DEVICE(0x1FB9, 0x0700) }, /* Lake Shore Model 737 VSM Controller */ { USB_DEVICE(0x1FB9, 0x0701) }, /* Lake Shore Model 776 Hall Matrix */ + { USB_DEVICE(0x2626, 0xEA60) }, /* Aruba Networks 7xxx USB Serial Console */ { USB_DEVICE(0x3195, 0xF190) }, /* Link Instruments MSO-19 */ { USB_DEVICE(0x3195, 0xF280) }, /* Link Instruments MSO-28 */ { USB_DEVICE(0x3195, 0xF281) }, /* Link Instruments MSO-28 */
Signature · 1 line
2.5.0
PATCH 68/123 USB: option: add 2020:4000 ID
In reply to Jiri SlabyFrom: Claudio Cappelli <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit f6d7fb37f92622479ef6da604f27561f5045ba1e upstream.
Add device Olivetti Olicard 300 (Network Connect: MT6225) - IDs 2020:4000.
T: Bus=01 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 10 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=2020 ProdID=4000 Rev=03.00 S: Manufacturer=Network Connect S: Product=MT6225 C: #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
--- drivers/usb/serial/option.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/option.c +1 -0
@@ -1755,6 +1755,7 @@ static const struct usb_device_id option_ids[] = { { USB_DEVICE_AND_INTERFACE_INFO(0x2001, 0x7d03, 0xff, 0x00, 0x00) }, { USB_DEVICE_AND_INTERFACE_INFO(0x07d1, 0x3e01, 0xff, 0xff, 0xff) }, /* D-Link DWM-152/C1 */ { USB_DEVICE_AND_INTERFACE_INFO(0x07d1, 0x3e02, 0xff, 0xff, 0xff) }, /* D-Link DWM-156/C1 */ + { USB_DEVICE_INTERFACE_CLASS(0x2020, 0x4000, 0xff) }, /* OLICARD300 - MT6225 */ { USB_DEVICE(INOVIA_VENDOR_ID, INOVIA_SEW858) }, { USB_DEVICE(VIATELECOM_VENDOR_ID, VIATELECOM_PRODUCT_CDS7) }, { } /* Terminating entry */
Signature · 1 line
2.5.0
PATCH 69/123 USB: serial: Destroy serial_minors IDR on module exit
In reply to Jiri SlabyFrom: Johannes Thumshirn <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d23f47d4927fd2f61b3a754d83c7bcec215b5cfe upstream.
Destroy serial_minors IDR on module exit, reclaiming the allocated memory.
This was detected by the following semantic patch (written by Luis Rodriguez <[email protected]>)
<SmPL>
@ defines_module_init @
declarer name module_init, module_exit;
declarer name DEFINE_IDR;
identifier init;
@@
module_init(init);
@ defines_module_exit @
identifier exit;
@@
module_exit(exit);
@ declares_idr depends on defines_module_init && defines_module_exit @ identifier idr;
@@
DEFINE_IDR(idr);
@ on_exit_calls_destroy depends on declares_idr && defines_module_exit @ identifier declares_idr.idr, defines_module_exit.exit;
@@
exit(void)
{
...
idr_destroy(&idr);
...
}
@ missing_module_idr_destroy depends on declares_idr && defines_module_exit && !on_exit_calls_destroy @ identifier declares_idr.idr, defines_module_exit.exit;
@@
exit(void)
{
...
+idr_destroy(&idr);
}
</SmPL>
--- drivers/usb/serial/usb-serial.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/usb-serial.c +1 -0
@@ -1300,6 +1300,7 @@ static void __exit usb_serial_exit(void)tty_unregister_driver (usb_serial_tty_driver);put_tty_driver (usb_serial_tty_driver);bus_unregister (&usb_serial_bus_type); +idr_destroy (&serial_minors); }
Signature · 1 line
2.5.0
PATCH 70/123 usb: xhci: Bugfix for NULL pointer deference in xhci_endpoint_init() function
In reply to Jiri SlabyFrom: AMAN DEEP <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 3496810663922617d4b706ef2780c279252ddd6a upstream.
virt_dev->num_cached_rings counts on freed ring and is not updated correctly. In xhci_free_or_cache_endpoint_ring() function, the free ring is added into cache and then num_rings_cache is incremented as below:
virt_dev->ring_cache[rings_cached] = virt_dev->eps[ep_index].ring; virt_dev->num_rings_cached++;
here, free ring pointer is added to a current index and then index is incremented.
So current index always points to empty location in the ring cache. For getting available free ring, current index should be decremented first and then corresponding ring buffer value should be taken from ring cache.
But In function xhci_endpoint_init(), the num_rings_cached index is accessed before decrement.
virt_dev->eps[ep_index].new_ring = virt_dev->ring_cache[virt_dev->num_rings_cached]; virt_dev->ring_cache[virt_dev->num_rings_cached] = NULL; virt_dev->num_rings_cached--; This is bug in manipulating the index of ring cache. And it should be as below: virt_dev->num_rings_cached--; virt_dev->eps[ep_index].new_ring = virt_dev->ring_cache[virt_dev->num_rings_cached]; virt_dev->ring_cache[virt_dev->num_rings_cached] = NULL;
--- drivers/usb/host/xhci-mem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/host/xhci-mem.c +1 -1
@@ -1331,10 +1331,10 @@ int xhci_endpoint_init(struct xhci_hcd *xhci,/* Attempt to use the ring cache */ if (virt_dev->num_rings_cached ==0 )return -ENOMEM ; + virt_dev->num_rings_cached--; virt_dev->eps[ep_index].new_ring = virt_dev->ring_cache[virt_dev->num_rings_cached]; virt_dev->ring_cache[virt_dev->num_rings_cached] =NULL ; - virt_dev->num_rings_cached--;xhci_reinit_cached_ring (xhci, virt_dev->eps[ep_index].new_ring,1 , type); }
Signature · 1 line
2.5.0
PATCH 71/123 dm stats: fix divide by zero if 'number_of_areas' arg is zero
In reply to Jiri SlabyFrom: Mikulas Patocka <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit dd4c1b7d0c95be1c9245118a3accc41a16f1db67 upstream.
If the number_of_areas argument was zero the kernel would crash on div-by-zero. Add better input validation.
--- drivers/md/dm-stats.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/md/dm-stats.c +2 -0
@@ -795,6 +795,8 @@ static int message_stats_create(struct mapped_device *md,return -EINVAL ;if (sscanf (argv[2 ],"/%u%c" , &divisor, &dummy) ==1 ) { +if (!divisor) +return -EINVAL ; step = end - start;if (do_div (step, divisor)) step++;
Signature · 1 line
2.5.0
PATCH 72/123 dm space map metadata: fix occasional leak of a metadata block on resize
In reply to Jiri SlabyFrom: Joe Thornber <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 6096d91af0b65a3967139b32d5adbb3647858a26 upstream.
The metadata space map has a simplified 'bootstrap' mode that is operational when extending the space maps. Whilst in this mode it's possible for some refcount decrement operations to become queued (eg, as a result of shadowing one of the bitmap indexes). These decrements were not being applied when switching out of bootstrap mode.
The effect of this bug was the leaking of a 4k metadata block. This is detected by the latest version of thin_check as a non fatal error.
--- drivers/md/persistent-data/dm-space-map-metadata.c | 50 +++++++++++++++------- 1 file changed, 35 insertions(+), 15 deletions(-)
drivers/md/persistent-data/dm-space-map-metadata.c +35 -15
@@ -204,6 +204,27 @@ static void in(struct sm_metadata *smm) smm->recursion_count++; } +static int apply_bops (struct sm_metadata *smm) +{ +int r =0 ; + +while (!brb_empty (&smm->uncommitted)) { +struct block_op bop; + + r =brb_pop (&smm->uncommitted, &bop); +if (r) { +DMERR ("bug in bop ring buffer" ); +break ; + } + + r =commit_bop (smm, &bop); +if (r) +break ; + } + +return r; +} +static int out (struct sm_metadata *smm) {int r =0 ;
@@ -216,21 +237,8 @@ static int out(struct sm_metadata *smm)return -ENOMEM ; } -if (smm->recursion_count ==1 ) { -while (!brb_empty (&smm->uncommitted)) { -struct block_op bop; - - r =brb_pop (&smm->uncommitted, &bop); -if (r) { -DMERR ("bug in bop ring buffer" ); -break ; - } - - r =commit_bop (smm, &bop); -if (r) -break ; - } - } +if (smm->recursion_count ==1 ) +apply_bops (smm); smm->recursion_count--;
@@ -702,6 +710,12 @@ static int sm_metadata_extend(struct dm_space_map *sm, dm_block_t extra_blocks) } old_len = smm->begin; + r =apply_bops (smm); +if (r) { +DMERR ("%s: apply_bops failed" , __func__); + goto out; + } + r =sm_ll_commit (&smm->ll);if (r) goto out;
@@ -769,6 +783,12 @@ int dm_sm_metadata_create(struct dm_space_map *sm,if (r)return r; + r =apply_bops (smm); +if (r) { +DMERR ("%s: apply_bops failed" , __func__); +return r; + } +return sm_metadata_commit (sm); }
Signature · 1 line
2.5.0
PATCH 73/123 dm btree remove: fix bug in redistribute3
In reply to Jiri SlabyFrom: Dennis Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4c7e309340ff85072e96f529582d159002c36734 upstream.
redistribute3() shares entries out across 3 nodes. Some entries were being moved the wrong way, breaking the ordering. This manifested as a BUG() in dm-btree-remove.c:shift() when entries were removed from the btree.
For additional context see:
https://www.redhat.com/archives/dm-devel/2015-May/msg00113.html
--- drivers/md/persistent-data/dm-btree-remove.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/md/persistent-data/dm-btree-remove.c +3 -3
@@ -309,8 +309,8 @@ static void redistribute3(struct dm_btree_info *info, struct btree_node *parent,if (s <0 && nr_center < -s) {/* not enough in central node */ -shift (left, center, nr_center); - s = nr_center - target; +shift (left, center, -nr_center); + s += nr_center;shift (left, right, s); nr_right += s; }else
@@ -323,7 +323,7 @@ static void redistribute3(struct dm_btree_info *info, struct btree_node *parent,if (s >0 && nr_center < s) {/* not enough in central node */ shift (center, right, nr_center); - s = target - nr_center; + s -= nr_center;shift (left, right, s); nr_left -= s; }else
Signature · 1 line
2.5.0
PATCH 74/123 dm btree: silence lockdep lock inversion in dm_btree_del()
In reply to Jiri SlabyFrom: Joe Thornber <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 1c7518794a3647eb345d59ee52844e8a40405198 upstream.
Allocate memory using GFP_NOIO when deleting a btree. dm_btree_del() can be called via an ioctl and we don't want to recurse into the FS or block layer.
--- drivers/md/persistent-data/dm-btree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/md/persistent-data/dm-btree.c +1 -1
@@ -255,7 +255,7 @@ int dm_btree_del(struct dm_btree_info *info, dm_block_t root)int r;struct del_stack *s; - s =kmalloc (sizeof (*s),GFP_KERNEL ); + s =kmalloc (sizeof (*s),GFP_NOIO );if (!s)return -ENOMEM ; s->info = info;
Signature · 1 line
2.5.0
PATCH 75/123 mmc: block: Add missing mmc_blk_put() in power_ro_lock_show()
In reply to Jiri SlabyFrom: Tomas Winkler <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 9098f84cced870f54d8c410dd2444cfa61467fa0 upstream.
Enclosing mmc_blk_put() is missing in power_ro_lock_show() sysfs handler, let's add it.
--- drivers/mmc/card/block.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/mmc/card/block.c +2 -0
@@ -205,6 +205,8 @@ static ssize_t power_ro_lock_show(struct device *dev, ret =snprintf (buf,PAGE_SIZE ,"%d\n" , locked); +mmc_blk_put (md); +return ret; }
Signature · 1 line
2.5.0
PATCH 76/123 drm/qxl: Do not cause spice-server to clean our objects
In reply to Jiri SlabyFrom: Frediano Ziglio <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2fa19535ca6abcbfd1ccc9ef694db52f49f77747 upstream.
If objects are moved back from system memory to VRAM (and spice id created again) memory is already initialized so we need to set flag to not clear memory.
If you don't do it after a while using desktop many images turns to black or transparents.
--- drivers/gpu/drm/qxl/qxl_cmd.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/qxl/qxl_cmd.c +1 -0
@@ -505,6 +505,7 @@ int qxl_hw_surface_alloc(struct qxl_device *qdev, cmd = (struct qxl_surface_cmd *)qxl_release_map (qdev, release); cmd->type =QXL_SURFACE_CMD_CREATE ; + cmd->flags =QXL_SURF_FLAG_KEEP_DATA ; cmd->u.surface_create.format = surf->surf.format; cmd->u.surface_create.width = surf->surf.width; cmd->u.surface_create.height = surf->surf.height;
Signature · 1 line
2.5.0
PATCH 77/123 drm/qxl: Do not leak memory if qxl_release_list_add fails
In reply to Jiri SlabyFrom: Frediano Ziglio <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 8451cc964c1d193b989c41a44e5e77109cc696f8 upstream.
If the function fails reference counter to the object is not decremented causing leaks.
This is hard to spot as it happens only on very low memory situations.
--- drivers/gpu/drm/qxl/qxl_ioctl.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/gpu/drm/qxl/qxl_ioctl.c +3 -1
@@ -122,8 +122,10 @@ static struct qxl_bo *qxlhw_handle_to_bo(struct qxl_device *qdev, qobj =gem_to_qxl_bo (gobj); ret =qxl_release_list_add (release, qobj); -if (ret) +if (ret) { +drm_gem_object_unreference_unlocked (gobj);return NULL ; + }return qobj; }
Signature · 1 line
2.5.0
PATCH 78/123 drm/radeon: take the mode_config mutex when dealing with hpds (v2)
In reply to Jiri SlabyFrom: Alex Deucher <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 39fa10f7e21574a70cecf1fed0f9b36535aa68a0 upstream.
Since we are messing with state in the worker.
v2: drop the changes in the mst worker
--- drivers/gpu/drm/radeon/radeon_irq_kms.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/radeon/radeon_irq_kms.c +2 -0
@@ -73,10 +73,12 @@ static void radeon_hotplug_work_func(struct work_struct *work)struct drm_mode_config *mode_config = &dev->mode_config;struct drm_connector *connector; +mutex_lock (&mode_config->mutex);if (mode_config->num_connector) {list_for_each_entry (connector, &mode_config->connector_list, head)radeon_connector_hotplug (connector); } +mutex_unlock (&mode_config->mutex);/* Just fire off a uevent and let userspace tell us what to do */ drm_helper_hpd_irq_event (dev); }
Signature · 1 line
2.5.0
PATCH 79/123 drm/radeon: compute ring fix hibernation (CI GPU family) v2.
In reply to Jiri SlabyFrom: Jérôme Glisse <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 161569deaa03cf3c00ed63352006193f250b0648 upstream.
In order for hibernation to reliably work we need to cleanup more thoroughly the compute ring. Hibernation is different from suspend resume as when we resume from hibernation the hardware is first fully initialize by regular kernel then freeze callback happens (which correspond to a suspend inside the radeon kernel driver) and turn off each of the block. It turns out we were not cleanly shutting down the compute ring. This patch fix that.
Hibernation and suspend to ram were tested (several times) on :
Bonaire
Hawaii
Mullins
Kaveri
Kabini
Changed since v1:
- Factor the ring stop logic into a function taking ring as arg.
--- drivers/gpu/drm/radeon/cik.c | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
drivers/gpu/drm/radeon/cik.c +34 -0
@@ -3520,6 +3520,31 @@ void cik_compute_ring_set_wptr(struct radeon_device *rdev,WDOORBELL32 (ring->doorbell_offset, ring->wptr); } +static void cik_compute_stop (struct radeon_device *rdev, +struct radeon_ring *ring) +{ +u32 j, tmp; + +cik_srbm_select (rdev, ring->me, ring->pipe, ring->queue,0 ); +/* Disable wptr polling. */ + tmp =RREG32 (CP_PQ_WPTR_POLL_CNTL ); + tmp &= ~WPTR_POLL_EN ; +WREG32 (CP_PQ_WPTR_POLL_CNTL , tmp); +/* Disable HQD. */ +if (RREG32 (CP_HQD_ACTIVE ) &1 ) { +WREG32 (CP_HQD_DEQUEUE_REQUEST ,1 ); +for (j =0 ; j < rdev->usec_timeout; j++) { +if (!(RREG32 (CP_HQD_ACTIVE ) &1 )) +break ; +udelay (1 ); + } +WREG32 (CP_HQD_DEQUEUE_REQUEST ,0 ); +WREG32 (CP_HQD_PQ_RPTR ,0 ); +WREG32 (CP_HQD_PQ_WPTR ,0 ); + } +cik_srbm_select (rdev,0 ,0 ,0 ,0 ); +} +/** * cik_cp_compute_enable - enable/disable the compute CP MEs *
@@ -3533,6 +3558,15 @@ static void cik_cp_compute_enable(struct radeon_device *rdev, bool enable)if (enable)WREG32 (CP_MEC_CNTL ,0 );else { +/* +* To make hibernation reliable we need to clear compute ring +* configuration before halting the compute ring. +*/ +mutex_lock (&rdev->srbm_mutex); +cik_compute_stop (rdev,&rdev->ring[CAYMAN_RING_TYPE_CP1_INDEX ]); +cik_compute_stop (rdev,&rdev->ring[CAYMAN_RING_TYPE_CP2_INDEX ]); +mutex_unlock (&rdev->srbm_mutex); +WREG32 (CP_MEC_CNTL , (MEC_ME1_HALT |MEC_ME2_HALT )); rdev->ring[CAYMAN_RING_TYPE_CP1_INDEX ].ready = false; rdev->ring[CAYMAN_RING_TYPE_CP2_INDEX ].ready = false;
Signature · 1 line
2.5.0
PATCH 80/123 drm/radeon: SDMA fix hibernation (CI GPU family).
In reply to Jiri SlabyFrom: Jérôme Glisse <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2ba8d1bb8f6b589037f7db1f01144fc80750e8f7 upstream.
In order for hibernation to reliably work we need to properly turn off the SDMA block, sadly after numerous attemps i haven't not found proper sequence for clean and full shutdown. So simply reset both SDMA block, this makes hibernation works reliably on sea island GPU family (CI)
Hibernation and suspend to ram were tested (several times) on :
Bonaire
Hawaii
Mullins
Kaveri
Kabini
--- drivers/gpu/drm/radeon/cik_sdma.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/gpu/drm/radeon/cik_sdma.c +11 -0
@@ -176,6 +176,17 @@ static void cik_sdma_gfx_stop(struct radeon_device *rdev) } rdev->ring[R600_RING_TYPE_DMA_INDEX ].ready = false; rdev->ring[CAYMAN_RING_TYPE_DMA1_INDEX ].ready = false; + +/* FIXME use something else than big hammer but after few days can not +* seem to find good combination so reset SDMA blocks as it seems we +* do not shut them down properly. This fix hibernation and does not +* affect suspend to ram. +*/ +WREG32 (SRBM_SOFT_RESET ,SOFT_RESET_SDMA |SOFT_RESET_SDMA1 ); + (void )RREG32 (SRBM_SOFT_RESET ); +udelay (50 ); +WREG32 (SRBM_SOFT_RESET ,0 ); + (void )RREG32 (SRBM_SOFT_RESET ); }/**
Signature · 1 line
2.5.0
PATCH 81/123 drm/radeon: Don't flush the GART TLB if rdev->gart.ptr == NULL
In reply to Jiri SlabyFrom: Michel Dänzer <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 233709d2cd6bbaaeda0aeb8d11f6ca7f98563b39 upstream.
This can be the case when the GPU is powered off, e.g. via vgaswitcheroo or runpm. When the GPU is powered up again, radeon_gart_table_vram_pin flushes the TLB after setting rdev->gart.ptr to non-NULL.
Fixes panic on powering off R7xx GPUs.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=61529
--- drivers/gpu/drm/radeon/radeon_gart.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
drivers/gpu/drm/radeon/radeon_gart.c +8 -4
@@ -250,8 +250,10 @@ void radeon_gart_unbind(struct radeon_device *rdev, unsigned offset, } } } -mb (); -radeon_gart_tlb_flush (rdev); +if (rdev->gart.ptr) { +mb (); +radeon_gart_tlb_flush (rdev); + } }/**
@@ -293,8 +295,10 @@ int radeon_gart_bind(struct radeon_device *rdev, unsigned offset, } } } -mb (); -radeon_gart_tlb_flush (rdev); +if (rdev->gart.ptr) { +mb (); +radeon_gart_tlb_flush (rdev); + }return 0 ; }
Signature · 1 line
2.5.0
PATCH 82/123 drm/radeon: add a dpm quirk for Sapphire Radeon R9 270X 2GB GDDR5
In reply to Jiri SlabyFrom: Alex Deucher <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 5dfc71bc44d91d1620505c064fa22b0b3db58a9d upstream.
bug:
https://bugs.freedesktop.org/show_bug.cgi?id=76490
--- drivers/gpu/drm/radeon/si_dpm.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/radeon/si_dpm.c +1 -0
@@ -2915,6 +2915,7 @@ static struct si_dpm_quirk si_dpm_quirk_list[] = {/* PITCAIRN - https://bugs.freedesktop.org/show_bug.cgi?id=76490 */ { PCI_VENDOR_ID_ATI, 0x6810, 0x1462, 0x3036, 0, 120000 }, { PCI_VENDOR_ID_ATI, 0x6811, 0x174b, 0xe271, 0, 120000 }, + { PCI_VENDOR_ID_ATI, 0x6810, 0x174b, 0xe271, 85000, 90000 }, { 0, 0, 0, 0 }, };
Signature · 1 line
2.5.0
PATCH 83/123 drm: add a check for x/y in drm_mode_setcrtc
In reply to Jiri SlabyFrom: Zhao Junwang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 01447e9f04ba1c49a9534ae6a5a6f26c2bb05226 upstream.
legacy setcrtc ioctl does take a 32 bit value which might indeed overflow
the checks of crtc_req->x > INT_MAX and crtc_req->y > INT_MAX aren't needed any more with this
v2: -polish the annotation according to Daniel's comment
--- drivers/gpu/drm/drm_crtc.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/gpu/drm/drm_crtc.c +5 -2
@@ -2071,8 +2071,11 @@ int drm_mode_setcrtc(struct drm_device *dev, void *data,if (!drm_core_check_feature (dev,DRIVER_MODESET ))return -EINVAL ; -/* For some reason crtc x/y offsets are signed internally. */ -if (crtc_req->x >INT_MAX || crtc_req->y >INT_MAX ) +/* +* Universal plane src offsets are only 16.16, prevent havoc for +* drivers using universal plane code internally. +*/ +if (crtc_req->x &0xffff0000 || crtc_req->y &0xffff0000 )return -ERANGE ;drm_modeset_lock_all (dev);
Signature · 1 line
2.5.0
PATCH 84/123 xfs: fix remote symlinks on V5/CRC filesystems
In reply to Jiri SlabyFrom: Eric Sandeen <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2ac56d3d4bd625450a54d4c3f9292d58f6b88232 upstream.
If we create a CRC filesystem, mount it, and create a symlink with a path long enough that it can't live in the inode, we get a very strange result upon remount:
# ls -l mnt total 4 lrwxrwxrwx. 1 root root 929 Jun 15 16:58 link -> XSLM
XSLM is the V5 symlink block header magic (which happens to be followed by a NUL, so the string looks terminated).
xfs_readlink_bmap() advanced cur_chunk by the size of the header for CRC filesystems, but never actually used that pointer; it kept reading from bp->b_addr, which is the start of the block, rather than the start of the symlink data after the header.
Looks like this problem goes back to v3.10.
Fixing this gets us reading the proper link target, again.
--- fs/xfs/xfs_symlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/xfs/xfs_symlink.c +1 -1
@@ -102,7 +102,7 @@ xfs_readlink_bmap( cur_chunk +=sizeof (struct xfs_dsymlink_hdr ); } -memcpy (link + offset, bp->b_addr, byte_cnt); +memcpy (link + offset, cur_chunk, byte_cnt); pathlen -= byte_cnt; offset += byte_cnt;
Signature · 1 line
2.5.0
PATCH 85/123 vTPM: set virtual device before passing to ibmvtpm_reset_crq
In reply to Jiri SlabyFrom: "Hon Ching \\\\(Vicky\\\\) Lo" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 9d75f08946e8485109458ccf16f714697c207f41 upstream.
tpm_ibmvtpm_probe() calls ibmvtpm_reset_crq(ibmvtpm) without having yet set the virtual device in the ibmvtpm structure. So in ibmvtpm_reset_crq, the phype call contains empty unit addresses, ibmvtpm->vdev->unit_address.
--- drivers/char/tpm/tpm_ibmvtpm.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/char/tpm/tpm_ibmvtpm.c +3 -2
@@ -618,6 +618,9 @@ static int tpm_ibmvtpm_probe(struct vio_dev *vio_dev, goto cleanup; } + ibmvtpm->dev = dev; + ibmvtpm->vdev = vio_dev; + crq_q = &ibmvtpm->crq_queue; crq_q->crq_addr = (struct ibmvtpm_crq *)get_zeroed_page (GFP_KERNEL );if (!crq_q->crq_addr) {
@@ -662,8 +665,6 @@ static int tpm_ibmvtpm_probe(struct vio_dev *vio_dev, crq_q->index =0 ; - ibmvtpm->dev = dev; - ibmvtpm->vdev = vio_dev;TPM_VPRIV (chip) = (void *)ibmvtpm;spin_lock_init (&ibmvtpm->rtce_lock);
Signature · 1 line
2.5.0
PATCH 86/123 libata: add ATA_HORKAGE_NOTRIM
In reply to Jiri SlabyFrom: Arne Fitzenreiter <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 71d126fd28de2d4d9b7b2088dbccd7ca62fad6e0 upstream.
Some devices lose data on TRIM whether queued or not. This patch adds a horkage to disable TRIM.
tj: Collapsed unnecessary if() nesting.
--- drivers/ata/libata-scsi.c | 3 ++- include/linux/libata.h | 1 + 2 files changed, 3 insertions(+), 1 deletion(-)
drivers/ata/libata-scsi.c +2 -1
@@ -2510,7 +2510,8 @@ static unsigned int ata_scsiop_read_cap(struct ata_scsi_args *args, u8 *rbuf) rbuf[14 ] = (lowest_aligned >>8 ) &0x3f ; rbuf[15 ] = lowest_aligned; -if (ata_id_has_trim (args->id)) { +if (ata_id_has_trim (args->id) && + !(dev->horkage &ATA_HORKAGE_NOTRIM )) { rbuf[14 ] |=0x80 ;/* TPE */ if (ata_id_has_zero_after_trim (args->id))
include/linux/libata.h +1 -0
@@ -428,6 +428,7 @@ enum {ATA_HORKAGE_NO_NCQ_TRIM = (1 <<19 ),/* don't use queued TRIM */ ATA_HORKAGE_NOLPM = (1 <<20 ),/* don't use LPM */ ATA_HORKAGE_WD_BROKEN_LPM = (1 <<21 ),/* some WDs have broken LPM */ + ATA_HORKAGE_NOTRIM = (1 << 24), /* don't use TRIM *//* DMA mask for user DMA control: User visible values; DO NOT renumber */
Signature · 1 line
2.5.0
PATCH 87/123 libata: force disable trim for SuperSSpeed S238
In reply to Jiri SlabyFrom: Arne Fitzenreiter <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit cda57b1b05cf7b8b99ab4b732bea0b05b6c015cc upstream.
This device loses blocks, often the partition table area, on trim. Disable TRIM.
http://pcengines.ch/msata16a.htm
--- drivers/ata/libata-core.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/ata/libata-core.c +3 -0
@@ -4232,6 +4232,9 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = { { "Crucial_CT*MX100*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM, }, { "Samsung SSD 8*", NULL, ATA_HORKAGE_NO_NCQ_TRIM, }, + /* devices that don't properly handle TRIM commands */ + { "SuperSSpeed S238*", NULL, ATA_HORKAGE_NOTRIM, }, +/* * Some WD SATA-I drives spin up and down erratically when the link * is put into the slumber mode. We don't have full list of the
Signature · 1 line
2.5.0
PATCH 88/123 tracing/filter: Do not WARN on operand count going below zero
In reply to Jiri SlabyFrom: "Steven Rostedt (Red Hat)" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit b4875bbe7e68f139bd3383828ae8e994a0df6d28 upstream.
When testing the fix for the trace filter, I could not come up with a scenario where the operand count goes below zero, so I added a WARN_ON_ONCE(cnt < 0) to the logic. But there is legitimate case that it can happen (although the filter would be wrong).
# echo '>' > /sys/kernel/debug/events/ext4/ext4_truncate_exit/filter
That is, a single operation without any operands will hit the path where the WARN_ON_ONCE() can trigger. Although this is harmless, and the filter is reported as a error. But instead of spitting out a warning to the kernel dmesg, just fail nicely and report it via the proper channels.
--- kernel/trace/trace_events_filter.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
kernel/trace/trace_events_filter.c +3 -1
@@ -1349,7 +1349,9 @@ static int check_preds(struct filter_parse_state *ps) } cnt--; n_normal_preds++; -WARN_ON_ONCE (cnt <0 ); +/* all ops should have operands */ +if (cnt <0 ) +break ; }if (cnt !=1 || !n_normal_preds || n_logical_preds >= n_normal_preds) {
Signature · 1 line
2.5.0
PATCH 89/123 tracing/filter: Do not allow infix to exceed end of string
In reply to Jiri SlabyFrom: "Steven Rostedt (Red Hat)" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 6b88f44e161b9ee2a803e5b2b1fbcf4e20e8b980 upstream.
While debugging a WARN_ON() for filtering, I found that it is possible for the filter string to be referenced after its end. With the filter:
# echo '>' > /sys/kernel/debug/events/ext4/ext4_truncate_exit/filter
The filter_parse() function can call infix_get_op() which calls infix_advance() that updates the infix filter pointers for the cnt and tail without checking if the filter is already at the end, which will put the cnt to zero and the tail beyond the end. The loop then calls infix_next() that has
ps->infix.cnt--; return ps->infix.string[ps->infix.tail++];
The cnt will now be below zero, and the tail that is returned is already passed the end of the filter string. So far the allocation of the filter string usually has some buffer that is zeroed out, but if the filter string is of the exact size of the allocated buffer there's no guarantee that the charater after the nul terminating character will be zero.
Luckily, only root can write to the filter.
--- kernel/trace/trace_events_filter.c | 6 ++++++ 1 file changed, 6 insertions(+)
kernel/trace/trace_events_filter.c +6 -0
@@ -1021,6 +1021,9 @@ static void parse_init(struct filter_parse_state *ps,static char infix_next (struct filter_parse_state *ps) { +if (!ps->infix.cnt) +return 0 ; + ps->infix.cnt--;return ps->infix.string[ps->infix.tail++];
@@ -1036,6 +1039,9 @@ static char infix_peek(struct filter_parse_state *ps)static void infix_advance (struct filter_parse_state *ps) { +if (!ps->infix.cnt) +return ; + ps->infix.cnt--; ps->infix.tail++; }
Signature · 1 line
2.5.0
PATCH 90/123 tracing: Have branch tracer use recursive field of task struct
In reply to Jiri SlabyFrom: "Steven Rostedt (Red Hat)" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 6224beb12e190ff11f3c7d4bf50cb2922878f600 upstream.
Fengguang Wu's tests triggered a bug in the branch tracer's start up test when CONFIG_DEBUG_PREEMPT set. This was because that config adds some debug logic in the per cpu field, which calls back into the branch tracer.
The branch tracer has its own recursive checks, but uses a per cpu variable to implement it. If retrieving the per cpu variable calls back into the branch tracer, you can see how things will break.
Instead of using a per cpu variable, use the trace_recursion field of the current task struct. Simply set a bit when entering the branch tracing and clear it when leaving. If the bit is set on entry, just don't do the tracing.
There's also the case with lockdep, as the local_irq_save() called before the recursion can also trigger code that can call back into the function. Changing that to a raw_local_irq_save() will protect that as well.
This prevents the recursion and the inevitable crash that follows.
--- kernel/trace/trace.h | 1 + kernel/trace/trace_branch.c | 17 ++++++++++------- 2 files changed, 11 insertions(+), 7 deletions(-)
kernel/trace/trace.h +1 -0
@@ -420,6 +420,7 @@ enum {TRACE_CONTROL_BIT , + TRACE_BRANCH_BIT,/* * Abuse of the trace_recursion. * As we need a way to maintain state if we are tracing the function
kernel/trace/trace_branch.c +10 -7
@@ -37,9 +37,12 @@ probe_likely_condition(struct ftrace_branch_data *f, int val, int expect)struct trace_branch *entry;struct ring_buffer *buffer;unsigned long flags; -int cpu, pc; +int pc;const char *p; +if (current->trace_recursion &TRACE_BRANCH_BIT ) +return ; +/* * I would love to save just the ftrace_likely_data pointer, but * this code can also be used by modules. Ugly things can happen
@@ -50,10 +53,10 @@ probe_likely_condition(struct ftrace_branch_data *f, int val, int expect)if (unlikely (!tr))return ; -local_irq_save (flags); - cpu =raw_smp_processor_id (); - data =per_cpu_ptr (tr->trace_buffer.data, cpu); -if (atomic_inc_return (&data->disabled) !=1 ) +raw_local_irq_save (flags); + current->trace_recursion |=TRACE_BRANCH_BIT ; + data =this_cpu_ptr (tr->trace_buffer.data); +if (atomic_read (&data->disabled)) goto out; pc =preempt_count ();
@@ -82,8 +85,8 @@ probe_likely_condition(struct ftrace_branch_data *f, int val, int expect)__buffer_unlock_commit (buffer, event); out: -atomic_dec (&data->disabled); -local_irq_restore (flags); + current->trace_recursion &= ~TRACE_BRANCH_BIT ; +raw_local_irq_restore (flags); } static inline
Signature · 1 line
2.5.0
PATCH 91/123 dmaengine: mv_xor: bug fix for racing condition in descriptors cleanup
In reply to Jiri SlabyFrom: Lior Amsalem <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 9136291f1dbc1d4d1cacd2840fb35f4f3ce16c46 upstream.
This patch fixes a bug in the XOR driver where the cleanup function can be called and free descriptors that never been processed by the engine (which result in data errors).
The cleanup function will free descriptors based on the ownership bit in the descriptors.
--- drivers/dma/mv_xor.c | 72 +++++++++++++++++++++++++++++++++------------------- drivers/dma/mv_xor.h | 1 + 2 files changed, 47 insertions(+), 26 deletions(-)
drivers/dma/mv_xor.c +46 -26
@@ -363,7 +363,8 @@ static void __mv_xor_slot_cleanup(struct mv_xor_chan *mv_chan)dma_cookie_t cookie =0 ;int busy =mv_chan_is_busy (mv_chan);u32 current_desc =mv_chan_get_current_desc (mv_chan); -int seen_current =0 ; +int current_cleaned =0 ; +struct mv_xor_desc *hw_desc;dev_dbg (mv_chan_to_devp (mv_chan),"%s %d\n" , __func__, __LINE__);dev_dbg (mv_chan_to_devp (mv_chan),"current_desc %x\n" , current_desc);
@@ -375,38 +376,57 @@ static void __mv_xor_slot_cleanup(struct mv_xor_chan *mv_chan)list_for_each_entry_safe (iter, _iter, &mv_chan->chain, chain_node) { -prefetch (_iter); -prefetch (&_iter->async_tx); -/* do not advance past the current descriptor loaded into the -* hardware channel, subsequent descriptors are either in -* process or have not been submitted -*/ -if (seen_current) -break ; +/* clean finished descriptors */ + hw_desc = iter->hw_desc; +if (hw_desc->status &XOR_DESC_SUCCESS ) { + cookie =mv_xor_run_tx_complete_actions (iter, mv_chan, + cookie); -/* stop the search if we reach the current descriptor and the -* channel is busy -*/ -if (iter->async_tx.phys == current_desc) { - seen_current =1 ; -if (busy) +/* done processing desc, clean slot */ +mv_xor_clean_slot (iter, mv_chan); + +/* break if we did cleaned the current */ +if (iter->async_tx.phys == current_desc) { + current_cleaned =1 ; +break ; + } + }else { +if (iter->async_tx.phys == current_desc) { + current_cleaned =0 ;break ; + } } - - cookie =mv_xor_run_tx_complete_actions (iter, mv_chan, cookie); - -if (mv_xor_clean_slot (iter, mv_chan)) -break ; }if ((busy ==0 ) && !list_empty (&mv_chan->chain)) { -struct mv_xor_desc_slot *chain_head; - chain_head =list_entry (mv_chan->chain.next, - struct mv_xor_desc_slot, - chain_node); - -mv_xor_start_new_chain (mv_chan, chain_head); +if (current_cleaned) { +/* +* current descriptor cleaned and removed, run +* from list head +*/ + iter =list_entry (mv_chan->chain.next, + struct mv_xor_desc_slot, + chain_node); +mv_xor_start_new_chain (mv_chan, iter); + }else { +if (!list_is_last (&iter->chain_node, &mv_chan->chain)) { +/* +* descriptors are still waiting after +* current, trigger them +*/ + iter =list_entry (iter->chain_node.next, + struct mv_xor_desc_slot, + chain_node); +mv_xor_start_new_chain (mv_chan, iter); + }else { +/* +* some descriptors are still waiting +* to be cleaned +*/ +tasklet_schedule (&mv_chan->irq_tasklet); + } + } }if (cookie >0 )
drivers/dma/mv_xor.h +1 -0
@@ -33,6 +33,7 @@#define XOR_OPERATION_MODE_XOR 0#define XOR_OPERATION_MODE_MEMCPY 2#define XOR_DESCRIPTOR_SWAP BIT(14) +#define XOR_DESC_SUCCESS 0x40000000#define XOR_CURR_DESC (chan) (chan->mmr_base + 0x210 + (chan->idx * 4))#define XOR_NEXT_DESC (chan) (chan->mmr_base + 0x200 + (chan->idx * 4))
Signature · 1 line
2.5.0
PATCH 92/123 hwmon: (mcp3021) Fix broken output scaling
In reply to Jiri SlabyFrom: "Stevens, Nick" <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 347d7e45bd09ce09cbc30d5cea9de377eb22f55c upstream.
The mcp3021 scaling code is dividing the VDD (full-scale) value in millivolts by the A2D resolution to obtain the scaling factor. When VDD is 3300mV (the standard value) and the resolution is 12-bit (4096 divisions), the result is a scale factor of 3300/4096, which is always one. Effectively, the raw A2D reading is always being returned because no scaling is applied.
This patch fixes the issue and simplifies the register-to-volts calculation, removing the unneeded "output_scale" struct member.
--- drivers/hwmon/mcp3021.c | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-)
drivers/hwmon/mcp3021.c +1 -13
@@ -31,14 +31,11 @@/* output format */ #define MCP3021_SAR_SHIFT 2#define MCP3021_SAR_MASK 0x3ff -#define MCP3021_OUTPUT_RES 10/* 10-bit resolution */ -#define MCP3021_OUTPUT_SCALE 4#define MCP3221_SAR_SHIFT 0#define MCP3221_SAR_MASK 0xfff#define MCP3221_OUTPUT_RES 12/* 12-bit resolution */ -#define MCP3221_OUTPUT_SCALE 1enum chips { mcp3021,
@@ -54,7 +51,6 @@ struct mcp3021_data {u16 sar_shift;u16 sar_mask;u8 output_res; -u8 output_scale; };static int mcp3021_read16 (struct i2c_client *client)
@@ -84,13 +80,7 @@ static int mcp3021_read16(struct i2c_client *client)static inline u16 volts_from_reg (struct mcp3021_data *data,u16 val) { -if (val ==0 ) -return 0 ; - - val = val * data->output_scale - data->output_scale /2 ; - -return val *DIV_ROUND_CLOSEST (data->vdd, - (1 << data->output_res) * data->output_scale); +return DIV_ROUND_CLOSEST (data->vdd * val,1 << data->output_res); } static ssize_t show_in_input(struct device *dev, struct device_attribute *attr,
@@ -132,14 +122,12 @@ static int mcp3021_probe(struct i2c_client *client, data->sar_shift =MCP3021_SAR_SHIFT ; data->sar_mask =MCP3021_SAR_MASK ; data->output_res =MCP3021_OUTPUT_RES ; - data->output_scale =MCP3021_OUTPUT_SCALE ;break ;case mcp3221: data->sar_shift =MCP3221_SAR_SHIFT ; data->sar_mask =MCP3221_SAR_MASK ; data->output_res =MCP3221_OUTPUT_RES ; - data->output_scale =MCP3221_OUTPUT_SCALE ;break ; }
Signature · 1 line
2.5.0
PATCH 93/123 md: fix a build warning
In reply to Jiri SlabyFrom: Firo Yang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4e023612325a9034a542bfab79f78b1fe5ebb841 upstream.
Warning like this:
drivers/md/md.c: In function "update_array_info":drivers/md/md.c:6394:26: warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses]
!mddev->persistent != info->not_persistent||
Fix it as Neil Brown said:mddev->persistent != !info->not_persistent ||
--- drivers/md/md.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/md/md.c +1 -1
@@ -6233,7 +6233,7 @@ static int update_array_info(struct mddev *mddev, mdu_array_info_t *info) mddev->ctime != info->ctime || mddev->level != info->level ||/* mddev->layout != info->layout || */ - !mddev->persistent != info->not_persistent|| + mddev->persistent != !info->not_persistent || mddev->chunk_sectors != info->chunk_size >>9 ||/* ignore bottom 8 bits of state, and allow SB_BITMAP_PRESENT to change */ ((state^info->state) &0xfffffe00 )
Signature · 1 line
2.5.0
PATCH 94/123 Btrfs: use kmem_cache_free when freeing entry in inode cache
In reply to Jiri SlabyFrom: Filipe Manana <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit c3f4a1685bb87e59c886ee68f7967eae07d4dffa upstream.
The free space entries are allocated using kmem_cache_zalloc(), through __btrfs_add_free_space(), therefore we should use kmem_cache_free() and not kfree() to avoid any confusion and any potential problem. Looking at the kfree() definition at mm/slab.c it has the following comment:
/*
* (...)
*
* Don't free memory not originally allocated by kmalloc()
* or you will run into trouble.
*/
So better be safe and use kmem_cache_free().
--- fs/btrfs/inode-map.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/btrfs/inode-map.c +1 -1
@@ -283,7 +283,7 @@ void btrfs_unpin_free_ino(struct btrfs_root *root)__btrfs_add_free_space (ctl, info->offset, count); free:rb_erase (&info->offset_index, rbroot); -kfree (info); +kmem_cache_free (btrfs_free_space_cachep, info); } }
Signature · 1 line
2.5.0
PATCH 95/123 Btrfs: fix memory leak in the extent_same ioctl
In reply to Jiri SlabyFrom: Filipe Manana <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 497b4050e0eacd4c746dd396d14916b1e669849d upstream.
We were allocating memory with memdup_user() but we were never releasing that memory. This affected pretty much every call to the ioctl, whether it deduplicated extents or not.
This issue was reported on IRC by Julian Taylor and on the mailing list by Marcel Ritter, credit goes to them for finding the issue.
--- fs/btrfs/ioctl.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/btrfs/ioctl.c +2 -1
@@ -2707,7 +2707,7 @@ static long btrfs_ioctl_file_extent_same(struct file *file, void __user *argp) {struct btrfs_ioctl_same_args tmp; -struct btrfs_ioctl_same_args *same; +struct btrfs_ioctl_same_args *same =NULL ;struct btrfs_ioctl_same_extent_info *info;struct inode *src = file->f_dentry->d_inode;struct file *dst_file =NULL ;
@@ -2833,6 +2833,7 @@ next: out:mnt_drop_write_file (file); +kfree (same);return ret; }
Signature · 1 line
2.5.0
PATCH 96/123 fuse: initialize fc->release before calling it
In reply to Jiri SlabyFrom: Miklos Szeredi <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 0ad0b3255a08020eaf50e34ef0d6df5bdf5e09ed upstream.
fc->release is called from fuse_conn_put() which was used in the error cleanup before fc->release was initialized.
[Jeremiah Mahler <[email protected]>: assign fc->release after calling fuse_conn_init(fc) instead of before.]
--- fs/fuse/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/fuse/inode.c +1 -1
@@ -1028,6 +1028,7 @@ static int fuse_fill_super(struct super_block *sb, void *data, int silent) goto err_fput;fuse_conn_init (fc); + fc->release = fuse_free_conn; fc->dev = sb->s_dev; fc->sb = sb;
@@ -1042,7 +1043,6 @@ static int fuse_fill_super(struct super_block *sb, void *data, int silent) fc->dont_mask =1 ; sb->s_flags |=MS_POSIXACL ; - fc->release = fuse_free_conn; fc->flags = d.flags; fc->user_id = d.user_id; fc->group_id = d.group_id;
Signature · 1 line
2.5.0
PATCH 97/123 crush: fix a bug in tree bucket decode
In reply to Jiri SlabyFrom: Ilya Dryomov <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 82cd003a77173c91b9acad8033fb7931dac8d751 upstream.
struct crush_bucket_tree::num_nodes is u8, so ceph_decode_8_safe() should be used. -Wconversion catches this, but I guess it went unnoticed in all the noise it spews. The actual problem (at least for common crushmaps) isn't the u32 -> u8 truncation though - it's the advancement by 4 bytes instead of 1 in the crushmap buffer.
--- net/ceph/osdmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ceph/osdmap.c +1 -1
@@ -89,7 +89,7 @@ static int crush_decode_tree_bucket(void **p, void *end, {int j;dout ("crush_decode_tree_bucket %p to %p\n" , *p, end); -ceph_decode_32_safe (p, end, b->num_nodes, bad); +ceph_decode_8_safe (p, end, b->num_nodes, bad); b->node_weights =kcalloc (b->num_nodes,sizeof (u32),GFP_NOFS );if (b->node_weights ==NULL )return -ENOMEM ;
Signature · 1 line
2.5.0
PATCH 98/123 ACPICA: Tables: Fix an issue that FACS initialization is performed twice
In reply to Jiri SlabyFrom: Lv Zheng <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit c04be18448355441a0c424362df65b6422e27bda upstream.
ACPICA commit 90f5332a15e9d9ba83831ca700b2b9f708274658
This patch adds a new FACS initialization flag for acpi_tb_initialize(). acpi_enable_subsystem() might be invoked several times in OS bootup process, and we don't want FACS initialization to be invoked twice. Lv Zheng.
--- drivers/acpi/acpica/utxfinit.c | 10 ++++++---- include/acpi/actypes.h | 1 + 2 files changed, 7 insertions(+), 4 deletions(-)
drivers/acpi/acpica/utxfinit.c +6 -4
@@ -165,10 +165,12 @@ acpi_status acpi_enable_subsystem(u32 flags)* Obtain a permanent mapping for the FACS. This is required for the * Global Lock and the Firmware Waking Vector */ - status =acpi_tb_initialize_facs (); -if (ACPI_FAILURE (status)) { -ACPI_WARNING ((AE_INFO ,"Could not map the FACS table" )); -return_ACPI_STATUS (status); +if (!(flags &ACPI_NO_FACS_INIT )) { + status =acpi_tb_initialize_facs (); +if (ACPI_FAILURE (status)) { +ACPI_WARNING ((AE_INFO ,"Could not map the FACS table" )); +return_ACPI_STATUS (status); + } }#endif /* !ACPI_REDUCED_HARDWARE */
include/acpi/actypes.h +1 -0
@@ -511,6 +511,7 @@ typedef u64 acpi_integer;#define ACPI_NO_ACPI_ENABLE 0x10#define ACPI_NO_DEVICE_INIT 0x20#define ACPI_NO_OBJECT_INIT 0x40 +#define ACPI_NO_FACS_INIT 0x80/* * Initialization state
Signature · 1 line
2.5.0
PATCH 99/123 iscsi-target: Convert iscsi_thread_set usage to kthread.h
In reply to Jiri SlabyFrom: Nicholas Bellinger <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 88dcd2dab5c23b1c9cfc396246d8f476c872f0ca upstream.
This patch converts iscsi-target code to use modern kthread.h API callers for creating RX/TX threads for each new iscsi_conn descriptor, and releasing associated RX/TX threads during connection shutdown.
This is done using iscsit_start_kthreads() -> kthread_run() to start new kthreads from within iscsi_post_login_handler(), and invoking kthread_stop() from existing iscsit_close_connection() code.
Also, convert iscsit_logout_post_handler_closesession() code to use cmpxchg when determing when iscsit_cause_connection_reinstatement() needs to sleep waiting for completion.
--- drivers/target/iscsi/iscsi_target.c | 104 +++++++++++++----------------- drivers/target/iscsi/iscsi_target_core.h | 7 ++ drivers/target/iscsi/iscsi_target_erl0.c | 13 ++-- drivers/target/iscsi/iscsi_target_login.c | 59 +++++++++++++++-- 4 files changed, 114 insertions(+), 69 deletions(-)
drivers/target/iscsi/iscsi_target.c +45 -59
@@ -518,7 +518,7 @@ static struct iscsit_transport iscsi_target_transport = {static int __init iscsi_target_init_module (void ) { -int ret =0 ; +int ret =0 , size;pr_debug ("iSCSI-Target " ISCSIT_VERSION "\n" );
@@ -527,6 +527,7 @@ static int __init iscsi_target_init_module(void)pr_err ("Unable to allocate memory for iscsit_global\n" );return -1 ; } +spin_lock_init (&iscsit_global->ts_bitmap_lock);mutex_init (&auth_id_lock);spin_lock_init (&sess_idr_lock);idr_init (&tiqn_idr);
@@ -536,15 +537,11 @@ static int __init iscsi_target_init_module(void)if (ret <0 ) goto out; - ret =iscsi_thread_set_init (); -if (ret <0 ) + size =BITS_TO_LONGS (ISCSIT_BITMAP_BITS ) *sizeof (long ); + iscsit_global->ts_bitmap =vzalloc (size); +if (!iscsit_global->ts_bitmap) { +pr_err ("Unable to allocate iscsit_global->ts_bitmap\n" ); goto configfs_out; - -if (iscsi_allocate_thread_sets (TARGET_THREAD_SET_COUNT ) != -TARGET_THREAD_SET_COUNT ) { -pr_err ("iscsi_allocate_thread_sets() returned" -" unexpected value!\n" ); - goto ts_out1; } lio_qr_cache = kmem_cache_create("lio_qr_cache",
@@ -553,7 +550,7 @@ static int __init iscsi_target_init_module(void)if (!lio_qr_cache) {pr_err ("nable to kmem_cache_create() for" " lio_qr_cache\n" ); - goto ts_out2; + goto bitmap_out; } lio_dr_cache = kmem_cache_create("lio_dr_cache",
@@ -597,10 +594,8 @@ dr_out:kmem_cache_destroy (lio_dr_cache); qr_out:kmem_cache_destroy (lio_qr_cache); -ts_out2: -iscsi_deallocate_thread_sets (); -ts_out1: -iscsi_thread_set_free (); +bitmap_out: +vfree (iscsit_global->ts_bitmap); configfs_out:iscsi_target_deregister_configfs (); out:
@@ -610,8 +605,6 @@ out: static void __exit iscsi_target_cleanup_module(void) { -iscsi_deallocate_thread_sets (); -iscsi_thread_set_free ();iscsit_release_discovery_tpg ();iscsit_unregister_transport (&iscsi_target_transport);kmem_cache_destroy (lio_qr_cache);
@@ -621,6 +614,7 @@ static void __exit iscsi_target_cleanup_module(void)iscsi_target_deregister_configfs (); +vfree (iscsit_global->ts_bitmap);kfree (iscsit_global); }
@@ -3649,17 +3643,16 @@ static int iscsit_send_reject(void iscsit_thread_get_cpumask (struct iscsi_conn *conn) { -struct iscsi_thread_set *ts = conn->thread_set;int ord, cpu;/* -* thread_id is assigned from iscsit_global->ts_bitmap from -* within iscsi_thread_set.c:iscsi_allocate_thread_sets() +* bitmap_id is assigned from iscsit_global->ts_bitmap from +* within iscsit_start_kthreads() * -* Here we use thread_id to determine which CPU that this -* iSCSI connection's iscsi_thread_set will be scheduled to +* Here we use bitmap_id to determine which CPU that this +* iSCSI connection's RX/TX threads will be scheduled to * execute upon. */ - ord = ts->thread_id %cpumask_weight (cpu_online_mask); + ord = conn->bitmap_id %cpumask_weight (cpu_online_mask);for_each_online_cpu (cpu) {if (ord-- ==0 ) {cpumask_set_cpu (cpu, conn->conn_cpumask);
@@ -3851,7 +3844,7 @@ check_rsp_state:switch (state) {case ISTATE_SEND_LOGOUTRSP :if (!iscsit_logout_post_handler (cmd, conn)) - goto restart; +return -ECONNRESET ;/* fall through */ case ISTATE_SEND_STATUS :case ISTATE_SEND_ASYNCMSG :
@@ -3879,8 +3872,6 @@ check_rsp_state: err:return -1 ; -restart: -return -EAGAIN ; }static int iscsit_handle_response_queue (struct iscsi_conn *conn)
@@ -3907,21 +3898,13 @@ static int iscsit_handle_response_queue(struct iscsi_conn *conn)int iscsi_target_tx_thread (void *arg) {int ret =0 ; -struct iscsi_conn *conn; -struct iscsi_thread_set *ts = arg; +struct iscsi_conn *conn = arg;/* * Allow ourselves to be interrupted by SIGINT so that a * connection recovery / failure event can be triggered externally. */ allow_signal (SIGINT ); -restart: - conn =iscsi_tx_thread_pre_handler (ts); -if (!conn) - goto out; - - ret =0 ; -while (!kthread_should_stop ()) {/* * Ensure that both TX and RX per connection kthreads
@@ -3930,11 +3913,9 @@ restart:iscsit_thread_check_cpumask (conn, current,1 );wait_event_interruptible (conn->queues_wq, - !iscsit_conn_all_queues_empty (conn) || - ts->status ==ISCSI_THREAD_SET_RESET ); + !iscsit_conn_all_queues_empty (conn)); -if ((ts->status ==ISCSI_THREAD_SET_RESET ) || -signal_pending (current)) +if (signal_pending (current)) goto transport_err; get_immediate:
@@ -3945,15 +3926,14 @@ get_immediate: ret =iscsit_handle_response_queue (conn);if (ret ==1 ) goto get_immediate; -else if (ret == -EAGAIN ) - goto restart; +else if (ret == -ECONNRESET ) + goto out;else if (ret <0 ) goto transport_err; } transport_err:iscsit_take_action_for_connection_exit (conn); - goto restart; out:return 0 ; }
@@ -4042,8 +4022,7 @@ int iscsi_target_rx_thread(void *arg)int ret;u8 buffer[ISCSI_HDR_LEN ], opcode;u32 checksum =0 , digest =0 ; -struct iscsi_conn *conn =NULL ; -struct iscsi_thread_set *ts = arg; +struct iscsi_conn *conn = arg;struct kvec iov;/* * Allow ourselves to be interrupted by SIGINT so that a
@@ -4051,11 +4030,6 @@ int iscsi_target_rx_thread(void *arg)*/ allow_signal (SIGINT ); -restart: - conn =iscsi_rx_thread_pre_handler (ts); -if (!conn) - goto out; -if (conn->conn_transport->transport_type ==ISCSI_INFINIBAND ) {struct completion comp;int rc;
@@ -4065,7 +4039,7 @@ restart:if (rc <0 ) goto transport_err; - goto out; + goto transport_err; }while (!kthread_should_stop ()) {
@@ -4143,8 +4117,6 @@ transport_err:if (!signal_pending (current))atomic_set (&conn->transport_failed,1 );iscsit_take_action_for_connection_exit (conn); - goto restart; -out:return 0 ; }
@@ -4206,7 +4178,24 @@ int iscsit_close_connection(if (conn->conn_transport->transport_type ==ISCSI_TCP )complete (&conn->conn_logout_comp); -iscsi_release_thread_set (conn); +if (!strcmp (current->comm,ISCSI_RX_THREAD_NAME )) { +if (conn->tx_thread && +cmpxchg (&conn->tx_thread_active, true, false)) { +send_sig (SIGINT , conn->tx_thread,1 ); +kthread_stop (conn->tx_thread); + } + }else if (!strcmp (current->comm,ISCSI_TX_THREAD_NAME )) { +if (conn->rx_thread && +cmpxchg (&conn->rx_thread_active, true, false)) { +send_sig (SIGINT , conn->rx_thread,1 ); +kthread_stop (conn->rx_thread); + } + } + +spin_lock (&iscsit_global->ts_bitmap_lock); +bitmap_release_region (iscsit_global->ts_bitmap, conn->bitmap_id, +get_order (1 )); +spin_unlock (&iscsit_global->ts_bitmap_lock);iscsit_stop_timers_for_cmds (conn);iscsit_stop_nopin_response_timer (conn);
@@ -4485,15 +4474,13 @@ static void iscsit_logout_post_handler_closesession( struct iscsi_conn *conn) {struct iscsi_session *sess = conn->sess; - -iscsi_set_thread_clear (conn,ISCSI_CLEAR_TX_THREAD ); -iscsi_set_thread_set_signal (conn,ISCSI_SIGNAL_TX_THREAD ); +int sleep =cmpxchg (&conn->tx_thread_active, true, false);atomic_set (&conn->conn_logout_remove,0 );complete (&conn->conn_logout_comp);iscsit_dec_conn_usage_count (conn); -iscsit_stop_session (sess,1 ,1 ); +iscsit_stop_session (sess, sleep, sleep);iscsit_dec_session_usage_count (sess);target_put_session (sess->se_sess); }
@@ -4501,13 +4488,12 @@ static void iscsit_logout_post_handler_closesession(static void iscsit_logout_post_handler_samecid (struct iscsi_conn *conn) { -iscsi_set_thread_clear (conn,ISCSI_CLEAR_TX_THREAD ); -iscsi_set_thread_set_signal (conn,ISCSI_SIGNAL_TX_THREAD ); +int sleep =cmpxchg (&conn->tx_thread_active, true, false);atomic_set (&conn->conn_logout_remove,0 );complete (&conn->conn_logout_comp); -iscsit_cause_connection_reinstatement (conn,1 ); +iscsit_cause_connection_reinstatement (conn, sleep);iscsit_dec_conn_usage_count (conn); }
drivers/target/iscsi/iscsi_target_core.h +7 -0
@@ -601,6 +601,11 @@ struct iscsi_conn {struct iscsi_session *sess;/* Pointer to thread_set in use for this conn's threads */ struct iscsi_thread_set *thread_set; +int bitmap_id; +int rx_thread_active; +struct task_struct *rx_thread; +int tx_thread_active; +struct task_struct *tx_thread;/* list_head for session connection list */ struct list_head conn_list; }____cacheline_aligned ;
@@ -881,10 +886,12 @@ struct iscsit_global {/* Unique identifier used for the authentication daemon */ u32 auth_id;u32 inactive_ts; +#define ISCSIT_BITMAP_BITS 262144/* Thread Set bitmap count */ int ts_bitmap_count;/* Thread Set bitmap pointer */ unsigned long *ts_bitmap; +spinlock_t ts_bitmap_lock;/* Used for iSCSI discovery session authentication */ struct iscsi_node_acl discovery_acl;struct iscsi_portal_group *discovery_tpg;
drivers/target/iscsi/iscsi_target_erl0.c +8 -5
@@ -864,7 +864,10 @@ void iscsit_connection_reinstatement_rcfr(struct iscsi_conn *conn) }spin_unlock_bh (&conn->state_lock); -iscsi_thread_set_force_reinstatement (conn); +if (conn->tx_thread && conn->tx_thread_active) +send_sig (SIGINT , conn->tx_thread,1 ); +if (conn->rx_thread && conn->rx_thread_active) +send_sig (SIGINT , conn->rx_thread,1 ); sleep:wait_for_completion (&conn->conn_wait_rcfr_comp);
@@ -889,10 +892,10 @@ void iscsit_cause_connection_reinstatement(struct iscsi_conn *conn, int sleep)return ; } -if (iscsi_thread_set_force_reinstatement (conn) <0 ) { -spin_unlock_bh (&conn->state_lock); -return ; - } +if (conn->tx_thread && conn->tx_thread_active) +send_sig (SIGINT , conn->tx_thread,1 ); +if (conn->rx_thread && conn->rx_thread_active) +send_sig (SIGINT , conn->rx_thread,1 );atomic_set (&conn->connection_reinstatement,1 );if (!sleep) {
drivers/target/iscsi/iscsi_target_login.c +54 -5
91 lines not on this page · raw message
Signature · 1 line
2.5.0
PATCH 100/123 iser-target: Fix possible deadlock in RDMA_CM connection error
In reply to Jiri SlabyFrom: Sagi Grimberg <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4a579da2586bd3b79b025947ea24ede2bbfede62 upstream.
Before we reach to connection established we may get an error event. In this case the core won't teardown this connection (never established it), so we take care of freeing it ourselves.
--- drivers/infiniband/ulp/isert/ib_isert.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-)
drivers/infiniband/ulp/isert/ib_isert.c +9 -5
@@ -205,7 +205,7 @@ fail:static void isert_free_rx_descriptors (struct isert_conn *isert_conn) { -struct ib_device *ib_dev = isert_conn->conn_cm_id->device; +struct ib_device *ib_dev = isert_conn->conn_device->ib_device;struct iser_rx_desc *rx_desc;int i;
@@ -633,9 +633,9 @@ out:static void isert_connect_release (struct isert_conn *isert_conn) { -struct ib_device *ib_dev = isert_conn->conn_cm_id->device;struct isert_device *device = isert_conn->conn_device;int cq_index; +struct ib_device *ib_dev = device->ib_device;pr_debug ("Entering isert_connect_release(): >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\n" );
@@ -643,7 +643,8 @@ isert_connect_release(struct isert_conn *isert_conn)isert_conn_free_frwr_pool (isert_conn);isert_free_rx_descriptors (isert_conn); -rdma_destroy_id (isert_conn->conn_cm_id); +if (isert_conn->conn_cm_id) +rdma_destroy_id (isert_conn->conn_cm_id);if (isert_conn->conn_qp) { cq_index = ((struct isert_cq_desc *)
@@ -798,12 +799,15 @@ isert_disconnected_handler(struct rdma_cm_id *cma_id,return 0 ; } -static void +static int isert_connect_error (struct rdma_cm_id *cma_id) {struct isert_conn *isert_conn = cma_id->qp->qp_context; + isert_conn->conn_cm_id =NULL ;isert_put_conn (isert_conn); + +return -1 ; } static int
@@ -833,7 +837,7 @@ isert_cma_handler(struct rdma_cm_id *cma_id, struct rdma_cm_event *event)case RDMA_CM_EVENT_REJECTED :/* FALLTHRU */ case RDMA_CM_EVENT_UNREACHABLE :/* FALLTHRU */ case RDMA_CM_EVENT_CONNECT_ERROR : -isert_connect_error (cma_id); + ret =isert_connect_error (cma_id);break ;default :pr_err ("Unhandled RDMA CMA event: %d\n" , event->event);
Signature · 1 line
2.5.0
PATCH 101/123 iser-target: release stale iser connections
In reply to Jiri SlabyFrom: Sagi Grimberg <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2f1b6b7d9a815f341b18dfd26a363f37d4d3c96a upstream.
When receiving a new iser connect request we serialize the pending requests by adding the newly created iser connection to the np accept list and let the login thread process the connect request one by one (np_accept_wait).
In case we received a disconnect request before the iser_conn has begun processing (still linked in np_accept_list) we should detach it from the list and clean it up and not have the login thread process a stale connection. We do it only when the connection state is not already terminating (initiator driven disconnect) as this might lead us to access np_accept_mutex after the np was released in live shutdown scenarios.
--- drivers/infiniband/ulp/isert/ib_isert.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-)
drivers/infiniband/ulp/isert/ib_isert.c +17 -1
@@ -58,6 +58,8 @@ static int isert_rdma_accept(struct isert_conn *isert_conn);struct rdma_cm_id *isert_setup_id (struct isert_np *isert_np); +static void isert_release_work (struct work_struct *work); +static void isert_qp_event_callback (struct ib_event *e,void *context) {
@@ -538,6 +540,7 @@ isert_connect_request(struct rdma_cm_id *cma_id, struct rdma_cm_event *event)mutex_init (&isert_conn->conn_mutex);spin_lock_init (&isert_conn->conn_lock);INIT_LIST_HEAD (&isert_conn->conn_frwr_pool); +INIT_WORK (&isert_conn->release_work, isert_release_work); isert_conn->conn_cm_id = cma_id; isert_conn->responder_resources = event->param.conn.responder_resources;
@@ -783,6 +786,7 @@ isert_disconnected_handler(struct rdma_cm_id *cma_id, {struct isert_np *isert_np = cma_id->context;struct isert_conn *isert_conn; +bool terminating = false;if (isert_np->np_cm_id == cma_id)return isert_np_cma_handler (cma_id->context, event);
@@ -790,12 +794,25 @@ isert_disconnected_handler(struct rdma_cm_id *cma_id, isert_conn = cma_id->qp->qp_context;mutex_lock (&isert_conn->conn_mutex); + terminating = (isert_conn->state ==ISER_CONN_TERMINATING );isert_conn_terminate (isert_conn);mutex_unlock (&isert_conn->conn_mutex);pr_info ("conn %p completing conn_wait\n" , isert_conn);complete (&isert_conn->conn_wait); +if (terminating) + goto out; + +mutex_lock (&isert_np->np_accept_mutex); +if (!list_empty (&isert_conn->conn_accept_node)) { +list_del_init (&isert_conn->conn_accept_node); +isert_put_conn (isert_conn); +queue_work (isert_release_wq, &isert_conn->release_work); + } +mutex_unlock (&isert_np->np_accept_mutex); + +out:return 0 ; }
@@ -2855,7 +2872,6 @@ static void isert_wait_conn(struct iscsi_conn *conn)wait_for_completion (&isert_conn->conn_wait_comp_err); -INIT_WORK (&isert_conn->release_work, isert_release_work);queue_work (isert_release_wq, &isert_conn->release_work); }
Signature · 1 line
2.5.0
PATCH 102/123 mmc: card: Fixup request missing in mmc_blk_issue_rw_rq
In reply to Jiri SlabyFrom: Ding Wang <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 29535f7b797df35cc9b6b3bca635591cdd3dd2a8 upstream.
The current handler of MMC_BLK_CMD_ERR in mmc_blk_issue_rw_rq function may cause new coming request permanent missing when the ongoing request (previoulsy started) complete end.
The problem scenario is as follows:
(1) Request A is ongoing;
(2) Request B arrived, and finally mmc_blk_issue_rw_rq() is called;
(3) Request A encounters the MMC_BLK_CMD_ERR error;
(4) In the error handling of MMC_BLK_CMD_ERR, suppose mmc_blk_cmd_err() end request A completed and return zero. Continue the error handling, suppose mmc_blk_reset() reset device success;
(5) Continue the execution, while loop completed because variable ret
is zero now;
(6) Finally, mmc_blk_issue_rw_rq() return without processing request B.
The process related to the missing request may wait that IO request complete forever, possibly crashing the application or hanging the system.
Fix this issue by starting new request when reset success.
--- drivers/mmc/card/block.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/mmc/card/block.c +5 -3
@@ -1863,9 +1863,11 @@ static int mmc_blk_issue_rw_rq(struct mmc_queue *mq, struct request *rqc)break ;case MMC_BLK_CMD_ERR : ret =mmc_blk_cmd_err (md, card, brq, req, ret); -if (!mmc_blk_reset (md, card->host, type)) -break ; - goto cmd_abort; +if (mmc_blk_reset (md, card->host, type)) + goto cmd_abort; +if (!ret) + goto start_new_req; +break ;case MMC_BLK_RETRY :if (retry++ <5 )break ;
Signature · 1 line
2.5.0
PATCH 103/123 __bitmap_parselist: fix bug in empty string handling
In reply to Jiri SlabyFrom: Chris Metcalf <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2528a8b8f457d7432552d0e2b6f0f4046bb702f4 upstream.
bitmap_parselist("", &mask, nmaskbits) will erroneously set bit zero in the mask. The same bug is visible in cpumask_parselist() since it is layered on top of the bitmask code, e.g. if you boot with "isolcpus=", you will actually end up with cpu zero isolated.
The bug was introduced in commit 4b060420a596 ("bitmap, irq: add smp_affinity_list interface to /proc/irq") when bitmap_parselist() was generalized to support userspace as well as kernelspace.
--- lib/bitmap.c | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-)
lib/bitmap.c +9 -8
@@ -603,12 +603,12 @@ static int __bitmap_parselist(const char *buf, unsigned int buflen,unsigned a, b;int c, old_c, totaldigits;const char __user __force *ubuf = (const char __user __force *)buf; -int exp_digit, in_range; +int at_start, in_range; totaldigits = c =0 ;bitmap_zero (maskp, nmaskbits); do { - exp_digit = 1; + at_start = 1; in_range = 0; a = b = 0;
@@ -637,11 +637,10 @@ static int __bitmap_parselist(const char *buf, unsigned int buflen,break ;if (c =='-' ) { -if (exp_digit || in_range) +if (at_start || in_range)return -EINVAL ; b =0 ; in_range =1 ; - exp_digit =1 ;continue ; }
@@ -651,16 +650,18 @@ static int __bitmap_parselist(const char *buf, unsigned int buflen, b = b *10 + (c -'0' );if (!in_range) a = b; - exp_digit =0 ; + at_start =0 ; totaldigits++; }if (!(a <= b))return -EINVAL ;if (b >= nmaskbits)return -ERANGE ; -while (a <= b) { -set_bit (a, maskp); - a++; +if (!at_start) { +while (a <= b) { +set_bit (a, maskp); + a++; + } } }while (buflen && c ==',' );return 0 ;
Signature · 1 line
2.5.0
PATCH 104/123 security_syslog() should be called once only
In reply to Jiri SlabyFrom: Vasily Averin <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d194e5d666225b04c7754471df0948f645b6ab3a upstream.
The final version of commit 637241a900cb ("kmsg: honor dmesg_restrict sysctl on /dev/kmsg") lost few hooks, as result security_syslog() are processed incorrectly:
- open of /dev/kmsg checks syslog access permissions by using check_syslog_permissions() where security_syslog() is not called if dmesg_restrict is set.
- syslog syscall and /proc/kmsg calls do_syslog() where security_syslog can be executed twice (inside check_syslog_permissions() and then directly in do_syslog())
With this patch security_syslog() is called once only in all syslog-related operations regardless of dmesg_restrict value.
--- kernel/printk/printk.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)
kernel/printk/printk.c +4 -7
@@ -383,11 +383,11 @@ static int check_syslog_permissions(int type, bool from_file)* already done the capabilities checks at open time. */ if (from_file && type !=SYSLOG_ACTION_OPEN ) -return 0 ; + goto ok;if (syslog_action_restricted (type)) {if (capable (CAP_SYSLOG )) -return 0 ; + goto ok;/* * For historical reasons, accept CAP_SYS_ADMIN too, with * a warning.
@@ -397,10 +397,11 @@ static int check_syslog_permissions(int type, bool from_file)"CAP_SYS_ADMIN but no CAP_SYSLOG " "(deprecated).\n" , current->comm, task_pid_nr(current)); -return 0 ; + goto ok; }return -EPERM ; } +ok:return security_syslog (type); }
@@ -1130,10 +1131,6 @@ int do_syslog(int type, char __user *buf, int len, bool from_file)if (error) goto out; - error =security_syslog (type); -if (error) -return error; -switch (type) {case SYSLOG_ACTION_CLOSE :/* Close log */ break ;
Signature · 1 line
2.5.0
PATCH 105/123 mac80211: prevent possible crypto tx tailroom corruption
In reply to Jiri SlabyFrom: Michal Kazior <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit ab499db80fcf07c18e4053f91a619500f663e90e upstream.
There was a possible race between ieee80211_reconfig() and ieee80211_delayed_tailroom_dec(). This could result in inability to transmit data if driver crashed during roaming or rekeying and subsequent skbs with insufficient tailroom appeared.
This race was probably never seen in the wild because a device driver would have to crash AND recover within 0.5s which is very unlikely.
I was able to prove this race exists after changing the delay to 10s locally and crashing ath10k via debugfs immediately after GTK rekeying. In case of ath10k the counter went below
0. This was harmless but other drivers which actually require tailroom (e.g. for WEP ICV or MMIC) could end up with the counter at 0 instead of >0 and introduce insufficient skb tailroom failures because mac80211 would not resize skbs appropriately anymore.
--- net/mac80211/main.c | 3 +++ 1 file changed, 3 insertions(+)
net/mac80211/main.c +3 -0
@@ -248,6 +248,7 @@ static void ieee80211_restart_work(struct work_struct *work) {struct ieee80211_local *local = container_of(work, struct ieee80211_local, restart_work); +struct ieee80211_sub_if_data *sdata;/* wait for scan work complete */ flush_workqueue (local->workqueue);
@@ -260,6 +261,8 @@ static void ieee80211_restart_work(struct work_struct *work)mutex_unlock (&local->mtx);rtnl_lock (); +list_for_each_entry (sdata, &local->interfaces, list) +flush_delayed_work (&sdata->dec_tailroom_needed_wk);ieee80211_scan_cancel (local);ieee80211_reconfig (local);rtnl_unlock ();
Signature · 1 line
2.5.0
PATCH 106/123 clocksource: exynos_mct: Avoid blocking calls in the cpu hotplug notifier
In reply to Jiri SlabyFrom: Damian Eppel <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 56a94f13919c0db5958611b388e1581b4852f3c9 upstream.
Whilst testing cpu hotplug events on kernel configured with DEBUG_PREEMPT and DEBUG_ATOMIC_SLEEP we get following BUG message, caused by calling request_irq() and free_irq() in the context of hotplug notification (which is in this case atomic context).
[ 40.785859] CPU1: Software reset [ 40.786660] BUG: sleeping function called from invalid context at mm/slub.c:1241 [ 40.786668] in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper/1 [ 40.786678] Preemption disabled at:[< (null)>] (null) [ 40.786681] [ 40.786692] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.19.0-rc4-00024-g7dca860 #36 [ 40.786698] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree) [ 40.786728] [<c0014a00>] (unwind_backtrace) from [<c0011980>] (show_stack+0x10/0x14) [ 40.786747] [<c0011980>] (show_stack) from [<c0449ba0>] (dump_stack+0x70/0xbc) [ 40.786767] [<c0449ba0>] (dump_stack) from [<c00c6124>] (kmem_cache_alloc+0xd8/0x170) [ 40.786785] [<c00c6124>] (kmem_cache_alloc) from [<c005d6f8>] (request_threaded_irq+0x64/0x128) [ 40.786804] [<c005d6f8>] (request_threaded_irq) from [<c0350b8c>] (exynos4_local_timer_setup+0xc0/0x13c) [ 40.786820] [<c0350b8c>] (exynos4_local_timer_setup) from [<c0350ca8>] (exynos4_mct_cpu_notify+0x30/0xa8) [ 40.786838] [<c0350ca8>] (exynos4_mct_cpu_notify) from [<c003b330>] (notifier_call_chain+0x44/0x84) [ 40.786857] [<c003b330>] (notifier_call_chain) from [<c0022fd4>] (__cpu_notify+0x28/0x44) [ 40.786873] [<c0022fd4>] (__cpu_notify) from [<c0013714>] (secondary_start_kernel+0xec/0x150) [ 40.786886] [<c0013714>] (secondary_start_kernel) from [<40008764>] (0x40008764)
Interrupts cannot be requested/freed in the CPU_STARTING/CPU_DYING notifications which run on the hotplugged cpu with interrupts and preemption disabled.
To avoid the issue, request the interrupts for all possible cpus in the boot code. The interrupts are marked NO_AUTOENABLE to avoid a racy request_irq/disable_irq() sequence. The flag prevents the request_irq() code from enabling the interrupt immediately.
The interrupt is then enabled in the CPU_STARTING notifier of the hotplugged cpu and again disabled with disable_irq_nosync() in the CPU_DYING notifier.
[ tglx: Massaged changelog to match the patch ]
--- drivers/clocksource/exynos_mct.c | 43 ++++++++++++++++++++++++++++------------ 1 file changed, 30 insertions(+), 13 deletions(-)
drivers/clocksource/exynos_mct.c +30 -13
@@ -418,15 +418,12 @@ static int exynos4_local_timer_setup(struct clock_event_device *evt)exynos4_mct_write (TICK_BASE_CNT , mevt->base +MCT_L_TCNTB_OFFSET );if (mct_int_type ==MCT_INT_SPI ) { - evt->irq = mct_irqs[MCT_L0_IRQ + cpu]; -if (request_irq (evt->irq, exynos4_mct_tick_isr, -IRQF_TIMER |IRQF_NOBALANCING , - evt->name, mevt)) { -pr_err ("exynos-mct: cannot register IRQ %d\n" , - evt->irq); + +if (evt->irq ==-1 )return -EIO ; - } -irq_force_affinity (mct_irqs[MCT_L0_IRQ + cpu],cpumask_of (cpu)); + +irq_force_affinity (evt->irq,cpumask_of (cpu)); +enable_irq (evt->irq); }else {enable_percpu_irq (mct_irqs[MCT_L0_IRQ ],0 ); }
@@ -439,10 +436,12 @@ static int exynos4_local_timer_setup(struct clock_event_device *evt)static void exynos4_local_timer_stop (struct clock_event_device *evt) { evt->set_mode (CLOCK_EVT_MODE_UNUSED , evt); -if (mct_int_type ==MCT_INT_SPI ) -free_irq (evt->irq,this_cpu_ptr (&percpu_mct_tick)); -else +if (mct_int_type ==MCT_INT_SPI ) { +if (evt->irq !=-1 ) +disable_irq_nosync (evt->irq); + }else {disable_percpu_irq (mct_irqs[MCT_L0_IRQ ]); + } } static int exynos4_mct_cpu_notify(struct notifier_block *self,
@@ -474,7 +473,7 @@ static struct notifier_block exynos4_mct_cpu_nb = {static void __init exynos4_timer_resources (struct device_node *np,void __iomem *base) { -int err; +int err, cpu;struct mct_clock_event_device *mevt =this_cpu_ptr (&percpu_mct_tick);struct clk *mct_clk, *tick_clk;
@@ -501,7 +500,25 @@ static void __init exynos4_timer_resources(struct device_node *np, void __iomemWARN (err,"MCT: can't request IRQ %d (%d)\n" , mct_irqs[MCT_L0_IRQ ], err); }else { -irq_set_affinity (mct_irqs[MCT_L0_IRQ ],cpumask_of (0 )); +for_each_possible_cpu (cpu) { +int mct_irq = mct_irqs[MCT_L0_IRQ + cpu]; +struct mct_clock_event_device *pcpu_mevt = +per_cpu_ptr (&percpu_mct_tick, cpu); + + pcpu_mevt->evt.irq =-1 ; + +irq_set_status_flags (mct_irq,IRQ_NOAUTOEN ); +if (request_irq (mct_irq, + exynos4_mct_tick_isr, +IRQF_TIMER |IRQF_NOBALANCING , + pcpu_mevt->name, pcpu_mevt)) { +pr_err ("exynos-mct: cannot register IRQ (cpu%d)\n" , + cpu); + +continue ; + } + pcpu_mevt->evt.irq = mct_irq; + } } err =register_cpu_notifier (&exynos4_mct_cpu_nb);
Signature · 1 line
2.5.0
PATCH 107/123 ideapad: fix software rfkill setting
In reply to Jiri SlabyFrom: Arnd Bergmann <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 4b200b4604bec3388426159f1656109d19fadf6e upstream.
This fixes a several year old regression that I found while trying to get the Yoga 3 11 to work. The ideapad_rfk_set function is meant to send a command to the embedded controller through ACPI, but as of c1f73658ed, it sends the index of the rfkill device instead of the command, and ignores the opcode field.
This changes it back to the original behavior, which indeed flips the rfkill state as seen in the debugfs interface.
--- drivers/platform/x86/ideapad-laptop.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/platform/x86/ideapad-laptop.c +1 -1
@@ -445,7 +445,7 @@ const struct ideapad_rfk_data ideapad_rfk_data[] = {static int ideapad_rfk_set (void *data,bool blocked) { -unsigned long opcode = (unsigned long )data; +int opcode = ideapad_rfk_data[(unsigned long )data].opcode;return write_ec_cmd (ideapad_handle, opcode, !blocked); }
Signature · 1 line
2.5.0
PATCH 108/123 dell-laptop: Fix allocating & freeing SMI buffer page
In reply to Jiri SlabyFrom: Pali Rohár <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit b8830a4e71b15d0364ac8e6c55301eea73f211da upstream.
This commit fix kernel crash when probing for rfkill devices in dell-laptop driver failed. Function free_page() was incorrectly used on struct page * instead of virtual address of SMI buffer.
This commit also simplify allocating page for SMI buffer by using __get_free_page() function instead of sequential call of functions alloc_page() and page_address().
--- drivers/platform/x86/dell-laptop.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)
drivers/platform/x86/dell-laptop.c +3 -5
@@ -264,7 +264,6 @@ static struct dmi_system_id dell_quirks[] = { };static struct calling_interface_buffer *buffer; -static struct page *bufferpage;static DEFINE_MUTEX (buffer_mutex);static int hwswitch_state;
@@ -550,12 +549,11 @@ static int __init dell_init(void)* Allocate buffer below 4GB for SMI data--only 32-bit physical addr * is passed to SMI handler. */ - bufferpage =alloc_page (GFP_KERNEL |GFP_DMA32 ); -if (!bufferpage) { + buffer = (void *)__get_free_page (GFP_KERNEL |GFP_DMA32 ); +if (!buffer) { ret = -ENOMEM ; goto fail_buffer; } - buffer =page_address (bufferpage);if (quirks && quirks->touchpad_led)touchpad_led_init (&platform_device->dev);
@@ -603,7 +601,7 @@ static int __init dell_init(void)return 0 ; fail_backlight: -free_page ((unsigned long )bufferpage); +free_page ((unsigned long )buffer); fail_buffer:platform_device_del (platform_device); fail_platform_device2:
Signature · 1 line
2.5.0
PATCH 109/123 USB: usbfs: allow URBs to be reaped after disconnection
In reply to Jiri SlabyFrom: Alan Stern <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 3f2cee73b650921b2e214bf487b2061a1c266504 upstream.
The usbfs API has a peculiar hole: Users are not allowed to reap their URBs after the device has been disconnected. There doesn't seem to be any good reason for this; it is an ad-hoc inconsistency.
The patch allows users to issue the USBDEVFS_REAPURB and USBDEVFS_REAPURBNDELAY ioctls (together with their 32-bit counterparts on 64-bit systems) even after the device is gone. If no URBs are pending for a disconnected device then the ioctls will return -ENODEV rather than -EAGAIN, because obviously no new URBs will ever be able to complete.
The patch also adds a new capability flag for USBDEVFS_GET_CAPABILITIES to indicate that the reap-after-disconnect feature is supported.
--- drivers/usb/core/devio.c | 63 +++++++++++++++++++++++---------------- include/uapi/linux/usbdevice_fs.h | 3 +- 2 files changed, 39 insertions(+), 27 deletions(-)
drivers/usb/core/devio.c +37 -26
@@ -1593,7 +1593,7 @@ static struct async *reap_as(struct dev_state *ps)for (;;) {__set_current_state (TASK_INTERRUPTIBLE ); as =async_getcompleted (ps); -if (as) +if (as || !connected (ps))break ;if (signal_pending (current))break ;
@@ -1616,7 +1616,7 @@ static int proc_reapurb(struct dev_state *ps, void __user *arg) }if (signal_pending (current))return -EINTR ; -return -EIO ; +return -ENODEV ; }static int proc_reapurbnonblock (struct dev_state *ps,void __user *arg)
@@ -1625,10 +1625,11 @@ static int proc_reapurbnonblock(struct dev_state *ps, void __user *arg)struct async *as; as =async_getcompleted (ps); - retval = -EAGAIN ;if (as) { retval =processcompl (as, (void __user *__user *)arg);free_async (as); + }else { + retval = (connected (ps) ? -EAGAIN : -ENODEV ); }return retval; }
@@ -1758,7 +1759,7 @@ static int proc_reapurb_compat(struct dev_state *ps, void __user *arg) }if (signal_pending (current))return -EINTR ; -return -EIO ; +return -ENODEV ; }static int proc_reapurbnonblock_compat (struct dev_state *ps,void __user *arg)
@@ -1766,11 +1767,12 @@ static int proc_reapurbnonblock_compat(struct dev_state *ps, void __user *arg)int retval;struct async *as; - retval = -EAGAIN ; as =async_getcompleted (ps);if (as) { retval =processcompl_compat (as, (void __user *__user *)arg);free_async (as); + }else { + retval = (connected (ps) ? -EAGAIN : -ENODEV ); }return retval; }
@@ -1942,7 +1944,8 @@ static int proc_get_capabilities(struct dev_state *ps, void __user *arg) {__u32 caps; - caps =USBDEVFS_CAP_ZERO_PACKET |USBDEVFS_CAP_NO_PACKET_SIZE_LIM ; + caps =USBDEVFS_CAP_ZERO_PACKET |USBDEVFS_CAP_NO_PACKET_SIZE_LIM | +USBDEVFS_CAP_REAP_AFTER_DISCONNECT ;if (!ps->dev->bus->no_stop_on_short) caps |=USBDEVFS_CAP_BULK_CONTINUATION ;if (ps->dev->bus->sg_tablesize)
@@ -2003,6 +2006,32 @@ static long usbdev_do_ioctl(struct file *file, unsigned int cmd,return -EPERM ;usb_lock_device (dev); + +/* Reap operations are allowed even after disconnection */ +switch (cmd) { +case USBDEVFS_REAPURB : +snoop (&dev->dev,"%s: REAPURB\n" , __func__); + ret =proc_reapurb (ps, p); + goto done; + +case USBDEVFS_REAPURBNDELAY : +snoop (&dev->dev,"%s: REAPURBNDELAY\n" , __func__); + ret =proc_reapurbnonblock (ps, p); + goto done; + +#ifdef CONFIG_COMPAT +case USBDEVFS_REAPURB32 : +snoop (&dev->dev,"%s: REAPURB32\n" , __func__); + ret =proc_reapurb_compat (ps, p); + goto done; + +case USBDEVFS_REAPURBNDELAY32 : +snoop (&dev->dev,"%s: REAPURBNDELAY32\n" , __func__); + ret =proc_reapurbnonblock_compat (ps, p); + goto done; +#endif + } +if (!connected (ps)) {usb_unlock_device (dev);return -ENODEV ;
@@ -2096,16 +2125,6 @@ static long usbdev_do_ioctl(struct file *file, unsigned int cmd, inode->i_mtime =CURRENT_TIME ;break ; -case USBDEVFS_REAPURB32 : -snoop (&dev->dev,"%s: REAPURB32\n" , __func__); - ret =proc_reapurb_compat (ps, p); -break ; - -case USBDEVFS_REAPURBNDELAY32 : -snoop (&dev->dev,"%s: REAPURBNDELAY32\n" , __func__); - ret =proc_reapurbnonblock_compat (ps, p); -break ; -case USBDEVFS_IOCTL32 :snoop (&dev->dev,"%s: IOCTL32\n" , __func__); ret =proc_ioctl_compat (ps,ptr_to_compat (p));
@@ -2117,16 +2136,6 @@ static long usbdev_do_ioctl(struct file *file, unsigned int cmd, ret =proc_unlinkurb (ps, p);break ; -case USBDEVFS_REAPURB : -snoop (&dev->dev,"%s: REAPURB\n" , __func__); - ret =proc_reapurb (ps, p); -break ; - -case USBDEVFS_REAPURBNDELAY : -snoop (&dev->dev,"%s: REAPURBNDELAY\n" , __func__); - ret =proc_reapurbnonblock (ps, p); -break ; -case USBDEVFS_DISCSIGNAL :snoop (&dev->dev,"%s: DISCSIGNAL\n" , __func__); ret =proc_disconnectsignal (ps, p);
@@ -2163,6 +2172,8 @@ static long usbdev_do_ioctl(struct file *file, unsigned int cmd, ret =proc_disconnect_claim (ps, p);break ; } + + done:usb_unlock_device (dev);if (ret >=0 ) inode->i_atime =CURRENT_TIME ;
include/uapi/linux/usbdevice_fs.h +2 -1
@@ -125,11 +125,12 @@ struct usbdevfs_hub_portinfo {char port [127 ];/* e.g. port 3 connects to device 27 */ }; -/* Device capability flags */ +/* System and bus capability flags */ #define USBDEVFS_CAP_ZERO_PACKET 0x01#define USBDEVFS_CAP_BULK_CONTINUATION 0x02#define USBDEVFS_CAP_NO_PACKET_SIZE_LIM 0x04#define USBDEVFS_CAP_BULK_SCATTER_GATHER 0x08 +#define USBDEVFS_CAP_REAP_AFTER_DISCONNECT 0x10/* USBDEVFS_DISCONNECT_CLAIM flags & struct */
Signature · 1 line
2.5.0
PATCH 110/123 watchdog: omap: assert the counter being stopped before reprogramming
In reply to Jiri SlabyFrom: Uwe Kleine-König <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 530c11d432727c697629ad5f9d00ee8e2864d453 upstream.
The omap watchdog has the annoying behaviour that writes to most registers don't have any effect when the watchdog is already running. Quoting the AM335x reference manual:
To modify the timer counter value (the WDT_WCRR register), prescaler ratio (the WDT_WCLR[4:2] PTV bit field), delay configuration value (the WDT_WDLY[31:0] DLY_VALUE bit field), or the load value (the WDT_WLDR[31:0] TIMER_LOAD bit field), the watchdog timer must be disabled by using the start/stop sequence (the WDT_WSPR register).
Currently the timer is stopped in the .probe callback but still there are possibilities that yield to a situation where omap_wdt_start is entered with the timer running (e.g. when /dev/watchdog is closed without stopping and then reopened). In such a case programming the timeout silently fails!
To circumvent this stop the timer before reprogramming.
Assuming one of the first things the watchdog user does is setting the timeout explicitly nothing too bad should happen because this explicit setting works fine.
--- drivers/watchdog/omap_wdt.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/watchdog/omap_wdt.c +7 -0
@@ -134,6 +134,13 @@ static int omap_wdt_start(struct watchdog_device *wdog)pm_runtime_get_sync (wdev->dev); +/* +* Make sure the watchdog is disabled. This is unfortunately required +* because writing to various registers with the watchdog running has no +* effect. +*/ +omap_wdt_disable (wdev); +/* initialize prescaler */ while (__raw_readl (base +OMAP_WATCHDOG_WPS ) &0x01 )cpu_relax ();
Signature · 1 line
2.5.0
PATCH 111/123 NFS: Fix size of NFSACL SETACL operations
In reply to Jiri SlabyFrom: Chuck Lever <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit d683cc49daf7c5afca8cd9654aaa1bf63cdf2ad9 upstream.
When encoding the NFSACL SETACL operation, reserve just the estimated size of the ACL rather than a fixed maximum. This eliminates needless zero padding on the wire that the server ignores.
--- fs/nfs/nfs3xdr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/nfs/nfs3xdr.c +1 -1
@@ -1342,7 +1342,7 @@ static void nfs3_xdr_enc_setacl3args(struct rpc_rqst *req,if (args->npages !=0 )xdr_write_pages (xdr, args->pages,0 , args->len);else -xdr_reserve_space (xdr,NFS_ACL_INLINE_BUFSIZE ); +xdr_reserve_space (xdr, args->len); error = nfsacl_encode(xdr->buf, base, args->inode, (args->mask & NFS_ACL) ?
Signature · 1 line
2.5.0
PATCH 112/123 fixing infinite OPEN loop in 4.0 stateid recovery
In reply to Jiri SlabyFrom: Olga Kornievskaia <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit e8d975e73e5fa05f983fbf2723120edcf68e0b38 upstream.
Problem: When an operation like WRITE receives a BAD_STATEID, even though recovery code clears the RECLAIM_NOGRACE recovery flag before recovering the open state, because of clearing delegation state for the associated inode, nfs_inode_find_state_and_recover() gets called and it makes the same state with RECLAIM_NOGRACE flag again. As a results, when we restart looking over the open states, we end up in the infinite loop instead of breaking out in the next test of state flags.
Solution: unset the RECLAIM_NOGRACE set because of
calling of nfs_inode_find_state_and_recover() after returning from calling recover_open() function.
--- fs/nfs/nfs4state.c | 2 ++ 1 file changed, 2 insertions(+)
fs/nfs/nfs4state.c +2 -0
@@ -1436,6 +1436,8 @@ restart:spin_unlock (&state->state_lock); }nfs4_put_open_state (state); +clear_bit (NFS4CLNT_RECLAIM_NOGRACE , + &state->flags);spin_lock (&sp->so_lock); goto restart; }
Signature · 1 line
2.5.0
PATCH 113/123 nfs: increase size of EXCHANGE_ID name string buffer
In reply to Jiri SlabyFrom: Jeff Layton <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 764ad8ba8cd4c6f836fca9378f8c5121aece0842 upstream.
The current buffer is much too small if you have a relatively long hostname. Bring it up to the size of the one that SETCLIENTID has.
--- include/linux/nfs_xdr.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/nfs_xdr.h +1 -1
@@ -1131,7 +1131,7 @@ struct nfs41_state_protection {struct nfs4_op_map allow; }; -#define NFS4_EXCHANGE_ID_LEN (48) +#define NFS4_EXCHANGE_ID_LEN (127)struct nfs41_exchange_id_args {struct nfs_client *client;nfs4_verifier *verifier;
Signature · 1 line
2.5.0
PATCH 114/123 SUNRPC: Fix a memory leak in the backchannel code
In reply to Jiri SlabyFrom: Trond Myklebust <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 88de6af24f2b48b06c514d3c3d0a8f22fafe30bd upstream.
req->rq_private_buf isn't initialised when xprt_setup_backchannel calls xprt_free_allocation.
--- net/sunrpc/backchannel_rqst.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/sunrpc/backchannel_rqst.c +1 -1
@@ -60,7 +60,7 @@ static void xprt_free_allocation(struct rpc_rqst *req)dprintk ("RPC: free allocations for req= %p\n" , req);WARN_ON_ONCE (test_bit (RPC_BC_PA_IN_USE , &req->rq_bc_pa_state)); - xbufp = &req->rq_private_buf; + xbufp = &req->rq_rcv_buf;free_page ((unsigned long )xbufp->head[0 ].iov_base); xbufp = &req->rq_snd_buf;free_page ((unsigned long )xbufp->head[0 ].iov_base);
Signature · 1 line
2.5.0
PATCH 115/123 9p: forgetting to cancel request on interrupted zero-copy RPC
In reply to Jiri SlabyFrom: Al Viro <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit a84b69cb6e0a41e86bc593904faa6def3b957343 upstream.
If we'd already sent a request and decide to abort it, we *must* issue TFLUSH properly and not just blindly reuse the tag, or we'll get seriously screwed when response eventually arrives and we confuse it for response to later request that had reused the same tag.
--- net/9p/client.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/9p/client.c +2 -1
@@ -839,7 +839,8 @@ static struct p9_req_t *p9_client_zc_rpc(struct p9_client *c, int8_t type,if (err <0 ) {if (err == -EIO ) c->status = Disconnected; - goto reterr; +if (err != -ERESTARTSYS ) + goto reterr; }if (req->status ==REQ_STATUS_ERROR ) {p9_debug (P9_DEBUG_ERROR ,"req_status error %d\n" , req->t_err);
Signature · 1 line
2.5.0
PATCH 116/123 9p: don't leave a half-initialized inode sitting around
In reply to Jiri SlabyFrom: Al Viro <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 0a73d0a204a4a04a1e110539c5a524ae51f91d6d upstream.
--- fs/9p/vfs_inode.c | 3 +-- fs/9p/vfs_inode_dotl.c | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-)
fs/9p/vfs_inode.c +1 -2
@@ -537,8 +537,7 @@ static struct inode *v9fs_qid_iget(struct super_block *sb,unlock_new_inode (inode);return inode; error: -unlock_new_inode (inode); -iput (inode); +iget_failed (inode);return ERR_PTR (retval); }
fs/9p/vfs_inode_dotl.c +1 -2
@@ -151,8 +151,7 @@ static struct inode *v9fs_qid_iget_dotl(struct super_block *sb,unlock_new_inode (inode);return inode; error: -unlock_new_inode (inode); -iput (inode); +iget_failed (inode);return ERR_PTR (retval); }
Signature · 1 line
2.5.0
PATCH 117/123 rbd: use GFP_NOIO in rbd_obj_request_create()
In reply to Jiri SlabyFrom: Ilya Dryomov <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 5a60e87603c4c533492c515b7f62578189b03c9c upstream.
rbd_obj_request_create() is called on the main I/O path, so we need to use GFP_NOIO to make sure allocation doesn't blow back on us. Not all callers need this, but I'm still hardcoding the flag inside rather than making it a parameter because a) this is going to stable, and b) those callers shouldn't really use rbd_obj_request_create() and will be fixed in the future.
More memory allocation fixes will follow.
--- drivers/block/rbd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/block/rbd.c +2 -2
@@ -1845,11 +1845,11 @@ static struct rbd_obj_request *rbd_obj_request_create(const char *object_name,rbd_assert (obj_request_type_valid (type)); size =strlen (object_name) +1 ; - name =kmalloc (size,GFP_KERNEL ); + name =kmalloc (size,GFP_NOIO );if (!name)return NULL ; - obj_request =kmem_cache_zalloc (rbd_obj_request_cache,GFP_KERNEL ); + obj_request =kmem_cache_zalloc (rbd_obj_request_cache,GFP_NOIO );if (!obj_request) {kfree (name);return NULL ;
Signature · 1 line
2.5.0
PATCH 118/123 agp/intel: Fix typo in needs_ilk_vtd_wa()
In reply to Jiri SlabyFrom: Chris Wilson <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 8b572a4200828b4e75cc22ed2f494b58d5372d65 upstream.
In needs_ilk_vtd_wa(), we pass in the GPU device but compared it against the ids for the mobile GPU and the mobile host bridge. That latter is impossible and so likely was just a typo for the desktop GPU device id (which is also buggy).
Fixes commit da88a5f7f7d434e2cde1b3e19d952e6d84533662
Author: Chris Wilson <[email protected]> Date: Wed Feb 13 09:31:53 2013 +0000
drm/i915: Disable WC PTE updates to w/a buggy IOMMU on ILK
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91127
References: https://bugzilla.freedesktop.org/show_bug.cgi?id=60391
--- drivers/char/agp/intel-gtt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/char/agp/intel-gtt.c +1 -1
@@ -583,7 +583,7 @@ static inline int needs_ilk_vtd_wa(void)/* Query intel_iommu to see if we need the workaround. Presumably that * was loaded first. */ -if ((gpu_devid ==PCI_DEVICE_ID_INTEL_IRONLAKE_M_HB || +if ((gpu_devid ==PCI_DEVICE_ID_INTEL_IRONLAKE_D_IG || gpu_devid ==PCI_DEVICE_ID_INTEL_IRONLAKE_M_IG ) && intel_iommu_gfx_mapped)return 1 ;
Signature · 1 line
2.5.0
PATCH 119/123 arm64: Don't report clear pmds and puds as huge
In reply to Jiri SlabyFrom: Christoffer Dall <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit fd28f5d439fca77348c129d5b73043a56f8a0296 upstream.
The current pmd_huge() and pud_huge() functions simply check if the table bit is not set and reports the entries as huge in that case. This is counter-intuitive as a clear pmd/pud cannot also be a huge pmd/pud, and it is inconsistent with at least arm and x86.
To prevent others from making the same mistake as me in looking at code that calls these functions and to fix an issue with KVM on arm64 that causes memory corruption due to incorrect page reference counting resulting from this mistake, let's change the behavior.
--- arch/arm64/mm/hugetlbpage.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm64/mm/hugetlbpage.c +2 -2
@@ -40,13 +40,13 @@ int huge_pmd_unshare(struct mm_struct *mm, unsigned long *addr, pte_t *ptep)int pmd_huge (pmd_t pmd) { -return !(pmd_val (pmd) &PMD_TABLE_BIT ); +return pmd_val (pmd) && !(pmd_val (pmd) &PMD_TABLE_BIT ); }int pud_huge (pud_t pud) {#ifndef __PAGETABLE_PMD_FOLDED -return !(pud_val (pud) &PUD_TABLE_BIT ); +return pud_val (pud) && !(pud_val (pud) &PUD_TABLE_BIT );#else return 0 ;#endif
Signature · 1 line
2.5.0
PATCH 120/123 hpfs: hpfs_error: Remove static buffer, use vsprintf extension %pV instead
In reply to Jiri SlabyFrom: Joe Perches <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit a28e4b2b18ccb90df402da3f21e1a83c9d4f8ec1 upstream.
Removing unnecessary static buffers is good.
Use the vsprintf %pV extension instead.
--- fs/hpfs/super.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
fs/hpfs/super.c +7 -4
@@ -52,17 +52,20 @@ static void unmark_dirty(struct super_block *s) }/* Filesystem error... */ -static char err_buf[1024 ]; -void hpfs_error (struct super_block *s,const char *fmt, ...) { +struct va_format vaf;va_list args;va_start (args, fmt); -vsnprintf (err_buf,sizeof (err_buf), fmt, args); + + vaf.fmt = fmt; + vaf.va = &args; + +pr_err ("filesystem error: %pV" , &vaf); +va_end (args); -printk ("HPFS: filesystem error: %s" , err_buf);if (!hpfs_sb (s)->sb_was_error) {if (hpfs_sb (s)->sb_err ==2 ) {printk ("; crashing the system because you wanted it\n" );
Signature · 1 line
2.5.0
PATCH 121/123 Fix firmware loader uevent buffer NULL pointer dereference
In reply to Jiri SlabyFrom: Linus Torvalds <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 6f957724b94cb19f5c1c97efd01dd4df8ced323c upstream.
The firmware class uevent function accessed the "fw_priv->buf" buffer without the proper locking and testing for NULL. This is an old bug (looks like it goes back to 2012 and commit 1244691c73b2: "firmware
loader: introduce firmware_buf"), but for some reason it's triggering only now in 4.2-rc1.
Shuah Khan is trying to bisect what it is that causes this to trigger more easily, but in the meantime let's just fix the bug since others are hitting it too (at least Ingo reports having seen it as well).
--- drivers/base/firmware_class.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
drivers/base/firmware_class.c +13 -3
@@ -527,10 +527,8 @@ static void fw_dev_release(struct device *dev)kfree (fw_priv); } -static int firmware_uevent (struct device *dev,struct kobj_uevent_env *env) +static int do_firmware_uevent (struct firmware_priv *fw_priv,struct kobj_uevent_env *env) { -struct firmware_priv *fw_priv =to_firmware_priv (dev); -if (add_uevent_var (env,"FIRMWARE=%s" , fw_priv->buf->fw_id))return -ENOMEM ;if (add_uevent_var (env,"TIMEOUT=%i" , loading_timeout))
@@ -541,6 +539,18 @@ static int firmware_uevent(struct device *dev, struct kobj_uevent_env *env)return 0 ; } +static int firmware_uevent (struct device *dev,struct kobj_uevent_env *env) +{ +struct firmware_priv *fw_priv =to_firmware_priv (dev); +int err =0 ; + +mutex_lock (&fw_lock); +if (fw_priv->buf) + err =do_firmware_uevent (fw_priv, env); +mutex_unlock (&fw_lock); +return err; +} +static struct class firmware_class = { .name ="firmware" , .class_attrs = firmware_class_attrs,
Signature · 1 line
2.5.0
PATCH 122/123 qla2xxx: Mark port lost when we receive an RSCN for it.
In reply to Jiri SlabyFrom: Chad Dupuis <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit ef86cb2059a14b4024c7320999ee58e938873032 upstream.
--- drivers/scsi/qla2xxx/qla_isr.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
drivers/scsi/qla2xxx/qla_isr.c +16 -1
@@ -536,8 +536,9 @@ qla2x00_async_event(scsi_qla_host_t *vha, struct rsp_que *rsp, uint16_t *mb)struct device_reg_2xxx __iomem *reg = &ha->iobase->isp;struct device_reg_24xx __iomem *reg24 = &ha->iobase->isp24;struct device_reg_82xx __iomem *reg82 = &ha->iobase->isp82; -uint32_t rscn_entry, host_pid; +uint32_t rscn_entry, host_pid, tmp_pid;unsigned long flags; +fc_port_t *fcport =NULL ;/* Setup to process RIO completion. */ handle_cnt =0 ;
@@ -932,6 +933,20 @@ skip_rio:if (qla2x00_is_a_vp_did (vha, rscn_entry))break ; +/* +* Search for the rport related to this RSCN entry and mark it +* as lost. +*/ +list_for_each_entry (fcport, &vha->vp_fcports, list) { +if (atomic_read (&fcport->state) !=FCS_ONLINE ) +continue ; + tmp_pid = fcport->d_id.b24; +if (fcport->d_id.b24 == rscn_entry) { +qla2x00_mark_device_lost (vha, fcport,0 ,0 ); +break ; + } + } +atomic_set (&vha->loop_down_timer,0 ); vha->flags.management_server_logged_in =0 ;
Signature · 1 line
2.5.0
PATCH 123/123 sg_start_req(): make sure that there's not too many elements in iovec
In reply to Jiri SlabyFrom: Al Viro <[email protected]>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 451a2886b6bf90e2fb378f7c46c655450fb96e81 upstream.
unfortunately, allowing an arbitrary 16bit value means a possibility of overflow in the calculation of total number of pages in bio_map_user_iov() - we rely on there being no more than PAGE_SIZE members of sum in the first loop there. If that sum wraps around, we end up allocating too small array of pointers to pages and it's easy to overflow it in the second loop.
[bwh: s/MAX_UIOVEC/UIO_MAXIOV/. This was fixed upstream by commit
fdc81f45e9f5 ("sg_start_req(): use import_iovec()"), but we don't have that function.]
--- drivers/scsi/sg.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/scsi/sg.c +3 -0
@@ -1694,6 +1694,9 @@ static int sg_start_req(Sg_request *srp, unsigned char *cmd) md->from_user =0 ; } +if (unlikely (iov_count >UIO_MAXIOV )) +return -EINVAL ; +if (iov_count) {int len, size =sizeof (struct sg_iovec ) * iov_count;struct iovec *iov;
Signature · 1 line
2.5.0
Quoted 8 lines · Jiri Slaby
This is the start of the stable review cycle for the 3.12.46 release. There are 123 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu Aug 6 16:39:14 CEST 2015. Anything received after that time might be too late.
Build results:
total: 129 pass: 129 fail: 0 Qemu test results: total: 42 pass: 42 fail: 0
Details are available at http://server.roeck-us.net:8010/builders.
Guenter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Quoted 13 lines · Guenter Roeck
Quoted 8 lines · Jiri Slaby
This is the start of the stable review cycle for the 3.12.46 release. There are 123 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu Aug 6 16:39:14 CEST 2015. Anything received after that time might be too late.
Build results: total: 129 pass: 129 fail: 0 Qemu test results:
total: 42 pass: 42 fail: 0Details are available at http://server.roeck-us.net:8010/builders.
Quoted 1 line · Shuah Khan
Compiled and booted on my test system. No demsg regressions.
Thank you both!
- --
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVwbtbAAoJEL0lsQQGtHBJUG8P/0NZqzt5UT9nKpk0jUCrkrq7 KKz2qZEXjEUWak9xD/bdadAkKEREp5Gui3tVM69LenPLjHx1YUJSP8Ieyb2laHC+ SCYhFdte/uEAXHio+XDfT0GCOlVSVICeeM/CKaj3sROog/NWpqzuDBiB6qQ4ZFg3 mNA4bihE7uV7Nudc8i4VtL9kKtDdIeU5R/EvQkHGKT6c0fsnyNl4vHyLqrq0QteP KzpQOL4qCChmiJYPfOC8oNH4Ya+OG2f7SInuUVEqp7oFJFnFLHlzobwAyfxmXK+y 0U4hcrUaOGXa6bWxV7nG/FKYl8imHlY4SqLj6RVnDg7LJDT6CzoT5cG7NJbykT6L LVROq0jDfRFQOf+6SqtPM3aqK99sNH2BNi1fCbgqYnQOkuxzZNiMZphEkqoLLLk3 Vi/+UdM719v1Fa0iysssAonlb0DszpHUWnHT2NpUZfjzEUS685E4fG83ue/zuqgo stidahoCAIZEl1XLfj0zSq3sMW7OC+iGeNjRa9IcEmluyzMInhFhLkNPyQ8ZAB3p cH0eZBEwuBANZBm+Kp6S3+eb3HbUnPZGz602MAcSz0ydWlzstw/dxibNQJOBYXYA yj5dS7NqayZywvC1KiD1OR3iX8arvjVFLem51KSmAVfgfzzqZVWmbY7J64J/jPLh +PdxGW2iLws1epJoFwgm
=rWLG
-----END PGP SIGNATURE-----
Quoted 8 lines · Jiri Slaby
This is the start of the stable review cycle for the 3.12.46 release. There are 123 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu Aug 6 16:39:14 CEST 2015. Anything received after that time might be too late.
Quoted 7 lines
The whole patch series can be found in one patch at:
http://kernel.org/pub/linux/kernel/people/jirislaby/stable-review/patch-3.12.46-rc1.xzand the diffstat can be found below.
thanks,
js
Compiled and booted on my test system. No demsg regressions.
thanks,
-- Shuah
Signature · 5 lines
Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America (Silicon Valley) [email protected] | (970) 217-8978