On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
lockdep splat indicating this seqcount is not correctly initialized, fix
that by using netdev_alloc_pcpu_stats() instead of an open coded
allocation.
Fixes: 459aa660eb1d ("gtp: add initial driver for datapath of GPRS Tunneling
On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
lockdep splat indicating this seqcount is not correctly initialized, fix
that. In commit 6c80f3fc2398 ("netvsc: report per-channel stats in
ethtool statistics") netdev_alloc_pcpu_stats() was removed in favor of
open-coding the 6
On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
lockdep splat indicating this seqcount is not correctly initialized, fix
that by using the proper helper function: netdev_alloc_pcpu_stats().
Fixes: 2ad7bf363841 ("ipvlan: Initial check-in of the IPVLAN driver.")
Signed-off-by:
On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
lockdep splat indicating this seqcount is not correctly initialized, fix
that. In commit 6c80f3fc2398 ("netvsc: report per-channel stats in
ethtool statistics") netdev_alloc_pcpu_stats() was removed in favor of
open-coding the 6
On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
lockdep splat indicating this seqcount is not correctly initialized, fix
that.
Fixes: 4197aa7bb818 ("ixgbevf: provide 64 bit statistics")
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |
On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
lockdep splat indicating this seqcount is not correctly initialized, fix
that.
Fixes: eeda8585522b ("b44: add 64 bit stats")
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/broadcom/b44.c | 1 +
1 file changed, 1 ins
On Tue, 1 Aug 2017, Prarit Bhargava wrote:
> On 08/01/2017 01:00 PM, John Stultz wrote:
> > Its been asked already, but I've not yet seen an answer.
>
> Sorry for missing this.
>
> > Is there a reason your not also adding PRINTK_TIME_BOOT here (which to
> > me would be more generally useful then
On Tue, Aug 01, 2017 at 07:14:57PM +0200, Juergen Gross wrote:
> On 01/08/17 16:44, Kirill A. Shutemov wrote:
> > On Tue, Aug 01, 2017 at 09:46:56AM +0200, Juergen Gross wrote:
> >> On 26/07/17 18:43, Kirill A. Shutemov wrote:
> >>> On Wed, Jul 26, 2017 at 09:28:16AM +0200, Juergen Gross wrote:
> >
For a secureexec, before memory layout selection has happened, reset the
stack rlimit to something sane to avoid the caller having control over
the resulting layouts.
$ ulimit -s
8192
$ ulimit -s unlimited
$ /bin/sh -c 'ulimit -s'
unlimited
$ sudo /bin/sh -c 'ulimit -s'
8192
Cc: Linus Torvalds
S
The bprm_secureexec hook can be moved earlier. Right now, it is called
during create_elf_tables(), via load_binary(), via search_binary_handler(),
via exec_binprm(). Nearly all (see exception below) state used by
bprm_secureexec is created during the bprm_set_creds hook, called from
prepare_binprm(
Instead of an additional secureexec check for pdeath_signal, just move it
up into the initial secureexec test. Neither perf nor arch code touches
pdeath_signal, so the relocation shouldn't change anything.
Signed-off-by: Kees Cook
Acked-by: Serge Hallyn
---
fs/exec.c | 7 +++
1 file changed
This removes the redundant pdeath_signal clearing in Smack: the check in
smack_bprm_committing_creds() matches the check in smack_bprm_set_creds()
(which used to be in the now-removed smack_bprm_securexec() hook) and
since secureexec is now being checked for clearing pdeath_signal, this
is redundan
Since it's already valid to set dumpability in the early part of
setup_new_exec(), we can consolidate the logic into a single place.
The BINPRM_FLAGS_ENFORCE_NONDUMP is set during would_dump() calls
before setup_new_exec(), so its test is safe to move as well.
Signed-off-by: Kees Cook
Acked-by: S
On Tue, Aug 01, 2017 at 07:15:55PM +0100, Ben Hutchings wrote:
> On Tue, 2017-07-25 at 12:18 -0700, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Johan Hovold
> >
> > commit 20777bc57c346b6994f4
Like dumpability, clearing pdeath_signal happens both in setup_new_exec()
and later in commit_creds(). The test in setup_new_exec() is different
from all other privilege comparisons, though: it is checking the new cred
(bprm) uid vs the old cred (current) euid. This appears to be a bug,
introduced
Instead of a separate function, open-code the cap_elevated test, which
lets us entirely remove bprm->cap_effective (to use the local "effective"
variable instead), and more accurately examine euid/egid changes via the
existing local "is_setid".
The following LTP tests were run to validate the chan
The examination of "current" to decide dumpability is wrong. This was a
check of and euid/uid (or egid/gid) mismatch in the existing process,
not the newly created one. This appears to stretch back into even the
"history.git" tree. Luckily, dumpability is later set in commit_creds().
In earlier ker
This removes the bprm_secureexec hook since the logic has been folded into
the bprm_set_creds hook for all LSMs now.
Cc: Eric W. Biederman
Signed-off-by: Kees Cook
Reviewed-by: John Johansen
Acked-by: James Morris
Acked-by: Serge Hallyn
---
fs/exec.c | 2 --
include/linux/ls
The cred_prepared bprm flag has a misleading name. It has nothing to do
with the bprm_prepare_cred hook, and actually tracks if bprm_set_creds has
been called. Rename this flag and improve its comment.
Cc: David Howells
Cc: Stephen Smalley
Cc: Casey Schaufler
Signed-off-by: Kees Cook
Acked-by:
The Smack bprm_secureexec hook can be merged with the bprm_set_creds
hook since it's dealing with the same information, and all of the details
are finalized during the first call to the bprm_set_creds hook via
prepare_binprm() (subsequent calls due to binfmt_script, etc, are ignored
via bprm->calle
The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
hook since it's dealing with the same information, and all of the details
are finalized during the first call to the bprm_set_creds hook via
prepare_binprm() (subsequent calls due to binfmt_script, etc, are ignored
via bprm->cal
The commoncap implementation of the bprm_secureexec hook is the only LSM
that depends on the final call to its bprm_set_creds hook (since it may
be called for multiple files, it ignores bprm->called_set_creds). As a
result, it cannot safely _clear_ bprm->secureexec since other LSMs may
have set it.
The AppArmor bprm_secureexec hook can be merged with the bprm_set_creds
hook since it's dealing with the same information, and all of the details
are finalized during the first call to the bprm_set_creds hook via
prepare_binprm() (subsequent calls due to binfmt_script, etc, are ignored
via bprm->ca
Based Linus's comments, my intent is to carry this series for -next and
send it as a distinct pull request during the v4.14 merge window. I'm
happy to adjust this plan as needed.
Changes from v4:
- fixed typo introduced during patch reordering
- rebased to v4.13-rc2 (mainly apparmor changes)
- fix
In commit 221af7f87b97 ("Split 'flush_old_exec' into two functions"),
the comment about the point of no return should have stayed in
flush_old_exec() since it refers to "bprm->mm = NULL;" line, but prior
changes in commits c89681ed7d0e ("remove steal_locks()"), and
fd8328be874f ("sanitize handling
Hi Joey,
On 07/23/2017 05:18 AM, joeyli wrote:
> Hi Yasuaki,
>
> On Fri, Jul 14, 2017 at 10:44:14PM +0800, joeyli wrote:
>> On Fri, Jul 14, 2017 at 10:37:13AM +0200, Michal Hocko wrote:
>>> On Thu 13-07-17 20:45:21, Joey Lee wrote:
On Thu, Jul 13, 2017 at 09:06:19AM +0200, Michal Hocko wro
Minchan Kim wrote:
> Nadav reported KSM can corrupt the user data by the TLB batching race[1].
> That means data user written can be lost.
>
> Quote from Nadav Amit
> "
> For this race we need 4 CPUs:
>
> CPU0: Caches a writable and dirty PTE entry, and uses the stale value for
> write later.
>
On 2017-08-01 21:07, Dmitry Torokhov wrote:
On Tue, Aug 01, 2017 at 08:51:40PM +0200, danilokrummr...@dk-develop.de
wrote:
On 2017-08-01 19:32, Dmitry Torokhov wrote:
>On Tue, Aug 01, 2017 at 06:26:14AM +0200, Danilo Krummrich wrote:
>>+ irq = gpio_to_irq(drvdata->gpio_clk);
>>+ if (
On Wed, Jul 26, 2017 at 01:21:37PM +0300, Andy Shevchenko wrote:
> On Tue, 2017-07-25 at 13:58 -0700, Dmitry Torokhov wrote:
> > When converting legacy board to use gpiod API() there migt be several
> > lookup tables in board file, let's provide a way to register them all
> > at
> > once.
>
> Look
On Wed, Aug 02, 2017 at 12:45:06AM +0900, Hector Martin wrote:
I'll fix it up this time, but please make sure to include a proper
commit message in the future.
> Cc: sta...@vger.kernel.org
> Signed-off-by: Hector Martin
Now applied, thanks.
Johan
On Tue, Aug 01, 2017 at 02:19:12PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 27, 2017 at 10:55:58AM -0400, Rik van Riel wrote:
> > On Tue, 2017-06-27 at 07:39 +0200, Peter Zijlstra wrote:
>
> > > If LLC < NUMA or !NUMA_BALANCING we have a region that needs to do
> > > _something_.
> >
> > Agreed
On Tue, Aug 01, 2017 at 12:32:57PM -0600, Logan Gunthorpe wrote:
> Couldn't create rdma QP - Invalid argument
> Unable to create QP.
> Failed to create QP.
Failing to create a QP makes me wonder if you have have this patch?
Subject: [PATCH v2 1/2] RDMA/uverbs: Fix the check for port number
Th
This is a 5 patch series which solves coding style issues
as marked by checkpatch.pl in the file pi433_if.h and
contains changes that have to be made in other files as a
consequence of the changes made in pi433_if.h
Signed-off-by: Rishabh Hardas
---
drivers/staging/pi433/pi433_if.h | 81
Hello,
On Tue, Aug 01, 2017 at 02:56:17PM +0900, Minchan Kim wrote:
> CPU0 CPU1CPU2CPU3
>
> Write the same
> value on page
>
> [cache PTE as
> dirty in TLB]
>
> MADV_FREE
> pte_mkclea
Signed-off-by: Rishabh Hardas
---
drivers/staging/pi433/rf69.h | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/pi433/rf69.h b/drivers/staging/pi433/rf69.h
index b81e076..e98e24e 100644
--- a/drivers/staging/pi433/rf69.h
+++ b/driver
Signed-off-by: Rishabh Hardas
---
drivers/staging/pi433/rf69.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/pi433/rf69.c b/drivers/staging/pi433/rf69.c
index f83523e..7fa63e1 100644
--- a/drivers/staging/pi433/rf69.c
+++ b/driver
Signed-off-by: Rishabh Hardas
---
drivers/staging/pi433/pi433_if.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c
index ed737f4..11c042b 100644
--- a/drivers/staging/pi433/pi433_if.c
+++ b/drivers/staging
Signed-off-by: Rishabh Hardas
---
drivers/staging/pi433/rf69_enum.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/pi433/rf69_enum.h
b/drivers/staging/pi433/rf69_enum.h
index fbfb59b..f51eec3 100644
--- a/drivers/staging/pi433/rf69_enum.h
+++
On 01/08/17 01:29 PM, Jason Gunthorpe wrote:
> On Tue, Aug 01, 2017 at 12:32:57PM -0600, Logan Gunthorpe wrote:
>> Couldn't create rdma QP - Invalid argument
>> Unable to create QP.
>> Failed to create QP.
>
> Failing to create a QP makes me wonder if you have have this patch?
>
> Subject: [PA
On 08/01/2017 01:44 AM, Arvind Yadav wrote:
omap_gpio_probe() can fail here and we must disable clock.
Signed-off-by: Arvind Yadav
---
drivers/gpio/gpio-omap.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
index f8c550de..dbf869f
Hi Arnd,
Le 22/07/2017 à 00:21, Arnd Bergmann a écrit :
> I ran into a link-time error with the atmel-quadspi driver on the
> EBSA110 platform:
>
> drivers/mtd/built-in.o: In function `atmel_qspi_run_command':
> :(.text+0x1ee3c): undefined reference to `_memcpy_toio'
> :(.text+0x1ee48): undefined
hi LINUX
http://www.atlpaintparties.com/emptycart.php?meant=27eh6t2r1krf
Warm Regards
The latest maintenance release Git v2.13.4 is now available at
the usual places.
There is no update that is particulary important or controversial in
this release; it is primarily to flush the safer fixes that have
already been in the 'master' branch in preparation for the v2.14.0
release down to
On Tue, Aug 1, 2017 at 12:02 PM, Mike Snitzer wrote:
> On Tue, Aug 01 2017 at 2:12pm -0400,
> Dan Williams wrote:
>
>> Now that dax is no longer a default property of a block-device, i.e.
>> ->direct_access() is not a block-device operation, we optionally enable
>> device-mapper dax support with
On Tue, Aug 1, 2017 at 3:39 AM, Juergen Gross wrote:
> When running as Xen pv-guest the exception frame on the stack contains
> %r11 and %rcx additional to the other data pushed by the processor.
>
> Instead of having a paravirt op being called for each exception type
> prepend the Xen specific co
On 08/01/2017 10:35 AM, Prarit Bhargava wrote:
On 08/01/2017 01:00 PM, John Stultz wrote:
On Tue, Aug 1, 2017 at 5:55 AM, Prarit Bhargava wrote:
printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
timestamp to printk messages. The local hardware clock loses time each
da
Jerome Brunet writes:
> Now that the clock source 0 is properly described in the CCF, use it
> instead of assuming the default value (xtal)
>
> Signed-off-by: Jerome Brunet
> ---
>
> This patchset depends on clock patchset adding the related clocks:
> * https://lkml.kernel.org/r/20170731115603.2
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
> /*
> * The cached intel_pqr_state is strictly per CPU and can never be
> * updated from a remote CPU. Functions which modify the state
> @@ -49,6 +47,8 @@
> */
> DEFINE_PER_CPU(struct intel_pqr_state, pqr_state);
>
> +DEFINE_PER_CPU_READ_MOSTLY
Jerome Brunet writes:
> Changing the card voltage on the p200 is not instantaneous, especially
> when switching from 3.3v to 1.8v.
>
> I take at least 70ms for the regulator to go from 3.3v to 1.8v. Add
> margin to that to make sure we don't upset the sdcard during the voltage
> switch
>
> Fixes:
On Tue, 1 Aug 2017 13:39:06 -0400 kan.li...@intel.com wrote:
> Kernel panic when calling the IRQ-safe __get_user_pages_fast in NMI
> handler.
>
> The bug was introduced by commit:
>
> 2947ba054a4d ("x86/mm/gup: Switch GUP to the generic
> get_user_page_fast() implementation")
>
> The origina
Neil Armstrong writes:
> This patch describes the GPIO lines usage on the Khadas VIM board.
>
> This is useful in the debugfs gpio file and using the cdev gpio API.
>
> Signed-off-by: Neil Armstrong
[...]
> + /* Bank BOOT */
> + "eMMC D0", "eMMC D1",
From: Arnaldo Carvalho de Melo
In 2be7e212d541 ("bpf: add bpf_skb_adjust_room helper") BPF_ADJ_ROOM_NET was
added to include/uapi/linux/bpf.h but BPF_ADJ_ROOM_NET_OPS was added to
tools/include/uapi/linux/bpf.h, making these files differ, fix it by using the
same name in both, BPF_ADJ_ROOM_NET, t
From: Arnaldo Carvalho de Melo
By using the _IOC_(DIR,NR,TYPE,SIZE) macros to lookup a 'type' keyed
table that then gets indexed by 'nr', falling back to a notation similar
to the one used by 'strace', only more compact, i.e.:
474.356 ( 0.007 ms): gnome-shell/22401 ioctl(fd: 8, cmd:
(READ|WR
From: Ingo Molnar
In this patch we changed the header checks:
perf build: Clarify header version warning message
Unfortunately the header checks were copied to various places and thus the
message got
out of sync. Fix some of them here.
Note that there's still old, misleading messages remain
rg/pub/scm/linux/kernel/git/acme/linux into perf/core
(2017-07-30 11:15:37 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-4.14-20170801
for you to fetch changes up to 81e3d8b2af2e7417f1d5164aab5c1a75955e8a5
From: Ingo Molnar
Change this:
Warning: arch/x86/include/asm/disabled-features.h differs from kernel
Warning: arch/x86/include/asm/cpufeatures.h differs from kernel
Warning: arch/powerpc/include/uapi/asm/kvm.h differs from kernel
Warning: arch/s390/include/uapi/asm/kvm.h differs from ker
From: Arnaldo Carvalho de Melo
We copy headers from include/, arch/ to allow tools/ use defines,
structs from newer kernels and still be able to build on older systems.
We then, as part of a build, check if those copies got out of sync, when
we emit a warning, so that we can check if something n
From: Arnaldo Carvalho de Melo
We will use it to generate tables for beautifying ioctl's 'cmd' arg.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-bqoq114h917u6ggazn8m1...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Mel
From: Arnaldo Carvalho de Melo
Also trying a new approach, using the copy of uapi/linux/perf_event.h we
auto generate the string tables, then include it in the ioctl cmd
beautifier.
This way either the perf developers will add the new commands to the
tools/ copy, like is happening with other are
From: Arnaldo Carvalho de Melo
Also trying a new approach, using a copy of uapi/linux/vhost.h we auto
generate the string tables, then include it in the ioctl cmd beautifier.
This way either the KVM developers will add the new commands to the
tools/ copy, like is happening with other areas of to
From: Arnaldo Carvalho de Melo
Not all subsystems use the fact that we may have the same _IOC_NR for
different _IOC_DIR, as in the end it'll result in a different ioctl
number.
So, for instance, vhost virtio has:
#define VHOST_GET_FEATURES _IOR(VHOST_VIRTIO, 0x00, __u64)
#define VHOST_
From: Arnaldo Carvalho de Melo
This time we try a new approach, using a copy of uapi/sound/asound.h we
auto generate the string tables, then include it in the ioctl cmd
beautifier.
This way either the sound developers will add the new commands to the
tools/ copy, like is happening with other are
Neil Armstrong writes:
> This patch describes the GPIO lines usage on the Nanopi K2 board.
>
> This is useful in the debugfs gpio file and using the cdev gpio API.
>
> Signed-off-by: Neil Armstrong
Applied to v4.14/dt64,
Thanks,
Kevin
From: Arnaldo Carvalho de Melo
We will use it to generate tables for beautifying ioctl's 'cmd' arg.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jason Wang
Cc: Jiri Olsa
Cc: "Michael S. Tsirkin"
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-nxwpq34hu6te1m2ra5m7o...@git.kernel.
From: Arnaldo Carvalho de Melo
Also trying a new approach, using a copy of uapi/linux/kvm.h we auto
generate the string tables, then include it in the ioctl cmd beautifier.
This way either the KVM developers will add the new commands to the
tools/ copy, like is happening with other areas of tool
2017-07-31 19:25-0700, Wanpeng Li:
> From: Wanpeng Li
>
> [ cut here ]
> WARNING: CPU: 5 PID: 2288 at arch/x86/kvm/vmx.c:11124
> nested_vmx_vmexit+0xd64/0xd70 [kvm_intel]
> CPU: 5 PID: 2288 Comm: qemu-system-x86 Not tainted 4.13.0-rc2+ #7
> RIP: 0010:nested_vmx_vmexit+
From: Arnaldo Carvalho de Melo
We will use it to generate tables for beautifying ioctl's 'cmd' arg.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-nxwpq34hu6te1m2ra5m7o...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Mel
From: Arnaldo Carvalho de Melo
We will use it to generate tables for beautifying ioctl's 'cmd' arg.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-wit4wwmrh9d37dtgtk0gl...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Mel
From: Arnaldo Carvalho de Melo
This time we try a new approach, using uapi/drm/ copies of drm.h and
i915_drm.h we auto generate the string tables, then include it in the
ioctl cmd beautifier.
This way either the DRM developers will add the new commands to the
tools/ copy, like is happening with
From: Ingo Molnar
Sync up (copy) the following v4.13 kernel headers to the tooling headers:
arch/arm/include/uapi/asm/kvm.h:
arch/arm64/include/uapi/asm/kvm.h:
arch/powerpc/include/uapi/asm/kvm.h:
arch/s390/include/uapi/asm/kvm.h:
- KVM ABI extensions, which do not affect perf toolin
From: Arnaldo Carvalho de Melo
So that we can build on older systems where otherwise we would end up
with:
CC /tmp/build/perf/trace/beauty/ioctl.o
trace/beauty/ioctl.c: In function 'ioctl__scnprintf_tty_cmd':
trace/beauty/ioctl.c:25:17: error: 'TIOCGEXCL' undeclared (first use in t
From: Arnaldo Carvalho de Melo
In 04df41e343db ("bpf: update tools/include/uapi/linux/bpf.h") the files
added in 40304b2a1567 ("bpf: BPF support for sock_ops") were added to
tools/include, but not in a verbatim way, missing the comments, which
ends up triggering this warning when build tools/perf
On Tue, Aug 01, 2017 at 12:11:09PM -0700, Florian Fainelli wrote:
> On 32-bit hosts and with CONFIG_DEBUG_LOCK_ALLOC we should be seeing a
> lockdep splat indicating this seqcount is not correctly initialized, fix
> that.
>
> Fixes: 4c3523623dc0 ("net: add driver for Netronome NFP4000/NFP6000 NIC
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") adds code
to free the descriptor in ds_done.
In cyclic mode, ds_done is never used and it's always NULL,
so the added code is not executed.
In non-cyclic mode, ds_done is used as a flag:
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") broke the
logic around ds_run/ds_done in case of non-cyclic DMA.
This v2 splits the initial patch in three parts:
- the real fix for non-cyclic mode
- another fix for a double free introdu
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") adds few
calls to ON_WARN_ONCE() to track the use of ds_run/ds_done.
After the two fixes:
- dmaengine: k3dma: fix non-cyclic mode
- dmaengine: k3dma: fix re-free of the same descriptor
the
On Tue, Aug 1, 2017 at 9:41 PM, Cyrille Pitchen
wrote:
> Le 22/07/2017 à 00:21, Arnd Bergmann a écrit :
>> --- a/drivers/mtd/spi-nor/atmel-quadspi.c
>> +++ b/drivers/mtd/spi-nor/atmel-quadspi.c
>> @@ -208,9 +208,9 @@ static int atmel_qspi_run_transfer(struct atmel_qspi *aq,
>> if (cmd->enab
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") broke the
logic around ds_run/ds_done in case of non-cyclic DMA.
This went unnoticed as the only user of k3dma was the i2s
audio driver but, with a patch set to enable dma on SPI, the
issu
Vivien Didelot writes:
> Second option is: we keep it KISS and let the driver define its noop,
> but as I explain, it is confusing, especially for the get operation.
In fact we should be good because the DSA layer will call
ds->ops->{g,s}et_mac_eee before phy_ethtool_{g,s}et_eee, so if the DSA
d
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
> Hardware uses RMID(Resource monitoring ID) to keep track of each of the
> RDT events associated with tasks. The number of RMIDs is dependent on
> the SKU and is enumerated via CPUID. We add support to manage the RMIDs
> which include managing the RMID al
If we return here and import_attach is true, then dma_buf_end_cpu_access()
will not be called balance dma_buf_begin_cpu_access().
Fix by setting ret instead of returning.
Signed-off-by: David Lechner
---
drivers/gpu/drm/tinydrm/mipi-dbi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
On 08/01/2017 09:56 PM, Arnaldo Carvalho de Melo wrote:
From: Arnaldo Carvalho de Melo
In 2be7e212d541 ("bpf: add bpf_skb_adjust_room helper") BPF_ADJ_ROOM_NET was
added to include/uapi/linux/bpf.h but BPF_ADJ_ROOM_NET_OPS was added to
tools/include/uapi/linux/bpf.h, making these files differ,
On 08/01/2017 09:56 PM, Arnaldo Carvalho de Melo wrote:
From: Arnaldo Carvalho de Melo
In 04df41e343db ("bpf: update tools/include/uapi/linux/bpf.h") the files
added in 40304b2a1567 ("bpf: BPF support for sock_ops") were added to
tools/include, but not in a verbatim way, missing the comments, w
On Tue, Aug 1, 2017 at 5:14 PM, Boris Brezillon
wrote:
> On Tue, 1 Aug 2017 16:22:21 +0200 Arnd Bergmann wrote:
>> On Tue, Aug 1, 2017 at 3:58 PM, Boris Brezillon
>> wrote:
>> > On Tue, 1 Aug 2017 15:34:14 +0200
>> > Boris Brezillon wrote:
>> >> On Tue, 1 Aug 2017 15:11:44 +0200
>> >> Arnd Berg
Hello, Peter.
On Sat, Jul 29, 2017 at 11:17:07AM +0200, Peter Zijlstra wrote:
> > * "cpu.shares" is replaced with "cpu.weight" and operates on the
> > standard scale defined by CGROUP_WEIGHT_MIN/DFL/MAX (1, 100, 1).
> > The weight is scaled to scheduler weight so that 100 maps to 1024
> >
Hi,
Today, we release the 2.10 stable versions of LTTng kernel and user-space
tracers. This release is named "KeKriek", which is a sour mashed
golden wheat ale brewed by the Dunham microbrewery in Quebec.
The new features included are:
- A new "blocking" mode for LTTng-UST (it has been requested
On Tue, Aug 1, 2017 at 8:04 AM, Kees Cook wrote:
>
> Do you want me to carry this for -next and send it as a distinct pull
> request for v4.14?
Yes, I think that would be preferred. I consider this a "execve()"
cleanup/change with implications for the security models rather than
the other way aro
On Mon, Jul 24, 2017 at 10:34:18PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in snprintf text
>
> Signed-off-by: Colin Ian King
Queued, thanks!
Luis
The subject is too vague and you need a changelog.
On Tue, Aug 01, 2017 at 05:11:29PM +0100, Ashish Kalra wrote:
> +static int inc_txqhead(struct ks_wlan_private *priv)
> +{
> + priv->tx_dev.qhead = (priv->tx_dev.qhead + 1) % TX_DEVICE_BUFF_SIZE;
> + return 0;
Just make these void if no o
>
> On Tue, 1 Aug 2017 13:39:06 -0400 kan.li...@intel.com wrote:
>
> > Kernel panic when calling the IRQ-safe __get_user_pages_fast in NMI
> > handler.
> >
> > The bug was introduced by commit:
> >
> > 2947ba054a4d ("x86/mm/gup: Switch GUP to the generic
> > get_user_page_fast() implementation
On Tue, 25 Jul 2017, Vikas Shivappa wrote:
> for_each_alloc_enabled_rdt_resource(r) {
> - kn_subdir = kernfs_create_dir(kn_info, r->name,
> - kn_info->mode, r);
> - if (IS_ERR(kn_subdir)) {
> - ret = PTR_ERR
On Tue, Aug 1, 2017 at 4:52 PM, Gary R Hook wrote:
> On 07/31/2017 03:49 PM, Arnd Bergmann wrote:
>>
>> The added support for version 5 CCPs introduced a false-positive
>> warning in the RSA implementation:
>>
>> drivers/crypto/ccp/ccp-ops.c: In function 'ccp_run_rsa_cmd':
>> drivers/crypto/ccp/cc
It is safer to init the EEE before the DSA layer call
phy_ethtool_set_eee, as sf2 and qca8k are doing.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/chip.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c
The port's PHY and MAC are both implied in EEE. The current code does
not call the PHY operations if the related device is NULL. Change that
by returning -ENODEV if there's no PHY device attached to the interface.
Signed-off-by: Vivien Didelot
---
net/dsa/slave.c | 18 ++
1 file
phy_ethtool_get_eee is already called by the DSA layer, thus remove the
duplicated call in the qca8k driver.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/qca8k.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/net/dsa/qca8k.c b/drivers/net/dsa/qca8k
If EEE is queried enabled, qca8k_set_eee calls qca8k_eee_enable_set
twice (because it is already called in qca8k_eee_init). Fix that.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/qca8k.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/dsa/qca8k.c b/drive
EEE implies configuring the port's PHY and MAC of both ends of the wire.
The current EEE support in DSA mixes PHY and MAC configuration, which is
bad because PHYs must be configured through a proper PHY driver. The DSA
switch operations for EEE are only meant for configuring the port's MAC,
which
All DSA drivers are calling phy_init_eee if eee_enabled is true.
Move up this statement in the DSA layer to simplify the DSA drivers.
qca8k does not require to cache the ethtool_eee structures from now on.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/bcm_sf2.c| 9 +
driver
The DSA switch operations for EEE are only meant to configure a port's
MAC EEE settings. The port's PHY EEE settings are accessed by the DSA
layer and must be made available via a proper PHY driver.
In order to reduce this confusion, remove the phy_device argument from
the .set_eee operation.
Sig
The PHY's EEE settings are already accessed by the DSA layer through the
Marvell PHY driver and there is nothing to be done for switch's MACs.
Remove all EEE support from the mv88e6xxx driver and simply return 0
from the EEE ops.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/chip.
701 - 800 of 1131 matches
Mail list logo