[PATCH 0/3] udf: Metadata partition fixes

This patchset (hopefully) fixes a problem with loading some Windows-generated UDF 2.5 filesystems, and two other problems I noticed along the way. This has only been tested on a single NetBSD-generated image (works before, works now) and a few Windows-7-generated images (triggered KASAN and failed

[PATCH 1/3] udf: Don't BUG on missing metadata partition descriptor

Currently, if a metadata partition map is missing its partition descriptor, then udf_get_pblock_meta25() will BUG() out the first time it is called. This is rather drastic for a corrupted filesystem, so just treat this case as an invalid mapping instead. Signed-off-by: Alden Tondettar ---

[PATCH 3/3] udf: Use correct partition reference number for metadata

UDF/OSTA terminology is confusing. Partition Numbers (PNs) are arbitrary 16-bit values, one for each physical partition in the volume. Partition Reference Numbers (PRNs) are indices into the the Partition Map Table and do not necessarily equal the PN of the mapped partition. The current metadata

[PATCH 3/3] udf: Use correct partition reference number for metadata

UDF/OSTA terminology is confusing. Partition Numbers (PNs) are arbitrary 16-bit values, one for each physical partition in the volume. Partition Reference Numbers (PRNs) are indices into the the Partition Map Table and do not necessarily equal the PN of the mapped partition. The current metadata

Re: [RFC PATCH] Increase in idle power with schedutil

On Wed, May 18, 2016 at 2:53 PM, Shilpasri G Bhat wrote: > This patch adds driver callback for fast_switch and below observations > on schedutil governor are done with this patch. > > In POWER8 there is a regression observed with schedutil compared to > ondemand.

Re: [RFC PATCH] Increase in idle power with schedutil

On Wed, May 18, 2016 at 2:53 PM, Shilpasri G Bhat wrote: > This patch adds driver callback for fast_switch and below observations > on schedutil governor are done with this patch. > > In POWER8 there is a regression observed with schedutil compared to > ondemand. With schedutil the frequency is

incoming merge conflict to linux-next

Hi Stephen, Dave Sterba's tree in linux-next has a few btrfs patches that we're not sending yet into Linus. We've got an update for Josef's enospc work that'll get sent in next week. So he prepped a pull for me that merged up a number of his branches but didn't include Josef's new code. It has

incoming merge conflict to linux-next

Hi Stephen, Dave Sterba's tree in linux-next has a few btrfs patches that we're not sending yet into Linus. We've got an update for Josef's enospc work that'll get sent in next week. So he prepped a pull for me that merged up a number of his branches but didn't include Josef's new code. It has

[PATCH 0/3] udf: Metadata partition fixes

This patchset (hopefully) fixes a problem with loading some Windows-generated UDF 2.5 filesystems, and two other problems I noticed along the way. This has only been tested on a single NetBSD-generated image (works before, works now) and a few Windows-7-generated images (triggered KASAN and failed

[PATCH 0/3] udf: Metadata partition fixes

This patchset (hopefully) fixes a problem with loading some Windows-generated UDF 2.5 filesystems, and two other problems I noticed along the way. This has only been tested on a single NetBSD-generated image (works before, works now) and a few Windows-7-generated images (triggered KASAN and failed

Re: usb: dwc2: regression on MyBook Live Duo / Canyonlands since 4.3.0-rc4

On Wednesday 18 May 2016 21:14:55 Christian Lamparter wrote: > On Tuesday, May 17, 2016 04:50:48 PM John Youn wrote: > > On 5/14/2016 6:11 AM, Christian Lamparter wrote: > Hey, that's really nice of you to do that :-D. Please keep me in the > loop (Cc) for those then. > > Yes, this needs

Re: usb: dwc2: regression on MyBook Live Duo / Canyonlands since 4.3.0-rc4

On Wednesday 18 May 2016 21:14:55 Christian Lamparter wrote: > On Tuesday, May 17, 2016 04:50:48 PM John Youn wrote: > > On 5/14/2016 6:11 AM, Christian Lamparter wrote: > Hey, that's really nice of you to do that :-D. Please keep me in the > loop (Cc) for those then. > > Yes, this needs

[PATCH 1/1] drm/msm/mdp4: avoid possible null pointer dereference

Do not dereference pll_rate before checking if it is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/msm/mdp/mdp4/mdp4_lvds_pll.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/msm/mdp/mdp4/mdp4_lvds_pll.c

[PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram

Signed-off-by: David Mosberger --- .../devicetree/bindings/nvmem/atmel-secumod.txt| 47 +++ drivers/nvmem/Kconfig | 7 + drivers/nvmem/Makefile | 2 + drivers/nvmem/atmel-secumod.c | 143

[PATCH 1/1] drm/msm/mdp4: avoid possible null pointer dereference

Do not dereference pll_rate before checking if it is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/msm/mdp/mdp4/mdp4_lvds_pll.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/msm/mdp/mdp4/mdp4_lvds_pll.c

[PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram

Signed-off-by: David Mosberger --- .../devicetree/bindings/nvmem/atmel-secumod.txt| 47 +++ drivers/nvmem/Kconfig | 7 + drivers/nvmem/Makefile | 2 + drivers/nvmem/atmel-secumod.c | 143

Re: [PATCH 4/6] cpufreq: conservative: Remove declaration of cs_dbs_gov

On Wed, May 18, 2016 at 2:25 PM, Viresh Kumar wrote: > The code doesn't use 'cs_dbs_gov' anymore before it is defined and the > extra line for declaring it can be removed. This sort of conflicts with a patch I've just posted (https://patchwork.kernel.org/patch/9122121/)

Re: [PATCH 4/6] cpufreq: conservative: Remove declaration of cs_dbs_gov

On Wed, May 18, 2016 at 2:25 PM, Viresh Kumar wrote: > The code doesn't use 'cs_dbs_gov' anymore before it is defined and the > extra line for declaring it can be removed. This sort of conflicts with a patch I've just posted (https://patchwork.kernel.org/patch/9122121/) and I'd prefer to go with

Re: [PATCH 5/6] cpufreq: Reuse gov_attr_* macros in schedutil governor

On Wed, May 18, 2016 at 2:25 PM, Viresh Kumar wrote: > These macros can be used by governors which don't use the common > governor code present in cpufreq_governor.c and should be moved to the > relevant header. > > Now that they are getting moved to the right header

Re: [PATCH 5/6] cpufreq: Reuse gov_attr_* macros in schedutil governor

On Wed, May 18, 2016 at 2:25 PM, Viresh Kumar wrote: > These macros can be used by governors which don't use the common > governor code present in cpufreq_governor.c and should be moved to the > relevant header. > > Now that they are getting moved to the right header file, reuse them in >

[PATCH 1/1] drm/mediatek: do not dereference NULL

After having verified that dpi is NULL we should not dereference it. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/mediatek/mtk_dpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c

[PATCH 1/1] drm/mediatek: do not dereference NULL

After having verified that dpi is NULL we should not dereference it. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/mediatek/mtk_dpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c b/drivers/gpu/drm/mediatek/mtk_dpi.c index

[PATCH 1/2] dma-buf/fence: add fence_collection fences

From: Gustavo Padovan struct fence_collection inherits from struct fence and carries a collection of fences that needs to be waited together. It is useful to translate a sync_file to a fence to remove the complexity of dealing with sync_files on DRM drivers. So

[PATCH 1/2] dma-buf/fence: add fence_collection fences

From: Gustavo Padovan struct fence_collection inherits from struct fence and carries a collection of fences that needs to be waited together. It is useful to translate a sync_file to a fence to remove the complexity of dealing with sync_files on DRM drivers. So even if there are many fences in

[PATCH 2/2] Documentation: add fence-collection to kernel DocBook

From: Gustavo Padovan Include fence-collection files in the DocBook. Signed-off-by: Gustavo Padovan --- Documentation/DocBook/device-drivers.tmpl | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 2/2] Documentation: add fence-collection to kernel DocBook

From: Gustavo Padovan Include fence-collection files in the DocBook. Signed-off-by: Gustavo Padovan --- Documentation/DocBook/device-drivers.tmpl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/DocBook/device-drivers.tmpl b/Documentation/DocBook/device-drivers.tmpl index

Re: [RFC PATCH 1/3] asm-generic: io: Add exec versions of ioremap

On Wed, May 18, 2016 at 10:25:03PM +0200, Arnd Bergmann wrote: > The ARM version of ioremap_exec() that gets added in this patch is cached > (like memremap()), but then the asm-generic version is not? This is > even more confusing, it should at least do roughly the same thing across >

Re: [RFC PATCH 1/3] asm-generic: io: Add exec versions of ioremap

On Wed, May 18, 2016 at 10:25:03PM +0200, Arnd Bergmann wrote: > The ARM version of ioremap_exec() that gets added in this patch is cached > (like memremap()), but then the asm-generic version is not? This is > even more confusing, it should at least do roughly the same thing across >

[PATCH v3 4/5] Revert "block: enable dax for raw block devices"

This reverts commit 5a023cdba50c5f5f2bc351783b3131699deb3937. The functionality is superseded by the new "Device DAX" facility. Cc: Jeff Moyer Cc: Christoph Hellwig Cc: Dave Chinner Cc: Andrew Morton Cc: Ross

[PATCH v3 4/5] Revert "block: enable dax for raw block devices"

This reverts commit 5a023cdba50c5f5f2bc351783b3131699deb3937. The functionality is superseded by the new "Device DAX" facility. Cc: Jeff Moyer Cc: Christoph Hellwig Cc: Dave Chinner Cc: Andrew Morton Cc: Ross Zwisler Cc: Jan Kara Signed-off-by: Dan Williams --- block/ioctl.c |

[PATCH v3 0/5] "Device DAX" for persistent memory

Changes since v2 [1]: 1/ Allow libnvdimm drivers to omit a ->remove() method (Johannes) 2/ Fix memory leak due to missing ida_destroy() in drivers/nvdimm/ and drivers/dax/ (Johannes) 3/ Mark some dev_dbg() instances as dev_info() (Johannes) 4/ Clarify RCU usage in dax.c (Johannes), acked-by

[PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory

Device DAX is the device-centric analogue of Filesystem DAX (CONFIG_FS_DAX). It allows memory ranges to be allocated and mapped without need of an intervening file system. Device DAX is strict, precise and predictable. Specifically this interface: 1/ Guarantees fault granularity with respect

[PATCH v3 0/5] "Device DAX" for persistent memory

Changes since v2 [1]: 1/ Allow libnvdimm drivers to omit a ->remove() method (Johannes) 2/ Fix memory leak due to missing ida_destroy() in drivers/nvdimm/ and drivers/dax/ (Johannes) 3/ Mark some dev_dbg() instances as dev_info() (Johannes) 4/ Clarify RCU usage in dax.c (Johannes), acked-by

[PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory

Device DAX is the device-centric analogue of Filesystem DAX (CONFIG_FS_DAX). It allows memory ranges to be allocated and mapped without need of an intervening file system. Device DAX is strict, precise and predictable. Specifically this interface: 1/ Guarantees fault granularity with respect

[PATCH v3 3/5] /dev/dax, core: file operations and dax-mmap

The "Device DAX" core enables dax mappings of performance / feature differentiated memory. An open mapping or file handle keeps the backing struct device live, but new mappings are only possible while the device is enabled. Faults are handled under rcu_read_lock to synchronize with the enabled

[PATCH v3 5/5] libnvdimm: release ida resources

ida instances allocate some internal memory for ->free_bitmap in addition to the base 'struct ida'. Use ida_destroy() to release that memory at module_exit(). Reported-by: Johannes Thumshirn Signed-off-by: Dan Williams --- drivers/nvdimm/core.c

[PATCH v3 3/5] /dev/dax, core: file operations and dax-mmap

The "Device DAX" core enables dax mappings of performance / feature differentiated memory. An open mapping or file handle keeps the backing struct device live, but new mappings are only possible while the device is enabled. Faults are handled under rcu_read_lock to synchronize with the enabled

[PATCH v3 5/5] libnvdimm: release ida resources

ida instances allocate some internal memory for ->free_bitmap in addition to the base 'struct ida'. Use ida_destroy() to release that memory at module_exit(). Reported-by: Johannes Thumshirn Signed-off-by: Dan Williams --- drivers/nvdimm/core.c|3 +++ drivers/nvdimm/dimm_devs.c

[PATCH v3 1/5] libnvdimm: stop requiring a driver ->remove() method

The dax_pmem driver was implementing an empty ->remove() method to satisfy the nvdimm bus driver that unconditionally calls ->remove(). Teach the core bus driver to check if ->remove() is NULL to remove that requirement. Reported-by: Johannes Thumshirn Signed-off-by: Dan

[PATCH v3 1/5] libnvdimm: stop requiring a driver ->remove() method

The dax_pmem driver was implementing an empty ->remove() method to satisfy the nvdimm bus driver that unconditionally calls ->remove(). Teach the core bus driver to check if ->remove() is NULL to remove that requirement. Reported-by: Johannes Thumshirn Signed-off-by: Dan Williams ---

[PATCH] cpufreq: Drop the 'initialized' field from struct cpufreq_governor

From: Rafael J. Wysocki The 'initialized' field in struct cpufreq_governor is only used by the conservative governor (as a usage counter) and the way that happens is far from straightforward and arguably incorrect. Namely, the value of 'initialized' is checked by

[PATCH] cpufreq: Drop the 'initialized' field from struct cpufreq_governor

From: Rafael J. Wysocki The 'initialized' field in struct cpufreq_governor is only used by the conservative governor (as a usage counter) and the way that happens is far from straightforward and arguably incorrect. Namely, the value of 'initialized' is checked by cpufreq_dbs_governor_init() and

Re: [PATCH] tty: vt: Fix soft lockup in fbcon cursor blink timer.

On 05/18/2016 01:24 PM, Scot Doyle wrote: On Wed, 18 May 2016, Ming Lei wrote: On Wed, May 18, 2016 at 4:49 AM, Pavel Machek wrote: On Tue 2016-05-17 11:41:04, David Daney wrote: From: David Daney We are getting somewhat random soft lockups with this

Re: [PATCH] tty: vt: Fix soft lockup in fbcon cursor blink timer.

On 05/18/2016 01:24 PM, Scot Doyle wrote: On Wed, 18 May 2016, Ming Lei wrote: On Wed, May 18, 2016 at 4:49 AM, Pavel Machek wrote: On Tue 2016-05-17 11:41:04, David Daney wrote: From: David Daney We are getting somewhat random soft lockups with this signature: [ 86.992215] []

Re: [PATCH 1/1] drm/gma500: mdfld: avoid possible null pointer dereference

On Wed, May 18, 2016 at 10:31 PM, Heinrich Schuchardt wrote: > Only dereference sender after checking if sender is NULL. Hi Heinrich I think we had a patch that did something similar a while ago. Don't remember what happened to it. We do check for !sender right before

Re: [PATCH 1/1] drm/gma500: mdfld: avoid possible null pointer dereference

On Wed, May 18, 2016 at 10:31 PM, Heinrich Schuchardt wrote: > Only dereference sender after checking if sender is NULL. Hi Heinrich I think we had a patch that did something similar a while ago. Don't remember what happened to it. We do check for !sender right before calling this function (at

Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram

Thanks for the feedback. Rob! I'll make the changes and resend the patch (which has now also been updated to work with linux-next).

Re: [PATCH] drivers: nvmem: atmel-secumod: New driver for Atmel Secumod nvram

Thanks for the feedback. Rob! I'll make the changes and resend the patch (which has now also been updated to work with linux-next).

Re: [PATCH v2 12/32] perf/x86/intel/cqm: schedule work for rotation task

On Wed, 11 May 2016, David Carrillo-Cisneros wrote: > Make execution of rotation a delayed_work that does a best effort > to rotate __cqm_min_progress_rate pmonrs per-second in every package. > > Reviewed-by: Stephane Eranian > Signed-off-by: David Carrillo-Cisneros

Re: [PATCH v2 12/32] perf/x86/intel/cqm: schedule work for rotation task

On Wed, 11 May 2016, David Carrillo-Cisneros wrote: > Make execution of rotation a delayed_work that does a best effort > to rotate __cqm_min_progress_rate pmonrs per-second in every package. > > Reviewed-by: Stephane Eranian > Signed-off-by: David Carrillo-Cisneros > --- >

Re: TODO Lists

On Tue, May 17, 2016 at 03:17:27PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, May 06, 2016 at 10:08:03AM -0700, Darren Hart escreveu: > > At kernel summit Greg suggested sending our TODO lists to him. We'd like to > > have > > a place to keep a feature wishlist and cleanups that aren't

Re: TODO Lists

On Tue, May 17, 2016 at 03:17:27PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, May 06, 2016 at 10:08:03AM -0700, Darren Hart escreveu: > > At kernel summit Greg suggested sending our TODO lists to him. We'd like to > > have > > a place to keep a feature wishlist and cleanups that aren't

Re: [PATCH v2 10/32] perf/x86/intel/cqm: introduce (I)state and limbo prmids

On Wed, 11 May 2016, David Carrillo-Cisneros wrote: > static inline bool __pmonr__in_astate(struct pmonr *pmonr) > { > lockdep_assert_held(&__pkg_data(pmonr, pkg_data_lock)); > - return pmonr->prmid; > + return pmonr->prmid && !pmonr->ancestor_pmonr; > } > > static inline bool

Re: [PATCH v2 10/32] perf/x86/intel/cqm: introduce (I)state and limbo prmids

On Wed, 11 May 2016, David Carrillo-Cisneros wrote: > static inline bool __pmonr__in_astate(struct pmonr *pmonr) > { > lockdep_assert_held(&__pkg_data(pmonr, pkg_data_lock)); > - return pmonr->prmid; > + return pmonr->prmid && !pmonr->ancestor_pmonr; > } > > static inline bool

Re: [PATCH v1] PM / sleep: make pm notifier called symmetrically

On Wed, May 18, 2016 at 8:07 AM, Lianwei Wang wrote: > This makes pm notifier PREPARE/POST symmetrical: if PREPARE > fails, we will only undo what ever happened on PREPARE. > > It fixes the unbalanced cpu hotplug enable in cpu pm notifier. Can you please describe the

Re: [PATCH v1] PM / sleep: make pm notifier called symmetrically

On Wed, May 18, 2016 at 8:07 AM, Lianwei Wang wrote: > This makes pm notifier PREPARE/POST symmetrical: if PREPARE > fails, we will only undo what ever happened on PREPARE. > > It fixes the unbalanced cpu hotplug enable in cpu pm notifier. Can you please describe the problem you're trying to

Re: [PATCH] tty: vt: Fix soft lockup in fbcon cursor blink timer.

On Wed, 18 May 2016, Ming Lei wrote: > On Wed, May 18, 2016 at 4:49 AM, Pavel Machek wrote: > > On Tue 2016-05-17 11:41:04, David Daney wrote: > >> From: David Daney > >> > >> We are getting somewhat random soft lockups with this signature: > >> > >> [

Re: [PATCH] tty: vt: Fix soft lockup in fbcon cursor blink timer.

On Wed, 18 May 2016, Ming Lei wrote: > On Wed, May 18, 2016 at 4:49 AM, Pavel Machek wrote: > > On Tue 2016-05-17 11:41:04, David Daney wrote: > >> From: David Daney > >> > >> We are getting somewhat random soft lockups with this signature: > >> > >> [ 86.992215] [] el1_irq+0xa0/0x10c > >> [

[PATCH 1/1] drm/gma500: mdfld: avoid possible null pointer dereference

Only dereference sender after checking if sender is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c

[PATCH 1/1] drm/gma500: mdfld: avoid possible null pointer dereference

Only dereference sender after checking if sender is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c

Re: [RFC 2/3] drm/mediatek: add support for Mediatek SoC MT2701

On 18 May 2016 at 09:33, YT Shen wrote: >> > @@ -108,6 +108,10 @@ int mtk_drm_gem_dumb_create(struct drm_file >> > *file_priv, struct drm_device *dev, >> > int ret; >> > >> > args->pitch = DIV_ROUND_UP(args->width * args->bpp, 8); >> > + /* >> > +

Re: [RFC 2/3] drm/mediatek: add support for Mediatek SoC MT2701

On 18 May 2016 at 09:33, YT Shen wrote: >> > @@ -108,6 +108,10 @@ int mtk_drm_gem_dumb_create(struct drm_file >> > *file_priv, struct drm_device *dev, >> > int ret; >> > >> > args->pitch = DIV_ROUND_UP(args->width * args->bpp, 8); >> > + /* >> > + * align to 8 bytes

Re: [RFC PATCH 1/3] asm-generic: io: Add exec versions of ioremap

On Wednesday 18 May 2016 18:51:02 Russell King - ARM Linux wrote: > On Wed, May 18, 2016 at 09:12:20AM -0500, Dave Gerlach wrote: > > Ok thank you for the pointer. I agree, the memremap API looks like a better > > fit for this. I think it likely makes the most sense to still add these > >

Re: [RFC PATCH 1/3] asm-generic: io: Add exec versions of ioremap

On Wednesday 18 May 2016 18:51:02 Russell King - ARM Linux wrote: > On Wed, May 18, 2016 at 09:12:20AM -0500, Dave Gerlach wrote: > > Ok thank you for the pointer. I agree, the memremap API looks like a better > > fit for this. I think it likely makes the most sense to still add these > >

[PATCH] HID: uhid: Fixes a bug with userspace bluetooth stacks, which causes hangs during certain operations

Many devices use userspace bluetooth stacks like BlueZ or Bluedroid in combination with uhid. If any of these stacks is used with a HID device for which the driver performs a HID request as part .probe (or technically another HID operation), this results in a deadlock situation. The deadlock

[PATCH] HID: uhid: Fixes a bug with userspace bluetooth stacks, which causes hangs during certain operations

Many devices use userspace bluetooth stacks like BlueZ or Bluedroid in combination with uhid. If any of these stacks is used with a HID device for which the driver performs a HID request as part .probe (or technically another HID operation), this results in a deadlock situation. The deadlock

new driver for drivers/virt/?

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Wednesday, May 18, 2016 1:27 PM > To: Jes Sorensen > Cc: Kershner, David A; cor...@lwn.net; t...@linutronix.de; > mi...@redhat.com; h...@zytor.com; Arfvidson, Erik; Sell, Timothy C; > hof...@osadl.org;

new driver for drivers/virt/?

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Wednesday, May 18, 2016 1:27 PM > To: Jes Sorensen > Cc: Kershner, David A; cor...@lwn.net; t...@linutronix.de; > mi...@redhat.com; h...@zytor.com; Arfvidson, Erik; Sell, Timothy C; > hof...@osadl.org;

Re: livepatch: change to a per-task consistency model

On Wed, 18 May 2016, Josh Poimboeuf wrote: > Yeah, I think this situation -- a task sleeping on an affected function > in uninterruptible state for a long period of time -- would be > exceedingly rare and not something we need to worry about for now. Plus in case task'd be in

Re: livepatch: change to a per-task consistency model

On Wed, 18 May 2016, Josh Poimboeuf wrote: > Yeah, I think this situation -- a task sleeping on an affected function > in uninterruptible state for a long period of time -- would be > exceedingly rare and not something we need to worry about for now. Plus in case task'd be in

Re: [PATCH 1/5] headers_check: don't warn about c++ guards

On 18 May 2016 at 17:07, Arnd Bergmann wrote: > A recent addition to the DRM tree for 4.7 added 'extern "C"' guards > for c++ to all the DRM headers, and that now causes warnings > in 'make headers_check': > > usr/include/drm/amdgpu_drm.h:38: userspace cannot reference function or

Re: [PATCH 1/5] headers_check: don't warn about c++ guards

On 18 May 2016 at 17:07, Arnd Bergmann wrote: > A recent addition to the DRM tree for 4.7 added 'extern "C"' guards > for c++ to all the DRM headers, and that now causes warnings > in 'make headers_check': > > usr/include/drm/amdgpu_drm.h:38: userspace cannot reference function or > variable

[PATCH] drm/mm: avoid possible null pointer dereference

Do not dereference node before the check if node is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/drm_mm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c index 04de6fd..cb39f45 100644

[PATCH] drm/mm: avoid possible null pointer dereference

Do not dereference node before the check if node is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/drm_mm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c index 04de6fd..cb39f45 100644 ---

Re: 4.5-rc0 regression: GPRS breaks after very short while

Hi! > On Wed, May 18, 2016 at 09:49:24AM +0200, Pavel Machek wrote: > > I was afraid another GSM chip desoldered itself in N900, but no, it > > seems to be software this time. > > > > In 4.4, GPRS is rock solid, can survive overnight ping. > > > > In 4.5-rc0 and v4.6, modem fails when I use

Re: 4.5-rc0 regression: GPRS breaks after very short while

Hi! > On Wed, May 18, 2016 at 09:49:24AM +0200, Pavel Machek wrote: > > I was afraid another GSM chip desoldered itself in N900, but no, it > > seems to be software this time. > > > > In 4.4, GPRS is rock solid, can survive overnight ping. > > > > In 4.5-rc0 and v4.6, modem fails when I use

[PATCH] ata: Use IS_ENABLED() instead of checking for built-in or module

The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either built-in or as a module, use that macro instead of open coding the same. Signed-off-by: Javier Martinez Canillas --- drivers/ata/ahci.c | 2 +- drivers/ata/pata_marvell.c | 2 +- 2 files

[PATCH] ata: Use IS_ENABLED() instead of checking for built-in or module

The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either built-in or as a module, use that macro instead of open coding the same. Signed-off-by: Javier Martinez Canillas --- drivers/ata/ahci.c | 2 +- drivers/ata/pata_marvell.c | 2 +- 2 files changed, 2 insertions(+),

Re: [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE

On Wed, 2016-05-18 at 14:29 -0400, Waiman Long wrote: > On 05/18/2016 01:21 PM, Jason Low wrote: > > On Wed, 2016-05-18 at 07:04 -0700, Davidlohr Bueso wrote: > >> On Tue, 17 May 2016, Waiman Long wrote: > >> > >>> Without using WRITE_ONCE(), the compiler can potentially break a > >>> write into

Re: [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE

On Wed, 2016-05-18 at 14:29 -0400, Waiman Long wrote: > On 05/18/2016 01:21 PM, Jason Low wrote: > > On Wed, 2016-05-18 at 07:04 -0700, Davidlohr Bueso wrote: > >> On Tue, 17 May 2016, Waiman Long wrote: > >> > >>> Without using WRITE_ONCE(), the compiler can potentially break a > >>> write into

Re: drivers/of: crash on boot

ce: [0.00] Unable to handle kernel NULL pointer dereference at virtual address 0058 [0.00] pgd = 08cb4000 [0.00] [0058] *pgd=00013fffe003, *pud=00013fffd003, *pmd= [0.00] Internal error: Oops: 9604 [#1] PREEMPT SMP [0.000

Re: drivers/of: crash on boot

ble to handle kernel NULL pointer dereference at virtual address 0058 [0.00] pgd = 08cb4000 [0.00] [0058] *pgd=00013fffe003, *pud=00013fffd003, *pmd= [0.00] Internal error: Oops: 9604 [#1] PREEMPT SMP [0.00] Modules linked in: [0.

Re: [PATCH 3/3] introduce task_rcu_dereference()

On 05/18, Peter Zijlstra wrote: > > OK, something like so then? Yes thanks! Just one note, > +struct task_struct *task_rcu_dereference(struct task_struct **ptask) > +{ > + struct sighand_struct *sighand; > + struct task_struct *task; > + > + /* > + * We need to verify that

Re: [PATCH 3/3] introduce task_rcu_dereference()

On 05/18, Peter Zijlstra wrote: > > OK, something like so then? Yes thanks! Just one note, > +struct task_struct *task_rcu_dereference(struct task_struct **ptask) > +{ > + struct sighand_struct *sighand; > + struct task_struct *task; > + > + /* > + * We need to verify that

Re: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts.

-ERUNONSUBJECT -- Steve On Tue, 17 May 2016 21:31:14 +0530 Soumya PN wrote: > In ftrace.c inside the function alloc_retstack_tasklist()(which will be > invoked when function_graph tracing is on) the tasklist_lock is being > held as reader while iterating through list of

Re: [PATCH] ftrace: As disabling interrupts is costly and write_lock variant of tasklist_lock is not held from interrupt context it is not necessary to disable interrupts.

-ERUNONSUBJECT -- Steve On Tue, 17 May 2016 21:31:14 +0530 Soumya PN wrote: > In ftrace.c inside the function alloc_retstack_tasklist()(which will be > invoked when function_graph tracing is on) the tasklist_lock is being > held as reader while iterating through list of threads. Here the

Re: [PATCH v2 09/32] perf/x86/intel/cqm: basic RMID hierarchy with per package RMIDs

On Wed, 11 May 2016, David Carrillo-Cisneros wrote: > /* > * A cache groups is a group of perf_events with the same target (thread, > * cgroup, CPU or system-wide). Each cache group receives has one RMID. > @@ -80,8 +85,68 @@ static inline int __cqm_prmid_update(struct prmid *prmid, > static

Re: [PATCH v2 09/32] perf/x86/intel/cqm: basic RMID hierarchy with per package RMIDs

On Wed, 11 May 2016, David Carrillo-Cisneros wrote: > /* > * A cache groups is a group of perf_events with the same target (thread, > * cgroup, CPU or system-wide). Each cache group receives has one RMID. > @@ -80,8 +85,68 @@ static inline int __cqm_prmid_update(struct prmid *prmid, > static

Re: drivers/of: crash on boot

On Wed, May 18, 2016 at 10:34 AM, Sasha Levin wrote: > Hi Rhyland, > > I'm seeing a crash on boot that seems to have been caused by > "drivers/of: Fix depth when unflattening devicetree": > > [ 61.145229] >

Re: drivers/of: crash on boot

On Wed, May 18, 2016 at 10:34 AM, Sasha Levin wrote: > Hi Rhyland, > > I'm seeing a crash on boot that seems to have been caused by > "drivers/of: Fix depth when unflattening devicetree": > > [ 61.145229] > == > > [ 61.147588]

Re: [PATCH] remove unused blkdev_dax_capable() function

On Wed, May 18, 2016 at 09:54:08AM +0200, Arnd Bergmann wrote: > The change from blkdev_dax_capable() to bdev_dax_capable() removed the only > user > of the former, so we now get a build warning: > > fs/block_dev.c:1244:13: error: 'blkdev_dax_capable' defined but not used >

Re: [PATCH] remove unused blkdev_dax_capable() function

On Wed, May 18, 2016 at 09:54:08AM +0200, Arnd Bergmann wrote: > The change from blkdev_dax_capable() to bdev_dax_capable() removed the only > user > of the former, so we now get a build warning: > > fs/block_dev.c:1244:13: error: 'blkdev_dax_capable' defined but not used >

Re: [PATCH] Fix for hang of Ordered task in TCM

On 5/18/16 12:53 AM, Nicholas A. Bellinger wrote: Hi Michael, On Fri, 2016-05-13 at 17:15 -0500, Michael Cyr wrote: If a command with a Simple task attribute is failed due to a Unit Attention, then a subsequent command with an Ordered task attribute will hang forever. The reason for this is

Re: [PATCH] Fix for hang of Ordered task in TCM

On 5/18/16 12:53 AM, Nicholas A. Bellinger wrote: Hi Michael, On Fri, 2016-05-13 at 17:15 -0500, Michael Cyr wrote: If a command with a Simple task attribute is failed due to a Unit Attention, then a subsequent command with an Ordered task attribute will hang forever. The reason for this is

Re: [Xen-devel] [PATCH] x86, locking: Remove ticket (spin)lock implementation

On Wed, May 18, 2016 at 03:13:44PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, May 18, 2016 at 08:43:02PM +0200, Peter Zijlstra wrote: > > > > We've unconditionally used the queued spinlock for many releases now. > > Like since 4.2? Yeah, that seems to be the right number. > I don't know of

Re: [Xen-devel] [PATCH] x86, locking: Remove ticket (spin)lock implementation

On Wed, May 18, 2016 at 03:13:44PM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, May 18, 2016 at 08:43:02PM +0200, Peter Zijlstra wrote: > > > > We've unconditionally used the queued spinlock for many releases now. > > Like since 4.2? Yeah, that seems to be the right number. > I don't know of

[PATCH] iwlwifi: mvm: fix merge damage in tx.c

From: Luca Coelho During the merge in commit 909b27f70643 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net"), there was a small merge damage where one instance of info was not converted into skb_info. Fix this. Signed-off-by: Luca Coelho

[PATCH] iwlwifi: mvm: fix merge damage in tx.c

From: Luca Coelho During the merge in commit 909b27f70643 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net"), there was a small merge damage where one instance of info was not converted into skb_info. Fix this. Signed-off-by: Luca Coelho ---

Re: [RFC PATCH 2/3] mmc: host: omap_hsmmc: Enable ADMA2

* Peter Ujfalusi [160518 03:26]: > On 05/18/16 11:45, Kishon Vijay Abraham I wrote: > > omap hsmmc host controller has ADMA2 feature. Enable it here > > for better read and write throughput. Add a new dt binding > > "ti,use_adma" to enable ADMA2. > > > > Signed-off-by:

Re: [RFC PATCH 2/3] mmc: host: omap_hsmmc: Enable ADMA2

* Peter Ujfalusi [160518 03:26]: > On 05/18/16 11:45, Kishon Vijay Abraham I wrote: > > omap hsmmc host controller has ADMA2 feature. Enable it here > > for better read and write throughput. Add a new dt binding > > "ti,use_adma" to enable ADMA2. > > > > Signed-off-by: Kishon Vijay Abraham I >

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