Re: [PATCH] clk: stm32h7: Add stm32h743 clock driver

Hi Stephen, On 04/06/2017 12:32 AM, Stephen Boyd wrote: On 03/15, gabriel.fernan...@st.com wrote: From: Gabriel Fernandez This patch enables clocks for STM32H743 boards. Like what clocks exactly? All of them? Yes all of them, it's new IP diff --git

Re: [PATCH V10 03/12] of: dma: Move range size workaround to of_dma_get_range()

Hi Frank, On 4/6/2017 11:54 AM, Frank Rowand wrote: On 04/04/17 03:18, Sricharan R wrote: From: Laurent Pinchart Invalid dma-ranges values should be worked around when retrieving the DMA range in of_dma_get_range(), not by all callers of the

[PATCH 4.4 13/26] USB: fix linked-list corruption in rh_call_control()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 1633682053a7ee8058e10c76722b9b28e97fb73f upstream. Using KASAN, Dmitry found a bug in the rh_call_control() routine: If buffer allocation fails,

Re: [PATCH v4 2/2] i2c: mux: ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

Hi Michael, I would still like to hear from someone with more gpio experience. Anyway, from my point of view, there's just a few minor things left, with comments inline as usual. Thanks for you patience! Cheers, peda On 2017-04-05 15:07, michael.henner...@analog.com wrote: > From: Michael

[PATCH 4.9 17/72] xfs: reject all unaligned direct writes to reflinked files

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 54a4ef8af4e0dc5c983d17fcb9cf5fd25666d94e upstream. We currently fall back from direct to buffered writes if we detect a remaining shared extent in the

[PATCH 4.4 10/26] ACPI: Do not create a platform_device for IOAPIC/IOxAPIC

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel commit 08f63d97749185fab942a3a47ed80f5bd89b8b7d upstream. No platform-device is required for IO(x)APICs, so don't even create them. [ rjw: This fixes a problem

Re: [PATCH] drm: bridge: dw-hdmi: fix input format/encoding from plat_data

On 04/06/2017 11:34 AM, Neil Armstrong wrote: > The plat_data->input_bus_format and plat_data->input_bus_encoding > are unsigned long and are alsways >=0, but the value 0 was still > considered as RGB888 like the default behaviour. > > This patch changes the if test to > 0. > > Thanks to Dan

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

On Thu, Apr 06, 2017 at 11:35:45AM +0200, Peter Zijlstra wrote: > On Thu, Apr 06, 2017 at 10:01:39AM +0200, Ingo Molnar wrote: > > I.e. just have a counter and these two APIs: > > > > static inline void migrate_disable(void) > > { > > current->migration_disabled++;

Re: [PATCH v6 19/39] media: Add i.MX media core driver

On Mon, 2017-03-27 at 17:40 -0700, Steve Longerbeam wrote: > Add the core media driver for i.MX SOC. > > Signed-off-by: Steve Longerbeam [...] > diff --git a/drivers/staging/media/imx/imx-media-of.c > b/drivers/staging/media/imx/imx-media-of.c > new file mode 100644

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

On Thu, Apr 06, 2017 at 11:25:42AM +0200, Sebastian Andrzej Siewior wrote: > > I.e. just have a counter and these two APIs: > > > > static inline void migrate_disable(void) > > { > > current->migration_disabled++; > plus > if (current->migration_disabled ==

Re: [HMM 01/16] mm/memory/hotplug: add memory type parameter to arch_add/remove_memory

> diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c > index 5f84433..0933261 100644 > --- a/arch/powerpc/mm/mem.c > +++ b/arch/powerpc/mm/mem.c > @@ -126,14 +126,31 @@ int __weak remove_section_mapping(unsigned long start, > unsigned long end) > return -ENODEV; > } > > -int

Re: [PATCH] MAINTAINERS: Add Laurent and Andrzej as maintainers for bridge drivers

Hi Laurent, On 4/6/2017 2:40 PM, Laurent Pinchart wrote: Hi Archit, On Wednesday 05 Apr 2017 16:53:50 Archit Taneja wrote: Add Laurent and Andrzej as maintainers for DRM bridge chip drivers. They actively review and contribute to bridge drivers and the bridge API. How about adding me as a

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

On 2017-04-06 11:32:24 [+0200], Peter Zijlstra wrote: > On Tue, Apr 04, 2017 at 08:42:02PM +0200, Sebastian Andrzej Siewior wrote: > > While converting the existing users I tried to stick with the rules > > above however… well mostly CPUFREQ tries to temporary switch the CPU > > mask to do

Re: [PATCH v3 02/19] HID: logitech-hidpp: Add scope to battery

On Mon, 27 Mar 2017, Benjamin Tissoires wrote: > From: Bastien Nocera > > Without a scope defined, UPower assumes that the battery provides > power to the computer it's connected to, like a laptop battery or a UPS. > > Tested-by: Peter Hutterer >

Re: XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1.

On Mon, Mar 13, 2017 at 07:06:01PM +0200, Krzysztof Kozlowski wrote: > > I bisected this to commit f1c131b45410 ("crypto: xts - Convert to > skcipher"). The s5p-sss driver stays the same... but the xts changes and > as a result we have a NULL pointer dereference (actually of value > 0004): > [

Re: [PATCH 3/3] perf tool, arm64, thunderx2: Add implementation defined events for ThunderX2

On Thu, Apr 06, 2017 at 09:50:33AM +0530, Ganapatrao Kulkarni wrote: > On Wed, Apr 5, 2017 at 3:35 PM, Mark Rutland wrote: > > On Wed, Apr 05, 2017 at 02:42:39PM +0530, Ganapatrao Kulkarni wrote: > >> On Tue, Apr 4, 2017 at 5:58 PM, Mark Rutland wrote:

Re: [PATCH v3 02/19] HID: logitech-hidpp: Add scope to battery

On Apr 06 2017 or thereabouts, Jiri Kosina wrote: > On Mon, 27 Mar 2017, Benjamin Tissoires wrote: > > > From: Bastien Nocera > > > > Without a scope defined, UPower assumes that the battery provides > > power to the computer it's connected to, like a laptop battery or a UPS.

Re: [RFC] [media] imx: assume MEDIA_ENT_F_ATV_DECODER entities output video on pad 1

On Wed, 2017-04-05 at 11:53 -0300, Mauro Carvalho Chehab wrote: [...] > There are a number of drivers that can work with different > types of TV demodulators. Typical examples of such hardware can be > found at em28xx, saa7134, cx88 drivers (among lots of other drivers). > Those drivers don't use

Re: [PATCH V5 2/4] dt-bindings: arm: Add bindings for SP9860G

Hello Greg, I guess there will be no further comments on this patchset :), could you please take the patches 2/3/4 through tty git? Thanks, Chunyan On 27 March 2017 at 14:06, Chunyan Zhang wrote: > Added bindings for Spreadtrum SP9860G board and SC9860 SoC. > This

Re: [PATCH V10 03/12] of: dma: Move range size workaround to of_dma_get_range()

Hi Frank, On 06/04/17 07:24, Frank Rowand wrote: > On 04/04/17 03:18, Sricharan R wrote: >> From: Laurent Pinchart >> >> Invalid dma-ranges values should be worked around when retrieving the >> DMA range in of_dma_get_range(), not by all callers of the

Re: [PATCHv3] EDAC, altera: Fix peripheral warnings for Cyclone5

On Wed, Apr 05, 2017 at 01:01:02PM -0500, thor.tha...@linux.intel.com wrote: > From: Thor Thayer > > The peripherals EDACs only exist on the Arria10 SoCFPGA. The Cyclone5 > initialization has EDAC warnings when the peripherals aren't found > in the device tree. Fix

Re: [PATCH v23 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

On Wed, Apr 05, 2017 at 07:38:09PM +0100, Mark Rutland wrote: > I tried to fix the issue that Lornzo raised, such that I could queue > these patches. From looking at this patch in more detail however, I > think there are further issues that need to be addressed. Looking again, I see that I was

Re: [PATCH 0/6] mm: make movable onlining suck less

On Wed 05-04-17 23:02:14, Michal Hocko wrote: [...] > OK, I was staring into the code and I guess I finally understand what is > going on here. Looking at arch_add_memory->...->register_mem_sect_under_node > was just misleading. I am still not 100% sure why but we try to do the > same thing later

Re: net/sched: latent livelock in dev_deactivate_many() due to yield() usage

On Thu, Apr 06, 2017 at 12:28:44PM +0200, Peter Zijlstra wrote: > On Wed, Apr 05, 2017 at 05:31:05PM -0700, Stephen Hemminger wrote: > > On Sun, 02 Apr 2017 06:28:41 +0200 > > Mike Galbraith wrote: > > > > > Livelock can be triggered by setting kworkers to SCHED_FIFO, then > > >

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

On Thu, 6 Apr 2017, Ingo Molnar wrote: > CPU hotplug and changing the affinity mask are the more complex cases, > because > there migrating or not migrating is a correctness issue: > > - CPU hotplug has to be aware of this anyway, regardless of whether it's > solved >via a counter of the

Re: [PATCH v3 8/9] drm/rockchip: gem: Don't alloc/free gem buf when dev_private is invalid

Hi Daniel, On 04/06/2017 04:26 PM, Daniel Vetter wrote: On Wed, Apr 05, 2017 at 12:28:40PM -0400, Sean Paul wrote: On Wed, Apr 05, 2017 at 04:29:26PM +0800, Jeffy Chen wrote: After unbinding drm, the userspace may still has a chance to access gem buf. Add a sanity check for a NULL

[PATCH] scsi: qla2xxx: remove some redundant pointer assignments

From: Colin Ian King There are several local or function parameter pointers that are being assigned NULL after a kfree where and these have no effect and hence can be removed. Fixes various cppcheck warnings: "Assignment of function parameter has no effect outside the

Re: [Nbd] [PATCH 3/4] treewide: convert PF_MEMALLOC manipulations to new helpers

On Thu, Apr 06, 2017 at 08:38:10AM +0200, Wouter Verhelst wrote: > On Wed, Apr 05, 2017 at 01:30:31PM +0200, Michal Hocko wrote: > > On Wed 05-04-17 09:46:59, Vlastimil Babka wrote: > > > We now have memalloc_noreclaim_{save,restore} helpers for robust setting > > > and > > > clearing of

Re: [PATCH v4 2/2] i2c: mux: ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

On 06.04.2017 10:39, Peter Rosin wrote: Hi Michael, I would still like to hear from someone with more gpio experience. I'll ping Linus. Anyway, from my point of view, there's just a few minor things left, with comments inline as usual. Thanks for you patience! Thanks for review.

Re: [RESEND PATCH V7 1/5] Documentation: devicetree: watchdog: da9062/61 watchdog timer binding

On 04/06/2017 01:28 AM, Steve Twiss wrote: From: Steve Twiss Add binding information for DA9062 and DA9061 watchdog. Example bindings for both DA9062 and DA9061 devices are added. For the DA9061 device, a fallback compatible line is added as a valid combination

Re: [PATCH 3/9] bio-integrity: bio_integrity_advance must update integrity seed

Looks good, Reviewed-by: Christoph Hellwig

Re: [PATCH 4/9] bio-integrity: fix interface for bio_integrity_trim v2

Please drop the v2 from the subject line and move your changelog either into the cover letter (preferred) or at least below the --- line. Otherwise looks good: Reviewed-by: Christoph Hellwig

Re: [PATCH v2 02/22] asm-generic/io.h: add ioremap_nopost remap interface

On Thu, Apr 06, 2017 at 12:53:12PM +0200, Luis R. Rodriguez wrote: > On Thu, Apr 06, 2017 at 11:26:36AM +0100, Lorenzo Pieralisi wrote: > > On Wed, Apr 05, 2017 at 01:38:12PM +0100, Lorenzo Pieralisi wrote: > > > On Wed, Apr 05, 2017 at 11:58:41AM +0100, Russell King - ARM Linux wrote: > > > > On

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

On Thu, Apr 06, 2017 at 12:58:27PM +0200, Thomas Gleixner wrote: > On Thu, 6 Apr 2017, Peter Zijlstra wrote: > > Because mainline will not get anything other than prempt_disable() for > > migrate_disable(). > > I'm not yet convinced of that. There is enough stuff which pointlessly > disables

Re: [PATCH v6 4/6] watchdog: iTCO_wdt: Add PMC specific noreboot update api

On 04/05/2017 03:54 PM, Kuppuswamy Sathyanarayanan wrote: In some SoCs, setting noreboot bit needs modification to PMC GC registers. But not all PMC drivers allow other drivers to memory map their GC region. This could create mem request conflict in watchdog driver. So this patch adds facility

Re: [PATCH 5/9] bio-integrity: fold bio_integrity_enabled to bio_integrity_prep

> --- a/Documentation/block/data-integrity.txt > +++ b/Documentation/block/data-integrity.txt > @@ -202,9 +202,6 @@ will require extra work due to the application tag. >added. It is up to the caller to ensure that the bio does not >change while I/O is in progress. > > -

Re: [PATCH 6/9] T10: Move opencoded contants to common header

Looks good, Reviewed-by: Christoph Hellwig

Re: [PATCH v2] iTCO_wdt: all versions count down twice

On 04/05/2017 04:41 AM, Paolo Bonzini wrote: The ICH9 is listed as having TCO v2, and indeed the behavior in the datasheet corresponds to v2 (for example the NO_REBOOT flag is accessible via the 16KiB-aligned Root Complex Base Address). However, the TCO counts twice just like in v1; the

[PATCH 4.9 27/72] xfs: Use xfs_icluster_size_fsb() to calculate inode alignment mask

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chandan Rajendra commit d5825712ee98d68a2c17bc89dad2c30276894cba upstream. When block size is larger than inode cluster size, the call to XFS_B_TO_FSBT(mp,

[PATCH 4.9 03/72] xfs: only update mount/resv fields on success in __xfs_ag_resv_init

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 4dfa2b84118fd6c95202ae87e62adf5000ccd4d0 upstream. Try to reserve the blocks first and only then update the fields in or hanging off the mount structure.

[PATCH 4.4 05/26] scsi: libsas: fix ata xfer length

4.4-stable review patch. If anyone has any objections, please let me know. -- From: John Garry commit 9702c67c6066f583b629cf037d2056245bb7a8e6 upstream. The total ata xfer length may not be calculated properly, in that we do not use the proper method to

[PATCH 4.9 04/72] xfs: use per-AG reservations for the finobt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 76d771b4cbe33c581bd6ca2710c120be51172440 upstream. Currently we try to rely on the global reserved block pool for block allocations for the free inode

[PATCH 4.9 29/72] xfs: try any AG when allocating the first btree block when reflinking

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 2fcc319d2467a5f5b78f35f79fd6e22741a31b1e upstream. When a reflink operation causes the bmap code to allocate a btree block we're currently doing single-AG

[PATCH 4.4 16/26] mm, hugetlb: use pte_present() instead of pmd_present() in follow_huge_pmd()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Naoya Horiguchi commit c9d398fa237882ea07167e23bcfc5e6847066518 upstream. I found the race condition which triggers the following bug when move_pages() and soft

Re: [PATCH v6 01/11] powerpc/powernv: Data structure and macros definitions

Madhavan Srinivasan writes: > +#define IMC_MAX_CHIPS32 > +#define IMC_MAX_PMUS 32 The max chips and PMUs we'd be able to work out from the device tre though, right? We could just allocate the correct amount of memory on boot. We

[PATCH 4.4 03/26] scsi: mpt3sas: fix hang on ata passthrough commands

4.4-stable review patch. If anyone has any objections, please let me know. -- From: James Bottomley commit ffb58456589443ca572221fabbdef3db8483a779 upstream. mpt3sas has a firmware failure where it can only handle one pass through ATA

[PATCH 4.4 17/26] MIPS: Lantiq: Fix cascaded IRQ setup

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 6c356eda225e3ee134ed4176b9ae3a76f793f4dd upstream. With the IRQ stack changes integrated, the XRX200 devices started emitting a constant stream of kernel

[PATCH 4.9 36/72] ALSA: hda - fix a problem for lineout on a Dell AIO machine

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit 2f726aec19a9d2c63bec9a8a53a3910ffdcd09f8 upstream. On this Dell AIO machine, the lineout jack does not work. We found the pin 0x1a is assigned to

[PATCH 4.10 07/81] xfs: fail _dir_open when readahead fails

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 7a652bbe366464267190c2792a32ce4fff5595ef upstream. When we open a directory, we try to readahead block 0 of the directory on the assumption

[PATCH 4.10 39/81] ASoC: rt5665: fix getting wrong work handler container

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bard Liao commit f1994a9c0930de4b2244816e62120cad08283cdc upstream. We got rt5665 private data from wrong work. It will result in kernel panic. Signed-off-by: Bard Liao

[PATCH 4.10 38/81] ASoC: Intel: Skylake: fix invalid memory access due to wrong reference of pointer

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Sakamoto commit d1a6fe41d3c4ff0d26f0b186d774493555ca5282 upstream. In 'skl_tplg_set_module_init_data()', a pointer to 'params' member of 'struct

[PATCH 4.10 40/81] HID: wacom: Dont add ghost interface as shared data

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Armstrong Skomra commit 8b4073596997f2ccbf68d8e72e07b827388a4536 upstream. A previous commit (below) adds a check for already probed interfaces to Wacom's matching

[PATCH 4.10 23/81] xfs: tune down agno asserts in the bmap code

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 410d17f67e583559be3a922f8b6cc336331893f3 upstream. In various places we currently assert that xfs_bmap_btalloc allocates from the same as the firstblock

[PATCH 4.10 09/81] xfs: check for obviously bad level values in the bmbt root

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit b3bf607d58520ea8c0666aeb4be60dbb724cd3a2 upstream. We can't handle a bmbt that's taller than BTREE_MAXLEVELS, and there's no such thing as a

[PATCH 4.10 08/81] xfs: filter out obviously bad btree pointers

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit d5a91baeb6033c3392121e4d5c011cdc08dfa9f7 upstream. Don't let anybody load an obviously bad btree pointer. Since the values come from disk, we

[PATCH 4.10 48/81] dt-bindings: rng: clocks property on omap_rng not always mandatory

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 74d1cf4897f919837efc4e34d800b996936eb38e upstream. Commit 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 device

[PATCH 4.10 36/81] ALSA: hda - fix a problem for lineout on a Dell AIO machine

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit 2f726aec19a9d2c63bec9a8a53a3910ffdcd09f8 upstream. On this Dell AIO machine, the lineout jack does not work. We found the pin 0x1a is assigned to

[PATCH 4.10 71/81] drm/armada: Fix compile fail

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 7357f89954b6d005df6ab8929759e78d7d9a80f9 upstream. I reported the include issue for tracepoints a while ago, but nothing seems to have happened.

[PATCH 4.10 41/81] mmc: sdhci: Disable runtime pm when the sdio_irq is enabled

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 923713b357455cfb9aca2cd3429cb0806a724ed2 upstream. SDIO cards may need clock to send the card interrupt to the host. On a cherrytrail tablet with a

[PATCH 4.10 37/81] ASoC: atmel-classd: fix audio clock rate

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Songjun Wu commit cd3ac9affc43b44f49d7af70d275f0bd426ba643 upstream. Fix the audio clock rate according to the datasheet. Reported-by: Dushara Jayasinghe

[PATCH v2 -tip 0/6] locking: Introduce range reader/writer lock

Changes from v1 (https://lwn.net/Articles/716383/), all in patch 2: - s/EXPORT_SYMBOL/EXPORT_SYMBOL_GPL - Made the tree walks a foreach loop, instead of while. - Fixed signal_pending() lockup issue for unaccounted waiters. - Fixed initialization macros. - Check condition before

[PATCH 4.10 35/81] ALSA: seq: Fix race during FIFO resize

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 2d7d54002e396c180db0c800c1046f0a3c471597 upstream. When a new event is queued while processing to resize the FIFO in snd_seq_fifo_clear(), it may lead to a

[PATCH 1/6] interval-tree: Build unconditionally

In preparation for range locking, this patch gets rid of CONFIG_INTERVAL_TREE option as we will unconditionally build it. Signed-off-by: Davidlohr Bueso --- drivers/gpu/drm/Kconfig | 2 -- drivers/gpu/drm/i915/Kconfig | 1 - lib/Kconfig | 14

[PATCH 4.10 51/81] parisc: Fix access fault handling in pa_memcpy()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 554bfeceb8a22d448cd986fc9efce25e833278a1 upstream. pa_memcpy() is the major memcpy implementation in the parisc kernel which is used to do any kind of

[PATCH 4.10 50/81] parisc: Avoid stalled CPU warnings after system shutdown

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 476e75a44b56038bee9207242d4bc718f6b4de06 upstream. Commit 73580dac7618 ("parisc: Fix system shutdown halt") introduced an endless loop for systems which

Re: [PATCH] drm: bridge: dw-hdmi: remove unused hdmi_bus_fmt_is_yuv420

On 04/05/2017 10:14 AM, Laurent Pinchart wrote: > Hi Neil, > > Thank you for the patch. > > On Wednesday 05 Apr 2017 09:32:59 Neil Armstrong wrote: >> Remove usused yet hdmi_bus_fmt_is_yuv420 function. >> >> Fixes: def23aa7e982 ("drm: bridge: dw-hdmi: Switch to V4L bus format and >> encodings")

[PATCH 4.10 27/81] xfs: use iomap new flag for newly allocated delalloc blocks

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit f65e6fad293b3a5793b7fa2044800506490e7a2e upstream. Commit fa7f138 ("xfs: clear delalloc and cache on buffered write failure") fixed one regression in

[PATCH 4.10 03/81] xfs: pull up iolock from xfs_free_eofblocks()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit a36b926180cda375ac2ec89e1748b47137cfc51c upstream. xfs_free_eofblocks() requires the IOLOCK_EXCL lock, but is called from different contexts where the

[PATCH 4.10 04/81] xfs: sync eofblocks scans under iolock are livelock prone

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit c3155097ad89a956579bc305856a1f2878494e52 upstream. The xfs_eofblocks.eof_scan_owner field is an internal field to facilitate invoking eofb scans from

[PATCH 4.10 06/81] xfs: fix toctou race when locking an inode to access the data map

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 4b5bd5bf3fb182dc504b1b64e0331300f156e756 upstream. We use di_format and if_flags to decide whether we're grabbing the ilock in btree mode

[PATCH 4.10 21/81] xfs: dont reserve blocks for right shift transactions

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 48af96ab92bc68fb645068b978ce36df2379e076 upstream. The block reservation for the transaction allocated in xfs_shift_file_space() is an artifact of the

[PATCH 4.10 26/81] xfs: Use xfs_icluster_size_fsb() to calculate inode alignment mask

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Chandan Rajendra commit d5825712ee98d68a2c17bc89dad2c30276894cba upstream. When block size is larger than inode cluster size, the call to XFS_B_TO_FSBT(mp,

[PATCH 4.10 22/81] xfs: Use xfs_icluster_size_fsb() to calculate inode chunk alignment

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Chandan Rajendra commit 8ee9fdbebc84b39f1d1c201c5e32277c61d034aa upstream. On a ppc64 system, executing generic/256 test with 32k block size gives the following

[PATCH 4.10 25/81] xfs: fix and streamline error handling in xfs_end_io

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 787eb485509f9d58962bd8b4dbc6a5ac6e2034fe upstream. There are two different cases of buffered I/O errors: - first we can have an already shutdown fs.

[PATCH 4.10 24/81] xfs: only reclaim unwritten COW extents periodically

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 3802a345321a08093ba2ddb1849e736f84e8d450 upstream. We only want to reclaim preallocations from our periodic work item. Currently this is archived by

[PATCH 4.10 02/81] KVM: nVMX: fix nested EPT detection

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ladi Prosek commit 7ad658b693536741c37b16aeb07840a2ce75f5b9 upstream. The nested_ept_enabled flag introduced in commit 7ca29de2136 was not computed correctly. We are

[PATCH 4.10 05/81] xfs: fix eofblocks race with file extending async dio writes

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit e4229d6b0bc9280f29624faf170cf76a9f1ca60e upstream. It's possible for post-eof blocks to end up being used for direct I/O writes. dio write performs an

[PATCH 11/11] EDAC: Rename report status accessors

From: Borislav Petkov Change them to have the edac_ prefix. No functionality change. Signed-off-by: Borislav Petkov --- drivers/acpi/acpi_extlog.c | 8 drivers/edac/edac_mc.c | 8 drivers/edac/pnd2_edac.c | 2 +- drivers/edac/sb_edac.c

[PATCH 05/11] EDAC: Move edac_op_state to edac_mc.c

From: Borislav Petkov ... as part of moving stuff away from edac_stub.c Signed-off-by: Borislav Petkov --- drivers/edac/edac_mc.c | 3 +++ drivers/edac/edac_stub.c | 3 --- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/edac/edac_mc.c

Re: [PATCH v3 1/8] trace: ras: add ARM processor error information trace event

Hi Steve, Sorry for reply late. On 2017/3/31 0:02, Steven Rostedt wrote: > On Thu, 30 Mar 2017 18:31:01 +0800 > Xie XiuQi wrote: > >> Add a new trace event for ARM processor error information, so that >> the user will know what error occurred. With this information the >>

[PATCH 04/11] EDAC: Remove edac_err_assert

From: Borislav Petkov ... and the glue around it. It is not needed anymore. Signed-off-by: Borislav Petkov --- drivers/edac/edac_mc.c | 18 +- drivers/edac/edac_stub.c | 3 --- include/linux/edac.h | 1 - 3 files changed, 1 insertion(+), 21

[PATCH 00/11] EDAC: Remove edac_stub.c

From: Borislav Petkov This was an ancient hack to hand in hw errors reported through an NMI into EDAC. And what a hack it was - it required a piece of the EDAC functionality to be always built-in and it called into it from NMI context. We could've simply converted it to a notifier

[PATCH 06/11] ACPI/extlog: Add EDAC dependency

From: Borislav Petkov We are calling EDAC functions - make the proper dependencies explicit. Signed-off-by: Borislav Petkov Cc: linux-a...@vger.kernel.org --- drivers/acpi/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 07/11] EDAC: Issue tracepoint only when it is defined

From: Borislav Petkov ... and this happens only when CONFIG_RAS is enabled. Signed-off-by: Borislav Petkov --- drivers/edac/edac_mc.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/drivers/edac/edac_mc.c b/drivers/edac/edac_mc.c

Re: [PATCH 02/24] Add the ability to lock down access to the running kernel image

On Wed, 5 Apr 2017, David Howells wrote: > +#include > +#include > + > +static __read_mostly bool kernel_locked_down; How about marking this __ro_after_init if ALLOW_LOCKDOWN_LIFT is not configured? -- James Morris

[PATCH 01/11] EDAC, highbank: Align Makefile directives

From: Borislav Petkov ... like the rest of the file. Signed-off-by: Borislav Petkov --- drivers/edac/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/edac/Makefile b/drivers/edac/Makefile index 52d735f29073..76517ebc0a7f

Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

On 30/03/17 22:06, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

[PATCH 4.10 16/81] xfs: correct null checks and error processing in xfs_initialize_perag

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bill O'Donnell commit b20fe4730ea5c037c16631fb0df659c7b6d4b3b1 upstream. If pag cannot be allocated, the current error exit path will trip a null pointer deference error

Re: [PATCH v2] HID: asus: support backlight on USB keyboards

Hi Carlo, On Apr 05 2017 or thereabouts, Carlo Caione wrote: > From: Carlo Caione > > The latest USB keyboards shipped on several ASUS laptop models > (including ROG laptop models such as GL702VMK) have the keyboards > backlight controlled by the keyboard firmware. > > The

Re: [PATCH V2] perf/x86: fix spurious NMI with PEBS Load Latency event

On Tue, Apr 04, 2017 at 03:14:06PM -0400, kan.li...@intel.com wrote: > From: Kan Liang > > Spurious NMIs will be observed when applying the following command. >while true ; do sudo perf record -b -a -e >

[PATCH 4.10 18/81] xfs: handle indlen shortage on delalloc extent merge

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 0e339ef8556d9e567aa7925f8892c263d79430d9 upstream. When a delalloc extent is created, it can be merged with pre-existing, contiguous, delalloc extents.

[PATCH 4.9 62/72] mm, hugetlb: use pte_present() instead of pmd_present() in follow_huge_pmd()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Naoya Horiguchi commit c9d398fa237882ea07167e23bcfc5e6847066518 upstream. I found the race condition which triggers the following bug when move_pages() and soft

[PATCH 4.9 61/72] mm: rmap: fix huge file mmap accounting in the memcg stats

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Weiner commit 553af430e7c981e6e8fa5007c5b7b5773acc63dd upstream. Huge pages are accounted as single units in the memcg's "file_mapped" counter. Account the

[PATCH 4.9 59/72] x86/mce: Fix copy/paste error in exception table entries

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit 26a37ab319a26d330bab298770d692bb9c852aff upstream. Back in commit: 92b0729c34cab ("x86/mm, x86/mce: Add memcpy_mcsafe()") ... I made a copy/paste

[PATCH 4.10 10/81] xfs: verify free block header fields

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit de14c5f541e78c59006bee56f6c5c2ef1ca07272 upstream. Perform basic sanity checking of the directory free block header fields so that we avoid

[PATCH 4.9 58/72] x86/mm/KASLR: Exclude EFI region from KASLR VA space randomization

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Baoquan He commit a46f60d76004965e5669dbf3fc21ef3bc3632eb4 upstream. Currently KASLR is enabled on three regions: the direct mapping of physical memory, vamlloc and vmemmap.

[PATCH 4.9 56/72] drm/vc4: Allocate the right amount of space for boot-time CRTC state.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Anholt commit 6d6e500391875cc372336c88e9a8af377be19c36 upstream. Without this, the first modeset would dereference past the allocation when trying to free the mm node.

[PATCH 4.9 48/72] ACPI: Do not create a platform_device for IOAPIC/IOxAPIC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Joerg Roedel commit 08f63d97749185fab942a3a47ed80f5bd89b8b7d upstream. No platform-device is required for IO(x)APICs, so don't even create them. [ rjw: This fixes a problem

[PATCH 4.9 47/72] ACPI: Fix incompatibility with mcount-based function graph tracing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 61b79e16c68d703dde58c25d3935d67210b7d71b upstream. Paul Menzel reported a warning: WARNING: CPU: 0 PID: 774 at

[PATCH 4.9 51/72] USB: fix linked-list corruption in rh_call_control()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 1633682053a7ee8058e10c76722b9b28e97fb73f upstream. Using KASAN, Dmitry found a bug in the rh_call_control() routine: If buffer allocation fails,

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