[+Ard in case I'm missing something]
On Mon, Apr 01, 2019 at 10:59:53PM +0800, pierre kuo wrote:
> > > With CONFIG_RANDOMIZE_BASE we can get a further change to memstart_addr
> > > after the place where you moved the initrd_{start,end} setting, which
> > > would result in a different value for __p
Hi Miquel,
On 4/1/19 10:23 AM, Miquel Raynal wrote:
[..]
>>
>> This patch is part of the ongoing efforts to enabling
>> -Wimplicit-fallthrough.
>>
>> Signed-off-by: Gustavo A. R. Silva
>> ---
>
> Applied to git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
> on nand/next.
>
Thank you
On Mon, Apr 01, 2019 at 11:02:37PM +0800, Chen, Rong A wrote:
>
> On 4/1/2019 10:29 PM, Qu Wenruo wrote:
> >
> > On 2019/4/1 下午10:02, Chen, Rong A wrote:
> >> On 4/1/2019 9:28 PM, Nikolay Borisov wrote:
> >>> On 1.04.19 г. 16:24 ч., kernel test robot wrote:
> FYI, we noticed the following
On Mon, Apr 1, 2019 at 4:41 AM Aleksa Sarai wrote:
>
> Eric pitched a procfs2 which would *just* be the PIDs some time ago (in
> an attempt to make it possible one day to mount /proc inside a container
> without adding a bunch of masked paths), though it was just an idea and
> I don't know if he e
On Mon, Apr 01, 2019 at 12:53:48PM +0200, Peter Zijlstra wrote:
> On Fri, Mar 29, 2019 at 03:05:54PM -0700, Paul E. McKenney wrote:
> > On Fri, Mar 29, 2019 at 02:51:26PM -0700, H. Peter Anvin wrote:
> > > On 3/29/19 2:09 PM, Paul E. McKenney wrote:
> > > >>
> > > >> Note: the atomic versions of th
On Mon, Apr 01, 2019 at 08:36:26AM -0700, Linus Torvalds wrote:
> On Mon, Apr 1, 2019 at 4:41 AM Aleksa Sarai wrote:
> >
> > Eric pitched a procfs2 which would *just* be the PIDs some time ago (in
> > an attempt to make it possible one day to mount /proc inside a container
> > without adding a bun
On Mon, Apr 1, 2019 at 8:36 AM Linus Torvalds
wrote:
>
> On Mon, Apr 1, 2019 at 4:41 AM Aleksa Sarai wrote:
> >
> > Eric pitched a procfs2 which would *just* be the PIDs some time ago (in
> > an attempt to make it possible one day to mount /proc inside a container
> > without adding a bunch of ma
Hi Alexander,
On 4/1/19 4:40 PM, Alexander Duyck wrote:
>> @@ -333,8 +328,7 @@ static struct tnode *tnode_alloc(int bits)
>> {
>> size_t size;
>>
>> -/* verify bits is within bounds */
>> -if (bits > TNODE_VMALLOC_MAX)
>> +if ((BITS_PER_LONG <= KEYLENGTH) && unlikely(bits >= BI
On Mon, Apr 01, 2019 at 05:04:30AM +, Anson Huang wrote:
> Use the new helper devm_platform_ioremap_resource() which wraps the
> platform_get_resource() and devm_ioremap_resource() together, to
> simplify the code.
>
> Signed-off-by: Anson Huang
Reviewed-by: Guenter Roeck
> ---
> drivers/
On Mon, Apr 01, 2019 at 08:44:14AM -0700, Paul E. McKenney wrote:
> On Mon, Apr 01, 2019 at 12:53:48PM +0200, Peter Zijlstra wrote:
> > On Fri, Mar 29, 2019 at 03:05:54PM -0700, Paul E. McKenney wrote:
> > > From Documentation/core-api/atomic_ops.rst:
> >
> > We should delete that file.
>
> Only
On 28/03/2019 17:08, Marc Gonzalez wrote:
> Copy init sequence from downstream:
> https://source.codeaurora.org/quic/la/kernel/msm-4.4/tree/arch/arm/boot/dts/qcom/msm8998-v2.dtsi?h=LE.UM.1.3.r3.25#n372
>
> Signed-off-by: Marc Gonzalez
> Reviewed-by: Vivek Gautam
> ---
> Changes from v2: Toggle
On Sat, Mar 30, 2019 at 06:13:16PM +0200, Evalds Iodzevics wrote:
> Hi back in the December of 2016 there was commit
> "1c52d859cb2d417e7216d3e56bb7fea88444cec9"
>
> witch was followed shortly by "c198b121b1a1d7a7171770c634cd49191bac4477"
>
> Unfortunately only the first commit was later include
On Mon, Apr 1, 2019 at 8:55 AM Daniel Colascione wrote:
>
>
> > I wonder if we really want a fill procfs2, or maybe we could just make
> > the pidfd readable (yes, it's a directory file descriptor, but we
> > could allow reading).
>
> What would read(2) read?
We could make it read anything, but i
struct i2c_device_id argument of probe() is not used, so use probe_new()
instead.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
index f6ce63
Use SPDX-License-Identifier instead of a verbose license text.
The original text refers to version 2 so also update MODULE_LICENSE() to
"GPL v2" instead of "GPL".
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff
Only smbus reads and write are done in the driver, plain i2c functionality
is not required.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
index 95aae84f7dc3..c4cc0abe37
Switch to regmap to simplify register accesses and remove the need for
pcf85063_stop_clock/pcf85063_start_clock.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/Kconfig| 1 +
drivers/rtc/rtc-pcf85063.c | 154 +++--
2 files changed, 62 insertions(+), 93
On Mon, Apr 1, 2019 at 4:55 PM Daniel Colascione wrote:
>
> On Mon, Apr 1, 2019 at 8:36 AM Linus Torvalds
> wrote:
> >
> > On Mon, Apr 1, 2019 at 4:41 AM Aleksa Sarai wrote:
> > >
> > > Eric pitched a procfs2 which would *just* be the PIDs some time ago (in
> > > an attempt to make it possible o
Allow reading the oscillator status bit. Also allow clearing it even if
that makes little sense and can't be done in a race free way.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 35 +++
1 file changed, 35 insertions(+)
diff --git a/drivers/r
The pcf85063 has one byte of nvram.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
index 0ac763c10744..04aaa83a5431 100644
--- a/drivers/rtc/rtc-
The PCF850363 has an offset correction with two modes:
With mode 0, the correction is triggered once every two hours and then
correction pulses are applied once per minute until the programmed
correction values have been implemented. This gives a step of 4.34 ppm.
With mode 1, the correction is t
As stated in a comment pcf85063a and pcf85063tp don't have the same number
of registers. Especially, pcf85063tp doesn't have alarm support.
Signed-off-by: Alexandre Belloni
---
.../devicetree/bindings/rtc/nxp,pcf85063.txt | 5 ++-
drivers/rtc/rtc-pcf85063.c| 33
The Micro Crystal RV8263 has the same IC as the pcf85063 but has an on
board crystal. This means that the CAP_SEL bit has to be cleared so the
correct capacitance is selected for the crystal.
Signed-off-by: Alexandre Belloni
---
.../devicetree/bindings/rtc/nxp,pcf85063.txt | 3 +-
drivers/rtc/
Add support for the alarms. The match on the weekday is not used as it it
not necessarily properly set.
The tested RTC shows a behaviour where setting an alarm on the second right
after an alarm that fired is not working, probably because of the circuit
that ensures an alarm only fires once. This
This is a standard BCD RTC that will fail in 2100.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
index afd98e863482..5e993162c5b2 100644
--- a/driver
This allows further improvement of the driver.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
index c4cc0abe37cb..afd98e863482 100644
--- a/dr
On Mon, 1 Apr 2019 11:25:29 -0300
Marcelo Schmitt wrote:
> Hello,
>
> I was looking for some work on staging: iio: ad9832 and made some
> observations while reading the driver.
>
> Apparently it had no devicetree documentation so I tried to elaborate
> one.
> It uses a platform_data variable t
On Mon, Apr 1, 2019 at 9:01 AM Linus Torvalds
wrote:
>
> On Mon, Apr 1, 2019 at 8:55 AM Daniel Colascione wrote:
> >
> >
> > > I wonder if we really want a fill procfs2, or maybe we could just make
> > > the pidfd readable (yes, it's a directory file descriptor, but we
> > > could allow reading).
On 27/03/2019 13:28, Harish Bandi wrote:
> +bool qca_is_wcn399x(enum qca_btsoc_type soc_type)
> +{
> + if ((soc_type == QCA_WCN3990) || (soc_type == QCA_WCN3998))
> + return true;
> +
> + return false;
> +}
Dunno if you saw my earlier comment.
The above is not very idiomatic.
> On Apr 1, 2019, at 9:36 AM, Linus Torvalds
> wrote:
>
>> On Mon, Apr 1, 2019 at 4:41 AM Aleksa Sarai wrote:
>>
>> Eric pitched a procfs2 which would *just* be the PIDs some time ago (in
>> an attempt to make it possible one day to mount /proc inside a container
>> without adding a bunch o
On Mon, 2019-04-01 at 18:08 +0200, Alexandre Belloni wrote:
> Use SPDX-License-Identifier instead of a verbose license text.
>
> The original text refers to version 2 so also update MODULE_LICENSE() to
> "GPL v2" instead of "GPL".
This is not necessary as GPL is the same as GPL v2
commit bf7fbee
On Mon, Apr 1, 2019 at 9:07 AM Jonathan Kowalski wrote:
>
> With the POLLHUP model on a simple pidfd, you'd know when the process
> you were referring to is dead (and one can map POLLPRI to dead and
> POLLHUP to zombie, etc).
Adding ->poll() to the pidfd should be easy. Again, it would be
trivial
On Mon, Apr 1, 2019 at 9:07 AM Jonathan Kowalski wrote:
>
> On Mon, Apr 1, 2019 at 4:55 PM Daniel Colascione wrote:
> >
> > On Mon, Apr 1, 2019 at 8:36 AM Linus Torvalds
> > wrote:
> > >
> > > On Mon, Apr 1, 2019 at 4:41 AM Aleksa Sarai wrote:
> > > >
> > > > Eric pitched a procfs2 which would
Certain bit operations that read/write bits take a base pointer and an
arbitrarily large offset to address the bit relative to that base.
Inline assembly constraints aren't expressive enough to tell the
compiler that the assembly directive is going to touch a specific memory
location of unknown siz
On Mon, Apr 1, 2019 at 5:15 PM Linus Torvalds
wrote:
>
> On Mon, Apr 1, 2019 at 9:07 AM Jonathan Kowalski wrote:
> >
> > With the POLLHUP model on a simple pidfd, you'd know when the process
> > you were referring to is dead (and one can map POLLPRI to dead and
> > POLLHUP to zombie, etc).
>
> Ad
On 01/04/2019 09:16:58-0700, Joe Perches wrote:
> On Mon, 2019-04-01 at 18:08 +0200, Alexandre Belloni wrote:
> > Use SPDX-License-Identifier instead of a verbose license text.
> >
> > The original text refers to version 2 so also update MODULE_LICENSE() to
> > "GPL v2" instead of "GPL".
>
> This
Use SPDX-License-Identifier instead of a verbose license text.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85063.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85063.c b/drivers/rtc/rtc-pcf85063.c
index 14a81fa916ca..ba65aa4a3040 100644
Hi Rob,
On 29/03/2019 14:11, Rob Herring wrote:
> On Thu, Mar 28, 2019 at 1:47 PM James Morse wrote:
>> On 28/03/2019 13:16, Rob Herring wrote:
>>> On Tue, Mar 12, 2019 at 02:51:00PM +0530, Yash Shah wrote:
DT documentation for L2 cache controller added.
diff --git a/Documentation/devi
On Mon, Apr 1, 2019 at 9:22 AM Daniel Colascione wrote:
>
> There's a subtlety: suppose I'm a library and I want to create a
> private subprocess. I use the new clone facility, whatever it is, and
> get a pidfd back. I need to be able to read the child's exit status
> even if the child exits befor
Arnaldo,
These contain more patches to make libtraceevent a stand alone library.
It also brings in some changes that are in the trace-cmd library.
There's a few name changes to the API function names to be more
descriptive as well as closer to what they actually do.
The "pevent" has been renam
From: "Steven Rostedt (VMware)"
As return is not a function we do not need parenthesis around the return
value. Also, a function returning bool does not need to add !!.
Signed-off-by: Steven Rostedt (VMware)
---
tools/lib/traceevent/event-parse-api.c | 4 ++--
1 file changed, 2 insertions(+),
From: Tzvetomir Stoyanov
This patch removes call to exit() from tep_filter_add_filter_str(). A library
function should not force the application to exit. In the current implementation
tep_filter_add_filter_str() calls exit() when a special "test_filters" mode is
set, used only for debugging purpo
From: "Steven Rostedt (VMware)"
The mono clocks can display in seconds instead of whole numbers:
trace-cmd-521 [001] 99176715281005: sched_waking:
comm=kworker/u16:2 pid=32118 prio=120 target_cpu=002
trace-cmd-521 [001] 99176715286349: sched_wake_idle_without_ipi: cpu=
From: Tzvetomir Stoyanov
Input arguments of libtraceevent APIs are renamed from "struct tep_handle
*pevent"
to "struct tep_handle *tep". This makes the API consistent with the chosen
naming convention: tep (trace event parser), instead of the old pevent.
Link:
http://lore.kernel.org/linux-trac
From: Tzvetomir Stoyanov
Rename some traceevent APIs for consistency:
tep_pid_is_registered() to tep_is_pid_registered()
tep_file_bigendian() to tep_is_file_bigendian()
to make the names and return values consistent with other tep_is_... APIs
tep_data_lat_fmt() to tep_data_latency_format()
From: Tzvetomir Stoyanov
The member "pevent" of the struct tep_event_filter is renamed to "tep".
This makes the struct consistent with the chosen naming convention:
tep (trace event parser), instead of the old pevent.
Link:
http://lore.kernel.org/linux-trace-devel/20190401132111.13727-4-tstoya.
From: Tzvetomir Stoyanov
The member "pevent" of the struct tep_event is renamed to "tep". This makes
the struct consistent with the chosen naming convention:
tep (trace event parser), instead of the old pevent.
Link:
http://lore.kernel.org/linux-trace-devel/20190401132111.13727-3-tstoya...@vmwa
On Mon, Apr 01, 2019 at 11:04:48AM +0530, Srinath Mannam wrote:
> Hi Lorenzo,
>
> Please see my reply below,
>
> On Fri, Mar 29, 2019 at 11:06 PM Lorenzo Pieralisi
> wrote:
> >
> > On Fri, Mar 01, 2019 at 10:22:16AM +0530, Srinath Mannam wrote:
> > > In the present driver outbound window configu
From: Tzvetomir Stoyanov
Existing API tep_list_events() is not thread safe, it uses the internal
array sort_events to keep cache of the sorted events and reuses it. This
patch implements a new API, tep_list_events_copy(), which allocates new
sorted array each time it is called. It could be used w
From: "Steven Rostedt (Red Hat)"
When trace-cmd report --debug is set, show the internal ring buffer entries
like time-extends and padding. This requires adding new kbuffer API to
retrieve these items.
Signed-off-by: Steven Rostedt (VMware)
---
tools/lib/traceevent/kbuffer-parse.c | 49 +++
From: Tzvetomir Stoyanov
APIs descriptions should describe the purpose of the function, its
parameters and return value. While working on man pages
implementation, I noticed mismatches in the descriptions of few APIs.
This patch changes the description of these APIs, making them
consistent with
From: "Steven Rostedt (VMware)"
With security updates, %p in the kernel is hashed to protect true kernel
locations. But trace_printk() is not allowed in production systems, and
when a pointer is used, there are many times that the actual address is
needed. "%px" produces the real address. But lib
From: Tzvetomir Stoyanov
This patch removes trivial filter tep APIs:
enum tep_filter_trivial_type
tep_filter_event_has_trivial()
tep_update_trivial()
tep_filter_clear_trivial()
Trivial filters is an optimization, used only in the first
version of KernelShark. The API is deprecated, the next
From: Tzvetomir Stoyanov
"pevent" to "tep" renaming of:
- all "pevent" input arguments of libtraceevent internal functions.
- all local "pevent" variables of libtraceevent.
This makes the implementation consistent with the chosen naming convention,
tep (trace event parser), and will avoid any c
From: Tzvetomir Stoyanov
Fixed few coding style problems in event-parse-api.c
Link:
http://lore.kernel.org/linux-trace-devel/20190325145017.30246-3-tstoya...@vmware.com
Signed-off-by: Tzvetomir Stoyanov
Signed-off-by: Steven Rostedt (VMware)
---
tools/lib/traceevent/event-parse-api.c | 30 +
From: Tzvetomir Stoyanov
As struct tep_handler definition is not exposed as part of libtraceevent API,
its fields
cannot be accessed directly by the library users. This patch implements new
APIs, which
can be used to access the struct tep_handler fields:
tep_get_event()- retrieves an e
On Mon, Apr 1, 2019 at 9:30 AM Linus Torvalds
wrote:
>
> On Mon, Apr 1, 2019 at 9:22 AM Daniel Colascione wrote:
> >
> > There's a subtlety: suppose I'm a library and I want to create a
> > private subprocess. I use the new clone facility, whatever it is, and
> > get a pidfd back. I need to be ab
Hi,
* H. Nikolaus Schaller [190331 10:08]:
> This is an ugly workaround for a regression introduced into v5.1-rc1 by
>
>
You should standardized commit references like this instead:
c1c04cea13dc ("gpio: of: Fix logic inversion")
Then please also include a proper Fixes tag.
You can configure
Commit-ID: faa3604eda325588451c9c1eb4c8a8d04c1cd633
Gitweb: https://git.kernel.org/tip/faa3604eda325588451c9c1eb4c8a8d04c1cd633
Author: Xiaochen Shen
AuthorDate: Sat, 30 Mar 2019 05:50:38 +0800
Committer: Borislav Petkov
CommitDate: Mon, 1 Apr 2019 18:45:27 +0200
x86/resctrl: Fix typos
On Mon, Apr 01, 2019 at 01:37:56PM +, Hugues FRUCHET wrote:
> Hi Andi,
>
> We have already discussed about that here:
> https://lore.kernel.org/patchwork/patch/866406/
>
> Now that strscpy is largely deployed within kernel, could you retest
> with the change I suggested ?
strscpy is not the
Hi Tony,
> Am 01.04.2019 um 18:46 schrieb Tony Lindgren :
>
> Hi,
>
> * H. Nikolaus Schaller [190331 10:08]:
>> This is an ugly workaround for a regression introduced into v5.1-rc1 by
>>
>>
>
> You should standardized commit references like this instead:
>
> c1c04cea13dc ("gpio: of: Fix log
* H. Nikolaus Schaller [190401 16:57]:
> > Am 01.04.2019 um 18:46 schrieb Tony Lindgren :
> > So what's the plan with this fix? Add this for v5.2-rc cycle,
> > then revert it later? I'd probably go directly for the proper
> > fix if possible.
>
> Well, I learned just some minutes ago that a new p
On Mon, Apr 01, 2019 at 06:06:29PM +0200, Greg KH wrote:
> On Sat, Mar 30, 2019 at 06:13:16PM +0200, Evalds Iodzevics wrote:
> > Hi back in the December of 2016 there was commit
> > "1c52d859cb2d417e7216d3e56bb7fea88444cec9"
> >
> > witch was followed shortly by "c198b121b1a1d7a7171770c634cd49191
On Tue, 26 Mar 2019 22:45:39 -0500
Parav Pandit wrote:
> During mdev parent registration in mdev_register_device(),
> if parent device is duplicate, it releases the reference of existing
> parent device.
> This is incorrect. Existing parent device should not be touched.
>
> Fixes: 7b96953bc640 (
From: Daniel Colascione
> Sent: 01 April 2019 17:45
...
> > Now, none of this was ever really used. The people who wanted AIO
> > wanted the brain-damaged POSIX kind of AIO, not something cool and
> > clever. So I suspect the whole exit-signal thing was just used for
> > random small per-project th
Hi all,
> Am 31.03.2019 um 12:07 schrieb H. Nikolaus Schaller :
>
> 2018-07-25 07:55:28:
>
> H. Nikolaus Schaller (4):
> DTS: GTA04: SPI / gpiolib: work around a regression that unhides a
>broken legacy handler, which makes the gta04 display inoperable
> REVERT: DTS: GTA04: SPI / gpiolib:
Hi All,
Please let me know if anyone has any inputs on this.
Regards,
Bharat
>
> The current Multi MSI data programming fails if multiple end points
> requesting MSI and multi MSI are connected with switch, i.e the current
> multi MSI data being given is not considering the number of vectors bei
On Tue, 26 Mar 2019 22:45:40 -0500
Parav Pandit wrote:
> Remove unused kref from the mdev_device structure.
>
> Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
> Reviewed By: Kirti Wankhede
Same here (Reviewed-by:).
> Reviewed-by: Maxim Levitsky
> Signed-off-by: Parav Pandit
> ---
On Tue, 26 Mar 2019 22:45:41 -0500
Parav Pandit wrote:
> There is no need use 'extern' for exported functions.
>
> Reviewed-by: Maxim Levitsky
> Signed-off-by: Parav Pandit
> ---
> include/linux/mdev.h | 21 ++---
> 1 file changed, 10 insertions(+), 11 deletions(-)
Acked-by:
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit ef82bcfa671b9a635bab5fa669005663d8b177c5 ]
In sctp_setsockopt_bindx()/__sctp_setsockopt_connectx(), it allocates
memory with addrs_size which is passed from userspace
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 89e4130939a20304f4059ab72179da81f5347528 ]
When a dual stack tcp listener accepts an ipv4 flow,
it should not attempt to use an ipv6 header or tcp_v6_iif() helper
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Erik Hugne
[ Upstream commit ea239314fe42ace880bdd834256834679346c80e ]
We move the check that prevents connecting service ranges to after
the RDM/DGRAM check, and move address sanity control t
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 9926cb5f8b0f0aea535735185600d74db7608550 ]
When running a syz script, a panic occurred:
[ 156.088228] BUG: KASAN: use-after-free in tipc_disc_timeout+0x9c9/0xb20
[
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Matteo Croce
[ Upstream commit c22da36688d6298f2e546dcc43fdc1ad35036467 ]
Similarly to commit a7603ac1fc8c ("geneve: change NET_UDP_TUNNEL
dependency to select"), GTP has a dependency on NET_UD
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Erik Hugne
[ Upstream commit 33872d79f5d1cbedaaab79669cc38f16097a9450 ]
When cancelling a subscription, we have to clear the cancel bit in the
request before iterating over any established subs
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 4477138fa0ae4e1b699786ef0600863ea6e6c61c ]
Same reasons than the ones explained in commit 4179cb5a4c92
("vxlan: test dev->flags & IFF_UP before calling netif_rx()
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit 5ceaeb99ffb4dc002d20f6ac243c19a85e2c7a76 ]
This patches fixes few issues in mv88e6390x_port_set_cmode().
1. When entering the function the old cmode may be 0,
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Claudiu Manoil
[ Upstream commit 7f07e5f1f778605e98cf2156d4db1ff3a3a1a74a ]
With a recent link mode advertisement code update this helper
providing local pause capability translation used for f
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dean Nelson
[ Upstream commit cd35ef91490ad8049dd180bb060aff7ee192eda9 ]
For the non-XDP case, commit 773225388dae15e72790 ("net: thunderx: Optimize
page recycling for XDP") added code to nicvf
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dean Nelson
[ Upstream commit b3e208069477588c06f4d5d986164b435bb06e6d ]
Commit 773225388dae15e72790 ("net: thunderx: Optimize page recycling for XDP")
added code to nicvf_alloc_page() that ina
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit d29f5aa0bc0c321e1b9e4658a2a7e08e885da52a ]
So far we effectively clear the BMCR register. Some PHY's can deal
with this (e.g. because they reset BMCR to a defa
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 1c87e79a002f6a159396138cd3f3ab554a2a8887 ]
Jianlin reported a crash:
[ 381.484332] BUG: unable to handle kernel NULL pointer dereference at
0068
[
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit 23c78343ec36990709b636a9e02bad814f4384ad ]
Bartek reported that after few cable unplug/replug cycles suddenly
replug isn't detected any longer. His system uses
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit b5f9bd15b88563b55a99ed588416881367a0ce5f ]
ila_xlat_nl_cmd_flush uses rhashtable walkers allocated from the
stack but it never frees them. This corrupts the walker
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 9180bb4f046064dfa4541488102703b402bb04e1 upstream.
In my latest patch I missed one rcu_read_unlock(), in case
device is down.
Fixes: 4477138fa0ae ("tun: properly test for I
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: David Sterba
commit 0cc068e6ee59c1fffbfa977d8bf868b7551d80ac upstream.
As readahead is an optimization, all errors are usually filtered out,
but still properly handled when the real read call i
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Righi
commit 3897b6f0a859288c22fb793fad11ec2327e60fcd upstream.
Parity page is incorrectly unmapped in finish_parity_scrub(), triggering
a reference counter bug on i386, i.e.:
[ 157.66
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Leroy
commit 27da80719ef132cf8c80eb406d5aeb37dddf78cc upstream.
The commit identified below adds MC_BTB_FLUSH macro only when
CONFIG_PPC_FSL_BOOK3E is defined. This results in the fo
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Bogdanov
[ Upstream commit a7faaa0c5dc7d091cc9f72b870d7edcdd6f43f12 ]
TCP/UDP checksum validity was propagated to skb
only if IP checksum is valid.
But for IPv6 there is no validity as t
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Filipe Manana
commit bf504110bc8aa05df48b0e5f0aa84bfb81e0574b upstream.
If we do a shrinking truncate against an inode which is already present
in the respective log tree and then rename it, as
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
[ Upstream commit 0b91bce1ebfc797ff3de60c8f4a1e6219a8a3187 ]
Christoph reported a stall while peeking datagram with an offset when
busy polling is enabled. __skb_try_recv_datagram()
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Finn Thain
[ Upstream commit bb9e5c5bcd76f4474eac3baf643d7a39f7bac7bb ]
The bug that Stan reported is as follows. After a restart, a 16-bit NIC
may be incorrectly identified as a 32-bit NIC and
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jerome Brunet
[ Upstream commit daa5c4d0167a308306525fd5ab9a5e18e21f4f74 ]
If an interrupt is already pending when the interrupt is enabled on the
GXL phy, no IRQ will ever be triggered.
The f
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
[ Upstream commit fae846e2b7124d4b076ef17791c73addf3b26350 ]
The device ID alone does not uniquely identify a device. Test both the
vendor and device ID to make sure we don't mis
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
commit 139a56170de67101791d6e6c8e940c6328393fe9 upstream.
qgroup_rsv_size is calculated as the product of
outstanding_extent * fs_info->nodesize. The product is calculated with
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olga Kornievskaia
commit 0cb98abb5bd13b9a636bde603d952d722688b428 upstream.
Allow the async rpc task for finish and update the open state if needed,
then free the slot. Otherwise, the async rpc
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 136824efaab2c095fc911048f7c7ddeda258c965 upstream.
This patch will enable WYSE AIO for Headset mode.
Signed-off-by: Kailang Yang
Signed-off-by: Takashi Iwai
Signed-off-by
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit 2b1d9c8f87235f593826b9cf46ec10247741fff9 upstream.
info->stream is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre varia
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 10f5b1b85ed10a80d45bc2db450e65bd792efaad upstream.
It will be lose Mic JD state when Chrome OS boot and headset was plugged.
Implement of reset combo jack JD. It will show n
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit c709f14f0616482b67f9fbcb965e1493a03ff30b upstream.
dev is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vuln
901 - 1000 of 1306 matches
Mail list logo
