[PATCH 4.9 203/206] xfs: fix crash and data corruption due to removal of busy COW extents

4.9-stable review patch. If anyone has any objections, please let me know. -- commit a1b7a4dea6166cf46be895bce4aac67ea5160fe8 upstream. There is a race window between write_cache_pages calling clear_page_dirty_for_io and XFS calling set_page_writeback, in which the mapping for

[PATCH 4.9 201/206] xfs: fix double-cleanup when CUI recovery fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Darrick J. Wong" commit 7a21272b088894070391a94fdd1c67014020fa1d upstream. Dan Carpenter reported a double-free of rcur if _defer_finish fails while we're recovering CUI items. Fix the error

[PATCH 4.9 175/206] xfs: dont skip cow forks w/ delalloc blocks in cowblocks scan

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 399372349a7f9b2d7e56e4fa4467c69822d07024 upstream. The cowblocks background scanner currently clears the cowblocks tag for inodes without any real allocations in the cow fo

Re: [PATCH v2] arm64: do not set dma masks that device connection can't handle

>> What issue "IOMMU doesn't solve"? >> >> Issue I'm trying to address is - inconsistency within swiotlb >> dma_map_ops, where (1) any wide mask is silently accepted, but (2) then >> mask is used to decide if bounce buffers are needed or not. This >> inconsistency causes NVMe+R-Car cobmo not workin

[PATCH 4.9 121/206] iommu/vt-d: Fix pasid table size encoding

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Pan commit 65ca7f5f7d1cdde6c25172fe6107cd16902f826f upstream. Different encodings are used to represent supported PASID bits and number of PASID table entries. The current code assigns ec

[PATCH 4.9 167/206] s390/pci: fix dma address calculation in map_sg

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 6b7df3ce92ac82ec3f4a2953b6fed77da7b38aaa upstream. __s390_dma_map_sg maps a dma-contiguous area. Although we only map whole pages we have to take into account that the area

[PATCH 4.9 166/206] s390/topology: always use s390 specific sched_domain_topology_level

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit ebb299a51059017ec253bd30781a83d1f6e11b24 upstream. The s390 specific sched_domain_topology_level should always be used, not only if the machine provides topology informati

Re: [PATCH 2/5] drivers: mmc: sunxi: limit A64 MMC2 to 8K DMA buffer

On Thu, Jan 05, 2017 at 11:33:28PM +, André Przywara wrote: > On 05/01/17 17:57, Maxime Ripard wrote: > > Hi Rob, > > > > On Wed, Jan 04, 2017 at 08:07:50AM -0600, Rob Herring wrote: > >> On Mon, Jan 02, 2017 at 11:03:43PM +, Andre Przywara wrote: > >>> From: Maxime Ripard > >>> > >>> Unl

[PATCH 4.9 155/206] f2fs: remove percpu_count due to performance regression

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 35782b233f37e48ecc469d9c7232f3f6a7fad41a upstream. This patch removes percpu_count usage due to performance regression in iozone. Fixes: 523be8a6b3 ("f2fs: use percpu_counte

[PATCH 4.9 119/206] iommu/amd: Missing error code in amd_iommu_init_device()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 24c790fbf5d8f54c8c82979db11edea8855b74bf upstream. We should set "ret" to -EINVAL if iommu_group_get() fails. Fixes: 55c99a4dc50f ("iommu/amd: Use iommu_attach_group()") S

[PATCH 4.9 112/206] clk: qcom: ipq806x: Fix board clk rates

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit cbf2e548ca8ad4bb274d014e9a70bd841d29948e upstream. The clocks on these boards run at 25 MHz, not 19.2 and 27 like other platforms. Unfortunately I copy/pasted from other sim

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

Hi Tony, On Tue, Dec 27, 2016 at 6:19 PM, Tony Lindgren wrote: > Having the pin control framework call pin controller functions > before it's probe has finished is not nice as the pin controller > device driver does not yet have struct pinctrl_dev handle. > > Let's fix this issue by adding deferr

Re: [PATCH] tools: gpio add .gitignore for generated files

On 01/10/2017 02:29 AM, Linus Walleij wrote: > On Thu, Jan 5, 2017 at 10:32 PM, Shuah Khan wrote: > >> Add .gitignore for generated files. >> >> Signed-off-by: Shuah Khan >> --- >> tools/gpio/.gitignore | 4 >> 1 file changed, 4 insertions(+) >> create mode 100644 tools/gpio/.gitignore >>

Re: [PATCH v7 00/19] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

On Mon, Jan 09, 2017 at 01:45:51PM +, Eric Auger wrote: > Eric Auger (17): > iommu: Rename iommu_dm_regions into iommu_resv_regions > iommu: Add a new type field in iommu_resv_region > iommu: iommu_alloc_resv_region > iommu: Only map direct mapped regions > iommu: iommu_get_group_resv

Re: [PATCH v7 11/19] iommu/arm-smmu: Implement reserved region get/put callbacks

On Mon, Jan 09, 2017 at 01:46:02PM +, Eric Auger wrote: > The get() populates the list with the MSI IOVA reserved window. > > At the moment an arbitray MSI IOVA window is set at 0x800 > of size 1MB. This will allow to report those info in iommu-group > sysfs. > > Signed-off-by: Eric Auger

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

On 01/10/2017 05:05 AM, Bartlomiej Zolnierkiewicz wrote: > > Hi, > > On Monday, January 09, 2017 07:21:31 PM Shuah Khan wrote: >> Fix dwc3_exynos_probe() to call clk_prepare_enable() only when suspend >> clock is specified. Call clk_disable_unprepare() from remove and probe >> error path only whe

Re: [PATCH v7 19/19] iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP anymore

On Mon, Jan 09, 2017 at 01:46:10PM +, Eric Auger wrote: > IOMMU_CAP_INTR_REMAP has been advertised in arm-smmu(-v3) although > on ARM this property is not attached to the IOMMU but rather is > implemented in the MSI controller (GICv3 ITS). > > Now vfio_iommu_type1 checks MSI remapping capabili

Re: [PATCH perf/core 1/4] perf-probe: Fix to show correct locations for events on modules

On Tue, 10 Jan 2017 10:18:35 -0300 Arnaldo Carvalho de Melo wrote: > Em Sat, Jan 07, 2017 at 02:25:09PM +0900, Masami Hiramatsu escreveu: > > Fix to show correct locations for events on modules by > > relocating given address. Currently the relocation is > > done when we failed to find the addres

Re: [RFC 2/6] perf/core: add a rb-tree index to inactive_groups

On Tue, Jan 10, 2017 at 02:24:58AM -0800, David Carrillo-Cisneros wrote: > Add a rb-tree that indexes inactive events by {CPU/cgroup,flexible,stamp}. > > The original idea by Peter Z. was to sort task events in an rb-tree using > {pmu,cpu,timestamp} as key. > > Having the PMU as part of the key g

Re: [PATCH v2] arm64: do not set dma masks that device connection can't handle

On 10/01/17 13:42, Arnd Bergmann wrote: > On Tuesday, January 10, 2017 1:25:12 PM CET Robin Murphy wrote: >> On 10/01/17 12:47, Nikita Yushchenko wrote: The point here is that an IOMMU doesn't solve your issue, and the IOMMU-backed DMA ops need the same treatment. In light of that, it rea

Re: [PATCH v7 12/19] iommu/arm-smmu-v3: Implement reserved region get/put callbacks

On Mon, Jan 09, 2017 at 01:46:03PM +, Eric Auger wrote: > iommu/arm-smmu: Implement reserved region get/put callbacks > > The get() populates the list with the MSI IOVA reserved window. > > At the moment an arbitray MSI IOVA window is set at 0x800 > of size 1MB. This will allow to report

Re: [PATCH v7 00/19] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

On Tue, Jan 10, 2017 at 03:09:24PM +0100, Joerg Roedel wrote: > On Mon, Jan 09, 2017 at 01:45:51PM +, Eric Auger wrote: > > Eric Auger (17): > > iommu: Rename iommu_dm_regions into iommu_resv_regions > > iommu: Add a new type field in iommu_resv_region > > iommu: iommu_alloc_resv_region >

Re: Dell XPS13 does not suspend with Linux 4.10-rc3

Lo! Paul Menzel wrote on 10.01.2017 15:08: > > Testing Linux 4.10-rc{1,2,3} the Dell XPS13 does not suspend with the > attached configuration. During quick tests I saw similar problems with the Fedora rawhide configuration in 4.10-rc{1,2} (haven't tried rc3/mainline yet). My free time was extremel

Re: [PATCH v4 7/9] arm64: cpufeature: Track user visible fields

On Mon, Jan 09, 2017 at 05:28:30PM +, Suzuki K. Poulose wrote: > Changes since V3: > - Mark ID_AA64ISAR0_EL1:RDM visible [...] > static const struct arm64_ftr_bits ftr_id_aa64isar0[] = { > - ARM64_FTR_BITS(FTR_STRICT, FTR_EXACT, ID_AA64ISAR0_RDM_SHIFT, 4, 0), > - ARM64_FTR_BITS(FTR_ST

Re: [PATCH v4 7/9] arm64: cpufeature: Track user visible fields

On 10/01/17 14:24, Catalin Marinas wrote: On Mon, Jan 09, 2017 at 05:28:30PM +, Suzuki K. Poulose wrote: Changes since V3: - Mark ID_AA64ISAR0_EL1:RDM visible [...] static const struct arm64_ftr_bits ftr_id_aa64isar0[] = { - ARM64_FTR_BITS(FTR_STRICT, FTR_EXACT, ID_AA64ISAR0_RDM_SH

[PATCH 4.9 153/206] md: MD_RECOVERY_NEEDED is set for mddev->recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 82a301cb0ea2df8a5c88213094a01660067c7fb4 upstream. Fixes: 90f5f7ad4f38("md: Wait for md_check_recovery before attempting device removal.") Reviewed-by: NeilBrown Signed-off-

[PATCH 4.9 116/206] clk: sunxi-ng: sun8i-h3: Set CLK_SET_RATE_PARENT for audio module clocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 0f6f9302b819ca352cfd4f42c18ec08d521f9cae upstream. The audio module clocks are supposed to be set according to the sample rate of the audio stream. The audio PLL provides th

Re: [RFC 1/6] perf/core: create active and inactive event groups

Hi, On Tue, Jan 10, 2017 at 02:24:57AM -0800, David Carrillo-Cisneros wrote: > Currently, perf uses pinned_groups and flexible_groups for sched in/out. > We can do better because: > - sched out only cares about the ACTIVE events, this is usually a small > set of events. > - There can be many

[PATCH 4.9 150/206] crypto: arm64/sha1-ce - fix for big endian

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit ee71e5f1e7d25543ee63a80451871f8985b8d431 upstream. The SHA1 digest is an array of 5 32-bit quantities, so we should refer to them as such in order for this code to work co

[PATCH 4.9 144/206] s390/crypto: unlock on error in prng_tdes_read()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 9e6e7c74315095fd40f41003850690c711e44420 upstream. We added some new locking but forgot to unlock on error. Fixes: 57127645d79d ("s390/zcrypt: Introduce new SHA-512 based

[PATCH 4.9 115/206] clk: sunxi-ng: sun8i-a23: Set CLK_SET_RATE_PARENT for audio module clocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chen-Yu Tsai commit 937ff9ded8b6ebe8963ade55bdd77a61ded88075 upstream. The audio module clocks are supposed to be set according to the sample rate of the audio stream. The audio PLL provides th

[PATCH 4.9 147/206] crypto: arm/aes-ce - fix for big endian

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 58010fa6f71c9577922b22e46014b95a4ec80fa0 upstream. The AES key schedule generation is mostly endian agnostic, with the exception of the rotation and the incorporation of t

[PATCH 4.9 143/206] mm, compaction: fix NR_ISOLATED_* stats for pfn based migration

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ming Ling commit 6afcf8ef0ca0a69d014f8edb613d94821f0ae700 upstream. Since commit bda807d44454 ("mm: migrate: support non-lru movable page migration") isolate_migratepages_block) can isolate !Pa

[PATCH 4.9 140/206] docs-rst: fix LaTeX \DURole renewcommand with Sphinx 1.3+

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit e2a91f4f42018994d7424d405900d17eba6555d0 upstream. PDF build on Kernel 4.9-rc? returns an error with Sphinx 1.3.x and Sphinx 1.4.x, when trying to solve some cross-

[PATCH 4.9 145/206] crypto: arm64/sha2-ce - fix for big endian

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 174122c39c369ed924d2608fc0be0171997ce800 upstream. The SHA256 digest is an array of 8 32-bit quantities, so we should refer to them as such in order for this code to work

[PATCH 4.9 142/206] mm: khugepaged: fix radix tree node leak in shmem collapse error path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Weiner commit 59749e6ce53735d8b696763742225f126e94603f upstream. The radix tree counts valid entries in each tree node. Entries stored in the tree cannot be removed by simpling storin

[PATCH 4.9 133/206] PCI/MSI: Check for NULL affinity mask in pci_irq_get_affinity()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit d1d111e073840b8dbc1ae90ba3fc274736451bdc upstream. If msi_setup_entry() fails to allocate an affinity mask, it logs a message but continues on and allocates an MSI entry with

[PATCH 4.9 134/206] irqchip/bcm7038-l1: Implement irq_cpu_offline() callback

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit 34c535793bcbf9263cf22f8a52101f796cdfab8e upstream. We did not implement an irq_cpu_offline callback for our irqchip, yet we support setting a given IRQ's affinity. This

[PATCH 4.9 129/206] target/iscsi: Fix double free in lio_target_tiqn_addtpg()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit a91918cd3ea11f91c68e08e1e8ce1b560447a80e upstream. This iscsit_tpg_add_portal_group() function is only called from lio_target_tiqn_addtpg(). Both functions free the "tpg"

[PATCH 4.9 138/206] rpmsg: qcom_smd: Correct return value for O_NONBLOCK

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson commit 1d74e7ed5dc1903ac081574a9b6aa94e7ba4ad45 upstream. qcom_smd_send() should return -EAGAIN for non-blocking channels with insufficient space, so that we can propagate this

[PATCH 4.9 136/206] genirq/affinity: Fix node generation from cpumask

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guilherme G. Piccoli commit c0af52437254fda8b0cdbaae5a9b6d9327f1fcd5 upstream. Commit 34c3d9819fda ("genirq/affinity: Provide smarter irq spreading infrastructure") introduced a better IRQ spre

[PATCH 4.9 114/206] clk: ti: dra7: fix "failed to lookup clock node gmac_gmii_ref_clk_div" boot message

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Grygorii Strashko commit f8d17344a60921c2387759fc0a85aa64299d1ec6 upstream. Prevent creating clk alias for non existing gmac_gmii_ref_clk_div clock and, this way, eliminate excessive error mess

Re: [PATCH v2 0/4] hv_util: adjust system time smoothly

Thomas Gleixner writes: > On Wed, 4 Jan 2017, Vitaly Kuznetsov wrote: > >> Changes since v1: >> - do do_settimeofday64() when ICTIMESYNCFLAG_SYNC flag is present in the >> request (Alex Ng) >> - add pr_debug() for the case when do_adjtimex() fails (Alex Ng) >> >> Original description: >> >> W

[PATCH 4.9 126/206] ASoC: samsung: i2s: Fixup last IRQ unsafe spin lock call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Charles Keepax commit 5faf071d08ddd1c1be66deaa93a09ccf43f5b538 upstream. Unfortunately, I seem to have missed a case where an IRQ safe spinlock was required, in samsung_i2s_dai_remove, when I f

[PATCH 4.9 125/206] ASoC: Intel: Skylake: Fix a shift wrapping bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit c8eabf821cac120afb78ca251b07cbf520406a7e upstream. "*val" is a u64. It definitely looks like we intend to use the high 32 bits as well. Fixes: 700a9a63f9c1 ("ASoC: Intel:

[PATCH 4.9 128/206] scsi: mvsas: fix command_active typo

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit af15769ffab13d777e55fdef09d0762bf0c249c4 upstream. gcc-7 notices that the condition in mvs_94xx_command_active looks suspicious: drivers/scsi/mvsas/mv_94xx.c: In function

[PATCH v2 3/6] pinctrl: Add a possibility to configure pins from a gpiolib based drivers

When a GPIO driver is backed by a pinctrl driver the GPIO driver often needs to call the pinctrl driver to configure certain things, like whether the pin is used as input or output. In addition to this there are other pin configurations applicable to GPIOs such as debounce timeout. To support this

[PATCH v2 4/6] pinctrl: intel: Add support for hardware debouncer

The next generation Intel GPIO hardware has two additional registers PADCFG2 and PADCFG3. The latter is marked as reserved but the former includes configuration for per-pad hardware debouncer. This patch adds support for that in the Intel pinctrl core driver. Since these are additional features on

[PATCH v2 2/6] pinctrl: intel: Convert to use devm_gpiochip_add_data()

This simplifies error handling and allows us to drop intel_pinctrl_remove() completely. Signed-off-by: Mika Westerberg Reviewed-by: Andy Shevchenko --- drivers/pinctrl/intel/pinctrl-broxton.c | 1 - drivers/pinctrl/intel/pinctrl-intel.c| 23 --- drivers/pinctrl

[PATCH v2 5/6] pinctrl: intel: Add support for 1k additional pull-down

The next generation Intel GPIO hardware supports additional 1k pull-down per-pad. Add support for this to the Intel core pinctrl driver. Signed-off-by: Mika Westerberg Reviewed-by: Andy Shevchenko --- drivers/pinctrl/intel/pinctrl-intel.c | 18 +- drivers/pinctrl/intel/pinctrl-i

[PATCH v2 1/6] pinctrl: broxton: Use correct PADCFGLOCK offset

PADCFGLOCK (and PADCFGLOCK_TX) offset in Broxton actually starts at 0x060 and not 0x090 as used in the driver. Fix it to use the correct offset. Signed-off-by: Mika Westerberg Reviewed-by: Andy Shevchenko --- drivers/pinctrl/intel/pinctrl-broxton.c | 2 +- 1 file changed, 1 insertion(+), 1 dele

[PATCH v2 6/6] pinctrl: intel: Add Intel Gemini Lake pin controller support

This driver adds pinctrl/GPIO support for Intel Gemini Lake SoC. The GPIO controller is based on the next generation GPIO hardware but still compatible with the one supported by the Intel core pinctrl/GPIO driver. This commit includes material from David E. Box. Signed-off-by: Mika Westerberg Re

[PATCH v2 0/6] pinctrl: Fixes and updates to Intel drivers

This series fixes one issue found on Broxton, updates the core driver to use devm_gpiochip_add_data() and finally add support for the next generation Intel GPIO hardware available starting from Intel Gemini Lake SoC. The Gemini Lake SoC brings hardware debouncer per-pad and 1k additional pull-down

[PATCH 4.9 111/206] Input: synaptics-rmi4 - unlock on error

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 792f497b22afd0563b94dd8fa129a05f762a2c25 upstream. We should unlock before returning on this error path. Fixes: 3a762dbd5347 ('[media] Input: synaptics-rmi4 - add support

[PATCH 4.9 122/206] iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xunlei Pang commit aec0e86172a79eb5e44aff1055bb953fe4d47c59 upstream. We met the DMAR fault both on hpsa P420i and P421 SmartArray controllers under kdump, it can be steadily reproduced on seve

[PATCH 4.9 077/206] ARM: dts: r8a7794: Correct hsusb parent clock

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit dc8ee9dbdba509fb58e23ba79f2e6059fe5d8b3b upstream. The parent clock of the HSUSB clock is the HP clock, not the MP clock. Fixes: c7bab9f929e51761 ("ARM: shmobile: r8a

[PATCH 4.9 079/206] arm64: dts: hip06: Correct hardware pin number of usb node

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kefeng Wang commit 4d75a171b67ffc3f4dadbd654c9d281091300eb2 upstream. The ohci/ehci hardware pin number should be 640/641, correct them. Fixes: commit aa8d3e74f54d ("arm64: dts: Add initial dt

x86-64: Maintain 16-byte stack alignment

I recently applied the patch https://patchwork.kernel.org/patch/9468391/ and ended up with a boot crash when it tried to run the x86 chacha20 code. It turned out that the patch changed a manually aligned stack buffer to one that is aligned by gcc. What was happening was that gcc can sta

[PATCH 4.9 074/206] USB: serial: kl5kusb105: abort on open exception path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pan Bian commit 3c3dd1e058cb01e835dcade4b54a6f13ffaeaf7c upstream. Function klsi_105_open() calls usb_control_msg() (to "enable read") and checks its return value. When the return value is unex

[PATCH 4.9 075/206] usb: gadget: Fix second argument of percpu_ida_alloc()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 03274445c01562d5352ea522431ab8c6175e2bbf upstream. Pass a task state as second argument to percpu_ida_alloc(). Fixes: commit 71e7ae8e1fb2 ("usb-gadget/tcm: Conversion to

Re: Problem on SCTP

On Tue, Jan 10, 2017 at 09:30:39AM +0800, Sun Paul wrote: > Packet received (From client) > == > > No. Time SourceSPort > Destination Protocol DPort Length Info > DSCP > 1 2017-0

[PATCH 4.9 073/206] ALSA: usb-audio: Fix bogus error return in snd_usb_create_stream()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 4763601a56f155ddf94ef35fc2c41504a2de15f5 upstream. The function returns -EINVAL even if it builds the stream properly. The bogus error code sneaked in during the code refact

[PATCH 4.9 106/206] hwmon: (amc6821) sign extension temperature

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jared Bents commit 4538bfbf2d9f1fc48c07ac0cc0ee58716fe7fe96 upstream. Converts the unsigned temperature values from the i2c read to be sign extended as defined in the datasheet so that negative

[PATCH 4.9 109/206] hwmon: (g762) Fix overflows and crash seen when writing limit attributes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 4fccd4a1e8944033bcd7693ea4e8fb478cd2059a upstream. Fix overflows seen when writing into fan speed limit attributes. Also fix crash due to division by zero, seen when certai

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

On 01/10/2017 04:20 AM, Sergei Shtylyov wrote: > Hello! > > On 01/10/2017 05:21 AM, Shuah Khan wrote: > >> Fix dwc3_exynos_probe() to call clk_prepare_enable() only when suspend >> clock is specified. Call clk_disable_unprepare() from remove and probe >> error path only when susp_clk has been set

[PATCH 4.9 108/206] hwmon: (nct7802) Fix overflows seen when writing into limit attributes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit c0d04e9112ad59d73f23f3b0f6726c5e798dfcbf upstream. Fix overflows seen when writing voltage and temperature limit attributes. The value passed to DIV_ROUND_CLOSEST() needs

[PATCH 4.9 098/206] cris: Only build flash rescue image if CONFIG_ETRAX_AXISFLASHMAP is selected

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 328cf6927bb72cadefddebbc9a23c793108147a2 upstream. If CONFIG_ETRAX_AXISFLASHMAP is not configured, the flash rescue image object file is empty. With recent versions of binu

[PATCH 4.9 103/206] x86/cpu: Probe CPUID leaf 6 even when cpuid_level == 6

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 3df8d9208569ef0b2313e516566222d745f3b94b upstream. A typo (or mis-merge?) resulted in leaf 6 only being probed if cpuid_level >= 7. Fixes: 2ccd71f1b278 ("x86/cpufeature:

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

On 01/10/2017 07:16 AM, Shuah Khan wrote: > On 01/10/2017 05:05 AM, Bartlomiej Zolnierkiewicz wrote: >> >> Hi, >> >> On Monday, January 09, 2017 07:21:31 PM Shuah Khan wrote: >>> Fix dwc3_exynos_probe() to call clk_prepare_enable() only when suspend >>> clock is specified. Call clk_disable_unprepar

[PATCH 4.9 093/206] mac80211: fix tid_agg_rx NULL dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 1c3d185a9a0b136a58e73b02912d593d0303d1da upstream. On drivers setting the SUPPORTS_REORDERING_BUFFER hardware flag, we crash when the peer sends an AddBA request while we a

[PATCH 4.9 096/206] mfd: tps65217: Fix page fault on unloading modules

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Milo Kim commit 40a50f8b307de8d08f3fa37c312fc16a7dd233e5 upstream. TPS65217 IRQ domain should be removed and initialised as NULL when the module is unloaded for the next use. When tps65217.ko i

[PATCH 4.9 085/206] mei: move write cb to completion on credentials failures

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Usyskin commit e09ee853c92011860a4bd2fbdf6126f60fc16bd3 upstream. The credentials handling was pushed to the write handlers but error handling wasn't done properly. Move write callbac

[PATCH 4.9 026/206] usb: storage: unusual_uas: Add JMicron JMS56x to unusual device

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 674aea07e38200ea6f31ff6d5f200f0cf6cdb325 upstream. This device gives the following error on detection. xhci_hcd :00:11.0: ERROR Transfer event for disabled endpoint or

[PATCH 4.9 081/206] [media] dibusb: fix possible memory leak in dibusb_rc_query()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 1f5ecaf985c46889278f51fcb7bc143f60f4eb14 upstream. 'buf' is malloced in dibusb_rc_query() and should be freed before leaving from the error handling cases, otherwise it will

Re: x86-64: Maintain 16-byte stack alignment

On Tue, Jan 10, 2017 at 10:33:40PM +0800, Herbert Xu wrote: > I recently applied the patch > > https://patchwork.kernel.org/patch/9468391/ > > and ended up with a boot crash when it tried to run the x86 chacha20 > code. It turned out that the patch changed a manually aligned > stack buffer

[PATCH 4.9 097/206] ath10k: use the right length of "background"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Iooss commit 31b239824ece321c09bdb8e61e1d14814eaba38b upstream. The word "background" contains 10 characters so the third argument of strncmp() need to be 10 in order to match this pref

[PATCH 4.9 082/206] USB: serial: io_ti: bind to interface after fw download

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit e35d6d7c4e6532a89732cf4bace0e910ee684c88 upstream. Bind to the interface, but do not register any ports, after having downloaded the firmware. The device will still disconne

[PATCH 4.9 084/206] mei: bus: fix mei_cldev_enable KDoc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Usyskin commit 5026c9cb0744a9cd40242743ca91a5d712f468c6 upstream. Adjust function name in KDoc. Fixes: d49dc5e76fc9 (mei: bus: use mei_cldev_ prefix for the API functions) Signed-off

[PATCH 4.9 086/206] staging: iio: ad7606: fix improper setting of oversampling pins

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eva Rachel Retuya commit b321a38d2407c7e425c54bc09be909a34e49f740 upstream. The oversampling ratio is controlled using the oversampling pins, OS [2:0] with OS2 being the MSB control bit, and OS

Re: [PATCH v7 2/7] perf/amd/iommu: Modify functions to query max banks and counters

On Mon, Jan 09, 2017 at 09:33:42PM -0600, Suthikulpanit, Suravee wrote: > +static struct amd_iommu *get_amd_iommu(uint idx) > +{ > + uint i = 0; > + struct amd_iommu *iommu = NULL; > + > + for_each_iommu(iommu) { > + if (i == idx) > + break; > +

[PATCH 4.9 066/206] usb: dwc3: pci: add Intel Gemini Lake PCI ID

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 8f8983a5683623b62b339d159573f95a1fce44f3 upstream. Intel Gemini Lake SoC has the same DWC3 than Broxton. Add the new ID to the supported Devices. Signed-off-by: Heikki K

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

On Tue, Jan 10, 2017 at 11:47:42AM +0100, Arnd Bergmann wrote: > I see that we have CONFIG_ARCH_PHYS_ADDR_T_64BIT on a couple of > 32-bit architectures without swiotlb (arc, arm, some mips32), and > there are several 64-bit architectures that do not have swiotlb > (alpha, parisc, s390, sparc). I be

[PATCH 4.9 068/206] usb: dwc3: gadget: Fix full speed mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Roger Quadros commit 9418ee15f718939aa7e650fd586d73765eb21f20 upstream. DCFG.DEVSPD == 0x3 is not valid and we need to set DCFG.DEVSPD to 0x1 for full speed mode. Same goes for DSTS.CONNECTSPD.

Re: [PATCH 2/2] tools: perf: fix build error in uapi/linux/mman.h

Em Tue, Jan 10, 2017 at 10:22:50AM +, Sudeep Holla escreveu: > All the other occurrence refer "uapi/asm-generic/*.h" directly instead > of "uapi/asm/*.h" in tools/include except mman.h. Without this patch, > the following build failure is seen. > Seen where? I don't see it here, and I build p

[PATCH 4.9 031/206] USB: fix problems with duplicate endpoint addresses

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 0a8fd1346254974c3a852338508e4a4cddbb35f1 upstream. When checking a new device's descriptors, the USB core does not check for duplicate endpoint addresses. This can cause a pr

Re: [PATCH v2 5/5] firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation

On Mon, Jan 09, 2017 at 10:09:51PM +0100, Julia Lawall wrote: > > > On Mon, 9 Jan 2017, Luis R. Rodriguez wrote: > > > On Mon, Dec 19, 2016 at 11:23:17AM +0100, Julia Lawall wrote: > > > > > > > > > On Fri, 16 Dec 2016, Luis R. Rodriguez wrote: > > > > > > > We need to ensure that when driver de

[PATCH 4.9 034/206] usb: dwc3: core: avoid Overflow events

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Felipe Balbi commit e71d363d9c611c99fb78f53bfee99616e7fe352c upstream. Now that we're handling so many transfers at a time and for some dwc3 revisions LPM events *must* be enabled, we can fall

[PATCH 4.9 063/206] usb: xhci-mem: use passed in GFP flags instead of GFP_KERNEL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit c95a9f83711bf53faeb4ed9bbb63a3f065613dfb upstream. We normally use the passed in gfp flags for allocations, it's just these two which were missed. Fixes: 22d45f01a836 ("us

Re: [PATCH] ovl: do not ignore disk quota if current task is not privileged

On Tue, Jan 10, 2017 at 02:26:48PM +0300, Konstantin Khlebnikov wrote: > If overlay was mounted by root then quota set for upper layer does not work > because overlay now always use mounter's credentials for operations. > > This patch adds second copy of credentials without CAP_SYS_RESOURCE and >

[PATCH 4.9 065/206] xhci: Fix race related to abort operation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi commit 1c111b6c3844a142e03bcfc2fa17bfbdea08e9dc upstream. Current abort operation has race. xhci_handle_command_timeout() xhci_abort_cmd_ring() xhci_write_64(C

Re: [PATCHv14 2/3] usb: USB Type-C connector class

On Tue, Jan 10, 2017 at 05:50:04AM -0800, Guenter Roeck wrote: > On 01/10/2017 12:54 AM, Heikki Krogerus wrote: > > Hi Guenter, > > > > On Mon, Jan 09, 2017 at 08:59:32AM -0800, Guenter Roeck wrote: > > > > +/** > > > > + * typec_register_partner - Register a USB Type-C Partner > > > > + * @port:

[PATCH 4.9 062/206] USB: serial: mos7720: fix parallel probe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit fde1faf872ed86d88e245191bc15a8e57368cd1c upstream. A static usb-serial-driver structure that is used to initialise the interrupt URB was modified during probe depending on t

[PATCH 4.9 060/206] USB: serial: mos7720: fix use-after-free on probe errors

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 91a1ff4d53c5184d383d0baeeaeab6f9736f2ff3 upstream. The interrupt URB was submitted on probe but never stopped on probe errors. This can lead to use-after-free issues in the

[PATCH 4.9 057/206] USB: serial: kobil_sct: fix NULL-deref in write

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 21ce57840243c7b70fbc1ebd3dceeb70bb6e9e09 upstream. Fix NULL-pointer dereference in write() should the device lack the expected interrupt-out endpoint: Unable to handle kern

[PATCH 4.9 053/206] USB: serial: ti_usb_3410_5052: fix NULL-deref at open

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit ef079936d3cd09e63612834fe2698eeada0d8e3f upstream. Fix NULL-pointer dereference in open() should a malicious device lack the expected endpoints: Unable to handle kernel NUL

[PATCH 4.9 029/206] USB: gadgetfs: fix use-after-free bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit add333a81a16abbd4f106266a2553677a165725f upstream. Andrey Konovalov reports that fuzz testing with syzkaller causes a KASAN use-after-free bug report in gadgetfs: BUG: KASAN:

Re: [PATCH] [Performance Events] Fix typo in tools/perf/evlist.c

Em Tue, Jan 10, 2017 at 08:00:06PM +0900, Soramichi AKIYAMA escreveu: > This patch fixes a typo: s/enable to/unable to/ Thanks, somehow it didn't apply cleanly, did it manually, added Fixes: tag, ended up as: commit c628c4d72895768624d0386b672992005c2561ac Author: Soramichi Akiyama Date: Tue J

[PATCH 4.9 094/206] nl80211: Use different attrs for BSSID and random MAC addr in scan req

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vamsi Krishna commit 2fa436b3a2a7009c11a3bc03fe0ff4c26e80fd87 upstream. NL80211_ATTR_MAC was used to set both the specific BSSID to be scanned and the random MAC address to be used when privacy

[PATCH 4.9 056/206] USB: serial: cyberjack: fix NULL-deref at open

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 3dca01114dcecb1cf324534cd8d75fd1306a516b upstream. Fix NULL-pointer dereference when clearing halt at open should the device lack a bulk-out endpoint. Unable to handle kern

Re: NVMe vs DMA addressing limitations

On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote: > Another workaround me might need is to limit amount of concurrent DMA > in the NVMe driver based on some platform quirk. The way that NVMe works, > it can have very large amounts of data that is concurrently mapped into > the device.

<    1   2   3   4   5   6   7   8   9   10   >