In linux version 4.4, a 32-bit process may fail to allocate 64M hugepage
memory by function shmat even though there is a 64M memory gap in
the process.
It is the adjusted length that causes the problem, introduced from
commit db4fbfb9523c935 ("mm: vm_unmapped_area() lookup function").
Accounting
FAST_DEC_LOOP was introduced from LZ4 1.9.0[1]
This change would be introduce 10% on decompress operation
according to LZ4 benchmark result on X86 devices.
Meanwhile, LZ4 with FAST_DEC_LOOP could get improvements on ARM64,
however clang compiler has downgrade if FAST_DEC_LOOP enabled.
So
> -Original Message-
> From: Shawn Guo
> Sent: 2019年5月17日 10:38
> To: Chuanhua Han
> Cc: Leo Li ; mark.rutl...@arm.com;
> linux-arm-ker...@lists.infradead.org; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Ying Zhang
> Subject: [EXT] Re: [PATCH] arm64: dts: ls1028a: fix
There are some print format mistakes in debug messages. Fix them.
Signed-off-by: Gaowei Pu
---
fs/jbd2/journal.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index 37e16d969925..565e99b67b30 100644
---
On Fri, May 17, 2019 at 05:59:36AM +0200, Paolo Bonzini wrote:
> Linus,
>
> The following changes since commit 7a223e06b1a411cef6c4cd7a9b9a33c8d225b10e:
>
> KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in
> tracing (2019-04-16 15:38:08 +0200)
>
> are available in the
Cc: += linux-g...@vger.kernel.org
On Thu, May 16, 2019 at 02:42:08PM -0700, Kun Yi wrote:
> The ledtrig-gpio logic assumes the input pin can be directly converted
> to IRQ using gpio_to_irq. This is problematic since there is no
> guarantee on the pinmux function nor the direction of the pin.
On Thu, May 16, 2019 at 02:42:09PM -0700, Kun Yi wrote:
> GPIO number 0 is a valid case to handle. Use -1 as initial value
> and use gpio_is_valid() to determine validity of the GPIO
> number.
I think it's more sensible to convert to gpiod instead.
Best regards
Uwe
> Signed-off-by: Kun Yi
>
On Wed, May 15, 2019 at 12:54:41PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.0.17 release.
> There are 137 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
Add support for Macronix NAND read retry.
Macronix NANDs support specific read operation for data recovery,
which can be enabled/disabled with a SET/GET_FEATURE.
Driver checks byte 167 of Vendor Blocks in ONFI parameter page table
to see if this high-reliability function is supported.
On Wed, May 15, 2019 at 12:55:35PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.177 release.
> There are 51 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
From: Naveen Kumar Parna
Resolved open brace { should be on the previous line checkpatch.pl
error. While addressing this error, also corrected the affected code
for below mentioned checkpatch errors.
ERROR: spaces required around that '<' (ctx:VxV)
ERROR: spaces required around that '=='
On Wed, May 15, 2019 at 12:56:24PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.3 release.
> There are 46 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.
Hi Chenxi,
Some words about the patch format.. not important tho.
One suggestion is that the subject line should be better written
as "[PATCH v2/v3/...] title" since it's more clear to know
which patch is the latest patch among these emails.
On 2019/5/17 13:56, Chenxi Mao wrote:
> FAST_DEC_LOOP
> -Original Message-
> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> Sent: Thursday, May 16, 2019 5:39 PM
> To: Anson Huang ; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; feste...@gmail.com;
On Thu, May 16, 2019 at 03:47:25PM -0700, Kevin Hilman wrote:
> Greg Kroah-Hartman writes:
>
> > On Wed, May 15, 2019 at 07:47:45AM -0700, kernelci.org bot wrote:
> >> stable-rc/linux-4.4.y boot: 98 boots: 1 failed, 92 passed with 3 offline,
> >> 1 untried/unknown, 1 conflict
[test code] The following is my test code.
/*
* first, we allocat large virtual memory;
* second, we allocate hugepage memory by shmat, and release one
* of the hugepage memory block;
* third, we allocate hugepage memory by shmat again, this will fail.
*/
#include
#include
#include
When CONFIG_OPTIMIZE_INLINING is enabled for s390, I see this warning:
arch/s390/mm/fault.c:127:15: warning: 'asce' may be used uninitialized in this
function [-Wmaybe-uninitialized]
switch (asce & _ASCE_TYPE_MASK) {
arch/s390/mm/fault.c:177:16: note: 'asce' was declared here
unsigned long
Commit e60fb8bf68d4 ("s390/cpacf: mark scpacf_query() as __always_inline")
was not enough to make sure to meet the 'i' (immediate) constraint for the
asm operands.
With CONFIG_OPTIMIZE_INLINING enabled, Laura Abbott reported error
with gcc 9.1.1:
In file included from
On May 16, 2019 10:23:31 PM GMT+02:00, "Dmitry V. Levin"
wrote:
>[looks like linux-abi is a typo, Cc'ed linux-api instead]
>
>On Thu, May 16, 2019 at 05:50:22PM +0100, Al Viro wrote:
>> [linux-abi cc'd]
>>
>> On Thu, May 16, 2019 at 06:31:52PM +0200, Christian Brauner wrote:
>> > On Thu, May
On (05/17/19 15:49), Masahiro Yamada wrote:
[..]
> @@ -211,6 +211,8 @@ static void dump_fault_info(struct pt_regs *regs)
> asce = S390_lowcore.kernel_asce;
> pr_cont("kernel ");
> break;
> + default:
> + unreachable();
> }
>
The following changes since commit 71ae5fc87c34ecbdca293c2a5c563d6be2576558:
Merge tag 'linux-kselftest-5.2-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest (2019-05-06
20:29:45 -0700)
are available in the git repository at:
On May 16, 2019 6:50:22 PM GMT+02:00, Al Viro wrote:
>[linux-abi cc'd]
>
>On Thu, May 16, 2019 at 06:31:52PM +0200, Christian Brauner wrote:
>> On Thu, May 16, 2019 at 05:22:59PM +0100, Al Viro wrote:
>> > On Thu, May 16, 2019 at 12:52:04PM +0100, David Howells wrote:
>> > >
>> > > Hi Linus, Al,
Is this patch going to be merged? Or still any blocking issue there?
Thanks,
Bo
-Original Message-
From: shuah [mailto:sh...@kernel.org]
Sent: Friday, April 19, 2019 10:05 PM
To: Tong, Bo ; l...@kernel.org; x...@kernel.org
Cc: linux-kselft...@vger.kernel.org;
Use struct_size() to keep code sample.
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo
Hi Xiang:
Got it and thanks.
Will follow the rules in next PS.
Chenxi
On 5/17/19 2:35 PM, Gao Xiang wrote:
> Hi Chenxi,
>
> Some words about the patch format.. not important tho.
>
> One suggestion is that the subject line should be better written
> as "[PATCH v2/v3/...] title" since it's
On Fri, 17 May 2019 15:49:22 +0900
Masahiro Yamada wrote:
> When CONFIG_OPTIMIZE_INLINING is enabled for s390, I see this warning:
>
> arch/s390/mm/fault.c:127:15: warning: 'asce' may be used uninitialized in
> this function [-Wmaybe-uninitialized]
> switch (asce & _ASCE_TYPE_MASK) {
>
On Fri, 17 May 2019 15:54:24 +0900
Masahiro Yamada wrote:
> Commit e60fb8bf68d4 ("s390/cpacf: mark scpacf_query() as __always_inline")
> was not enough to make sure to meet the 'i' (immediate) constraint for the
> asm operands.
>
> With CONFIG_OPTIMIZE_INLINING enabled, Laura Abbott reported
On Thu, May 16, 2019 at 02:21:46PM +0100, Raphael Gault wrote:
> In order to prevent the userspace processes which are trying to access
> the registers from the pmu registers on a big.LITTLE environment we
> introduce a hook to handle undefined instructions.
>
> The goal here is to prevent the
Christian Brauner wrote:
> If you still prefer to have cloexec flags
> for the 4 new syscalls then yes,
> if they could at least all have the same name
> (FSMOUNT_CLOEXEC?) that would be good.
They don't all have the same value (see OPEN_TREE_CLOEXEC).
Note that I also don't want to blindly
On 17/05/2019 04.45, Peter Xu wrote:
> Hi, Thomas,
>
> On Thu, May 16, 2019 at 03:02:57PM +0200, Thomas Huth wrote:
>> So far the KVM selftests are compiled without any compiler warnings
>> enabled. That's quite bad, since we miss a lot of possible bugs this
>> way. Let's enable at least "-Wall"
Use the new struct_size() helper to keep code simple.
Signed-off-by: xiaolinkui
---
arch/s390/include/asm/idals.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/s390/include/asm/idals.h b/arch/s390/include/asm/idals.h
index 15578fd..6fb7ace 100644
---
On Fri, May 17, 2019 at 12:34:02AM -0600, Kelsey Skunberg wrote:
> On Wed, May 15, 2019 at 12:56:24PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.1.3 release.
> > There are 46 patches in this series, all will be posted as a response
> > to this one.
On Fri, May 17, 2019 at 9:13 AM David Howells wrote:
>
> Christian Brauner wrote:
>
> > If you still prefer to have cloexec flags
> > for the 4 new syscalls then yes,
> > if they could at least all have the same name
> > (FSMOUNT_CLOEXEC?) that would be good.
>
> They don't all have the same
Fixes: ba5625c3e27 ("clk: imx: Add clock driver support for imx8mm")
To Frac pll, the gate shift is 13, however to Int PLL the gate shift
is 11.
Cc:
Signed-off-by: Peng Fan
Reviewed-by: Fabio Estevam
Reviewed-by: Jacky Bai
---
V2:
Update commit with Fixes, Add R-b and cc stable
On May 17, 2019 9:13:26 AM GMT+02:00, David Howells wrote:
>Christian Brauner wrote:
>
>> If you still prefer to have cloexec flags
>> for the 4 new syscalls then yes,
>> if they could at least all have the same name
>> (FSMOUNT_CLOEXEC?) that would be good.
>
>They don't all have the same value
Dear Friend,
With due respect to your person and much sincerity of purpose’ I have a
business proposal which I will like to handle with you. $35 Million USD
is involved. But be rest assured that everything is legal and risk free
as I have concluded all the arrangements and the legal papers
Use the new struct_size() helper to keep code simple.
Signed-off-by: xiaolinkui
---
lib/assoc_array.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/assoc_array.c b/lib/assoc_array.c
index edc3c14..0e69b5b 100644
--- a/lib/assoc_array.c
+++ b/lib/assoc_array.c
@@
Hi,
On Thu, May 16, 2019 at 06:10:39PM +0200, Jernej Skrabec wrote:
> mmc1 node where wifi module is connected doesn't have properly defined
> power supplies so wifi module is never powered up. Fix that by
> specifying additional power supplies.
>
> Additionally, this STB may have either Realtek
On Thu, May 16, 2019 at 11:57:15AM +, Quentin Deslandes wrote:
> Returns error code from 'vnt_int_start_interrupt()' so the device's private
> buffers will be correctly freed and 'struct ieee80211_hw' start function
> will return an error code.
>
> Signed-off-by: Quentin Deslandes
> ---
>
On Fri, May 17, 2019 at 02:10:47AM +0800, Frank Lee wrote:
> > On Sun, May 12, 2019 at 11:41:28PM +0200, Ondřej Jirman wrote:
> > > > > +static int tsens_get_temp(void *data, int *temp)
> > > > > +{
> > > > > + struct tsensor *s = data;
> > > > > + struct tsens_device *tmdev = s->tmdev;
> > > > >
On Thu, May 16, 2019 at 12:42:20PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Both acpi_pci_need_resume() and acpi_dev_needs_resume() check if the
> current ACPI wakeup configuration of the device matches what is
> expected as far as system wakeup from sleep states is
On Fri, 17 May 2019 at 06:21, Stephen Rothwell wrote:
>
> Hi all,
>
> Please do not add any v5.3 material to your linux-next included
> trees/branches until after v5.2-rc1 has been released.
>
> Changes since 20190516:
>
> The kvm tree gained conflicts against Linus' tree.
When I built arm64 I
Hello Rob,
> From: Rob Herring
> Sent: 17 May 2019 03:31
> Subject: Re: [PATCH v2 1/2] dt-bindings: Add vendor prefix for HopeRun
>
> On Wed, May 15, 2019 at 11:35 AM Fabrizio Castro
> wrote:
> >
> > Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree
> > vendor prefixes as
I'm announcing the release of the 4.4.180 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
On (05/17/19 16:27), Sergey Senozhatsky wrote:
> > ... but most likely it's utterly wrong.
> >
>
> JFI, I removed kmemleak annotation
meeehhh
kmemleak: 2046 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
unreferenced object 0x95cbea4e6060 (size 16):
comm "Web Content",
Hi,
On 5/17/19 8:10 AM, Peter Zijlstra wrote:
> On Thu, May 16, 2019 at 02:21:46PM +0100, Raphael Gault wrote:
>> In order to prevent the userspace processes which are trying to access
>> the registers from the pmu registers on a big.LITTLE environment we
>> introduce a hook to handle undefined
diff --git a/Makefile b/Makefile
index 92fe701e5582..ceb8f4bf6245 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 176
+SUBLEVEL = 177
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/mips/ath79/setup.c b/arch/mips/ath79/setup.c
index
I'm announcing the release of the 4.9.177 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.14.120 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web
I'm announcing the release of the 4.19.44 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
diff --git a/Makefile b/Makefile
index a9de3c45a7ef..436d49582d3b 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 119
+SUBLEVEL = 120
EXTRAVERSION =
NAME = Petit Gorille
diff --git
diff --git a/Makefile b/Makefile
index be894b3a97d5..dd11f5a83d2f 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 43
+SUBLEVEL = 44
EXTRAVERSION =
NAME = "People's Front"
diff --git
I'm announcing the release of the 5.0.17 kernel.
All users of the 5.0 kernel series must upgrade.
The updated 5.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.0.y
and can be browsed at the normal kernel.org git web browser:
On Fri, May 17, 2019 at 01:51:56AM +0800, Frank Lee wrote:
> > > +struct sun50i_thermal_chip {
> > > + int sensor_num;
> > > + int offset;
> > > + int scale;
> > > + int ft_deviation;
> > > + int temp_calib_base;
> > > + int temp_data_base;
> > > +
I'm announcing the release of the 5.1.3 kernel.
All users of the 5.1 kernel series must upgrade.
The updated 5.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.1.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 58ec07990e76..f6c763aff4f3 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 1
-SUBLEVEL = 2
+SUBLEVEL = 3
EXTRAVERSION =
NAME = Shy Crocodile
diff --git
On Fri, May 17, 2019 at 02:13:58AM +0800, Frank Lee wrote:
> On Sun, May 12, 2019 at 9:41 PM Maxime Ripard
> wrote:
> >
> > Hi,
> >
> > On Sun, May 12, 2019 at 04:26:14AM -0400, Yangtao Li wrote:
> > > This patch adds binding document for allwinner h6 thermal controller.
> > >
> > >
Hi, Stu:
On Tue, 2019-05-14 at 14:13 +0800, Stu Hsieh wrote:
> This patch add mediatek mipicsi driver for mt2712,
> including probe function to get the value from device tree,
> and register to v4l2 the host device.
>
> Signed-off-by: Stu Hsieh
> ---
>
On Fri, May 17, 2019 at 07:09:31AM +0200, Greg KH wrote:
> On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> > We are building the upstream kernel. There are a few patches, but
> > nothing related to objtool.
> >
> > Unless you mean mainline/stable by upstream, I haven't tried that.
Здравейте!
Нуждаете ли се от мотивационен пакет за персонала, който е удобен и
привлекателен, както за работодателя, така и за служителите?
В такъв случай Ви препоръчваме да обмислите използването на все по-популярните
ваучери за храна - работодателят осигурява ваучери за определена сума, а
On Wed, 2019-05-15 at 21:48 +0800, Nicolas Boichat wrote:
> On Sat, Apr 27, 2019 at 11:36 AM Long Cheng wrote:
> >
> > Modify uart rx and complete for DMA.
>
> I don't know much about the DMA framework, but can you please explain
> why you are making the changes in this CL? I see that you are
Hi,
On Thu, May 16, 2019 at 01:26:31PM -0400, Yangtao Li wrote:
> This patchset supprt H6 thermal controller.
The discussion is still ongoing on the v1, it would have been better
to wait a bit on it to settle before sending a new version.
Anyway, some comment made there still apply.
Maxime
--
Hi Greg,
On 16.05.19 18:49, Greg Kroah-Hartman wrote:
> Jon, thanks for the testing, I'll go drop this patch now from the final
> version.
That's fine, I wanted to suggest this too. I have some time to look at
this next week. So there is no hurry with this patch.
> Daniel, if you can come up
On Thu, May 16, 2019 at 11:51:55PM +, Song Liu wrote:
> Hi,
>
> We found a failure with selftests/bpf/tests_prog in test_stacktrace_map (on
> bpf/master
> branch).
>
> After digging into the code, we found that perf_callchain_kernel() is giving
> empty
> callchain for tracepoint
Thanks, a bunch Greg! :)
On 09:37 Fri 17 May , Greg KH wrote:
I'm announcing the release of the 5.1.3 kernel.
All users of the 5.1 kernel series must upgrade.
The updated 5.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Am 16.05.2019 um 23:33 schrieb Madhumitha Prabakaran:
Fix the warning issued by checkpatch
Prefer kernel type 'u32' over 'uint32_t'.
Along with that include a blank line after a declaration
to maintain Linux kernel coding style.
Signed-off-by: Madhumitha Prabakaran
Acked-by: Stefan Wahren
Returns error code from 'vnt_int_start_interrupt()' so the device's private
buffers will be correctly freed and 'struct ieee80211_hw' start function
will return an error code.
Signed-off-by: Quentin Deslandes
---
v2: returns 'status' value to caller instead of removing it.
v3: add patch version
I guess HOSTCFLAGS_gen_opcode_table.o was blindly copied from
HOSTCFLAGS_gen_facilities.o
The reason of adding $(LINUXINCLUDE) to HOSTCFLAGS_gen_facilities.o
is because gen_facilities.c references some CONFIG options. (Kbuild
does not cater to this for host tools automatically.)
On the other
'targets' should be specified to include .*.cmd files to evaluate
if_changed or friends.
Here, facility-defs.h and dis-defs.h are generated by filechk.
Because filechk does not generate .*.cmd file, the 'targets' addition
is meaningless. The filechk correctly updates the target when its
content
On Thu, May 16, 2019 at 12:09:31PM +0800, YueHaibing wrote:
> If ulite_probe is not called or failed to registed
> uart_register_driver, unload the module will call
> uart_unregister_driver, which will tigger NULL
> pointer dereference like this:
>
> BUG: KASAN: null-ptr-deref in
The top level Makefile adds -Wall globally for all host tools:
KBUILD_HOSTCFLAGS := -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 \
I see two "-Wall" added for compiling these tools.
Of course, it is allowed to pass the same option multiple times, but
we do not need to do so.
As you can see in scripts/Kbuild.include, the filechk creates the
parent directory of the target as needed.
This Makefile does not need to explicitly create the directory.
Signed-off-by: Masahiro Yamada
---
arch/s390/tools/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git
On Fri, May 17, 2019 at 06:48:37AM +0200, Jiri Slaby wrote:
> On 16. 05. 19, 15:59, Michal Hocko wrote:
> >> However, I tend to agree with Michal that (ab)using node[0].memcg_lrus
> >> to check if a list_lru is memcg aware looks confusing. I guess we could
> >> simply add a bool flag to list_lru
On Fri, May 17, 2019 at 09:10:18AM +0200, Peter Zijlstra wrote:
> On Thu, May 16, 2019 at 02:21:46PM +0100, Raphael Gault wrote:
> > In order to prevent the userspace processes which are trying to access
> > the registers from the pmu registers on a big.LITTLE environment we
> > introduce a hook
Hello,
Did this pull request somehow slipped through?
---
Thanks & Best Regards, Laurentiu
On 01.05.2019 23:37, Li Yang wrote:
> Hi arm-soc maintainers,
>
> Please help to merge for-next patches for the upcoming merge window. Thanks
>
> Regards,
> Leo
>
>
> The following changes since
Hi!
> commit 25dc1d6cc3082aab293e5dad47623b550f7ddd2a upstream.
>
> Even if this file was not in an uapi directory, it was exported because
> it was listed in the Kbuild file.
>
While good idea for mainline, I don't think this belongs to stable.
Dropping it should not result in problems.
On Thu, May 16, 2019 at 6:42 PM Kamal Dasu wrote:
>
> Added a flag to indicate a panic_write so that low level drivers can
> use it to take required action where applicable, to ensure oops data
> gets written to assigned mtd device.
>
> Signed-off-by: Kamal Dasu
> ---
> drivers/mtd/mtdcore.c
On Wed 2019-05-15 12:55:03, Greg Kroah-Hartman wrote:
> [ Upstream commit 351f339faa308c1c1461314a18c832239a841ca0 ]
>
> The dynamic-debug statements for command payload output only get emitted
> when the command is not ND_CMD_CALL. Move the output payload dumping
> ahead of the early return path
On Fri, May 17, 2019 at 09:46:00AM +0200, Peter Zijlstra wrote:
> On Thu, May 16, 2019 at 11:51:55PM +, Song Liu wrote:
> > Hi,
> >
> > We found a failure with selftests/bpf/tests_prog in test_stacktrace_map (on
> > bpf/master
> > branch).
> >
> > After digging into the code, we found
From: Colin Ian King
Currently in the case where SMB2_ioctl returns the -EOPNOTSUPP error
there is a memory leak of pneg_inbuf. Fix this by returning via
the out_free_inbuf exit path that will perform the relevant kfree.
Addresses-Coverity: ("Resource leak")
Fixes: 969ae8e8d4ee ("cifs: Accept
On Thu, May 16, 2019 at 6:42 PM Kamal Dasu wrote:
>
> If mtd_oops is in progress, switch to polling during NAND command
> completion instead of relying on DMA/interrupts so that the mtd_oops
> buffer can be completely written in the assigned NAND partition.
With the new flag the semantics
On Fri, May 17, 2019 at 4:11 PM Peter Zijlstra wrote:
>
> On Fri, May 17, 2019 at 09:46:00AM +0200, Peter Zijlstra wrote:
> > On Thu, May 16, 2019 at 11:51:55PM +, Song Liu wrote:
> > > Hi,
> > >
> > > We found a failure with selftests/bpf/tests_prog in test_stacktrace_map
> > > (on
On Wed 2019-05-15 12:55:33, Greg Kroah-Hartman wrote:
> [ Upstream commit a8fd48b50deaa20808bbf0f6685f6f1acba6a64c ]
>
> Preemption disabled at:
> [] dev_set_rx_mode+0x1c/0x38
> Call trace:
> [] dump_backtrace+0x0/0x3d0
> [] show_stack+0x14/0x20
> [] dump_stack+0xac/0xe4
> []
On 17. 05. 19, 10:00, Vladimir Davydov wrote:
> On Fri, May 17, 2019 at 06:48:37AM +0200, Jiri Slaby wrote:
>> On 16. 05. 19, 15:59, Michal Hocko wrote:
However, I tend to agree with Michal that (ab)using node[0].memcg_lrus
to check if a list_lru is memcg aware looks confusing. I guess
On Fri, May 17, 2019 at 8:33 AM Masahiro Yamada
wrote:
>
> In the recent build test of linux-next, Stephen saw a build error
> caused by a broken .tmp_versions/*.mod file:
>
> https://lkml.org/lkml/2019/5/13/991
>
> drivers/net/phy/asix.ko and drivers/net/usb/asix.ko have the same
> basename,
On 17/05/2019 08:44, Daniel Wagner wrote:
> Hi Greg,
>
> On 16.05.19 18:49, Greg Kroah-Hartman wrote:
>> Jon, thanks for the testing, I'll go drop this patch now from the final
>> version.
>
> That's fine, I wanted to suggest this too. I have some time to look at
> this next week. So there is
On 16/05/2019 20:40, Alex Williamson wrote:
On Fri, 10 May 2019 10:22:35 +0200
Pierre Morel wrote:
We implement a capability intercafe for VFIO_IOMMU_GET_INFO and add the
first capability: VFIO_IOMMU_INFO_CAPABILITIES.
When calling the ioctl, the user must specify
On 5/16/2019 7:04 PM, Bjorn Helgaas wrote:
On Tue, May 14, 2019 at 09:00:19AM +0530, Vidya Sagar wrote:
On 5/13/2019 12:55 PM, Christoph Hellwig wrote:
On Mon, May 13, 2019 at 10:36:13AM +0530, Vidya Sagar wrote:
Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs to enable drivers
using
On Thu, May 16, 2019 at 06:27:53PM +0530, stumm...@codeaurora.org wrote:
> Hi Christoph, Al,
>
> Can you please consider this patch for merging?
I've been sitting on this for a while, mostly because I can't convince
myself it is safe. What protects other threads from using ->s_dentry
just when
On Fri, May 17, 2019 at 09:04:20AM +0100, Mark Rutland wrote:
> Remember that this is in an undefined (trap) handler.
>
> If userspace _attempts_ to write to the registers, the CPU will trap to the
> kernel. The comment is perhaps misleading; when we "do nothing", the common
> trap handling code
On Thu, May 16, 2019 at 04:32:18PM +0100, Stefan Hajnoczi wrote:
> On Fri, May 10, 2019 at 02:58:37PM +0200, Stefano Garzarella wrote:
> > When the socket is released, we should free all packets
> > queued in the per-socket list in order to avoid a memory
> > leak.
> >
> > Signed-off-by: Stefano
save_pgd is allocated by kmalloc_array. And it is dereferenced in the
following codes. However, memory allocation functions such as
kmalloc_array may fail. Dereferencing this save_pgd null pointer may
cause the kernel go wrong. Thus we should check this allocation and add
error handling code.
On Fri 17-05-19 14:19:51, Gaowei Pu wrote:
> There are some print format mistakes in debug messages. Fix them.
>
> Signed-off-by: Gaowei Pu
Looks good. You can add:
Reviewed-by: Jan Kara
Honza
> ---
> fs/jbd2/journal.c | 18
On Fri, May 17, 2019 at 4:15 PM Kairui Song wrote:
>
> On Fri, May 17, 2019 at 4:11 PM Peter Zijlstra wrote:
> >
> > On Fri, May 17, 2019 at 09:46:00AM +0200, Peter Zijlstra wrote:
> > > On Thu, May 16, 2019 at 11:51:55PM +, Song Liu wrote:
> > > > Hi,
> > > >
> > > > We found a failure with
Hi Linus,
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
tags/nds32-for-linus-5.2-rc1
for you to fetch
On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra wrote:
>
> On Fri, May 17, 2019 at 07:09:31AM +0200, Greg KH wrote:
> > On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> > > We are building the upstream kernel. There are a few patches, but
> > > nothing related to objtool.
> > >
> > >
Enable Vivante GPU driver for stm32mp157c-ed1 board.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v2:
* move GPU reserved memeory out of bottom DDR to let free this area for
U-Boot
v1:
* Initial
---
---
arch/arm/boot/dts/stm32mp157c-ed1.dts | 16
Append Vivante GPU DT configuration.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v2:
v1:
* Initial
---
---
arch/arm/boot/dts/stm32mp157c.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
Add and enable Vivante GPU on stm32mp157c for ED1, DK1 and DK2 boards.
---
Version history:
v2:
* move GPU reserved memeory out of bottom DDR to let free this area for
U-Boot
v1:
* Initial
---
Pierre-Yves MORDRET (3):
ARM: dts: stm32: Add Vivante GPU support on
Enable Vivante GPU driver for stm32mp157a-dk1 and dk2 boards.
Signed-off-by: Pierre-Yves MORDRET
---
Version history:
v2:
* move GPU reserved memeory out of bottom DDR to let free this area for
U-Boot
v1:
* Initial
---
---
arch/arm/boot/dts/stm32mp157a-dk1.dts |
1 - 100 of 617 matches
Mail list logo