4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 8681ef1f3d295bd3600315325f3b3396d76d02f6 ]
Fixes: 3b89ea9c5902 ("net: Fix for_each_netdev_feature on Big endian")
Suggested-by: Eric Dumazet
Signed-off-by:
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 07bd14ccc3049f9c0147a91a4227a571f981601a ]
Add the missing unlock before return from function set_fan_div()
in the error handling case.
Fixes: c9c63915519b ("hwmon: (lm80) fix a miss
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
[ Upstream commit 3bed3cc4156eedf652b4df72bdb35d4f1a2a739d ]
This patch addresses the fact that there are drivers, specifically tun,
that will call into the network page fragmen
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kai-Heng Feng
[ Upstream commit 1765f5dcd00963e33f1b8a4e0f34061fbc0e2f7f ]
Another platform requires even longer delay to make the device work
correctly after S3.
So increase the delay to 300m
Hi Bo,
On 2019/2/21 22:28, Bo YU wrote:
> From: Bo Yu
>
> Fix sparse warnings:
>
> drivers/staging/erofs/utils.c:134:6: warning: symbol
> 'erofs_try_to_release_workgroup' was not declared. Should it be static?
>
> Fixes: 51232df5e4b26("staging: erofs: fix race when the managed cache is
> enab
Hello,
syzbot found the following crash on:
HEAD commit:c433570458e4 ax25: fix a use-after-free in ax25_fillin_cb()
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=1352f84b40
kernel config: https://syzkaller.appspot.com/x/.config?x=4b137b8ba637eb77
dashboar
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hauke Mehrtens
[ Upstream commit 3b89ea9c5902acccdbbdec307c85edd1bf52515e ]
The features attribute is of type u64 and stored in the native endianes on
the system. The for_each_set_bit() macro t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre Torgue
[ Upstream commit 224babd62d6f19581757a6d8bae3bf9501fc10de ]
GMAC IP is little-endian and used on several kind of CPU (big or little
endian). Main callbacks functions of the st
Le 21/02/2019 à 14:51, Michael Ellerman a écrit :
Christophe Leroy writes:
Now that mmu_mapin_ram() is able to handle other blocks
than the one starting at 0, the WII can use it for all
its blocks.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/pgtable_32.c | 27 +--
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
[ Upstream commit 3bed3cc4156eedf652b4df72bdb35d4f1a2a739d ]
This patch addresses the fact that there are drivers, specifically tun,
that will call into the network page fragmen
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hauke Mehrtens
[ Upstream commit 3b89ea9c5902acccdbbdec307c85edd1bf52515e ]
The features attribute is of type u64 and stored in the native endianes on
the system. The for_each_set_bit() macro t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 2c4cc9712364c051b1de2d175d5fbea6be948ebf ]
ICMP handlers are not very often stressed, we should
make them more resilient to bugs that might surface in
the future.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit cf657d22ee1f0e887326a92169f2e28dc932fd10 upstream.
Due to quadratic behavior of x25_new_lci(), syzbot was able
to trigger an rcu stall.
Fix this by not blocking BH for the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit cf657d22ee1f0e887326a92169f2e28dc932fd10 upstream.
Due to quadratic behavior of x25_new_lci(), syzbot was able
to trigger an rcu stall.
Fix this by not blocking BH for the
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit d5be7f632bad0f489879eed0ff4b99bd7fe0b74c ]
Syzkaller again found a path to a kernel crash through bad gso input.
By building an excessively large packet to cause an skb field to wrap
Hello,
syzbot found the following crash on:
HEAD commit:b71acb0e3721 Merge branch 'linus' of git://git.kernel.org/..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1672a39b40
kernel config: https://syzkaller.appspot.com/x/.config?x=b03c5892bb940c76
da
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Petr Machata
[ Upstream commit 289460404f6947ef1c38e67d680be9a84161250b ]
The function-local variable "delay" enters the loop interpreted as delay
in bits. However, inside the loop it gets ove
From: YueHaibing
KASAN has found use-after-free in fixed_mdio_bus_init,
commit 0c692d07842a ("drivers/net/phy/mdio_bus.c: call
put_device on device_register() failure") call put_device()
while device_register() fails,give up the last reference
to the device and allow mdiobus_release to be execute
On Thu, Feb 21, 2019 at 11:34:51AM +, Steven Price wrote:
> Exposing the pud/pgd levels of the page tables to walk_page_range() means
> we may come across the exotic large mappings that come with large areas
> of contiguous memory (such as the kernel's linear map).
>
> Expose p?d_large() from
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e75913c93f7cd5f338ab373c34c93a655bd309cb ]
Follow those steps:
# ip addr add 2001:123::1/32 dev eth0
# ip addr add 2001:123:456::2/64 dev eth0
# ip addr del 2001:123::1/32 dev eth
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
commit 07bd14ccc3049f9c0147a91a4227a571f981601a upstream.
Add the missing unlock before return from function set_fan_div()
in the error handling case.
Fixes: c9c63915519b ("hwmon:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 63530aba7826a0f8e129874df9c4d264f9db3f9e upstream.
syzbot found that ax25 routes where not properly protected
against concurrent use [1].
In this particular report the bug
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c09551c6ff7fe16a79a42133bcecba5fc2fc3291 ]
According to the algorithm described in the comment block at the
beginning of ip_rt_send_redirect, the host should try to send
'ip_rt_redir
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 1765f5dcd00963e33f1b8a4e0f34061fbc0e2f7f ]
Another platform requires even longer delay to make the device work
correctly after S3.
So increase the delay to 300ms.
BugLink: https://
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 225d9464268599a5b4d094d02ec17808e44c7553 ]
In the unlikely event that the kmalloc call in vmci_transport_socket_init()
fails, we end-up calling vmci_transport_destruct() with a NULL
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 88a8121dc1d3d0dbddd411b79ed236b6b6ea415c ]
Since commit cb9f1b783850, scapy (which uses an AF_PACKET socket in
SOCK_RAW mode) is unable to send a basic icmp packet over a sit tunnel:
On Thu, Feb 21, 2019 at 2:05 AM Kees Cook wrote:
> On Mon, Feb 18, 2019 at 4:52 PM Jann Horn wrote:
> > AFAICS the byte_at_a_time loop exits when max==0 is reached, and then
> > if `res >= count` (in other words, if we've copied as many bytes as
> > requested, haven't encountered a null byte so f
4.9-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 07bd14ccc3049f9c0147a91a4227a571f981601a ]
Add the missing unlock before return from function set_fan_div()
in the error handling case.
Fixes: c9c63915519b ("hwmon: (lm80) fix a miss
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 4179cb5a4c924cd233eaadd081882425bc98f44e ]
netif_rx() must be called under a strict contract.
At device dismantle phase, core networking clears IFF_UP
and flush_all_backlogs() is ca
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit d2fd6e81912a665993b24dcdc1c1384a42a54f7e ]
The disable_acs_redir parameter stores a pointer to the string passed to
pci_setup(). However, the string passed to PCI setup is actually
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 04c03114be82194d4a4858d41dba8e286ad1787c ]
soukjin bae reported a crash in tcp_v4_err() handling
ICMP_DEST_UNREACH after tcp_write_queue_head(sk)
returned a NULL
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Blumenstingl
commit 83e418a805d880a8b18add07f94d19b2a5a80307 upstream.
Commit bb364890323cca ("mmc: meson-gx: Free irq in release() callback")
changed the _probe code to use request_thr
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Kocialkowski
[ Upstream commit 197f9ab7f08ce4b9ece662f747c3991b2f0fbb57 ]
Some PHY drivers like the generic one do not provide a read_status
callback on their own but rely on genphy_read_s
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mao Wenan
[ Upstream commit 9060cb719e61b685ec0102574e10337fa5f445ea ]
KASAN has found use-after-free in sockfs_setattr.
The existed commit 6d8c50dcb029 ("socket: close race condition between
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit bdcc5bc25548ef6b08e2e43937148f907c212292 upstream.
Since mISDN_close() uses dev->pending to iterate over active
timers, there is a chance that one timer got removed from the
On Thu, Feb 21, 2019 at 03:15:30PM +0100, Greg Kroah-Hartman wrote:
> Ugh, good catch!
>
> Any hint as to what type of testing that you did that caught this? I
> keep asking people to run some kvm tests, but so far no one is :(
We caught this at SUSE while testing candidate kernel updates for on
4.9-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e75913c93f7cd5f338ab373c34c93a655bd309cb ]
Follow those steps:
# ip addr add 2001:123::1/32 dev eth0
# ip addr add 2001:123:456::2/64 dev eth0
# ip addr del 2001:123::1/32 dev eth0
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jose Abreu
[ Upstream commit 8a7493e58ad688eb23b81e45461c5d314f4402f1 ]
We are saving the status of EEE even before we try to enable it. This
leads to a race with XMIT function that tries to ar
On 21/02/2019 14:32, Qii Wang wrote:
> On Wed, 2019-02-20 at 16:25 +0100, Matthias Brugger wrote:
>>
>> On 20/02/2019 13:33, Qii Wang wrote:
>>> Add MT8183 i2c binding to binding file. Compare to MT2712 i2c
>>> controller, MT8183 has different registers, offsets, and clock.
>>>
>>> Signed-off-by
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 04c03114be82194d4a4858d41dba8e286ad1787c ]
soukjin bae reported a crash in tcp_v4_err() handling
ICMP_DEST_UNREACH after tcp_write_queue_head(sk)
returned a NULL
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit cf657d22ee1f0e887326a92169f2e28dc932fd10 upstream.
Due to quadratic behavior of x25_new_lci(), syzbot was able
to trigger an rcu stall.
Fix this by not blocking BH for the
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 225d9464268599a5b4d094d02ec17808e44c7553 ]
In the unlikely event that the kmalloc call in vmci_transport_socket_init()
fails, we end-up calling vmci_transport_destruct() with a NULL v
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 224babd62d6f19581757a6d8bae3bf9501fc10de ]
GMAC IP is little-endian and used on several kind of CPU (big or little
endian). Main callbacks functions of the stmmac drivers take care a
Hello,
syzbot found the following crash on:
HEAD commit:48b161983ae5 Merge tag 'xarray-5.0-rc3' of git://git.infra..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10cc68ef40
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
das
4.20-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 63530aba7826a0f8e129874df9c4d264f9db3f9e upstream.
syzbot found that ax25 routes where not properly protected
against concurrent use [1].
In this particular report the bug
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit a8e911d13540487942d53137c156bd7707f66e5d ]
If the kernel is configured with KASAN_EXTRA, the stack size is
increasted significantly because this option sets "-fstack-reuse" to
"none"
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 07bd14ccc3049f9c0147a91a4227a571f981601a ]
Add the missing unlock before return from function set_fan_div()
in the error handling case.
Fixes: c9c63915519b ("hwmon: (lm80) fix a mis
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 289460404f6947ef1c38e67d680be9a84161250b ]
The function-local variable "delay" enters the loop interpreted as delay
in bits. However, inside the loop it gets overwritten by the resul
4.20-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit c4c07b4d6fa1f11880eab8e076d3d060ef3f55fc upstream.
The generic ASN.1 decoder infrastructure doesn't guarantee that callbacks
will get as much data as they expect; callbacks ha
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 83e418a805d880a8b18add07f94d19b2a5a80307 ]
Commit bb364890323cca ("mmc: meson-gx: Free irq in release() callback")
changed the _probe code to use request_threaded_irq() instead of
de
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 4974d5f678abb34401558559d47e2ea3d1c15cba ]
After commit c706863bc890 ("net: ip6_gre: always reports o_key to
userspace"), ip6gre and ip6gretap tunnels started reporting TUNNEL_KEY
ou
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 8a7493e58ad688eb23b81e45461c5d314f4402f1 ]
We are saving the status of EEE even before we try to enable it. This
leads to a race with XMIT function that tries to arm EEE timer before
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 816db7663565cd23f74ed3d5c9240522e3fb0dda ]
When fail, translate_desc() returns negative value, otherwise the
number of iovs. So we should fail when the return value is negative
inste
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Roedel
The stable backport of upstream commit
904e14fb7cb96 KVM: VMX: make MSR bitmaps per-VCPU
has a bug in vmx_msr_bitmap_mode(). It enables the x2apic
MSR-bitmap when the kern
On Wed, Feb 20, 2019 at 12:17 AM Joel Fernandes wrote:
>
> Firstly, I want to apologize for not testing this and other corner cases you
> brought up. I should have known better. Since my build was working, I assumed
> that the feature is working. For that, I am very sorry.
You do not need to ap
4.20-stable review patch. If anyone has any objections, please let me know.
--
Commit 582a32e708823e5957fd73ccd78dc4a9e49d21ea upstream.
This reverts commit eff896288872d687d9662000ec9ae11b6d61766f, which
deferred the processing of persistent memory reservations to a point
where
4.20-stable review patch. If anyone has any objections, please let me know.
--
Commit 8a5b403d71affa098009cc3dff1b2c45113021ad upstream.
In the irqchip and EFI code, we have what basically amounts to a quirk
to work around a peculiarity in the GICv3 architecture, which permits
t
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 3b89ea9c5902acccdbbdec307c85edd1bf52515e ]
The features attribute is of type u64 and stored in the native endianes on
the system. The for_each_set_bit() macro takes a pointer to a 32
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 04c03114be82194d4a4858d41dba8e286ad1787c ]
soukjin bae reported a crash in tcp_v4_err() handling
ICMP_DEST_UNREACH after tcp_write_queue_head(sk)
returned a NULL pointer.
Current lo
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 9060cb719e61b685ec0102574e10337fa5f445ea ]
KASAN has found use-after-free in sockfs_setattr.
The existed commit 6d8c50dcb029 ("socket: close race condition between
sock_close()
and
This is the start of the stable review cycle for the 4.20.12 release.
There are 32 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 Sat Feb 23 12:52:26 UTC 2019.
Anything receiv
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 225d9464268599a5b4d094d02ec17808e44c7553 ]
In the unlikely event that the kmalloc call in vmci_transport_socket_init()
fails, we end-up calling vmci_transport_destruct() with a NULL
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 2c4cc9712364c051b1de2d175d5fbea6be948ebf ]
ICMP handlers are not very often stressed, we should
make them more resilient to bugs that might surface in
the future.
If there is no pac
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit c09551c6ff7fe16a79a42133bcecba5fc2fc3291 ]
According to the algorithm described in the comment block at the
beginning of ip_rt_send_redirect, the host should try to send
'ip_rt_redir
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 197f9ab7f08ce4b9ece662f747c3991b2f0fbb57 ]
Some PHY drivers like the generic one do not provide a read_status
callback on their own but rely on genphy_read_status being called
direct
This is the start of the stable review cycle for the 4.19.25 release.
There are 30 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 Sat Feb 23 12:52:29 UTC 2019.
Anything receiv
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit bdcc5bc25548ef6b08e2e43937148f907c212292 upstream.
Since mISDN_close() uses dev->pending to iterate over active
timers, there is a chance that one timer got removed from th
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 3b89ea9c5902acccdbbdec307c85edd1bf52515e ]
The features attribute is of type u64 and stored in the native endianes on
the system. The for_each_set_bit() macro takes a pointer to a 32
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 63530aba7826a0f8e129874df9c4d264f9db3f9e upstream.
syzbot found that ax25 routes where not properly protected
against concurrent use [1].
In this particular report the bug
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 4974d5f678abb34401558559d47e2ea3d1c15cba ]
After commit c706863bc890 ("net: ip6_gre: always reports o_key to
userspace"), ip6gre and ip6gretap tunnels started reporting TUNNEL_KEY
ou
On Thu, Feb 21, 2019 at 3:56 PM Heikki Krogerus
wrote:
> On Thu, Feb 21, 2019 at 03:46:46PM +0200, Andy Shevchenko wrote:
> > On Tue, Feb 19, 2019 at 2:00 PM Heikki Krogerus
> > wrote:
> > >
> > > In ACPI, and now also in DT, the USB connectors usually have
> > > their own device nodes. In case o
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Qian Cai
commit a8e911d13540487942d53137c156bd7707f66e5d upstream.
If the kernel is configured with KASAN_EXTRA, the stack size is
increasted significantly because this option sets "-fstack-re
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 7c0db24cc431e2196d98a5d5ddaa9088e2fcbfe5 ]
The GPIO interrupt controller on the espressobin board only supports edge
interrupts.
If one enables the use of hardware interrupts in the
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 2c4cc9712364c051b1de2d175d5fbea6be948ebf ]
ICMP handlers are not very often stressed, we should
make them more resilient to bugs that might surface in
the future
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 8681ef1f3d295bd3600315325f3b3396d76d02f6 ]
Fixes: 3b89ea9c5902 ("net: Fix for_each_netdev_feature on Big endian")
Suggested-by: Eric Dumazet
Signed-off-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
[ Upstream commit d5be7f632bad0f489879eed0ff4b99bd7fe0b74c ]
Syzkaller again found a path to a kernel crash through bad gso input.
By building an excessively large packet to c
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Kocialkowski
[ Upstream commit 197f9ab7f08ce4b9ece662f747c3991b2f0fbb57 ]
Some PHY drivers like the generic one do not provide a read_status
callback on their own but rely on genphy_read_
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jose Abreu
[ Upstream commit 8a7493e58ad688eb23b81e45461c5d314f4402f1 ]
We are saving the status of EEE even before we try to enable it. This
leads to a race with XMIT function that tries to a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre Torgue
[ Upstream commit 224babd62d6f19581757a6d8bae3bf9501fc10de ]
GMAC IP is little-endian and used on several kind of CPU (big or little
endian). Main callbacks functions of the s
On Thu, 21 Feb 2019 16:52:52 +0900
Masami Hiramatsu wrote:
> Basically OK to me.
> Could you use probe_kernel_read() in this context, since probe_mem_read() is a
> wrapper function for template code.
>
> With that change,
>
> Acked-by: Masami Hiramatsu
This already hit Linus's tree. I was abl
3.18-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e75913c93f7cd5f338ab373c34c93a655bd309cb ]
Follow those steps:
# ip addr add 2001:123::1/32 dev eth0
# ip addr add 2001:123:456::2/64 dev eth0
# ip addr del 2001:123::1/32 dev eth
> -Original Message-
> From: Peter Rosin [mailto:p...@axentia.se]
> Sent: Thursday, 21 February, 2019 07:12 PM
> To: Pankaj Bansal ; Leo Li
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] drivers: mux: Add Generic regmap bitfield-based
> multiplexer in mmio-mux
>
> Hi!
>
>
On Fri, Feb 15, 2019 at 03:50:04PM -0500, Waiman Long wrote:
> The atomic_long_cmpxchg_acquire() in rwsem_try_read_lock_unqueued() is
> replaced by atomic_long_try_cmpxchg_acquire() to simpify the code and
> generate slightly better assembly code. There is no functional change.
Might be nice to il
From: Bo Yu
Fix sparse warnings:
drivers/staging/erofs/utils.c:134:6: warning: symbol
'erofs_try_to_release_workgroup' was not declared. Should it be static?
Fixes: 51232df5e4b26("staging: erofs: fix race when the managed cache is
enabled")
Cc: Gao Xiang
Cc: Chao Yu
CC: Greg Kroah-Hartman
S
On Thu, Feb 21, 2019 at 11:34:52AM +, Steven Price wrote:
> From: James Morse
>
> Exposing the pud/pgd levels of the page tables to walk_page_range() means
> we may come across the exotic large mappings that come with large areas
> of contiguous memory (such as the kernel's linear map).
>
>
On Thu, Feb 21, 2019 at 02:06:23PM +0100, Gerd Hoffmann wrote:
> On Thu, Feb 21, 2019 at 01:20:11PM +0100, Daniel Vetter wrote:
> > On Thu, Feb 21, 2019 at 12:35:34PM +0100, Gerd Hoffmann wrote:
> > > Problem: qxl switches from native mode back into vga compatibility mode
> > > when it notices som
On Wed, Feb 13, 2019 at 05:00:17PM -0500, Waiman Long wrote:
> Modify __down_read_trylock() to optimize for an unlocked rwsem and make
> it generate slightly better code.
>
> Before this patch, down_read_trylock:
>
>0x <+0>: callq 0x5
>0x0005 <+5>: jm
Hi!
On 18/02/2019 13:59, Will Deacon wrote:
> [+James, who knows how to decode these things]
Decode is a strong term!
This stuff is printed by Cavium's secure-world software. All I'm doing is
spotting the
bits that vary between the out we've seen!
> On Mon, Feb 18, 2019 at 02:56:47PM +0100, D
Hi Waiman,
On Fri, Feb 15, 2019 at 03:50:02PM -0500, Waiman Long wrote:
> Moves all the owner setting code closer to the rwsem-xadd fast paths
> directly within rwsem.h file.
>
> For __down_read() and __down_read_killable(), it is assumed that
> rwsem will be marked as reader-owned when the funct
Libudev relies on having a subsystem link for non-root devices. To
avoid libudev (and potentially other userspace tools) choking on the
matrix device let us introduce a matrix bus and with it the matrix
bus subsytem. Also make the matrix device reside within the matrix
bus.
Doing this we remove th
On Thu, Feb 21, 2019 at 02:52:13PM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The stable backport of upstream commit
>
> 904e14fb7cb96 KVM: VMX: make MSR bitmaps per-VCPU
>
> has a bug in vmx_msr_bitmap_mode(). It enables the x2apic
> MSR-bitmap when the kernel emulates x2apic fo
On Fri, Feb 15, 2019 at 03:50:03PM -0500, Waiman Long wrote:
> We don't need to expose rwsem internal functions which are not supposed
> to be called directly from other kernel code.
>
> Signed-off-by: Waiman Long
> ---
> include/linux/rwsem.h | 7 ---
> kernel/locking/rwsem.h | 7 +++
>
The goal of this patch is to standardize the device-driver interface
for the VFIO_AP ap_matrix_device to satisfy user-land tools working on
hot-plug (UDEV/LIBVIRT).
Christian Borntraeger reported libvirt looping when a matrix device
was available before the libvirt start.
Marc Hartmayer debugged
Den 21.02.2019 12.35, skrev Gerd Hoffmann:
> It'll be useful for other drivers too, so move it to drm_fb_helper.c
> (and rename it of course). Also add docs.
>
> Signed-off-by: Gerd Hoffmann
> ---
> include/drm/drm_fb_helper.h | 2 ++
> drivers/gpu/drm/drm_fb_helper.c | 39 +
On Fri, Feb 15, 2019 at 03:50:01PM -0500, Waiman Long wrote:
> The rwsem_down_read_failed*() functions were relocted from above the
> optimistic spinning section to below that section. This enables the
> reader functions to use optimisitic spinning in future patches. There
> is no code change.
>
>
On 21/02/2019 at 14:45, Claudiu Beznea - M18063 wrote:
> From: Claudiu Beznea
>
> Add documentation for SAM9X60 shutdown controller.
>
> Signed-off-by: Claudiu Beznea
Acked-by: Nicolas Ferre
Thanks Claudiu. Regards,
Nicolas
> ---
> Documentation/devicetree/bindings/arm/atmel-sysregs.tx
On Wed, Feb 20, 2019 at 06:53:08PM -0800, Subhra Mazumdar wrote:
>
> On 2/18/19 9:49 AM, Linus Torvalds wrote:
> > On Mon, Feb 18, 2019 at 9:40 AM Peter Zijlstra wrote:
> > > However; whichever way around you turn this cookie; it is expensive and
> > > nasty.
> > Do you (or anybody else) have nu
On Thu, Feb 21, 2019 at 02:38:36PM +0100, Ludovic BARRE wrote:
> hi Russell & Ulf
>
> On 2/21/19 11:30 AM, Russell King - ARM Linux admin wrote:
> > On Thu, Feb 21, 2019 at 10:27:39AM +, Russell King - ARM Linux admin
> > wrote:
> > > On Thu, Feb 21, 2019 at 11:10:49AM +0100, Ludovic Barre wr
On 2/20/19 9:22 AM, Jagan Teki wrote:
On Tue, Feb 12, 2019 at 5:08 PM Jagan Teki wrote:
Add missing dt-binding documentation for lm75 hwmon sensor.
Signed-off-by: Jagan Teki
---
Changes for v2:
- Add all compatible nodes available in lm75.
.../devicetree/bindings/hwmon/lm75.txt|
On Thu, Feb 21, 2019 at 03:46:46PM +0200, Andy Shevchenko wrote:
> On Tue, Feb 19, 2019 at 2:00 PM Heikki Krogerus
> wrote:
> >
> > In ACPI, and now also in DT, the USB connectors usually have
> > their own device nodes. In case of USB Type-C, those
> > connector (port) nodes are child nodes of th
701 - 800 of 1235 matches
Mail list logo