Re: [patch 13/16] x86/ldt: Introduce LDT write fault handler

On Tue, 12 Dec 2017, Linus Torvalds wrote: > On Tue, Dec 12, 2017 at 9:32 AM, Thomas Gleixner wrote: > > From: Thomas Gleixner > > > > When the LDT is mapped RO, the CPU will write fault the first time it uses > > a segment descriptor in order to set the

[PATCH 2/2] crypto: seqiv - Remove unused alg/spawn variable

This patch remove two unused variable and some dead "code" using it. Fixes: 92932d03c2b3 ("crypto: seqiv - Remove AEAD compatibility code") Signed-off-by: Corentin Labbe --- crypto/seqiv.c | 5 - 1 file changed, 5 deletions(-) diff --git a/crypto/seqiv.c

[PATCH 1/2] crypto: echainiv - Remove unused alg/spawn variable

This patch remove two unused variable and some dead "code" using it. Fixes: 66008d4230f6 ("crypto: echainiv - Remove AEAD compatibility code") Signed-off-by: Corentin Labbe --- crypto/echainiv.c | 5 - 1 file changed, 5 deletions(-) diff --git a/crypto/echainiv.c

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, Dec 12, 2017 at 06:20:02AM +, Al Viro wrote: > Umm... What's wrong with > > #define FIELD_FOO 0,4 > #define FIELD_BAR 6,12 > #define FIELD_BAZ 18,14 > > A macro can bloody well expand to any sequence of tokens - le32_get_bits(v, > FIELD_BAZ) > will become le32_get_bits(v, 18, 14)

Re: System-wide hard RLIMIT_STACK in 4.14.4+ w/ SELinux

On 12/12/2017 11:23 AM, Kees Cook wrote: On Tue, Dec 12, 2017 at 2:58 AM, Tomáš Trnka wrote: Hello, Commit 04e35f4495dd560db30c25efca4eecae8ec8c375 "exec: avoid RLIMIT_STACK races with prlimit()" that made it into 4.14.4 effectively changes the default hard RLIMIT_STACK on

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, 12 Dec 2017 19:45:32 +, Al Viro wrote: > On Tue, Dec 12, 2017 at 06:20:02AM +, Al Viro wrote: > > > Umm... What's wrong with > > > > #define FIELD_FOO 0,4 > > #define FIELD_BAR 6,12 > > #define FIELD_BAZ 18,14 > > > > A macro can bloody well expand to any sequence of tokens -

Re: [PATCH v1 5/7] iio: adc: ina2xx: Use a monotonic clock for delay calculation

On Sun, 10 Dec 2017 21:47:37 +0100 Stefan Brüns wrote: > On Sunday, December 10, 2017 6:31:57 PM CET Jonathan Cameron wrote: > > On Fri, 8 Dec 2017 18:41:50 +0100 > > > > Stefan Brüns wrote: > > > The iio timestamp clock is user

Re: UDL's fbdev doesn't work for user-space apps

Hi Pavel, On Sat, 2017-12-09 at 18:20 +0100, Pavel Machek wrote: > On Mon 2017-12-04 11:50:40, Jose Abreu wrote: > > > > Hi Alexey, > > > > On 04-12-2017 11:32, Alexey Brodkin wrote: > > > > > > My first [probably incorrect] assumption is Xserver requires fbdev > > > (/dev/fbX) > > > and it

Re: [RFC 0/5] Add I3C subsystem

On Mon, 31 Jul 2017 21:17:45 +0200 Wolfram Sang wrote: > Hi Boris, > > > This patch series is a proposal for a new I3C [1] subsystem. > > Nice. Good luck with that! > > Some hi-level comments from me related to I2C. I can't say a lot more > because the specs are not

Re: [PATCH v2 2/3] dt-bindings: Add optional nvmem BD address bindings to ti,wlink-st

On Thu, Dec 07, 2017 at 08:57:39PM -0600, David Lechner wrote: > This adds optional nvmem consumer properties to the ti,wlink-st device tree > bindings to allow specifying the BD address. > > Signed-off-by: David Lechner > --- > > v2 changes: > * Renamed "mac-address" to

Re: [PATCH] KVM: PPC: Book3S HV: Fix pending_pri value in kvmppc_xive_get_icp()

On Tue, 2017-12-12 at 18:23 +0100, Laurent Vivier wrote: > When we migrate a VM from a POWER8 host (XICS) to a POWER9 host > (XICS-on-XIVE), we have an error: > > qemu-kvm: Unable to restore KVM interrupt controller state \ > (0xff00) for CPU 0: Invalid argument > > This is because

Re: [PATCHSET v2] blk-mq: reimplement timeout handling

On 12/12/2017 12:01 PM, Tejun Heo wrote: > Changes from the last version[1] > > - BLK_EH_RESET_TIMER handling fixed. > > - s/request->gstate_seqc/request->gstate_seq/ > > - READ_ONCE() added to blk_mq_rq_udpate_state(). > > - Removed left over blk_clear_rq_complete() invocation from >

Re: [PATCH v2 2/2] dm unstripe: Add documentation for unstripe target

On Tue, Dec 12, 2017 at 01:10:13PM -0500, Mike Snitzer wrote: > On Mon, Dec 11 2017 at 11:00am -0500, > Scott Bauer wrote: > > OK, but I'm left wondering: why doesn't the user avoid striping across > the cores? > > Do the Intel NVMe drives not provide the ability to

Re: [PATCH 1/2] PCI: rcar: Fix use-after-free in probe error path

On Thu, Dec 07, 2017 at 11:15:19AM +0100, Geert Uytterhoeven wrote: > If CONFIG_DEBUG_SLAB=y, and no PCIe card is inserted, the kernel crashes > during probe on r8a7791/koelsch: > > rcar-pcie fe00.pcie: PCIe link down > Unable to handle kernel paging request at virtual address

Re: [PATCH v2] PCI: keystone: fix interrupt-controller-node lookup

On Tue, Dec 12, 2017 at 06:07:31PM +, Lorenzo Pieralisi wrote: > On Tue, Dec 12, 2017 at 11:25:37AM -0600, Bjorn Helgaas wrote: > > On Mon, Dec 11, 2017 at 10:42:33AM +, Lorenzo Pieralisi wrote: > > > On Mon, Dec 11, 2017 at 11:29:55AM +0100, Johan Hovold wrote: > > > > On Fri, Nov 17,

Re: [PATCH net-next v5 2/2] net: thunderx: add timestamping support

On Mon, 2017-12-11 at 15:36 -0800, Richard Cochran wrote: > On Mon, Dec 11, 2017 at 05:14:31PM +0300, Aleksey Makarov wrote: > > @@ -880,6 +889,46 @@ static void nic_pause_frame(struct nicpf *nic, int vf, > > struct pfc *cfg) > > } > > } > > > > +/* Enable or disable HW timestamping by BGX

[PATCH] vfio: Simplify capability helper

The vfio_info_add_capability() helper requires the caller to pass a capability ID, which it then uses to fill in header fields, assuming hard coded versions. This makes for an awkward and rigid interface. The only thing we want this helper to do is allocate sufficient space in the caps buffer and

Re: [patch 1/2] mm, mmu_notifier: annotate mmu notifiers with blockable invalidate callbacks

On Mon, Dec 11, 2017 at 02:11:55PM -0800, David Rientjes wrote: > --- a/drivers/misc/sgi-gru/grutlbpurge.c > +++ b/drivers/misc/sgi-gru/grutlbpurge.c > @@ -298,6 +298,7 @@ struct gru_mm_struct *gru_register_mmu_notifier(void) > return ERR_PTR(-ENOMEM); >

Re: [PATCH v3 29/33] dt-bindings: nds32 CPU Bindings

On Fri, Dec 08, 2017 at 05:12:12PM +0800, Greentime Hu wrote: > From: Greentime Hu > > This patch adds nds32 CPU binding documents. > > Signed-off-by: Vincent Chen > Signed-off-by: Rick Chen > Signed-off-by: Zong Li

Re: [patch 13/16] x86/ldt: Introduce LDT write fault handler

On Tue, 12 Dec 2017, Dave Hansen wrote: > On 12/12/2017 11:21 AM, Thomas Gleixner wrote: > > The only critical interaction is the return to user path (user CS/SS) and > > we made sure with the LAR touching that these are precached in the CPU > > before we go into fragile exit code. > > How do we

Re: [PATCH v4 08/12] clk: qcom: Add KPSS ACC/GCC driver

On Fri, Dec 08, 2017 at 03:12:26PM +0530, Sricharan R wrote: > From: Stephen Boyd > > The ACC and GCC regions present in KPSSv1 contain registers to > control clocks and power to each Krait CPU and L2. For CPUfreq > purposes probe these devices and expose a mux clock that

Re: [PATCH v4 05/12] clk: qcom: Add MSM8960/APQ8064's HFPLLs

On Fri, Dec 08, 2017 at 03:12:23PM +0530, Sricharan R wrote: > From: Stephen Boyd > > Describe the HFPLLs present on MSM8960 and APQ8064 devices. > > Signed-off-by: Stephen Boyd > --- > drivers/clk/qcom/gcc-msm8960.c | 172 >

Re: [PATCH V2 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support

On Mon, 2017-11-20 at 15:10 +0100, Jiri Olsa wrote: > On Fri, Nov 17, 2017 at 05:54:05PM -0800, Megha Dey wrote: > > SNIP > > > +/* Branch Monitoring default and mask values */ > > +#define BM_MAX_WINDOW_SIZE 0x3ff > > +#define BM_MAX_THRESHOLD 0x7f > > +#define BM_MAX_EVENTS

Re: [PATCH V2 3/3] x86, bm: Add documentation on Intel Branch Monitoring

On Mon, 2017-11-20 at 15:07 +0100, Jiri Olsa wrote: > On Fri, Nov 17, 2017 at 05:54:06PM -0800, Megha Dey wrote: > > SNIP > > > +IV. User-configurable inputs > > + > > + > > +Several sysfs entries are provided in /sys/devices/intel_bm/ to configure > > +controls for

linux-next: Signed-off-by missing for commit in the usb.current tree

Hi Greg, Commit 32fd87b3bbf5 ("USB: core: only clean up what we allocated") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell

Re: [PATCH v1] scripts/decodecode: Make it take multiline Code line

On Tue, 12 Dec 2017 12:03:23 +0200 Andy Shevchenko wrote: > In case of running scripts/decodecode without any parameters in order to give > a > copy'n'pasted Code line from, for example, email it would parse only first > line > of it, while in emails it's

Re: [PATCH v4 09/12] clk: qcom: Add Krait clock controller driver

On Fri, Dec 08, 2017 at 03:12:27PM +0530, Sricharan R wrote: > From: Stephen Boyd > > The Krait CPU clocks are made up of a primary mux and secondary > mux for each CPU and the L2, controlled via cp15 accessors. For > Kraits within KPSSv1 each secondary mux accepts a

Re: WARNING in lock_release

On Mon, Nov 20, 2017 at 05:24:00AM -0800, syzbot wrote: > Hello, > > syzbot has tested the proposed patch and the reproducer did not > trigger crash: > > Tested-by: syzbot > > Once the fix is committed, please reply to this email with: > #syz fix: exact-commit-title

Re: [PATCH v3 1/8] SOC: brcmstb: add memory API

On Tue, Dec 5, 2017 at 3:59 PM, Bjorn Helgaas wrote: > On Tue, Nov 14, 2017 at 05:12:05PM -0500, Jim Quinlan wrote: >> From: Florian Fainelli >> >> This commit adds a memory API suitable for ascertaining the sizes of >> each of the N memory controllers

Re: arm64: unhandled level 0 translation fault

Hi Will, On Tue, Dec 12, 2017 at 5:57 PM, Will Deacon wrote: > On Tue, Dec 12, 2017 at 05:00:33PM +0100, Geert Uytterhoeven wrote: >> On Tue, Dec 12, 2017 at 4:11 PM, Geert Uytterhoeven >> wrote: >> > On Tue, Dec 12, 2017 at 11:36 AM, Will Deacon

Re: [PATCH V2 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support

On Mon, 2017-11-20 at 12:57 +0100, Peter Zijlstra wrote: > On Fri, Nov 17, 2017 at 05:54:05PM -0800, Megha Dey wrote: > > + mutex_lock(_counter_mutex); > > + for (i = 0; i < BM_MAX_COUNTERS; i++) { > > + if (bm_counter_owner[i] == NULL) { > > + counter_to_use = i; >

Re: [PATCH v2] eeprom: at25: Add DT support for EEPROMs with odd address bits

On Fri, Dec 08, 2017 at 02:46:41PM +0100, Geert Uytterhoeven wrote: > Certain EEPROMS have a size that is larger than the number of address > bytes would allow, and store the MSB of the address in bit 3 of the > instruction byte. > > This can be described in platform data using

Re: [PATCH] au0828: fix use-after-free at USB probing

Hey Andrey, Quoting Andrey Konovalov : On Thu, Nov 23, 2017 at 2:31 AM, Gustavo A. R. Silva wrote: Hi Andrey, I have successfully installed and tested syzkaller with QEMU. Can you please tell me how to reproduce this bug or share with me the

Re: [PATCH] drm/i915/gvt/fb_decoder: Fix out-of-bounds read

Hi Zhenyu, Quoting Zhenyu Wang : On 2017.12.09 00:37:59 -0600, Gustavo A. R. Silva wrote: In case function skl_format_to_drm returns -EINVAL, fmt turns into a huge number as fmt is of type u32, hence there is an out-of-bounds read when using fmt as an index for array

Re: WARNING in mark_buffer_dirty

On Wed, Nov 15, 2017 at 11:46:00PM -0800, syzbot wrote: > WARNING: CPU: 3 PID: 13366 at fs/buffer.c:1108 > mark_buffer_dirty+0x48b/0x5d0 fs/buffer.c:1108 > Kernel panic - not syncing: panic_on_warn set ... > > hub 1-0:1.0: activate --> -22 > CPU: 3 PID: 13366 Comm: syzkaller183798 Not tainted >

linux-next: error while fetching the spi-nor tree

Hi Cyrille, Fetching the spi-nor tree (git://git.infradead.org/l2-mtd.git#spi-nor/next) this morning, I get theses errors: remote: error: Could not read 6e408e3aa1643624ea7da50ad5b27a226a16a654 remote: fatal: bad tree object 6e408e3aa1643624ea7da50ad5b27a226a16a654 remote: aborting due to

Re: [PATCH net-next] net: dsa: lan9303: Introduce lan9303_read_wait

Hi Vivien. Den 12. des. 2017 19:08, skrev Vivien Didelot: Hi Egil, Egil Hjelmeland writes: Simplify lan9303_indirect_phy_wait_for_completion() and lan9303_switch_wait_for_completion() by using a new function lan9303_read_wait() Signed-off-by: Egil Hjelmeland

Re: [PATCH v11 2/2] leds: lm3692x: Introduce LM3692x dual string driver

Hi Dan, Thanks for the updated patch set. I found two minor issues but fixed them by myself and applied both patches to the for-next branch of linux-leds.git. Please refer below and let me know if you have any objections to my amendments. On 12/12/2017 07:15 PM, Dan Murphy wrote: > Introducing

Re: KASAN: stack-out-of-bounds Read in xfrm_state_find (3)

Hi Steffen, On Fri, Dec 01, 2017 at 08:27:43AM +0100, Steffen Klassert wrote: > On Wed, Nov 22, 2017 at 08:05:00AM -0800, syzbot wrote: > > syzkaller has found reproducer for the following crash on > > 0c86a6bd85ff0629cd2c5141027fc1c8bb6cde9c > >

Re: linux-next: Signed-off-by missing for commit in the usb.current tree

On Tue, Dec 12, 2017 at 9:50 PM, Stephen Rothwell wrote: > Hi Greg, > > Commit > > 32fd87b3bbf5 ("USB: core: only clean up what we allocated") > > is missing a Signed-off-by from its author. AFAIU, Alan has a better patch ("USB: core: prevent malicious bNumInterfaces

linux-next: the drivers-x86 tree has moved?

Hi Darren, I noticed commit 960652046899 ("MAINTAINERS: Update tree for platform-drivers-x86") Should I also change linu-next to use the new tree? -- Cheers, Stephen Rothwell

Re: [PATCH 1/1] dt-bindings: arm: document supported STM32 SoC family

On Fri, Dec 08, 2017 at 02:56:34PM +0100, Ludovic Barre wrote: > From: Ludovic Barre > > This adds a list of supported STM32 SoC bindings. > > Signed-off-by: Gwenael Treuveur > Signed-off-by: Ludovic Barre > --- >

[PATCH v3 net-next] net: ethernet: ti: cpdma: correct error handling for chan create

It's not correct to return NULL when that is actually an error and function returns errors in any other wrong case. In the same time, the cpsw driver and davinci emac doesn't check error case while creating channel and it can miss actual error. Also remove WARNs replacing them on dev_err msgs.

Re: UDL's fbdev doesn't work for user-space apps

On Tue 2017-12-12 19:48:05, Alexey Brodkin wrote: > Hi Pavel, > > On Sat, 2017-12-09 at 18:20 +0100, Pavel Machek wrote: > > On Mon 2017-12-04 11:50:40, Jose Abreu wrote: > > > > > > Hi Alexey, > > > > > > On 04-12-2017 11:32, Alexey Brodkin wrote: > > > > > > > > My first [probably incorrect]

Re: [PATCH v3 1/8] SOC: brcmstb: add memory API

[+cc Lorenzo] On Tue, Dec 12, 2017 at 03:53:28PM -0500, Jim Quinlan wrote: > On Tue, Dec 5, 2017 at 3:59 PM, Bjorn Helgaas wrote: > > On Tue, Nov 14, 2017 at 05:12:05PM -0500, Jim Quinlan wrote: > >> From: Florian Fainelli > >> > >> This commit adds a

Re: [PATCH v3 3/6] leds: lp8860: Update the dt parsing for LED labeling

Hi Dan, Thanks for the patch set. On 12/12/2017 07:58 PM, Dan Murphy wrote: > Update the DT parsing for the label node so that > the label is retrieved from the device child as > opposed to being part of the parent. > > This will align this driver with the LED > binding documentation > >

Re: linux-next: Signed-off-by missing for commit in the usb.current tree

On Wed, Dec 13, 2017 at 07:50:57AM +1100, Stephen Rothwell wrote: > Hi Greg, > > Commit > > 32fd87b3bbf5 ("USB: core: only clean up what we allocated") > > is missing a Signed-off-by from its author. Yeah, due to how it got to me, that makes sense, thanks for the notice. I really gotta go

Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

OK, I built a kernel 4.14.5 from vanilla kernel.org sources using the Fedora .config (couldn't get the Fedora package to build). I see no difference with both [0, 1] patches applied and the tpm modules loaded -- no keyboard or touchpad. [Note: I'm not *consciously* using the TPM for anything,

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

On Tue, Dec 12, 2017 at 09:10:11AM -0500, David Miller wrote: > From: Willem de Bruijn > Date: Mon, 11 Dec 2017 16:56:56 -0500 > > > On Mon, Dec 11, 2017 at 4:44 PM, Greg Kroah-Hartman > > wrote: > >> On Mon, Dec 11, 2017 at

Re: WARNING in kmalloc_slab (3)

On Mon, Dec 04, 2017 at 12:26:32PM +0300, Dan Carpenter wrote: > On Mon, Dec 04, 2017 at 09:18:05AM +0100, Dmitry Vyukov wrote: > > On Mon, Dec 4, 2017 at 9:14 AM, Dan Carpenter > > wrote: > > > On Sun, Dec 03, 2017 at 12:16:08PM -0800, Eric Biggers wrote: > > >> Looks

Re: linux-next: error while fetching the spi-nor tree

Hi Stephen, I've just added 2 commits about 8 hours ago, nothing special. Could the issue be explained by an unlikely bad timing? I don't see anything wrong when fetching the tree or when browsing the web server: http://git.infradead.org/l2-mtd.git/shortlog/refs/heads/spi-nor/next Please, let

Re: possible deadlock in fifo_open

On Fri, Dec 01, 2017 at 04:53:01AM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

Re: [linux-sunxi] [PATCH v2 3/6] ARM: sun4i: Convert to CCU

On Tue, Dec 12, 2017 at 9:26 AM, Priit Laes wrote: > On Mon, Dec 11, 2017 at 02:22:30PM -0800, Kevin Hilman wrote: >> On Sun, Mar 26, 2017 at 10:20 AM, Priit Laes wrote: >> > Convert sun4i-a10.dtsi to new CCU driver. >> > >> > Signed-off-by: Priit Laes

Re: possible deadlock in do_io_accounting

On Mon, Dec 04, 2017 at 10:41:01AM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

Re: [patch 1/2] mm, mmu_notifier: annotate mmu notifiers with blockable invalidate callbacks

On Tue, 12 Dec 2017, Dimitri Sivanich wrote: > > --- a/drivers/misc/sgi-gru/grutlbpurge.c > > +++ b/drivers/misc/sgi-gru/grutlbpurge.c > > @@ -298,6 +298,7 @@ struct gru_mm_struct *gru_register_mmu_notifier(void) > > return ERR_PTR(-ENOMEM); > > STAT(gms_alloc); >

Re: [PATCH v3 3/6] leds: lp8860: Update the dt parsing for LED labeling

Jacek On 12/12/2017 03:13 PM, Jacek Anaszewski wrote: > Hi Dan, > > Thanks for the patch set. > > On 12/12/2017 07:58 PM, Dan Murphy wrote: >> Update the DT parsing for the label node so that >> the label is retrieved from the device child as >> opposed to being part of the parent. >> >> This

Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

Re: [PATCH v5] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

On Tue, Dec 12, 2017 at 04:32:54PM +, Mark Brown wrote: > On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote: > > Currently there is no support for the TSCS42xx audio CODEC. > > > > Add support for it. > > > > v5 attempts to address all issues raised in the previous reviews. > >

[PATCH] ARM: exynos_defconfig - enable CONFIG_EXYNOS_IOMMU

EXYNOS_IOMMU is disabled in exynos_defconfig since it is known to cause boot failures on Exynos Chrome-books. The recommendation is for IOMMU to be enabled manually on systems as needed. A recent exynos_drm change added a warning message when EXYNOS_IOMMU is disabled. It is necessary to enable it

Re: [intel-sgx-kernel-dev] [PATCH v7 4/8] intel_sgx: driver for Intel Software Guard Extensions

On Thu, 2017-12-07 at 18:05 +0200, Jarkko Sakkinen wrote: > On Thu, Dec 07, 2017 at 02:46:39PM +, Christopherson, Sean J wrote: > > > > > > > > + for (i = 0; i < 2; i++) { > > > + va_page = list_first_entry(>va_pages, > > > +    struct sgx_va_page,

Re: [patch 13/16] x86/ldt: Introduce LDT write fault handler

On Tue, Dec 12, 2017 at 12:37 PM, Thomas Gleixner wrote: > On Tue, 12 Dec 2017, Dave Hansen wrote: > >> On 12/12/2017 11:21 AM, Thomas Gleixner wrote: >> > The only critical interaction is the return to user path (user CS/SS) and >> > we made sure with the LAR touching that

Re: [PATCH v1] clk: tegra20: Add 216 MHz entry for PLL_X

On 12.12.2017 18:17, Peter De Schrijver wrote: > On Tue, Dec 12, 2017 at 03:08:08PM +0300, Dmitry Osipenko wrote: >> On 12.12.2017 13:02, Peter De Schrijver wrote: >>> On Mon, Dec 11, 2017 at 09:50:09PM +0300, Dmitry Osipenko wrote: The cpufreq driver uses 216 MHz as the lowest CPU clock

Re: [PATCH 2/6] blk-mq: replace timeout synchronization with a RCU and generation based scheme

On Tue, 2017-12-12 at 11:01 -0800, Tejun Heo wrote: > +/* > + * Bits for request->gstate. The lower two bits carry MQ_RQ_* state value > + * and the upper bits the generation number. > + */ > +enum mq_rq_state { > + MQ_RQ_IDLE = 0, > + MQ_RQ_IN_FLIGHT = 1, > + > +

Re: [PATCHSET v2] blk-mq: reimplement timeout handling

Hello, Jens. On Tue, Dec 12, 2017 at 01:23:01PM -0700, Jens Axboe wrote: > I like this a lot, it's a lot less fragile and more intuitive/readable > than what we have now. And apparently less error prone... I'll do > some testing with this. Great. > BTW, since youadd a few more BLK_MQ_F_BLOCKING

Re: [patch 13/16] x86/ldt: Introduce LDT write fault handler

On Tue, 12 Dec 2017, Thomas Gleixner wrote: > On Tue, 12 Dec 2017, Dave Hansen wrote: > > > On 12/12/2017 11:21 AM, Thomas Gleixner wrote: > > > The only critical interaction is the return to user path (user CS/SS) and > > > we made sure with the LAR touching that these are precached in the CPU >

Re: [PATCH v3 net-next] net: ethernet: ti: cpdma: correct error handling for chan create

On 12/12/2017 03:06 PM, Ivan Khoronzhuk wrote: It's not correct to return NULL when that is actually an error and function returns errors in any other wrong case. In the same time, the cpsw driver and davinci emac doesn't check error case while creating channel and it can miss actual error.

Re: [patch 13/16] x86/ldt: Introduce LDT write fault handler

On Tue, 12 Dec 2017, Andy Lutomirski wrote: > On Tue, Dec 12, 2017 at 12:37 PM, Thomas Gleixner wrote: > > On Tue, 12 Dec 2017, Dave Hansen wrote: > > > >> On 12/12/2017 11:21 AM, Thomas Gleixner wrote: > >> > The only critical interaction is the return to user path (user

[PATCH 0/8] target-iSCSI: Adjustments for several function implementations

From: Markus Elfring Date: Tue, 12 Dec 2017 22:22:11 +0100 Some update suggestions were taken into account from static source code analysis. Markus Elfring (8): Less function calls in chap_server_compute_md5() after error detection Move resetting of seven

[PATCH 1/8] target/iscsi: Less function calls in chap_server_compute_md5() after error detection

From: Markus Elfring Date: Tue, 12 Dec 2017 18:00:41 +0100 The functions "crypto_free_shash", "kfree" and "kzfree" were called in a few cases by the chap_server_compute_md5() function during error handling even if the passed variable contained a null pointer. *

Re: [PATCH 2/6] blk-mq: replace timeout synchronization with a RCU and generation based scheme

Hello, Bart. On Tue, Dec 12, 2017 at 09:37:11PM +, Bart Van Assche wrote: > Have you considered the following instead of introducing MQ_RQ_IDLE and > MQ_RQ_IN_FLIGHT? I think this could help to limit the number of new atomic > operations introduced in the hot path by this patch series. But

[PATCH 2/8] target/iscsi: Move resetting of seven variables in chap_server_compute_md5()

From: Markus Elfring Date: Tue, 12 Dec 2017 19:43:47 +0100 Move the resetting of these array variables so that this operation will be performed only if memory allocations succeeded before in this function. Signed-off-by: Markus Elfring

Re: [patch 13/16] x86/ldt: Introduce LDT write fault handler

On Tue, 12 Dec 2017, Thomas Gleixner wrote: > On Tue, 12 Dec 2017, Thomas Gleixner wrote: > > On Tue, 12 Dec 2017, Dave Hansen wrote: > > > > > On 12/12/2017 11:21 AM, Thomas Gleixner wrote: > > > > The only critical interaction is the return to user path (user CS/SS) > > > > and > > > > we

[PATCH 3/8] target/iscsi: Delete 36 error messages for a failed memory allocation

From: Markus Elfring Date: Tue, 12 Dec 2017 21:07:16 +0100 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 4/8] target/iscsi: Delete an unnecessary variable initialisation in iscsit_allocate_ooo_cmdsn()

From: Markus Elfring Date: Tue, 12 Dec 2017 21:13:49 +0100 The local variable "ooo_cmdsn" will be reassigned by a following statement. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 5/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_copy_param_list()

From: Markus Elfring Date: Tue, 12 Dec 2017 21:15:55 +0100 The variable "param_list" will be reassigned by a following statement. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

Re: [intel-sgx-kernel-dev] [PATCH v7 4/8] intel_sgx: driver for Intel Software Guard Extensions

On Fri, 2017-12-08 at 07:31 -0800, Christopherson, Sean J wrote: > Jarkko Sakkinen wrote: > > On Thu, Dec 07, 2017 at 02:46:39PM +, Christopherson, Sean J wrote: > > > > + for (i = 0; i < 2; i++) { > > > > + va_page = list_first_entry(>va_pages, > > >

[PATCH 6/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_create_default_params()

From: Markus Elfring Date: Tue, 12 Dec 2017 21:18:39 +0100 The variable "param" will eventually be set to an appropriate pointer a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[RFC PATCH 1/2] dt: bindings: as3645a: Update dt node example with standard

Update the DT binding to remove the device name from the DT parent node as well as removing the device name from the label. The LED label will be generated based off the id name stored in the local driver so the LED function can be indicated in the label DT entry. Also removed the indentation on

[PATCH] leds: as3645a: Fix checkpatch warnings

Fix two checkpatch warnings for 80 char length and for a quoted string across multiple line warnings. Signed-off-by: Dan Murphy --- drivers/leds/leds-as3645a.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/leds/leds-as3645a.c

[RFC PATCH 2/2] leds: as3645a: Update LED label generation

Generate the LED label based off either the DT label node or off the I2C ID in the i2c device id struct. If the label is used then this should denote the LED function. As an example it would be as3645a: Otherwise if the label is not used the LED label will be as3645a:flash and

[PATCH 7/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_set_default_param()

From: Markus Elfring Date: Tue, 12 Dec 2017 21:21:31 +0100 The local variable "param" will be reassigned by a following statement. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

RE: [PATCH] acpi: acpica: add acpi status check prior walking through namespace

Another way to look at this is that the kernel should not be calling ACPI interfaces if ACPI is disabled. > -Original Message- > From: Vadim Lomovtsev [mailto:vadim.lomovt...@caviumnetworks.com] > Sent: Tuesday, December 12, 2017 7:59 AM > To: Moore, Robert ;

[PATCH 8/8] target/iscsi: Improve 16 size determinations

From: Markus Elfring Date: Tue, 12 Dec 2017 22:06:00 +0100 Replace the specification of data types by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [PATCH 4.14 000/164] 4.14.6-stable review

On 12/12/2017 05:43 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.6 release. > There are 164 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 000/148] 4.9.69-stable review

On 12/12/2017 05:43 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.69 release. > There are 148 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: UDL's fbdev doesn't work for user-space apps

Den 04.12.2017 12.32, skrev Alexey Brodkin: Hello, I'm trying to use DisplayLink USB2.0-to-HDMI adapter as the one and only video output and I want to get Xserver working on top of that. I'm not very familiar with all the parts of Linux GPU/video stack (especially its user-space counterpart)

Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote: > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkal...@googlegroups.com. > Please credit me with: Reported-by: syzbot > > syzbot

[PATCH v3 1/3] Bluetooth: hci_ll: add support for setting public address

This adds support for setting the public address on Texas Instruments Bluetooth chips using a vendor-specific command. This has been tested on a CC2560A chip. The TI wiki also indicates that this command should work on TI WL17xx/WL18xx Bluetooth chips. During review, there was some question as

Re: possible deadlock in proc_pid_attr_write

On Sat, Dec 09, 2017 at 02:43:00AM -0800, syzbot wrote: > > syzbot will keep track of this bug report. > Once a fix for this bug is merged into any tree, reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

[PATCH] Bluetooth: hci_ll: Add optional nvmem BD address source

This adds an optional nvmem consumer to get a BD address from an external source. The BD address is then set in the Bluetooth chip after the firmware has been loaded. This has been tested working with a TI CC2560A chip (in a LEGO MINDSTORMS EV3). Signed-off-by: David Lechner

[PATCH v3 2/3] dt-bindings: Add optional nvmem BD address bindings to ti,wlink-st

This adds optional nvmem consumer properties to the ti,wlink-st device tree bindings to allow specifying the BD address. Reviewed-by: Rob Herring Signed-off-by: David Lechner --- Documentation/devicetree/bindings/net/ti,wilink-st.txt | 5 + 1 file

[PATCH v3 0/3] Bluetooth: hci_ll: Get BD address from NVMEM

This series adds supporting getting the BD address from a NVMEM provider for "LL" HCI controllers (Texas Instruments). v3 changes: * Additional comments on why swapping bytes is needed. * Fixed comment style and trailing whitespace. * Rework error handling for nvmem cell code. v2 changes: *

Re: [RFC 0/5] Add I3C subsystem

> MIPI has opened the I3C spec [1], it can be downloaded here [2]. Wow, that's good news. And so fast. Congrats and thanks a lot! signature.asc Description: PGP signature

[PATCH v4 1/6] dt: bindings: lp8860: Update bindings for lp8860

Update the lp8860 bindings to fix various issues found. Add address-cells and size-cells, rename enable-gpio to enable-gpios, update the node name to the device name and indent the node example. Signed-off-by: Dan Murphy --- v4 - No changes v3 - Indicatd enable-gpios is active

[PATCH v4 6/6] leds: lp8860: Various fixes to align with LED framework

Update the driver to conform with the LED framework. Use devm_led_classdev_register Destroy mutex on exit Remove dependency on CONFIG_OF in the driver and move to the Kconfig Update the MODULE_LICENSE to GPL v2 Remove setting of MAX brightness as the LED framework does this. Signed-off-by: Dan

[PATCH v4 0/6] Updated LP8860 driver series

All v4 - Fix checkpatch warning for code indentation on the leds: lp8860: Update the dt parsing for LED labeling patch. v3 - Made changes to the patch set to address concerns on DT node naming conventions based on discussion in the RFC patch https://patchwork.kernel.org/patch/10089047/ also

[PATCH v4 5/6] leds: lp8860: Add DT parsing to retrieve the trigger node

Add the ability to parse the DT and set the default trigger mode for the LED. Signed-off-by: Dan Murphy --- v4 - No changes v3 - no changes - https://patchwork.kernel.org/patch/10093751/ v2 - no changes drivers/leds/leds-lp8860.c | 4 1 file changed, 4 insertions(+)

[PATCH] staging: pi433: Fix disordered switch case

Case: SHAPING_0_5 is writing DATAMODUL_MODLATION_SHAPE_0_3 value and vice versa Signed-off-by: Kari Argillander --- I have checked that defines are correct accounting to the datasheet. My first patch. Hopefully everything goes like needs to. I do not know if this

[PATCH v4 2/6] dt: bindings: lp8860: Update DT label binding

Update the lp8860 label binding to the LED standard as documented in Documentation/devicetree/bindings/leds/common.txt Signed-off-by: Dan Murphy --- v4 - No changes v3 - Added address and size cells, updated label with color and inserted spaces around the reg node -

[PATCH v4 4/6] dt: bindings: lp8860: Add trigger binding to the lp8860

Add a default trigger optional node to the child node. This will allow the driver to set the trigger for a backlight. Signed-off-by: Dan Murphy --- v4 - No changes v3 - Removed optional and rebased - https://patchwork.kernel.org/patch/10093755/ v2 - Moved binding changes to

  1   2   3   4   5   6   7   8   9   10   >