> Patch #1 and #4 are minor cleanups which follow the boyscout rule:
> "Always leave the campground cleaner than you found it."
> I
> am also looking for suggestions how to handle these cross-tree changes
> (patch #2 belongs to the linux-gpio tree, patches #1, 3 and #4 should
> go through the
Hi Maxime,
On Tue, 28 May 2019 at 13:10, Maxime Ripard wrote:
>
> On Mon, May 27, 2019 at 10:14:52PM +0200, Clément Péron wrote:
> > Hi,
> >
> > This series has been first proposed by Jernej Skrabec[1].
> > As this series is mandatory for SPDIF/I2S support and because he is
> > busy on Cedrus
On Sun, Jun 09, 2019 at 08:06:18PM +0200, Martin Blumenstingl wrote:
> The stmmac driver currently ignores the GPIO flags which are passed via
> devicetree because it operates with legacy GPIO numbers instead of GPIO
> descriptors.
Hi Martin
I don't think this is the reason. I think historically
From: Jarod Wilson
Date: Fri, 7 Jun 2019 11:02:34 -0400
> On 6/7/19 10:59 AM, Jarod Wilson wrote:
>> Seeing bonding debug log data along the lines of "event: 5" is a bit
>> spartan,
>> and often requires a lookup table if you don't remember what every
>> event is.
>> Make use of
From: Jarod Wilson
Date: Fri, 7 Jun 2019 10:59:25 -0400
> This set improves a few somewhat terse bonding debug messages, fixes some
> errors in others, and then standarizes the majority of them, using new
> slave_* printk macros that wrap around netdev_* to ensure both master
> and slave
s390:tinyconfig fails to build with gcc 8.3.0.
arch/s390/include/asm/ctl_reg.h:52:2: error: impossible constraint in 'asm'
asm volatile( \
^~~
arch/s390/include/asm/ctl_reg.h:62:2: note: in expansion of macro '__ctl_store'
__ctl_store(reg, cr, cr);
^~~
From: Huazhong Tan
Date: Fri, 7 Jun 2019 10:03:01 +0800
> This patch-set includes code optimizations, cleanups and bugfixes for
> the HNS3 ethernet controller driver.
Series applied, thanks.
From: Grygorii Strashko
Date: Thu, 6 Jun 2019 19:30:37 +0300
> I grouped all patches in one series for better illustration of the changes,
> but in general Pateches 1-4 are netdev matarieal (first) and other patches
> are platform specific.
Patch 1-4 applied to net-next.
Hi!
> > > This patch series introduces TTY keyboard status request, a feature of
> > > the n_tty line discipline that reserves a character in struct termios
> > > (^T by default) and reacts to it by printing a short informational line
> > > to the terminal and sending a Unix signal to the tty's
From: "Enrico Weigelt, metux IT consult"
Date: Thu, 6 Jun 2019 16:43:17 +0200
> From: Enrico Weigelt
>
> fix an uninitialized variable:
>
> CC net/ipv4/fib_semantics.o
> net/ipv4/fib_semantics.c: In function 'fib_check_nh_v4_gw':
> net/ipv4/fib_semantics.c:1027:12: warning: 'err' may
On Sun, Jun 09, 2019 at 07:41:39PM +0200, Pavel Machek wrote:
> Hi!
>
> > This patch series introduces TTY keyboard status request, a feature of
> > the n_tty line discipline that reserves a character in struct termios
> > (^T by default) and reacts to it by printing a short informational line
>
The of_clk structure has a period field that is set up initially by
timer_of_clk_init(), that period value need to be adjusted for a case of
TIMER1-9 that are running at a fixed rate that doesn't match the clock's
rate. Note that the period value is currently used only by some of the
clocksource
Hello,
I took a look at tegra-timer once again and spotted few more things that
could be improved in addition to [0] which is already in linux-next.
Please apply this small series in addition to [0], thanks in advance!
[0] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=111529
It was left unnoticed by accident, which means that the code could be
cleaned up a tad more.
Signed-off-by: Dmitry Osipenko
---
drivers/clocksource/timer-tegra.c | 40 +++
1 file changed, 25 insertions(+), 15 deletions(-)
diff --git
There is no need to cast void because kernel allows to do that without
a warning message from a compiler.
Signed-off-by: Dmitry Osipenko
---
drivers/clocksource/timer-tegra.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/timer-tegra.c
On Sat, Jun 08, 2019 at 05:31:13PM -0400, Steven Rostedt wrote:
On Sat, 1 Jun 2019 09:14:34 -0400
Sasha Levin wrote:
From: Masami Hiramatsu
[ Upstream commit 3dd1f7f24f8ceec00bbbc364c2ac3c893f0fdc4c ]
Fix to make the type of $comm "string". If we set the other type to $comm
argument, it
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Cc: Daniel Mack
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/leds/leds-lt3593.txt | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git
Switch to using generic LED support for composing LED class
device name.
Signed-off-by: Jacek Anaszewski
Cc: Baolin Wang
Acked-by: Pavel Machek
---
drivers/leds/leds-sc27xx-bltc.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
diff --git
Introduce dedicated properties for conveying information about
LED function and color. Mark old "label" property as deprecated.
Additionally function-enumerator property is being provided
for the cases when neither function nor color can be used
for LED differentiation.
Signed-off-by: Jacek
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Cc: Baolin Wang
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/leds/leds-sc27xx-bltc.txt | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
Switch to using generic LED support for composing LED class
device name.
Signed-off-by: Jacek Anaszewski
Tested-by: Dan Murphy
Acked-by: Pavel Machek
---
drivers/leds/leds-lm3601x.c | 38 +-
1 file changed, 17 insertions(+), 21 deletions(-)
diff --git
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Cc: Oleh Kravchenko
Reviewed-by: Rob Herring
---
.../devicetree/bindings/leds/leds-cr0014114.txt| 26 --
1 file changed, 19 insertions(+), 7 deletions(-)
Switch to using generic LED support for composing LED class
device name.
After switching to new led_classdev_register_ext() the validity
of struct led_classdev's name property is no longer guaranteed,
and therefore rely on struct device's kobj.name instead.
Signed-off-by: Jacek Anaszewski
Cc:
Switch to using generic LED support for composing LED class
device name.
Signed-off-by: Jacek Anaszewski
Cc: Daniel Mack
Acked-by: Pavel Machek
---
drivers/leds/leds-lt3593.c | 20
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/drivers/leds/leds-lt3593.c
Switch to using generic LED support for composing LED class
device name.
While at it, avoid iterating through available child of nodes
in favor of obtaining single expected child node using single
call to of_get_next_available_child().
Signed-off-by: Jacek Anaszewski
Acked-by: Pavel Machek
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Reviewed-by: Rob Herring
Reviewed-by: Dan Murphy
---
Documentation/devicetree/bindings/leds/leds-lp8860.txt | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Reviewed-by: Dan Murphy
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/leds/leds-lm3601x.txt | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff
Switch to using generic LED support for composing LED class
device name.
After switching to new led_classdev_register_ext() the validity
of struct led_classdev's name property is no longer guaranteed,
and therefore rely on struct device's kobj.name instead.
Signed-off-by: Jacek Anaszewski
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/leds/leds-aat1290.txt | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Cc: Simon Shields
Reviewed-by: Rob Herring
---
.../devicetree/bindings/leds/leds-an30259a.txt | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Cc: Linus Walleij
Reviewed-by: Rob Herring
---
.../devicetree/bindings/leds/leds-gpio.txt | 23 +++---
1 file changed, 16 insertions(+), 7 deletions(-)
diff
Switch to using generic LED support for composing LED class
device name.
At this occassion remove initialization of struct led_classdev's
dev->of_node property in the driver, since now it will be taken from
fwnode assigned to struct led_init_data and passed to the new
Switch to using generic LED support for composing LED class
device name.
At this occassion remove initialization of struct led_classdev's
dev->of_node property in the driver, since now it will be taken from
fwnode assigned to struct led_init_data and passed to the new
Switch to using generic LED support for composing LED class
device name.
Signed-off-by: Jacek Anaszewski
Cc: Simon Shields
---
drivers/leds/leds-an30259a.c | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/drivers/leds/leds-an30259a.c
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Also, fix malformed syntax of address-cells and size-cells
in the example.
Signed-off-by: Jacek Anaszewski
Cc: Sakari Ailus
Reviewed-by: Rob Herring
---
.../devicetree/bindings/leds/ams,as3645a.txt | 22
Add a documentation for standard LED functions with regard
to differences in meaning between cases when devicename section
of LED name is present or not.
Signed-off-by: Jacek Anaszewski
---
Documentation/leds/led-functions.txt | 223 +++
Add generic support for composing LED class device name. The newly
introduced led_compose_name() function composes device name according
to either or pattern,
depending on the configuration of initialization data.
Backward compatibility with in-driver hard-coded LED class device
names is
Switch to using generic LED support for composing LED class
device name.
Signed-off-by: Jacek Anaszewski
Cc: Linus Walleij
---
drivers/leds/leds-gpio.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/drivers/leds/leds-gpio.c
Add initial set of common LED function definitions.
Signed-off-by: Jacek Anaszewski
Cc: Baolin Wang
Cc: Daniel Mack
Cc: Linus Walleij
Cc: Oleh Kravchenko
Cc: Sakari Ailus
Cc: Simon Shields
Reviewed-by: Rob Herring
Acked-by: Pavel Machek
Reviewed-by: Dan Murphy
---
Replace of_led_classdev_register() with led_classdev_register_ext(), which
accepts easily extendable struct led_init_data, instead of the fixed
struct device_node argument. The latter can be now passed in an fwnode
property of the struct led_init_data.
The modification is driven by the need for
Refer to new "function" and "color" properties and mark "label"
as deprecated.
Signed-off-by: Jacek Anaszewski
Reviewed-by: Dan Murphy A
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/leds/leds-lm3692x.txt | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff
Add common LED color identifiers.
Signed-off-by: Jacek Anaszewski
Cc: Baolin Wang
Cc: Daniel Mack
Cc: Linus Walleij
Cc: Oleh Kravchenko
Cc: Sakari Ailus
Cc: Simon Shields
Reviewed-by: Rob Herring
Acked-by: Pavel Machek
Reviewed-by: Dan Murphy
---
include/dt-bindings/leds/common.h | 11
Changes from v4:
- switched "charge" function name to "charging"
- added "cpu", "mute", "micmute", "disk-activity", "panic", "mtd" LED functions
to cover all existing triggers and removed now redundant "nand" and "mmc"
- added "capslock", "scrollock", "numlock" LED functions
- removed now
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Sunday 9 June 2019 12:28
> To: Dragan Cvetic
> Cc: a...@arndb.de; Michal Simek ;
> linux-arm-ker...@lists.infradead.org; robh...@kernel.org;
> mark.rutl...@arm.com; devicet...@vger.kernel.org;
>
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Sunday 9 June 2019 12:23
> To: Dragan Cvetic
> Cc: a...@arndb.de; Michal Simek ;
> linux-arm-ker...@lists.infradead.org; robh...@kernel.org;
> mark.rutl...@arm.com; devicet...@vger.kernel.org;
>
On Sat, May 25, 2019 at 5:18 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:4dde821e Merge tag 'xfs-5.2-fixes-1' of git://git.kernel.o..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=107db73aa0
> kernel config:
On 2019 Jun 09, Klaus Kusche wrote:
>
> Hello,
>
> Same problem for linux 5.1.7:
> Kernel building fails with the same relocation error.
>
> 5.1.5 does not have the problem, builds fine for me.
>
> Is there anything I can do to investigate the problem?
>
Please try linux 5.1.8. The
Change stmmac_mdio_reset() to use device_property_read_u32_array()
instead of of_property_read_u32_array().
This is meant as a cleanup because we can drop the struct device_node
variable. Also it will make it easier to get rid of struct
stmmac_mdio_bus_data (or at least make it private) in the
A simplified version of the existing code looks like this:
if (priv->device->of_node) {
struct device_node *np = priv->device->of_node;
if (!np)
return 0;
The second "if" never evaluates to true because the first "if" checks
for exactly the opposite.
Drop the redundant
Recent Amlogic SoCs (G12A which includes S905X2 and S905D2 as well as
G12B which includes S922X) use GPIOZ_14 or GPIOZ_15 for the PHY reset
line. These GPIOs are special because they are marked as "3.3V input
tolerant open drain (OD) pins" which means they can only drive the pin
output LOW (to
Switch stmmac_mdio_reset to use GPIO descriptors. GPIO core handles the
"snps,reset-gpio" for GPIO descriptors so we don't need to take care of
it inside the driver anymore.
The advantage of this is that we now preserve the GPIO flags which are
passed via devicetree. This is required on some
The stmmac driver currently ignores the GPIO flags which are passed via
devicetree because it operates with legacy GPIO numbers instead of GPIO
descriptors. stmmac assumes that the GPIO is "active HIGH" by default.
This can be overwritten by setting "snps,reset-active-low" to make the
reset line
The PHY reset line and interrupt line are swapped on the X96 Max
compared to the Odroid-N2 schematics. This means:
- GPIOZ_14 is the interrupt line (on the Odroid-N2 it's the reset line)
- GPIOZ_15 is the reset line (on the Odroid-N2 it's the interrupt line)
Also the GPIOZ_14 and GPIOZ_15 pins
Hi!
> On Thu, Jun 6, 2019 at 2:06 AM Joe Perches wrote:
> > Perhaps a checkpatch change too:
> >
> > The first block updates unsigned only bitfields
> > The second tests uapi definitions and suggests "__
> Good.
>
> In addition,
>
> "warn if __u8, __u16, __u32, __u64 are used outside of
Hi!
> This patch series introduces TTY keyboard status request, a feature of
> the n_tty line discipline that reserves a character in struct termios
> (^T by default) and reacts to it by printing a short informational line
> to the terminal and sending a Unix signal to the tty's foreground
>
On Sun, Jun 09, 2019 at 06:38:26PM +0200, Greg KH wrote:
> On Sun, Jun 09, 2019 at 12:39:08PM +, Kirill Smelkov wrote:
> > Hello stable team,
> >
> > Please consider applying the following 2 patches to Linux-4.14 stable
> > tree. The patches fix regression introduced in 3.14 where both read
From: David Ahern
[ Upstream commit 4b2a2bfeb3f056461a90bd621e8bd7d03fa47f60 ]
Commit cd9ff4de0107 changed the key for IFF_POINTOPOINT devices to
INADDR_ANY but neigh_xmit which is used for MPLS encapsulations was not
updated to use the altered key. The result is that every packet Tx does
a
From: Jakub Kicinski
[ Upstream commit e52972c11d6b1262964db96d65934196db621685 ]
Commit 38030d7cb779 ("net/tls: avoid NULL-deref on resync during device
removal")
tried to fix a potential NULL-dereference by taking the
context rwsem. Unfortunately the RX resync may get called
from soft IRQ,
From: David Ahern
[ Upstream commit 64c6f4bbca748c3b2101469a76d88b7cd1c00476 ]
Ian and Alan both reported seeing overflows after upgrades to 5.x kernels:
neighbour: arp_cache: neighbor table overflow!
Alan's mpls script helped get to the bottom of this bug. When a new entry
is created the
From: Erez Alfasi
[ Upstream commit 135dd9594f127c8a82d141c3c8430e9e2143216a ]
Querying EEPROM high pages data for SFP module is currently
not supported by our driver but is still tried, resulting in
invalid FW queries.
Set the EEPROM ethtool data length to 256 for SFP module to
limit the
From: Olivier Matz
[ Upstream commit b9aa52c4cb457e7416cc0c95f475e72ef4a61336 ]
The following code returns EFAULT (Bad address):
s = socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6);
setsockopt(s, SOL_IPV6, IPV6_HDRINCL, 1);
sendto(ipv6_icmp6_packet, addr); /* returns -1, errno = EFAULT */
From: Paul Burton
commit e4f2d1af7163becb181419af9dece9206001e0a6 upstream.
The pistachio platform uses the U-Boot bootloader & generally boots a
kernel in the uImage format. As such it's useful to build one when
building the kernel, but to do so currently requires the user to
manually specify
From: Xin Long
[ Upstream commit 0a90478b93a46bdcd56ba33c37566a993e455d54 ]
With the topo:
h1 ---| rp1|
| route rp3 |--- h3 (192.168.200.1)
h2 ---| rp2|
If rp1 bc_forwarding is set while rp2 bc_forwarding is not, after
doing "ping
From: Miklos Szeredi
commit a2bc92362941006830afa3dfad6caec1f99acbf5 upstream.
Prior to sending COPY_FILE_RANGE to userspace filesystem, we must flush all
dirty pages in both the source and destination files.
This patch adds the missing flush of the source file.
Tested on libfuse-3.5.0 with:
From: Eugeniy Paltsev
commit a8c715b4dd73c26a81a9cc8dc792aa715d8b4bb2 upstream.
As of today if userspace process tries to access a kernel virtual addres
(0x7000_ to 0x7_) such that a legit kernel mapping already
exists, that process hangs instead of being killed with SIGSEGV
Fix
From: Yihao Wu
commit ba851a39c9703f09684a541885ed176f8fb7c868 upstream.
When a waiter is waked by CB_NOTIFY_LOCK, it will retry
nfs4_proc_setlk(). The waiter may fail to nfs4_proc_setlk() and sleep
again. However, the waiter is already removed from clp->cl_lock_waitq
when handling
From: Zhu Yanjun
[ Upstream commit 85cb928787eab6a2f4ca9d2a798b6f3bed53ced1 ]
When the following tests last for several hours, the problem will occur.
Server:
rds-stress -r 1.1.1.16 -D 1M
Client:
rds-stress -r 1.1.1.14 -s 1.1.1.16 -D 1M -T 30
The following will occur.
"
Starting
From: Trond Myklebust
commit 7987b694ade8cc465ce10fb3dceaa614f13ceaf3 upstream.
The addition of rpc_check_timeout() to call_decode causes an Oops
when the RPCSEC_GSS credential is rejected.
The reason is that rpc_decode_header() will call xprt_release() in
order to free task->tk_rqstp, which is
From: Dan Carpenter
commit 110080cea0d0e4dfdb0b536e7f8a5633ead6a781 upstream.
There are a couple potential integer overflows here.
round_up(m->size + (m->addr & ~PAGE_MASK), PAGE_SIZE);
The first thing is that the "m->size + (...)" addition could overflow,
and the second is that
From: Dan Carpenter
commit bd17cc5a20ae9aaa3ed775f360b75ff93cd66a1d upstream.
The limit here is supposed to be how much of the page is left, but it's
just using PAGE_SIZE as the limit.
The other thing to remember is that snprintf() returns the number of
bytes which would have been copied if we
From: Helen Koike
commit c16b85559dcfb5a348cc085a7b4c75ed49b05e2c upstream.
Async update callbacks are expected to set the old_fb in the new_state
so prepare/cleanup framebuffers are balanced.
Calling drm_atomic_set_fb_for_plane() (which gets a reference of the new
fb and put the old fb) is
This is the start of the stable review cycle for the 5.1.9 release.
There are 70 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 should be made by Tue 11 Jun 2019 04:40:04 PM UTC.
Anything
From: Helen Koike
commit d985a3533274ef7dd1ccb25cb05a72259b25268f upstream.
In the case of async update, modifications are done in place, i.e. in the
current plane state, so the new_state is prepared and the new_state is
cleaned up (instead of the old_state, unlike what happens in a
normal sync
From: Aaron Liu
commit bdb1ccb080dafc1b4224873a5b759ff85a7d1c10 upstream.
In amdgpu_atif_handler, when hotplug event received, remove
ATPX_DGPU_REQ_POWER_FOR_DISPLAYS check. This bit's check will cause missing
system resume.
Signed-off-by: Aaron Liu
Reviewed-by: Alex Deucher
Signed-off-by:
From: Alex Deucher
commit 9d6fea5744d6798353f37ac42a8a653a2607ca69 upstream.
In case we need to use them for GPU reset prior initializing the
asic. Fixes a crash if the driver attempts to reset the GPU at driver
load time.
Acked-by: Christian König
Signed-off-by: Alex Deucher
Cc:
From: Helen Koike
commit 332af874db929f92931727bfe191b2c666438c81 upstream.
Async update callbacks are expected to set the old_fb in the new_state
so prepare/cleanup framebuffers are balanced.
Calling drm_atomic_set_fb_for_plane() (which gets a reference of the new
fb and put the old fb) is
From: Tina Zhang
commit 387a4c2b55291b37e245c840813bd8a8bd06ed49 upstream.
Stack struct intel_gvt_gtt_entry value needs to be initialized before
being used, as the fields may contain garbage values.
W/o this patch, set_ggtt_entry prints:
-
274.046840:
From: Jiri Kosina
commit ec527c318036a65a083ef68d8ba95789d2212246 upstream.
As explained in
0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
we always, no matter what, have to bring up x86 HT siblings during boot at
least once in order to avoid first MCE bringing the
From: Paolo Abeni
[ Upstream commit 720f1de4021f09898b8c8443f3b3e995991b6e3a ]
Currently, the process issuing a "start" command on the pktgen procfs
interface, acquires the pktgen thread lock and never release it, until
all pktgen threads are completed. The above can blocks indefinitely any
From: Yihao Wu
commit 52b042ab9948cc367b61f9ca9c18603aa7813c3a upstream.
Commit b7dbcc0e433f "NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a
waiter"
found this bug. However it didn't fix it.
This commit replaces schedule_timeout() with wait_woken() and
default_wake_function() with
On Sun, Jun 9, 2019 at 10:40 PM Joe Perches wrote:
>
> On Sun, 2019-06-09 at 22:08 +0900, Masahiro Yamada wrote:
> > On Sun, Jun 9, 2019 at 8:57 PM Joe Perches wrote:
> > > On Sun, 2019-06-09 at 16:14 +0900, Masahiro Yamada wrote:
> > > > Hi Joe,
> > > >
> > > > On Thu, Jun 6, 2019 at 2:06 AM
From: Kees Cook
commit b77fa617a2ff4d6beccad3d3d4b3a1f2d10368aa upstream.
Since the console writer does not use the preallocated crash dump buffer
any more, there is no reason to perform locking around it.
Fixes: 70ad35db3321 ("pstore: Convert console write to use ->write_buf")
Signed-off-by:
From: Xin Long
[ Upstream commit 0a90478b93a46bdcd56ba33c37566a993e455d54 ]
With the topo:
h1 ---| rp1|
| route rp3 |--- h3 (192.168.200.1)
h2 ---| rp2|
If rp1 bc_forwarding is set while rp2 bc_forwarding is not, after
doing "ping
From: Jann Horn
commit de9f869616dd95e95c00bdd6b0fcd3421e8a4323 upstream.
get_desc() computes a pointer into the LDT while holding a lock that
protects the LDT from being freed, but then drops the lock and returns the
(now potentially dangling) pointer to its caller.
Fix it by giving the
From: Emil Lenngren
commit f4cb4d7b46f6409382fd981eec9556e1f3c1dc5d upstream.
The datasheet specifies the upper four bits are reserved.
Testing on real hardware shows that these bits can indeed be nonzero.
Signed-off-by: Emil Lenngren
Reviewed-by: Boris Brezillon
Signed-off-by: Miquel Raynal
From: Xin Long
[ Upstream commit b7999b07726c16974ba9ca3bb9fe98ecbec5f81c ]
In Jianlin's testing, netperf was broken with 'Connection reset by peer',
as the cookie check failed in rt6_check() and ip6_dst_check() always
returned NULL.
It's caused by Commit 93531c674315 ("net/ipv6: separate
From: Willem de Bruijn
[ Upstream commit afa0925c6fcc6a8f610e996ca09bc3215048033c ]
Rollover used to use a complex RCU mechanism for assignment, which had
a race condition. The below patch fixed the bug and greatly simplified
the logic.
The feature depends on fanout, but the state is private
From: Miklos Szeredi
commit 35d6fcbb7c3e296a52136347346a698a35af3fda upstream.
Do the proper cleanup in case the size check fails.
Tested with xfstests:generic/228
Reported-by: kbuild test robot
Reported-by: Dan Carpenter
Fixes: 0cbade024ba5 ("fuse: honor RLIMIT_FSIZE in
From: Roger Pau Monne
commit 1d5c76e66433382a1e170d1d5845bb0fed7467aa upstream.
There's no reason to request physically contiguous memory for those
allocations.
[boris: added CC to stable]
Cc: sta...@vger.kernel.org
Reported-by: Ian Jackson
Signed-off-by: Roger Pau Monné
Reviewed-by:
From: Andres Rodriguez
commit 30d62d4453e49f85dd17b2ba60bbb68b6593dba0 upstream.
Add vendor/product pairs for the Valve Index HMDs.
Signed-off-by: Andres Rodriguez
Cc: Dave Airlie
Cc: # v4.15
Signed-off-by: Dave Airlie
Link:
From: Greg Kroah-Hartman
This reverts commit ca8648816e3dcc8dadba0e79a034f61c85eb206d which is
commit a1e8783db8e0d58891681bc1e6d9ada66eae8e20 upstream.
Petr writes:
Karl has reported to me today, that he's experiencing weird
reboot hang on his devices with 4.9.180 kernel and
From: Helen Koike
commit 89a4aac0ab0e6f5eea10d7bf4869dd15c3de2cd4 upstream.
In the case of a normal sync update, the preparation of framebuffers (be
it calling drm_atomic_helper_prepare_planes() or doing setups with
drm_framebuffer_get()) are performed in the new_state and the respective
From: Jann Horn
commit de9f869616dd95e95c00bdd6b0fcd3421e8a4323 upstream.
get_desc() computes a pointer into the LDT while holding a lock that
protects the LDT from being freed, but then drops the lock and returns the
(now potentially dangling) pointer to its caller.
Fix it by giving the
From: Daniel Drake
commit 396dd8143bdd94bd1c358a228a631c8c895a1126 upstream.
On many (all?) the Gemini Lake systems we work with, there is frequent
momentary graphical corruption at the top of the screen, and it seems
that disabling framebuffer compression can avoid this.
The ticket was
From: Zhu Yanjun
[ Upstream commit 85cb928787eab6a2f4ca9d2a798b6f3bed53ced1 ]
When the following tests last for several hours, the problem will occur.
Server:
rds-stress -r 1.1.1.16 -D 1M
Client:
rds-stress -r 1.1.1.14 -s 1.1.1.16 -D 1M -T 30
The following will occur.
"
Starting
From: Erez Alfasi
[ Upstream commit 135dd9594f127c8a82d141c3c8430e9e2143216a ]
Querying EEPROM high pages data for SFP module is currently
not supported by our driver but is still tried, resulting in
invalid FW queries.
Set the EEPROM ethtool data length to 256 for SFP module to
limit the
From: Jiri Slaby
commit 4cdd17ba1dff20ffc99fdbd2e6f0201fc7fe67df upstream.
We need to compute the uart state only on the first open. This is
usually what is done in the ->install hook. serial_core used to do this
in ->open on every open. So move it to ->install.
As a side effect, it ensures
From: Hangbin Liu
[ Upstream commit 4970b42d5c362bf873982db7d93245c5281e58f4 ]
This reverts commit e9919a24d3022f72bcadc407e73a6ef17093a849.
Nathan reported the new behaviour breaks Android, as Android just add
new rules and delete old ones.
If we return 0 without adding dup rules, Android
On Tue, Jun 04, 2019 at 07:44:54PM -0700, Roman Gushchin wrote:
> Let's reparent memcg slab memory on memcg offlining. This allows us
> to release the memory cgroup without waiting for the last outstanding
> kernel object (e.g. dentry used by another application).
>
> So instead of reparenting
101 - 200 of 795 matches
Mail list logo
