Re: [PATCH v2 5/6] firmware: Add request_firmware_prefer_user() function

On Fri, Nov 10, 2017 at 10:08:19PM +0100, Pali Rohár wrote: > On Friday 10 November 2017 21:26:01 Luis R. Rodriguez wrote: > > On Fri, Nov 10, 2017 at 12:38:27AM +0100, Pali Rohár wrote: > > > This function works pretty much like request_firmware(), but it prefer > > > usermode helper. If usermode

Re: [PATCH] umh: Optimize 'proc_cap_handler()'

On Fri, Oct 20, 2017 at 09:33:31PM +0200, Christophe JAILLET wrote: > If 'write' is 0, we can avoid a call to spin_lock/spin_unlock. > > Signed-off-by: Christophe JAILLET Thanks for the patch! Acked-by: Luis R. Rodriguez I'll bounce a copy to

Re: [PATCH v6 4/9] i2c: refactor i2c_master_{send_recv}

On Sat, 4 Nov 2017 21:20:04 +0100 Wolfram Sang wrote: > Those two functions are very similar, the only differences are that one > needs the I2C_M_RD flag for its message while the other one needs the > buffer casted to drop the const. Introduce a generic helper

[PATCH] x86, kaiser: fix 32-bit SYSENTER

This is a fix on top of the KAISER [v3] patches I posted earlier. It is a fix for: [PATCH 05/30] x86, kaiser: prepare assembly for entry/exit CR3 switching I made a mistake and stopped running the 32-bit selftests at some point. My changes from one of Borislav's review comments ended

[PATCH 1/3] drm: add connector info/property for non-desktop displays [v2]

From: Dave Airlie This adds the infrastructure needed to quirk displays using edid and to mark them a non-desktop. A non-desktop display is one which shouldn't normally be included as a part of a desktop environment. This is meant to cover head mounted devices like HTC

[PATCH 2/3] drm/fb: add support for not enabling fbcon on non-desktop displays [v2]

From: Dave Airlie We don't want fbcon to get used on non-desktop dislays, don't pass them as enabled connectors to the fb helper setup. This prevents my HMD from getting disorted fbcon, and from affecting other displays console. v2: Change description from non-standard to

[PATCH 0/3] drm: Add connector info/property for non-desktop [v2]

This is the same as the series for non-standard displays but uses the phrase 'non-desktop' instead. No functional changes.

[PATCH 3/3] drm/edid: quirk HTC vive headset as non-desktop. [v2]

From: Dave Airlie This uses the EDID info from my HTC Vive to mark it as non-desktop. v2: Change description from non-standard to non-desktop Signed-off-by: Dave Airlie --- drivers/gpu/drm/drm_edid.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

Re: [kernel-hardening] Re: vDSO maximum stack usage, stack probes, and -fstack-check

> On Nov 10, 2017, at 8:02 AM, Hector Martin 'marcan' wrote: > >> On 2017-11-10 23:57, Andy Lutomirski wrote: >> This code is so wrong I don't even no where to start. Seriously, sub, >> orq, add? How about just orq with an offset? How about a *load* >> instead of a store? > >

Re: [kernel-hardening] Re: vDSO maximum stack usage, stack probes, and -fstack-check

> On Nov 10, 2017, at 8:36 AM, Hector Martin 'marcan' wrote: > >> On 2017-11-11 01:02, Hector Martin 'marcan' wrote: >> Not entirely sure what's going on here. > > Actually, if you think about it, it doesn't matter that it skips the > first page, since it's probing one page

[PATCH] tty: vt: replace _manual_ swap with swap macro in set_selection

Make use of the swap macro instead of _manually_ swapping values and remove unnecessary variable tmp. This makes the code easier to read and maintain. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/tty/vt/selection.c

Re: [RFC PATCH 0/2] x86: Fix missing core serialization on migration

On Fri, Nov 10, 2017 at 1:57 PM, Mathieu Desnoyers wrote: > > That core serializing instruction is not that much about I$ vs D$ > consistency, but rather about the processor speculatively executing code > ahead of its retirement point. Ref. Intel Architecture

[PATCH] staging: speakup: selection: replace _manual_ swap with swap macro

Make use of the swap macro instead of _manually_ swapping values and remove unnecessary variable tmp. This makes the code easier to read and maintain. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva ---

Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl

Hi Michael, Tobin, On 11/08/17 04:10, Michael Ellerman wrote: > "Tobin C. Harding" writes: >> Currently we are leaking addresses from the kernel to user space. This >> script is an attempt to find some of those leakages. Script parses >> `dmesg` output and /proc and /sys files for

Re: [RFC PATCH for 4.15 05/10] x86: Introduce sync_core_before_usermode

- On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote: > On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers > wrote: >> Introduce an architecture function that ensures the current CPU >> issues a core serializing instruction before returning to

Re: [RFC PATCH for 4.15 05/10] x86: Introduce sync_core_before_usermode

> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers > wrote: > > - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote: > >> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers >> wrote: >>> Introduce an

Re: [jump_label_test] WARNING: CPU: 0 PID: 1 at kernel/jump_label.c:761 jump_label_test+0x63/0xab

On Fri, Nov 10, 2017 at 04:32:45PM -0500, Jason Baron wrote: > > On 11/09/2017 03:56 PM, Paul E. McKenney wrote: > > On Thu, Nov 09, 2017 at 03:13:24PM -0500, Jason Baron wrote: > >> On 11/08/2017 02:01 AM, Fengguang Wu wrote: > >>> On Tue, Nov 07, 2017 at 05:17:38PM -0500, Jason Baron wrote: >

Re: [PATCH v6 5/9] i2c: add i2c_master_{send|recv}_dmasafe

On Sat, 4 Nov 2017 21:20:05 +0100 Wolfram Sang wrote: > Use the new helper to create variants of i2c_master_{send|recv} which > mark their buffers as DMA safe. > > Signed-off-by: Wolfram Sang Can't really argue with such a

Re: [PATCH] iio: mma8452: add power_mode sysfs configuration

On Mon, 6 Nov 2017 08:19:58 +0100 Martin Kepplinger wrote: > This adds the power_mode sysfs interface to the device as documented in > sysfs-bus-iio. > > --- > > Note that I explicitely don't sign off on this. > > This is a starting point for anybody who can test it and

Re: [PATCH v4 0/4] fix the clock setting for SAR ADC

On Tue, 7 Nov 2017 22:36:00 +0100 Martin Blumenstingl wrote: > Hi Yixun, > > On Tue, Nov 7, 2017 at 3:09 PM, Yixun Lan wrote: > > patch [1/4]: > > Fix wrong SARADC/SANA clock gate bit in Meson-GXBB/GXL, > > the published

Re: [PATCH v2 1/6] PM / core: Add LEAVE_SUSPENDED driver flag

On Sat, Nov 11, 2017 at 12:45 AM, Rafael J. Wysocki wrote: > On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote: >> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote: >>> From: Rafael J. Wysocki >>>

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

>-Original Message- >From: Jiri Olsa [mailto:jo...@redhat.com] >Sent: Saturday, November 4, 2017 6:26 AM >To: Megha Dey >Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux- >d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com; >h...@zytor.com;

[PATCH 1/4] mm: fix device-dax pud write-faults triggered by get_user_pages()

Currently only get_user_pages_fast() can safely handle the writable gup case due to its use of pud_access_permitted() to check whether the pud entry is writable. In the gup slow path pud_write() is used instead of pud_access_permitted() and to date it has been unimplemented, just calls BUG_ON().

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Fri, Nov 10, 2017 at 03:26:27PM -0800, Patrick McLean wrote: > > > On 2017-11-10 10:42 AM, Linus Torvalds wrote: > > On Thu, Nov 9, 2017 at 5:58 PM, Patrick McLean wrote: > >> > >> Something must have changed since 4.13.8 to trigger this though. > > > > Arnd pointed to

Re: [PATCH] firmware: cleanup - group and document up private firmware parameters

On Mon, Sep 18, 2017 at 05:15:01PM +0200, Greg KH wrote: > On Thu, Sep 14, 2017 at 03:54:22PM -0700, Luis R. Rodriguez wrote: > > +enum fw_priv_reqs { > > + FW_PRIV_REQ_FALLBACK= 1 << 0, > > + FW_PRIV_REQ_FALLBACK_UEVENT = 1 << 1, > > + FW_PRIV_REQ_NO_CACHE

Re: [PATCH v2 1/6] PM / core: Add LEAVE_SUSPENDED driver flag

On Sat, Nov 11, 2017 at 12:45 AM, Rafael J. Wysocki wrote: > On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote: >> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote: [cut] >> Moreover, you should check the return value from

[PATCH] of: Document exactly what of_find_node_by_name() puts

It isn't clear if this function of_node_put()s the 'from' argument, or the node it finds in the search. Clearly indicate which variable is touched. Signed-off-by: Stephen Boyd --- drivers/of/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

RE: [PATCH v17 5/6] vfio: ABI for mdev display dma-buf operation

> -Original Message- > From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On > Behalf Of Gerd Hoffmann > Sent: Friday, November 10, 2017 3:03 PM > To: Alex Williamson > Cc: Tian, Kevin ; Yuan, Hang

Hello,

-- Good day! What is the best way to reach you for business? I am writing you because I have an opportunity to present to you. I have a business that I would like to discuss with you. Waiting to read from you soon. Thank you

Re: [PATCH] clk: hi3660: fix incorrect uart3 clock freqency

On 08/07, Guodong Xu wrote: > From: Zhong Kaihua > > UART3 clock rate is doubled in previous commit. > > This error is not detected until recently a mezzanine board which makes > real use of uart3 port (through LS connector of 96boards) was setup > and tested on

Re: [PATCH] clk: hisilicon: Delete an error message for a failed memory allocation in hisi_register_clkgate_sep()

On 09/26, SF Markus Elfring wrote: > From: Markus Elfring > Date: Tue, 26 Sep 2017 22:00:05 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus

Re: [PATCH 1/1] ALSA: usb: initial USB Audio Device Class 3.0 support

On Thu, Nov 9, 2017 at 10:33 AM, Greg Kroah-Hartman wrote: > On Thu, Nov 09, 2017 at 09:16:52AM +0100, Takashi Iwai wrote: >> On Thu, 09 Nov 2017 09:04:58 +0100, >> Greg Kroah-Hartman wrote: >> > >> > On Wed, Nov 08, 2017 at 03:38:35PM +0100, Takashi Iwai wrote: >> > >

Re: [PATCH] tcp: Export to userspace the TCP state names for the trace events

On Sat, 11 Nov 2017 02:06:00 + Yafang Shao wrote: > 2017-11-10 15:07 GMT+00:00 Steven Rostedt : > > On Fri, 10 Nov 2017 12:56:06 +0800 > > Yafang Shao wrote: > > > >> Could the macro tcp_state_name() be renamed ？ > >> If is

Re: [f2fs-dev] [RFC PATHC 2/2] f2fs: apply write hints to select the type of segment for direct write

On 2017/11/9 13:51, Hyunchul Lee wrote: > From: Hyunchul Lee > > Select the type of the segment using write hints, when blocks are > allocated for direct write. > > There are unhandled corner cases. Hints are not applied in > in-place update. And if the blocks of a file is

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

>-Original Message- >From: Jiri Olsa [mailto:jo...@redhat.com] >Sent: Saturday, November 4, 2017 6:25 AM >To: Megha Dey >Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux- >d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com; >h...@zytor.com;

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

>-Original Message- >From: Jiri Olsa [mailto:jo...@redhat.com] >Sent: Saturday, November 4, 2017 6:25 AM >To: Megha Dey >Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux- >d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com; >h...@zytor.com;

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

>-Original Message- >From: Jiri Olsa [mailto:jo...@redhat.com] >Sent: Saturday, November 4, 2017 6:26 AM >To: Megha Dey >Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux- >d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com; >h...@zytor.com;

Re: [PATCH] random: add regrand

Forgot to Cc: linux-kernel. On Fri, Nov 10, 2017 at 01:30:39PM -0800, Jörn Engel wrote: > Regrand is a replacement for drivers/char/random.c. It is supposed to > achieve the following design goals: > > 1. /dev/random shall never block. > 2. /dev/urandom shall never return bad randomness. > 3.

Re: [PATCH] firmware: cleanup - group and document up private firmware parameters

On Fri, Sep 15, 2017 at 10:30:46AM +0200, Martin Fuzzey wrote: > On 15/09/17 00:54, Luis R. Rodriguez wrote: > > The above benefits makes the code much easier to understand and maintain. > > Yes I agree it is much cleaner that way. > > A couple of nitpicks below. > > > +/** > > + * enum

[PATCHv2] slub: Fix sysfs duplicate filename creation when slub_debug=O

From: Miles Chen When slub_debug=O is set. It is possible to clear debug flags for an "unmergeable" slab cache in kmem_cache_open(). It makes the "unmergeable" cache became "mergeable" in sysfs_slab_add(). These caches will generate their "unique IDs" by

Re: mmotm 2017-11-10-15-56 uploaded (lib/test_find_bit.c)

On 11/10/2017 03:56 PM, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of

Re: [PATCH] staging: speakup: selection: replace _manual_ swap with swap macro

Gustavo A. R. Silva, on ven. 10 nov. 2017 16:13:03 -0600, wrote: > Make use of the swap macro instead of _manually_ swapping values > and remove unnecessary variable tmp. > > This makes the code easier to read and maintain. > > This code was detected with the help of Coccinelle. > >

Re: [PATCH] of: Document exactly what of_find_node_by_name() puts

On 11/10/2017 05:45 PM, Stephen Boyd wrote: > It isn't clear if this function of_node_put()s the 'from' > argument, or the node it finds in the search. Clearly indicate > which variable is touched. > > Signed-off-by: Stephen Boyd > --- > drivers/of/base.c | 2 +- > 1 file

Re: [PATCH v4] af_netlink: ensure that NLMSG_DONE never fails in dumps

IIRC, 4.14 comes tomorrow-ish? If possible, it would be nice to get this in 4.14 before then, so it doesn't have to take time to trickle down through stable. Jason On Thu, Nov 9, 2017 at 1:04 PM, Jason A. Donenfeld wrote: > The way people generally use netlink_dump is that they

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Fri, Nov 10, 2017 at 08:13:06PM -0500, J. Bruce Fields wrote: > On Fri, Nov 10, 2017 at 03:26:27PM -0800, Patrick McLean wrote: > > > > > > On 2017-11-10 10:42 AM, Linus Torvalds wrote: > > > On Thu, Nov 9, 2017 at 5:58 PM, Patrick McLean > > > wrote: > > >> > > >>

Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown

> My assumption here is: > 1) there are some less important and so security-insensitive firmwares, >by which I mean that such firmwares won't be expected to be signed in >terms of vulnerability or integrity. >(I can't give you examples though.) > 2) firmware's signature will be

Re: [PATCH v4] af_netlink: ensure that NLMSG_DONE never fails in dumps

From: "Jason A. Donenfeld" Date: Sat, 11 Nov 2017 11:26:12 +0900 > IIRC, 4.14 comes tomorrow-ish? If possible, it would be nice to get > this in 4.14 before then, so it doesn't have to take time to trickle > down through stable. Jason I'm already pushing my luck as-is with the

Re: [PATCH 1/9] include: Move compat_timespec/ timeval to compat_time.h

On Fri, 10 Nov 2017 14:42:51 -0800 Deepa Dinamani wrote: > diff --git a/arch/x86/include/asm/ftrace.h b/arch/x86/include/asm/ftrace.h > index 09ad88572746..db25aa15b705 100644 > --- a/arch/x86/include/asm/ftrace.h > +++ b/arch/x86/include/asm/ftrace.h > @@ -49,7 +49,7 @@

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

On Wed, 8 Nov 2017 16:43:17 -0800 Patrick McLean wrote: > As of 4.13.11 (and also with 4.14-rc) we have an issue where when > serving nfs4 sometimes we get the following BUG. When this bug happens, > it usually also causes the motherboard to no longer POST until we >

Re: [PATCH v4] af_netlink: ensure that NLMSG_DONE never fails in dumps

On Sat, Nov 11, 2017 at 11:37 AM, David Miller wrote: > Jason I'm already pushing my luck as-is with the pull request I made > yesterday. > > I've seen your original requst to get this in, you don't have to say > it multiple times. > > We can get this into the merge window

Re: [alsa-devel] [PATCH 1/1] ALSA: usb: initial USB Audio Device Class 3.0 support

On Wed, Nov 8, 2017 at 9:38 PM, Pierre-Louis Bossart wrote: > Nice work, thanks! I double-checked all the descriptors and values and > didn't find anything problematic, the main comment I have is that the clock > source/selection could probably be refactored

Lieber Benutzer

Lieber Benutzer Ihre E-Mail-Adresse hat 15 GB überschritten, die vom Webmaster erstellt wurden. Wir haben derzeit 15,3 GB und können in den nächsten 24 Stunden keine neuen Nachrichten senden oder empfangen. Geben Sie Ihre Daten unten ein, um Ihr Konto zu bestätigen und zu aktualisieren:

[RFC 4/7] x86/asm: Fix assumptions that the HW TSS is at the beginning of cpu_tss

I'm going to move SYSENTER_stack to the beginning of cpu_tss to help detect overflow. Before this can happen, I need to fix several code paths that hardcode assumptions about the old layout. Signed-off-by: Andy Lutomirski --- arch/x86/include/asm/desc.h | 2 +-

[RFC 0/7] Prep code for better stack switching

This isn't quite done (the TSS remap patch is busted on 32-bit, but that's a straightforward fix), but it should be ready for at least a conceptual review. The idea here is to prepare us to have all kernel data needed for user mode execution and early entry located in the fixmap. To do this, I

[RFC 3/7] x86/fixmap: Generalize the GDT fixmap mechanism

Currently, the GDT is an ad-hoc array of pages, one per CPU, in the fixmap. Generalize it to be an array of a new struct cpu_entry_area so that we can cleanly add new things to it. Signed-off-by: Andy Lutomirski --- arch/x86/include/asm/desc.h | 9 +

[RFC 5/7] x86/asm: Rearrange struct cpu_tss to enlarge SYSENTER_stack and fix alignment

The Intel SDM says (Volume 3, 7.2.1): Avoid placing a page boundary in the part of the TSS that the processor reads during a task switch (the first 104 bytes). The processor may not correctly perform address translations if a boundary occurs in this area. During a task switch, the

[RFC 6/7] x86/asm: Remap the TSS into the cpu entry area

This has a secondary purpose: it puts the entry stack into a region with a well-controlled layout. A subsequent patch will take advantage of this to streamline the SYSCALL entry code to be able to find it more easily. XXX: This either needs to not happen on 32-bit or we need to fix the 32-bit

[RFC 7/7] x86/unwind/64: Add support for the SYSENTER stack

Signed-off-by: Andy Lutomirski --- arch/x86/include/asm/stacktrace.h | 1 + arch/x86/kernel/dumpstack_32.c| 3 +++ arch/x86/kernel/dumpstack_64.c| 23 +++ 3 files changed, 27 insertions(+) diff --git a/arch/x86/include/asm/stacktrace.h

[RFC 2/7] x86/gdt: Put per-cpu GDT remaps in ascending order

We currently have CPU 0's GDT at the top of the GDT range and higher-numbered CPUs at lower addreses. This happens because the fixmap is upside down (index 0 is the top of the fixmap). Flip it so that GDTs are in ascending order by virtual address. This will simplify a future patch that will

[RFC 1/7] x86/asm/64: Allocate and enable the SYSENTER stack

This will simplify some future code changes that will want some temporary stack space in more places. It also lets us get rid of a SWAPGS_UNSAFE_STACK user. This does not depend on CONFIG_IA32_EMULATION because we'll want the stack space even without IA32 emulation. Signed-off-by: Andy

Re: [RFC 5/7] x86/asm: Rearrange struct cpu_tss to enlarge SYSENTER_stack and fix alignment

On Fri, Nov 10, 2017 at 8:05 PM, Andy Lutomirski wrote: > The Intel SDM says (Volume 3, 7.2.1): > >Avoid placing a page boundary in the part of the TSS that the >processor reads during a task switch (the first 104 bytes). The >processor may not correctly perform

Re: [f2fs-dev] [PATCH] f2fs: validate before set/clear free nat bitmap

On 2017/11/10 15:41, LiFan wrote: > In flush_nat_entries, all dirty nats will be flushed and if > their new address isn't NULL_ADDR, their bitmaps will be updated, > the free_nid_count of the bitmaps will be increaced regardless > of whether the nats have already been occupied before. > This could

[PATCH 3/4] mm: replace pmd_write with pmd_access_permitted in fault + gup paths

The 'access_permitted' helper is used in the gup-fast path and goes beyond the simple _PAGE_RW check to also: * validate that the mapping is writable from a protection keys standpoint * validate that the pte has _PAGE_USER set since all fault paths where pmd_write is must be referencing

[PATCH 4/4] mm: replace pte_write with pte_access_permitted in fault + gup paths

The 'access_permitted' helper is used in the gup-fast path and goes beyond the simple _PAGE_RW check to also: * validate that the mapping is writable from a protection keys standpoint * validate that the pte has _PAGE_USER set since all fault paths where pte_write is must be referencing

[PATCH 2/4] mm: replace pud_write with pud_access_permitted in fault + gup paths

The 'access_permitted' helper is used in the gup-fast path and goes beyond the simple _PAGE_RW check to also: * validate that the mapping is writable from a protection keys standpoint * validate that the pte has _PAGE_USER set since all fault paths where pud_write is must be referencing

[PATCH 0/4] fix device-dax pud crash and fixup {pte,pmd,pud}_write

Andrew, Here is a new version to the pud_write() fix [1], and some follow-on patches to use the '_access_permitted' helpers in fault and get_user_pages() paths where we are checking if the thread has access to write. I explicitly omit conversions for places where the kernel is checking the

[PATCH] usb: ulpi: Add missing of_node_get() in ulpi_of_register()

In ulpi_of_register() we call of_find_node_by_name() which unconditionally calls of_node_put() on the 'from' argument. We haven't called of_node_get() though, so we've put the node once without getting it first. Add the of_node_get() call so that things are properly balanced. Fixes: ef6a7bcfb01c

Re: [PATCH] tcp: Export to userspace the TCP state names for the trace events

2017-11-10 15:07 GMT+00:00 Steven Rostedt : > On Fri, 10 Nov 2017 12:56:06 +0800 > Yafang Shao wrote: > >> Could the macro tcp_state_name() be renamed ？ >> If is included in include/net/tcp.h, it will > > Ideally, you don't want to include

Re: [nfsd4] potentially hardware breaking regression in 4.14-rc and 4.13.11

[ Bringing in the gcc plugin people and the kernel hardening list, since it now is no longer even remotely looking like a nfsd, vfs or filesystem issue any more ] Kees, Emese, the whole thread is on lkml, but there's clearly something horribly wrong with RANDSTRUCT, and it's not new even though

Re: [PATCH 0/2][v5] Add the ability to do BPF directed error injection

From: Josef Bacik Date: Tue, 7 Nov 2017 15:28:41 -0500 > I'm sending this through Dave since it'll conflict with other BPF changes in > his > tree, but since it touches tracing as well Dave would like a review from > somebody on the tracing side. ... > A lot of our error

Re: [PATCH v5 15/37] tracing: Add variable support to hist triggers

On Fri, 10 Nov 2017 16:28:41 +0900 Namhyung Kim wrote: > > + hist_data->attrs->var_defs.expr[n_vars++] = s; > > + > > + hist_data->attrs->var_defs.n_vars = n_vars; > > + > > + if (n_vars == TRACING_MAP_VARS_MAX) > > +

Re: [PATCH 1/2] rtc: at91rm9200: stop calculating yday in at91_rtc_readalarm

On 10/11/2017 at 09:59, Alexandre Belloni wrote: > Calculating yday in the read_alarm callback is useless as this value is > never used later. Also, it was buggy anyway because at the time this is > done, tm_year is always 0 as the alarm register doesn't hold the year. > > Signed-off-by:

Re: [PATCH v2] checkpatch: Fix checks for Kconfig help text

On Fri, 2017-11-10 at 14:42 +0800, Leo Yan wrote: > If one patch has Kconfig section, the check script variable '$is_start' > will be set by first 'config' line and the variable '$is_end' is to be > set by the second 'config' line. But patches often only has one > 'config' line so we have no

Re: [alsa-devel] [PATCH] ASoC: Intel: common: Replace sst_acpi_check_hid with acpi_dev_present

On 11/10/2017 05:33 AM, Hans de Goede wrote: Hi, On 09-11-17 22:07, Jeremy Cline wrote: Replace the sst_acpi_check_hid helper function added in commit 915ae2b9f0fe ("ASoC: Intel: Create a helper to search for matching machine") with the generic acpi_dev_present helper function and remove the

N900 kernel support

Hi! Yesterday I updated https://elinux.org/N900 page based on data which I found in linux git repository. So driver status should be up-to-date. I would like to ask, what is current status of the bluetooth driver? It is working on N900, or it has a problems? Also are the any plans for bringing

Re: [PATCH 0/4] make function arg and structures as const

On Fri, Nov 10, 2017 at 10:09:46AM -0500, Anna Schumaker wrote: > > > On 11/09/2017 09:21 PM, J. Bruce Fields wrote: > > On Tue, Oct 17, 2017 at 12:40:27PM -0400, Jeff Layton wrote: > >> On Tue, 2017-10-17 at 18:14 +0200, Bhumika Goyal wrote: > >>> Make the function argument as const. After

Re: staging: pi433: Possible bug in rf69.c

Hi Dan, I checked it on my local SVN. You are right. I submitted the code with '&'. Accodring to a check-in message on my SVN, there was a bugreport end of July and most probably a patch - either from me, you, Joseph Wright, Colin King or Julia Lawall, changing '&' to '|'. I guess the patch for

Re: [PATCH 4/4] arm64: dts: qcom: msm8916: add bindings for i2c1, i2c3, i2c5

On Thu 09 Nov 09:14 PST 2017, Damien Riegel wrote: > Hi Bjorn, > > > On Thu, Nov 09, 2017 at 09:00:16AM -0800, Bjorn Andersson wrote: > > On Wed 01 Nov 10:53 PDT 2017, Damien Riegel wrote: > > > > I think it's better to use the word "nodes" (add nodes...) > > Will reword that. > > > > > >

Re: [PATCHv4 0/6] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

On (11/10/17 10:11), Luck, Tony wrote: > On Fri, Nov 10, 2017 at 08:48:24AM +0900, Sergey Senozhatsky wrote: > > All Ack-s/Tested-by-s were dropped, since the patch set has been > > reworked. I'm kindly asking arch-s maintainers and developers to test it > > once again. Sorry for any

WireGuard Upstreaming Roadmap (November 2017)

Hi folks, This relates to WireGuard [0]. Following a very nice conference with the Linux kernel networking subsystem community [1,2], I thought it might be a good idea to spell out the roadmap for the coming months and the trajectory into upstream, based on my discussions with several developers

Re: [PATCHv4 5/6] symbol lookup: introduce dereference_symbol_descriptor()

On (11/10/17 10:09), Luck, Tony wrote: > On Fri, Nov 10, 2017 at 08:48:29AM +0900, Sergey Senozhatsky wrote: > > -Examples:: > > - > > - printk("Going to call: %pF\n", gettimeofday); > > - printk("Going to call: %pF\n", p->func); > > - printk("%s: called from %pS\n", __func__, (void

[PATCH 0/2] managed resources for ili210x

Hi Dmitry, this is another patch of my series for switching the touchscreen drivers to to the managed resource allocators. The second patch is very trivial and perhaps bothering only me, feel free to ignore. Thanks, Andi Andi Shyti (2): Input: ili210x - use managed allocated resources

[PATCH 2/2] Input: ili210x - use separate error handling for different allocators

Split the error between devm_kzalloc and devm_input_allocate_device, there is no need to call the second allocator if the first has failed. Besides this doesn't provide practical advantages. Signed-off-by: Andi Shyti --- drivers/input/touchscreen/ili210x.c | 5 - 1 file

[PATCH 1/2] Input: ili210x - use managed allocated resources

Use managed allocated resources to simplify error handling during probing. Adjust goto labels and remove function accordingly. Signed-off-by: Andi Shyti --- drivers/input/touchscreen/ili210x.c | 36 +++- 1 file changed, 11 insertions(+), 25

[PATCH 13/14] nubus: Add expansion_type values for various Mac models

Add an expansion slot attribute to allow drivers to properly handle cards like Comm Slot cards and PDS cards without declaration ROMs. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- arch/m68k/include/asm/macintosh.h | 9 ++-

[PATCH 12/14] nubus: Rename struct nubus_dev

It is misleading to use "dev" to mean a functional resource. And in adopting the Linux Driver Model, struct nubus_board will embed a struct device. Drivers will then bind with boards, not with functional resources. Rename struct nubus_dev as struct nubus_functional_resource. This is the vendor's

[PATCH 02/14] nubus: Fix up header split

Due to the '#ifdef __KERNEL__' being located in the wrong place, some definitions from the kernel API were placed in the UAPI header during the scripted header split. Fix this. Also, remove the duplicate comment which is only relevant to the UAPI header. Fixes: 607ca46e97a1 ("UAPI: (Scripted)

[PATCH 01/14] nubus: Avoid array underflow and overflow

Check array indices. Avoid sprintf. Use buffers of sufficient size. Use appropriate types for the parameters to nubus_get_rsrc_{mem,str}() functions. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/nubus/nubus.c | 29

[PATCH 04/14] nubus: Fix log spam

Testing shows that a single Radius PrecisionColor 24X display board, which has 95 functional resources, produces over a thousand lines of log messages. Suppress these messages with pr_debug(). Remove some redundant messages relating to nubus_get_subdir() calls. Fix the format block debug messages

[PATCH 03/14] nubus: Use static functions where possible

This fixes a couple of warnings from 'make W=1': drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot' drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus' Tested-by: Stan Johnson Signed-off-by: Finn Thain

Re: [PATCH net-next 1/2] net/ncsi: Improve general state logging

From: Samuel Mendoza-Jonas Date: Wed, 8 Nov 2017 16:30:44 +1100 > The NCSI driver is mostly silent which becomes a headache when trying to > determine what has occurred on the NCSI connection. This adds additional > logging in a few key areas such as state transitions and

Re: [PATCH net-next 2/2] net/ncsi: Don't return error on normal response

From: Samuel Mendoza-Jonas Date: Wed, 8 Nov 2017 16:30:45 +1100 > Several response handlers return EBUSY if the data corresponding to the > command/response pair is already set. There is no reason to return an > error here; the channel is advertising something as enabled

[PATCH net v3 01/12] net/macsonic: Convert to nubus_driver

Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/net/ethernet/natsemi/macsonic.c | 170 ++-- 1 file changed, 118 insertions(+), 52 deletions(-) diff --git a/drivers/net/ethernet/natsemi/macsonic.c

[PATCH net v3 00/12] Fixes, cleanup and modernization for some legacy ethernet NIC drivers

This patch series adds support for the Linux Driver Model for Mac NIC drivers, fixes some logging bugs, removes dead code, and adopts netif_* calls to reduce code duplication. All up, about 100 lines of code are eliminated. This patch series has been tested on a variety of Macs, with coverage

[PATCH net v3 11/12] net/macmace: Fix and clean up log messages

Don't log unexpanded "eth%d". Log the chip revision in the probe message (consistent with mace.c). Drop redundant debug messages for FIFO events recorded in the interface statistics (also consistent with mace.c). Tested-by: Stan Johnson Signed-off-by: Finn Thain

[PATCH net v3 07/12] net/mac89x0: Fix and modernize log messages

Fix log message fragments which no longer produce the desired output (since the behaviour of printk() was changed). Add missing printk severity levels. Drop deprecated "out of memory" message as per checkpatch advice. Signed-off-by: Finn Thain ---

[PATCH net v3 12/12] net/smc9194: Remove bogus CONFIG_MAC reference

AFAIK the only version of smc9194.c with Mac support is the one in the linux-mac68k CVS repo, which never made it to the mainline. Despite that, as of v2.3.45, arch/m68k/config.in listed CONFIG_SMC9194 under CONFIG_MAC. This mistake got carried over into Kconfig in v2.5.55. (See pre-git era

[PATCH net v3 10/12] net/mac8390: Fix log messages

Use dev_foo() and log the slot number instead of the unexpanded "eth%d". Disambiguate the two identical "Card type %s is unsupported" messages. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/net/ethernet/8390/mac8390.c | 36

[PATCH net v3 09/12] net/8390: Fix redundant code

The patch which introduced the 8390 core module parameter 'msg_enable' failed to do anything useful with it: it merely causes an ancient version string to be logged. Remove the other code that logs the same string. Use the msg_enable module parameter as the default value for ei_local->msg_enable.

Re: [PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

From: Lipeng Date: Wed, 8 Nov 2017 15:52:21 +0800 > This patch-set introduces some bug fixes and code improvements. > As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using > GENMASK in hns3 driver}, which exists in net-next, not exists in net, so > push

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