On 10/30/18 12:08 PM, luca abeni wrote:
> Hi Peter,
>
> On Tue, 30 Oct 2018 11:45:54 +0100
> Peter Zijlstra wrote:
> [...]
>>> 2. This is related to perf_event_open syscall reproducer does
>>> before becoming DEADLINE and entering the busy loop. Enabling of
>>> perf swevents generates lot of
On Mon, Oct 29, 2018 at 09:33:14PM +0100, Thomas Gleixner wrote:
> Andrei,
>
> On Sat, 20 Oct 2018, Andrei Vagin wrote:
> > When a container is migrated to another host, we have to restore its
> > monotonic and boottime clocks, but we still expect that the container
> > will continue using the
On Wed, 2018-10-31 at 09:41 -0400, YU Bo wrote:
> Hi,
> On Tue, Oct 30, 2018 at 08:01:50AM -0700, Joe Perches wrote:
> > On Tue, 2018-10-30 at 08:01 -0400, Bo YU wrote:
> > > Fix warning from checkpatch.pl use pr_* to replace printk
> >
> > If you look at msg, it can be unterminated with newline.
On 2018-10-31, Joel Fernandes wrote:
> I suggest to maintainers we take this in as an intermediate solution
> since we don't have anything close to it and this is a real issue, and
> the fix proposed is simple.
I would suggest we wait until after LPC to see what Christian's design
is (given
On Wed, 31 Oct 2018 14:18:19 +
Mark Rutland wrote:
> On Wed, Oct 31, 2018 at 02:19:07PM +0100, Jiri Kosina wrote:
> > Other architectures do rely on that. That's exactly for example why
> > on x86 we use '-pg -mfentry', to make sure we hook the function
> > *before* prologue.
>
> Ah, I'd
On 10/31/18 5:40 PM, Juri Lelli wrote:
> On 31/10/18 17:18, Daniel Bristot de Oliveira wrote:
>> On 10/30/18 12:08 PM, luca abeni wrote:
>>> Hi Peter,
>>>
>>> On Tue, 30 Oct 2018 11:45:54 +0100
>>> Peter Zijlstra wrote:
>>> [...]
> 2. This is related to perf_event_open syscall reproducer
Hi Grygorii,
On 31/10/18 16:39, Grygorii Strashko wrote:
[...]
> I'd try to provide some additional information here.
> (Sry, I'll still use term "events")
>
> As Lokesh explained in other mail on K3 SoC everything is generic and most
> of resources allocated dynamicaly:
> - generic DMA
On Fri, 2018-10-26 at 11:12 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> [... cut ...]
>
> The new governor introduced here, the timer events oriented (TEO)
> governor, uses the same basic strategy as menu: it always tries to
> find the deepest idle state that can be used in
On Thu, Oct 25, 2018 at 11:40 AM Jaewon Kim wrote:
>
> This patch supports dynamic device-tree for AMBA device.
> The AMBA device must be registered on the AMBA bus, not the platform bus.
I'm not convinced we should even support this. There's a limited
number of AMBA devices. They would almost
On Wed, 31 Oct 2018 18:27:02 +0100,
Joe Perches wrote:
>
> On Wed, 2018-10-31 at 18:00 +0100, Takashi Iwai wrote:
> > On Wed, 31 Oct 2018 17:44:57 +0100,
> > Arnaldo Carvalho de Melo wrote:
> > > From: Arnaldo Carvalho de Melo
> > >
> > > To silence this perf build warning:
> > >
> > >
On 10/31/2018 11:21 AM, Marc Zyngier wrote:
Hi Grygorii,
[...]
Well, I'm convinced that we do not want a networking driver to be tied
to an interrupt architecture, and that the two should be completely
independent. But that's my own opinion. I can only see two solutions
moving forward:
1)
> My objections fundamentally is that I can find real problems when I look
> at the code.
Eric.
You have repeatedly stated that there are "thinkos, typos and bugs" in the
code, but you have not been very forthcoming in actually disclosing *what*
those things are.
You had a go at rewriting it
On 31/10/18 18:38, Santosh Shilimkar wrote:
> On 10/31/2018 11:21 AM, Marc Zyngier wrote:
>> Hi Grygorii,
>>
>
> [...]
>
>>
>> Well, I'm convinced that we do not want a networking driver to be tied
>> to an interrupt architecture, and that the two should be completely
>> independent. But that's
From: Colin Ian King
Trivial fix to clean up indentation issues, add one level of
indentation on two if statements.
Signed-off-by: Colin Ian King
---
drivers/pinctrl/mediatek/pinctrl-moore.c | 4 ++--
drivers/pinctrl/mediatek/pinctrl-paris.c | 4 ++--
2 files changed, 4 insertions(+), 4
Update compat_sys_preadv64v2 and compat_sys_pwritev64v2 to handle the
offset argument == -1, which should use and update the the current file
offset.
--
H.J.
From 934a68be8a092dba9558bdf8025239934efb5d7e Mon Sep 17 00:00:00 2001
From: "H.J. Lu"
Date: Wed, 3 Oct 2018 08:07:18 -0700
Subject:
On Tue, 2018-10-30 at 11:13 +, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to clean up indentation issues
[]
> diff --git a/drivers/staging/vt6656/main_usb.c
> b/drivers/staging/vt6656/main_usb.c
> index ccafcc2c87ac..b613a1d113bb 100644
> ---
The Cadence Sierra PHY supports a number of different protocols. This
series adds a driver with support for USB3 and PCIe modes.
Only one clock frequency is currently supported, so the value of clock
provided in device tree is ignored.
Changes since v1:
* Moved subnode resets into each subnode
Hi,
On 31-10-18 16:51, Randy Dunlap wrote:
On 10/30/18 8:59 PM, Stephen Rothwell wrote:
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181030:
on i386:
ld: drivers/virt/vboxguest/vboxguest_core.o: in
Stefan Wahren writes:
> We should never assume to get a reply from the firmware otherwise
> the call could block forever and the user don't get informed. So
> define a timeout of 1 sec and print a stacktrace once in the unlikely
> case the timeout expired.
>
> Signed-off-by: Stefan Wahren
Convert the GPIO driver to use the GPIO irqchip library
GPIOLIB_IRQCHIP instead of reimplementing the same.
Signed-off-by: Nishad Kamdar
---
drivers/staging/greybus/Kconfig | 1 +
drivers/staging/greybus/gpio.c | 123 ++--
2 files changed, 21 insertions(+), 103
On Wed, Oct 31, 2018 at 11:07:22AM -0400, Waiman Long wrote:
> On 10/31/2018 10:10 AM, Peter Zijlstra wrote:
> > On Wed, Oct 31, 2018 at 09:54:17AM +0800, Yi Sun wrote:
> >> On 18-10-23 17:33:28, Yi Sun wrote:
> >>> On 18-10-23 10:51:27, Peter Zijlstra wrote:
> Can you try and explain why
On Wed, Oct 31, 2018 at 06:26:05PM +0100, Oleg Nesterov wrote:
> On 10/30, Paul E. McKenney wrote:
> >
> > On Mon, Oct 22, 2018 at 06:14:40PM +0200, Oleg Nesterov wrote:
> > > > >
> > > > > Damn.
> > > > >
> > > > > This
Hi,
On Wed, Oct 31, 2018 at 10:09 AM Palmer Dabbelt wrote:
>
> On Tue, 30 Oct 2018 23:47:06 PDT (-0700), Olof Johansson wrote:
> > A couple of fixes for build breakage or warnings, and a small whitespace/asm
> > cleanup. The non-cleanups would be good to see in 4.20 to keep builds green.
>
> I'm
asm_volatile_goto should also be defined for other compilers that support
asm goto.
Signed-off-by: Nick Desaulniers
---
V1 -> V2: drop changes to include/linux/compiler-gcc.h.
include/linux/compiler_types.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/linux/compiler_types.h
On Tue, Oct 30, 2018 at 6:24 PM Zhang Rui wrote:
>
> Thermal management updates for v4.20-rc1 [..]
Pulled,
Linus
On Wed, Oct 31, 2018 at 11:21 AM, Thomas Gleixner wrote:
> Add SPDX identifiers to all files in kernel/time and remove the license
> boiler plates.
>
> Aside of that use the chance to get rid of (stale) file references and tidy
> up the top of file comments as they are touched anyway by this
On Wed, Oct 31, 2018 at 7:28 AM Konstantin Ryabitsev
wrote:
>
> Regarding your case specifically, what's a good cutoff period for
> treating a pull request as effectively ignored/abandoned (i.e. no
> matching commit-id ever found in the repo). I'm guessing about a month,
> or do you want to go
28fa741c27e6d57f6bf594ba3c444ce79e671e09:
perf/core: Clean up inconsisent indentation (2018-10-30 09:51:58 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-urgent-for-mingo-4.20-20181031
for you to fetch changes up
From: Arnaldo Carvalho de Melo
Generalizing pkey_alloc__scnprintf_access_rights(), so that we can use
it with other flags-like arguments, such as mount's mountflags argument.
Cc: Adrian Hunter
Cc: Benjamin Peterson
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link:
From: Leo Yan
Since commit edeb0c90df35 ("perf tools: Stop fallbacking to kallsyms for
vdso symbols lookup"), the kernel address cannot be properly parsed to
kernel symbol with command 'perf script -k vmlinux'. The reason is
CoreSight samples is always to set CPU mode as PERF_RECORD_MISC_USER,
From: Colin Ian King
Trivial fix to clean up indentation issues, remove spaces
Signed-off-by: Colin Ian King
---
drivers/pcmcia/i82092.c | 34 --
1 file changed, 16 insertions(+), 18 deletions(-)
diff --git a/drivers/pcmcia/i82092.c b/drivers/pcmcia/i82092.c
From: Arnaldo Carvalho de Melo
Enabling --overwrite mode allows us to to use just the most recent
records, which helps in high core count machines such as Knights
Landing/Mill, but right now is being disabled by default as the pausing
used in this technique is leading to loss of metadata events
From: "David S. Miller"
When processing using 'perf report -g caller', which is the default, we
ended up reverting the callchain entries received from the kernel, but
simply reverting throws away the information that tells that from a
point onwards the addresses are for userspace, kernel, guest
From: Arnaldo Carvalho de Melo
The pathname beautifiers so far support just one augmented pathname per
syscall, so do it just for mount's first arg, later this will get fixed.
With:
# perf probe -l
probe:vfs_getname(on getname_flags:73@acme/git/linux/fs/namei.c with
pathname)
#
From: Arnaldo Carvalho de Melo
We'll use it to create tables for the 'flags' argument to the 'mount'
and 'umount' syscalls.
Add it to check_headers.sh so that when a new protocol gets added we get
a notification during the build process.
Cc: Adrian Hunter
Cc: Benjamin Peterson
Cc: David
From: Arnaldo Carvalho de Melo
# trace -e mount mount -o ro -t debugfs nodev /mnt
0.000 ( 1.040 ms): mount/27235 mount(dev_name: 0x5601cc8c64e0, dir_name:
0x5601cc8c6500, type: 0x5601cc8c6480, flags: RDONLY) = 0
# trace -e mount mount -o remount,relatime -t debugfs nodev /mnt
From: Arnaldo Carvalho de Melo
When trying to trace the 'umount' syscall on x86_64 I noticed that it
was failing:
# trace -e umount umount /mnt
event syntax error: 'umount'
\___ parser error
Run 'perf list' for a list of valid events
Usage: perf trace [] []
From: Arnaldo Carvalho de Melo
To silence this perf build warning:
Warning: Kernel ABI header at 'tools/include/uapi/linux/fs.h' differs from
latest version at 'include/uapi/linux/fs.h'
diff -u tools/include/uapi/linux/fs.h include/uapi/linux/fs.h
Due to just two comments added by:
From: Arnaldo Carvalho de Melo
In ebebbf082357 ("perf top: Switch default mode to overwrite mode") we
forgot to leave a way to disable that new default, add a --overwrite
option that can be disabled using --no-overwrite, since the code already
in such a way that we can readily disable this mode.
From: Arnaldo Carvalho de Melo
By using the SCA_FILENAME beautifier, that works when either the
probe:vfs_getname probe is in place or with the eBPF program
tools/perf/examples/bpf/augmented_syscalls.c:
# perf probe -l
probe:vfs_getname (on getname_flags:73@acme/git/linux/fs/namei.c with
From: Arnaldo Carvalho de Melo
The intention is to have this as a library, since it is not perf
specific at all.
I did the switch for the files where I'm the only contributor, with the
exception of a few lines changed by Jiri Olsa.
Acked-by: Jiri Olsa
Cc: Adrian Hunter
Cc: David Ahern
Cc:
From: Arnaldo Carvalho de Melo
It'll use tools/include copy of linux/fs.h to generate a table to be
used by tools, initially by the 'mount' and 'umount' beautifiers in
'perf trace', but that could also be used to translate from a string
constant to the integer value to be used in a eBPF or
From: Arnaldo Carvalho de Melo
Take mount's 'flags' arg, to cope with this semantic, as defined in do_mount in
fs/namespace.c:
/*
* Pre-0.97 versions of mount() didn't have a flags word. When the
* flags word was introduced its top half was required to have the
* magic value
On Wed, Oct 31, 2018 at 04:06:43PM +, Mel Gorman wrote:
> An external fragmentation event was previously described as
>
> When the page allocator fragments memory, it records the event using
> the mm_page_alloc_extfrag event. If the fallback_order is smaller
> than a pageblock
On Tue, 30 Oct 2018 23:47:06 PDT (-0700), Olof Johansson wrote:
A couple of fixes for build breakage or warnings, and a small whitespace/asm
cleanup. The non-cleanups would be good to see in 4.20 to keep builds green.
I'm happy to just keep them all together, since the cleanups are
Hi Linus,
The following changes since commit 84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d:
Linux 4.19 (2018-10-22 07:37:37 +0100)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-4.20-rc1
for you to fetch changes up to
On Wed, Oct 31, 2018 at 5:25 PM, Andy Lutomirski wrote:
> I had an old patch to do much the same thing:
It's a perennial idea. :-)
> https://lore.kernel.org/patchwork/patch/345098/
>
> Can you comment as to how your API compares to my old patch?
Sure. Basically, my approach is sort-of
Hi Arnaldo,
On Wed, Oct 31, 2018 at 12:45:50PM -0300, Arnaldo Carvalho de Melo wrote:
> So I noticed the following build failure thare point to:
>
> commit 09d62154f61316f7e97eae3f31ef8770c7e4b386
> Author: Daniel Borkmann
> Date: Fri Oct 19 15:51:02 2018 +0200
>
> tools, perf: add and
On Wed, Oct 31, 2018 at 03:59:12PM +, Daniel Colascione wrote:
> Add a simple proc-based kill interface. To use /proc/pid/kill, just
> write the signal number in base-10 ASCII to the kill file of the
> process to be killed: for example, 'echo 9 > /proc/$$/kill'.
>
> Semantically,
On Tue, Oct 30, 2018 at 1:49 PM Alex Williamson
wrote:
>
> VFIO updates for v4.20
Pulled,
Linus
On Tue, 2018-10-30 at 11:57 +, Colin Ian King wrote:
> $SUBJECT should be:
>
> tlclk: clean an indentation issue, remove extraneous tabs
Perhaps add missing braces for the last else uses as well?
> On 30/10/2018 11:56, Colin King wrote:
> > From: Colin Ian King
[]
> > diff --git
"For licencing details see kernel-base/COPYING" and similar license
references have no value over the SPDX identifier. Remove them.
Signed-off-by: Thomas Gleixner
Cc: Ingo Molnar
---
include/linux/hrtimer.h |2 --
kernel/time/clockevents.c|3 ---
kernel/time/hrtimer.c|
The SPDX identifier defines the license of the files already. No need for
the boilerplates.
Signed-off-by: Thomas Gleixner
Cc: John Stultz
Cc: Paul E. McKenney
---
kernel/time/alarmtimer.c |4
kernel/time/clocksource.c | 14 --
kernel/time/jiffies.c | 25
The SPDX identifier defines the license of the file already. No need for
the boilerplate.
Remove also the completely outdated Montavista snail mail address.
Signed-off-by: Thomas Gleixner
Cc: Corey Minyard
---
kernel/time/posix-timers.c | 20 +---
1 file changed, 1
Remove the pointless filenames in the top level comments. They have no
value at all and just occupy space. While at it tidy up some of the
comments and remove a stale one.
Signed-off-by: Thomas Gleixner
---
include/linux/hrtimer.h |2 --
kernel/time/clockevents.c|
Add SPDX identifiers to all files in kernel/time and remove the license
boiler plates.
Aside of that use the chance to get rid of (stale) file references and tidy
up the top of file comments as they are touched anyway by this work.
This work is based on a script and data from Philippe
The SPDX identifier is enough. Remove the license boilerplate.
Signed-off-by: Thomas Gleixner
Cc: Kees Cook
Cc: David Riley
Cc: Colin Cross
---
kernel/time/test_udelay.c |9 -
kernel/time/timekeeping_debug.c | 10 --
2 files changed, 19 deletions(-)
---
The SPDX identifier defines the license of the file already. No need for
the boilerplate.
Signed-off-by: Thomas Gleixner
Cc: Nicolas Pitre
Cc: Mark Brown
Cc: Arnd Bergmann
---
kernel/time/posix-stubs.c |4
1 file changed, 4 deletions(-)
--- a/kernel/time/posix-stubs.c
+++
On Wed, Oct 31, 2018 at 11:29 AM wrote:
>
> V1 -> V2: drop changes to include/linux/compiler-gcc.h.
Now the subject line of the patch doesn't match the patch any more..
Linus
From: Jagan Teki
OrangePi Lite2 is Allwinner H6 based open-source SBC,
which support:
- Allwinner H6 Quad-core 64-bit ARM Cortex-A53
- GPU Mali-T720
- 1GB LPDDR3 RAM
- AXP805 PMIC
- AP6356S Wifi/BT
- USB 2.0, USB 3.0 Host, OTG
- HDMI port
- 5V/2A DC power supply
Signed-off-by: Jagan Teki
---
Orangepi H6 boards, One Plus and Lite2 shares common
nodes like axp805, uart, mmc0 etc and the common differences
between them is Ethernet is available in One Plus where
as Wifi, USB3, CSI port is available in Lite2.
So, add common orangepi nodes into sun50i-h6-orangepi.dtsi
Signed-off-by: Jagan
On 10/31/2018 11:42 AM, Marc Zyngier wrote:
On 31/10/18 18:38, Santosh Shilimkar wrote:
On 10/31/2018 11:21 AM, Marc Zyngier wrote:
Hi Grygorii,
[...]
Well, I'm convinced that we do not want a networking driver to be tied
to an interrupt architecture, and that the two should be
On Wed, Oct 31, 2018 at 10:27 AM Palmer Dabbelt wrote:
>
> On Wed, 31 Oct 2018 04:16:10 PDT (-0700), a...@brainfault.org wrote:
> > On Wed, Oct 31, 2018 at 4:06 PM Vincent Chen wrote:
> >>
> >> RISC-V permits each vendor to develop respective extension ISA based
> >> on RISC-V standard ISA.
On Wed, Oct 31, 2018 at 10:46:19AM +0100, Dmitry Vyukov wrote:
> On Wed, Oct 31, 2018 at 4:18 AM, Matthew Wilcox wrote:
> > On Tue, Oct 30, 2018 at 08:00:03AM -0700, syzbot wrote:
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:4b42745211af Merge tag 'armsoc-soc' of
> >>
Some of Huawei laptops come with a LED in the mic mute key. This patch
enables and disable this LED when the internal microphone status is
changed.
Signed-off-by: Ayman Bagabas
---
include/linux/huawei_wmi.h| 7
sound/pci/hda/huawei_wmi_helper.c | 66
On Wed, Oct 31, 2018 at 8:18 PM, Matthew Wilcox wrote:
> On Wed, Oct 31, 2018 at 10:46:19AM +0100, Dmitry Vyukov wrote:
>> On Wed, Oct 31, 2018 at 4:18 AM, Matthew Wilcox wrote:
>> > On Tue, Oct 30, 2018 at 08:00:03AM -0700, syzbot wrote:
>> >> syzbot found the following crash on:
>> >>
>> >>
This driver adds support for missing hotkeys on some Huawei laptops.
Currently, only Huawei Matebook X Pro is supported. The driver
recognizes the following keys: brightness keys, micmute, wlan, and
Huawei special key. The brightness keys are ignored since they work out
of the box.
Signed-off-by:
Thanks for your review feedback, Andy! I'll send a v3 shortly with those
changes you suggested. I've added some comments inline below.
On 10/20/2018 12:40 PM, Andy Shevchenko wrote:
> On Fri, Oct 19, 2018 at 8:24 PM Dan O'Donovan wrote:
>
>> +static int upboard_get_functions_count(struct
Em Wed, Oct 31, 2018 at 07:08:29PM +0100, Daniel Borkmann escreveu:
> On 10/31/2018 06:44 PM, Will Deacon wrote:
> > Diff below...
> I just gave this a spin on 16.04 and it resolves the build issue, thanks
> for the quick fix, Will!
> Tested-by: Daniel Borkmann
It buildz, ship it:
# time dm
Hi Dan,
On Wed, Oct 31, 2018 at 9:45 PM Dan O'Donovan wrote:
> The UP2 board features a Raspberry Pi compatible pin header (HAT) and a
> board-specific expansion connector (EXHAT). Both expose assorted
> functions from either the SoC (such as GPIO, I2C, SPI, UART...) or other
> on-board devices
On Mon, Oct 01, 2018 at 03:03:30PM -0700, Dave Hansen wrote:
> On 10/01/2018 02:42 PM, Jethro Beekman wrote:
> >
> > 1) Even though the vDSO function exists, userspace may still call
> > `ENCLU[EENTER]` manually, so the fault handling as described in the
> > current patch should also be
On 10/31/18, Randy Dunlap wrote:
> On 10/30/18 8:59 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v4.21/v5.1 code to your linux-next included trees
>> until after the merge window closes.
>>
>> Changes since 20181030:
>>
>
>
> on i386:
>
> ld:
On 10/31/2018 09:30 PM, Linus Walleij wrote:
> Hi Dan,
>
> On Wed, Oct 31, 2018 at 9:45 PM Dan O'Donovan wrote:
>
>> The UP2 board features a Raspberry Pi compatible pin header (HAT) and a
>> board-specific expansion connector (EXHAT). Both expose assorted
>> functions from either the SoC (such
On Wed, Oct 31, 2018 at 10:44 AM Ilya Dryomov wrote:
>
> - a series that fixes some old memory allocation issues in libceph
> (myself). We no longer allocate memory in places where allocation
> failures cannot be handled and BUG when the allocation fails.
>
> - support for copy_file_range()
Commit-ID: f932184e282f574cfd34afee917a10b782fd3e76
Gitweb: https://git.kernel.org/tip/f932184e282f574cfd34afee917a10b782fd3e76
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 25 Oct 2018 17:24:45 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 30 Oct 2018 11:46:23 -0300
Commit-ID: 23c07a23cbed389d0b9c7a06486574621df8d1a4
Gitweb: https://git.kernel.org/tip/23c07a23cbed389d0b9c7a06486574621df8d1a4
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 26 Oct 2018 13:51:45 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 30 Oct 2018 11:46:23 -0300
Commit-ID: 476c92cacf383c83584ba02d06c88cf18f062afb
Gitweb: https://git.kernel.org/tip/476c92cacf383c83584ba02d06c88cf18f062afb
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 26 Oct 2018 13:23:25 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 30 Oct 2018 11:46:23 -0300
Commit-ID: 73d141adcea66de656d0c8336811f2b0bbd9700c
Gitweb: https://git.kernel.org/tip/73d141adcea66de656d0c8336811f2b0bbd9700c
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 25 Oct 2018 15:18:06 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 30 Oct 2018 11:46:23 -0300
On Wed, Oct 31, 2018 at 12:59 PM Mark Salter wrote:
>
> c6x changes for 4.20
Pulled,
Linus
On Wed, Oct 31, 2018 at 1:42 PM Palmer Dabbelt wrote:
>
> On Wed, 31 Oct 2018 12:20:40 PDT (-0700), Olof Johansson wrote:
> > On Tue, Oct 30, 2018 at 5:37 AM Anup Patel wrote:
> >>
> >> The printk timestamps are very useful information to visually see
> >> where kernel is spending time during
Am Mittwoch, 31. Oktober 2018, 23:48:07 CET schrieb Linus Torvalds:
> On Wed, Oct 31, 2018 at 2:22 PM Richard Weinberger wrote:
> >
> > - Removal of old and dead code
> > - A bug fix for our tty driver
> > - Other minor cleanups across the code base
>
> Pulled. I may not like recent rebases, but
From: Paul Cercueil
[ Upstream commit 54f919a04cf221bc1601d1193682d4379dacacbd ]
The driver calls clk_get() with the clock name set to NULL, which means
that the driver could only work when probed from devicetree. From now
on, we explicitly require the driver to be probed from devicetree.
From: Emmanuel Grumbach
[ Upstream commit 155f7e0441cd121b1e673d465a35e99f4b9b2f0b ]
Fix a bug that happens in the following scenario:
1) suspend without WoWLAN
2) mac80211 calls drv_stop because of the suspend
3) __iwl_mvm_mac_stop deallocates the aux station
4) during drv_stop the firmware
From: Casey Schaufler
[ Upstream commit dcb569cf6ac99ca899b8109c128b6ae52477a015 ]
This fixes a pair of problems in the Smack ptrace checks
related to checking capabilities. In both cases, as reported
by Lukasz Pawelczyk, the raw capability calls are used rather
than the Smack wrapper that
From: Sanskriti Sharma
[ Upstream commit ce49d8436cffa9b7a6a5f110879d53e89dbc6746 ]
Ensure that all code paths in strbuf_addv() call va_end() on the
ap_saved copy that was made.
Fixes the following coverity complaint:
Error: VARARGS (CWE-237): [#def683]
tools/perf/util/strbuf.c:106:
From: Ivan Khoronzhuk
[ Upstream commit 9737cc99dd14b5b8b9d267618a6061feade8ea68 ]
After flushing all mcast entries from the table, the ones contained in
mc list of ndev are not restored when promisc mode is toggled off,
because they are considered as synched with ALE, thus, in order to
restore
From: Alexandre Belloni
[ Upstream commit 9612f8f503804d2fd2f63aa6ba1e58bba4612d96 ]
The IRQ work is added before the struct rtc is allocated and registered,
but this struct is used in the IRQ handler. This may lead to a NULL pointer
dereference.
Switch to
From: Masami Hiramatsu
[ Upstream commit 819319fc93461c07b9cdb3064f154bd8cfd48172 ]
Make reuse_unused_kprobe() to return error code if
it fails to reuse unused kprobe for optprobe instead
of calling BUG_ON().
Signed-off-by: Masami Hiramatsu
Cc: Anil S Keshavamurthy
Cc: David S . Miller
Cc:
From: Javier Martinez Canillas
[ Upstream commit 0d6d0d62d9505a9816716aa484ebd0b04c795063 ]
For TPM 1.2 chips the system setup utility allows to set the TPM device in
one of the following states:
* Active: Security chip is functional
* Inactive: Security chip is visible, but is not
From: Selvin Xavier
[ Upstream commit d455f29f6d76a5f94881ca1289aaa1e90617ff5d ]
Fix possible recursive lock warning. Its a false warning as the locks are
part of two differnt HW Queue data structure - cmdq and creq. Debug kernel
is throwing the following warning and stack trace.
[
From: James Smart
[ Upstream commit ca7fb76e091f889cfda1287c07a9358f73832b39 ]
On io completion, the driver is taking an adapter wide lock and nulling the
scsi command back pointer. The nulling of the back pointer is to signify the
io was completed and the scsi_done() routine was called.
From: Chao Yu
[ Upstream commit 5cd1f387a13b5188b4edb4c834310302a85a6ea2 ]
Testcase to reproduce this bug:
1. mkfs.f2fs -O extra_attr -O inode_crtime /dev/sdd
2. mount -t f2fs /dev/sdd /mnt/f2fs
3. touch /mnt/f2fs/file
4. xfs_io -f /mnt/f2fs/file -c "fsync"
5. godown /mnt/f2fs
6. umount
From: Tonghao Zhang
[ Upstream commit 4c1ef72e9b71a19fb405ebfcd37c0a5e16fa44ca ]
It is a serious driver defect to enable MSI or MSI-X more than once. Doing
so may panic the kernel as in the stack trace below:
Call Trace:
sysfs_add_one+0xa5/0xd0
create_dir+0x7c/0xe0
From: James Smart
[ Upstream commit ca7fb76e091f889cfda1287c07a9358f73832b39 ]
On io completion, the driver is taking an adapter wide lock and nulling the
scsi command back pointer. The nulling of the back pointer is to signify the
io was completed and the scsi_done() routine was called.
From: Viresh Kumar
[ Upstream commit 51c99dd2c06b234575661fa1e0a1dea6c3ef566f ]
We can not call dev_pm_opp_of_cpumask_remove_table() freely anymore
since the latest OPP core updates as that uses reference counting to
free resources. There are cases where no static OPPs are added (using
DT) for
From: Will Deacon
[ Upstream commit 22839869f21ab3850fbbac9b425ccc4c0023926f ]
The sigaltstack(2) system call fails with -ENOMEM if the new alternative
signal stack is found to be smaller than SIGMINSTKSZ. On architectures
such as arm64, where the native value for SIGMINSTKSZ is larger than
the
From: Chao Yu
[ Upstream commit 19c73a691ccf6fb2f12d4e9cf9830023966cec88 ]
Testcase to reproduce this bug:
1. mkfs.f2fs /dev/sdd
2. mount -t f2fs /dev/sdd /mnt/f2fs
3. touch /mnt/f2fs/file
4. sync
5. chattr +A /mnt/f2fs/file
6. xfs_io -f /mnt/f2fs/file -c "fsync"
7. godown /mnt/f2fs
8. umount
From: Masami Hiramatsu
[ Upstream commit 819319fc93461c07b9cdb3064f154bd8cfd48172 ]
Make reuse_unused_kprobe() to return error code if
it fails to reuse unused kprobe for optprobe instead
of calling BUG_ON().
Signed-off-by: Masami Hiramatsu
Cc: Anil S Keshavamurthy
Cc: David S . Miller
Cc:
From: Paolo Valente
[ Upstream commit cbeb869a3d1110450186b738199963c5e68c2a71 ]
BFQ schedules entities (which represent either per-process queues or
groups of queues) as a function of their timestamps. In particular, as
a function of their (virtual) finish times. The finish time of an
entity
From: Geert Uytterhoeven
[ Upstream commit 760eea43f8c6d48684f1f34b8a02fddc1456e849 ]
The workqueue used for monitoring the hardware may run while the device
is already suspended. Fix this by using the freezable system workqueue
instead, cfr. commit 51e20d0e3a60cf46 ("thermal: Prevent polling
201 - 300 of 2040 matches
Mail list logo
