kmemdup has implemented the function that kmalloc() + memcpy().
We prefer to kmemdup rather than code opened implementation.
This issue was detected with the help of coccinelle.
Signed-off-by: Wen Yang
CC: Kishon Vijay Abraham I
CC: Lorenzo Pieralisi
CC: Bjorn Helgaas
CC: Gustavo Pimentel
CC
On 06. 12. 18 6:27, Masahiro Yamada wrote:
> Hi Michal,
>
> On Thu, Dec 6, 2018 at 12:41 AM Michal Simek wrote:
>>
>> On 03. 12. 18 8:50, Masahiro Yamada wrote:
>>> "make ARCH=microblaze help" mentions simpleImage..unstrip,
>>> but it never works because Makefile assumes "system.unstrip" is
>>> t
>
> On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote:
> > >
> > > Just use qxl_num_crtc directly everywhere instead of using
> > > qdev->monitors_config->max_allowed. Drops pointless indirection
> > > and also is less confusing.
> > >
> >
> > To me is MORE confusing, why compari
On Thu, Dec 06, 2018 at 01:30:19PM +0100, Florian Weimer wrote:
> * Christian Brauner:
>
> > /* zombies */
> > Zombies can be signaled just as any other process. No special error will be
> > reported since a zombie state is an unreliable state (cf. [3]).
>
> I still disagree with this analysis.
On Mon, Dec 03, 2018 at 01:44:35PM -0300, Ezequiel Garcia wrote:
> The current kref and kobject documentation may be
> insufficient to understand these common pitfalls regarding
> object lifetime and object releasing.
>
> Add a bit more documentation and improve the warnings
> seen by the user, po
On Mon, Dec 03, 2018 at 08:21:41PM +0200, Andy Shevchenko wrote:
> The platform_device_register_full() might return an error pointer. If we
> instantiate platform device which is optional we may simplify the routine at
> removal stage by simply calling platform_device_unregister(). For now it
> req
היי, שמי אדמס, אני רוצה ליצור ידידות טובה איתך. נא לדבר אנגלית?
Am Mittwoch, 5. Dezember 2018, 14:03:29 CET schrieb agajjar:
>
> On 12/1/2018 3:38 PM, Oskari Lemmela wrote:
> > Rockpro64 is not able boot if kernel is compiled with
> > CONFIG_DRM_ROCKCHIP=m
> >
> > Enable Rockpro64 board HDMI output to fix issue.
>
> Hi Oskari,
>
> Could you please describe t
Hi Fabio,
> On Thu, Dec 6, 2018 at 6:23 AM Lukasz Majewski wrote:
>
> > At the time of development - I've checked my NXP related patches
> > with W=1 passed to make. No warnings observed then.
>
> In linux-next the warning happens without W=1.
I will check this latter this week...
Best reg
Hi,
On 06. 12. 18 6:08, Masahiro Yamada wrote:
> Hi Michal,
>
> On Thu, Dec 6, 2018 at 1:41 AM Michal Simek wrote:
>>
>> On 03. 12. 18 8:50, Masahiro Yamada wrote:
>>> This patch set fixes various issues in microblaze Makefiles.
>>>
>>> BTW, "simpleImage." works like a phony target to generate t
On Tue, 4 Dec 2018 17:34:03 -0800
Nadav Amit wrote:
> This patch is a preparatory patch for a following patch that makes
> module allocated pages non-executable. The patch sets the page as
> executable after allocation.
>
> In the future, we may get better protection of executables. For example,
Hi Lukasz,
On Thu, Dec 6, 2018 at 11:08 AM Lukasz Majewski wrote:
> I will check this latter this week...
Reading the spi dt-binding it states that the spi slave node is optional.
If I remove it like this, then the warning is gone:
--- a/arch/arm/boot/dts/vf610-bk4.dts
+++ b/arch/arm/boot/dts
* Jürg Billeter:
> On Thu, 2018-12-06 at 13:30 +0100, Florian Weimer wrote:
>> * Christian Brauner:
>>
>> > /* zombies */
>> > Zombies can be signaled just as any other process. No special error will be
>> > reported since a zombie state is an unreliable state (cf. [3]).
>>
>> I still disagree w
The following patches add arm pl353 static memory controller driver and NAND
driver for Xilinx Zynq SoC. The arm pl353 smc supports two interfaces
i.e nand and NOR/SRAM memory interfaces. The current implementation supports
only a single SMC instance and nand specific configuration.
Xilinx Zynq TR
* Christian Brauner:
> On Thu, Dec 06, 2018 at 01:30:19PM +0100, Florian Weimer wrote:
>> * Christian Brauner:
>>
>> > /* zombies */
>> > Zombies can be signaled just as any other process. No special error will be
>> > reported since a zombie state is an unreliable state (cf. [3]).
>>
>> I still
On Thu, 2018-12-06 at 14:12 +0100, Florian Weimer wrote:
> * Jürg Billeter:
>
> > On Thu, 2018-12-06 at 13:30 +0100, Florian Weimer wrote:
> > > * Christian Brauner:
> > >
> > > > /* zombies */
> > > > Zombies can be signaled just as any other process. No special error
> > > > will be
> > > > re
On Wed, Dec 05, 2018 at 12:48:54PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> It has been reported that ftrace_replace_code() which is called by
> ftrace_modify_all_code() can cause a soft lockup warning for an
> allmodconfig kernel. This is because all the debug options e
kmemdup has implemented the function that kmalloc() + memcpy().
We prefer to kmemdup rather than code opened implementation.
This issue was detected with the help of coccinelle.
Signed-off-by: Wen Yang
CC: Hannes Reinecke
CC: "James E.J. Bottomley"
CC: "Martin K. Petersen"
CC: linux-s...@vger
kmemleak_scan() goes through all online nodes and tries
to scan all used pages.
We can do better and use pfn_to_online_page(), so in case we have
CONFIG_MEMORY_HOTPLUG, offlined pages will be skiped automatically.
For boxes where CONFIG_MEMORY_HOTPLUG is not present, pfn_to_online_page()
will fallb
* Jürg Billeter:
> On Thu, 2018-12-06 at 14:12 +0100, Florian Weimer wrote:
>> * Jürg Billeter:
>>
>> > On Thu, 2018-12-06 at 13:30 +0100, Florian Weimer wrote:
>> > > * Christian Brauner:
>> > >
>> > > > /* zombies */
>> > > > Zombies can be signaled just as any other process. No special error
Add driver for arm pl353 static memory controller. This controller is used in
Xilinx Zynq SoC for interfacing the NAND and NOR/SRAM memory devices.
Signed-off-by: Naga Sureshkumar Relli
Reviewed-by: Linus Walleij
---
Changes in v13:
- Fixed sparse warnings
- Fixed check-patch --strict warnings
From: Lan Tianyu
This patch is to move tlb flush in kvm_set_pte_rmapp() to
kvm_mmu_notifier_change_pte() in order to avoid redundant tlb flush.
Signed-off-by: Lan Tianyu
---
arch/x86/kvm/mmu.c | 8 ++--
virt/kvm/kvm_main.c | 5 -
2 files changed, 6 insertions(+), 7 deletions(-)
diff
From: Lan Tianyu
This patch is to flush tlb directly in the kvm_set_pte_rmapp()
and return 0.
Signed-off-by: Lan Tianyu
---
arch/x86/kvm/mmu.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 3b0f60e88f54..64bd848f021e 100644
--- a/arch/x86
From: Lan Tianyu
Originally, flush tlb is done by slot_handle_level_range(). This patch
is to flush tlb directly in the kvm_zap_gfn_range() when range
flush is available.
Signed-off-by: Lan Tianyu
---
Change since v4:
Move operation of setting flush_tlb out of for loop.
---
arch/x86/kv
From: Lan Tianyu
The patch is to make kvm_set_spte_hva() return int and caller can
check return value to determine flush tlb or not.
Signed-off-by: Lan Tianyu
---
arch/arm/include/asm/kvm_host.h | 2 +-
arch/arm64/include/asm/kvm_host.h | 2 +-
arch/mips/include/asm/kvm_host.h| 2 +-
From: Lan Tianyu
This patch is to replace kvm_flush_remote_tlbs() with kvm_flush_
remote_tlbs_with_address() in some functions without logic change.
Signed-off-by: Lan Tianyu
---
arch/x86/kvm/mmu.c | 31 +--
arch/x86/kvm/paging_tmpl.h | 3 ++-
2 files chang
Allwinner A64 CSI controller has similar features as like in
H3, So add support for A64 via H3 fallback.
Also updated CSI_SCLK to use 300MHz via assigned-clocks, since
the default clock 600MHz seems unable to drive the sensor(ov5640)
to capture the image.
Signed-off-by: Jagan Teki
---
Changes fo
Some camera modules have the SoC feeding a master clock to the sensor
instead of having a standalone crystal. This clock signal is generated
from the clock control unit and output from the CSI MCLK function of
pin PE1.
Add a pinmux setting for it for camera sensors to reference.
Signed-off-by: Ja
Allwinner A64 CSI has single channel time-multiplexed BT.656
CMOS sensor interface like H3.
Add a compatible string for it with H3 fallback compatible string,
in this case the H3 driver can be used.
Signed-off-by: Jagan Teki
---
Changes for v2:
- none
Documentation/devicetree/bindings/media/su
Adding brackets allows to multiply the register value,
masked by TS1_RAMP_COEFF_MASK, by an ADJUST value
properly and not to multiply ADJUST by register value and
then mask the whole.
Signed-off-by: David Hernandez Sanchez
Fixes: 1d693155 ("thermal: add stm32 thermal driver")
diff --git a/driver
Calling stm_thermal_read_factory_settings before clocking
internal peripheral causes bad register values and makes
temperature computation wrong.
Calling stm_thermal_read_factory_settings inside
stm_thermal_prepare fixes this problem as internal
peripheral is well clocked at this stage.
Signed-of
On Thu, Dec 6, 2018 at 2:59 PM Greg Kroah-Hartman
wrote:
>
> On Mon, Dec 03, 2018 at 08:21:41PM +0200, Andy Shevchenko wrote:
> > The platform_device_register_full() might return an error pointer. If we
> > instantiate platform device which is optional we may simplify the routine at
> > removal st
Add pl353 static memory controller devicetree binding information.
Signed-off-by: Naga Sureshkumar Relli
Reviewed-by: Linus Walleij
---
Changes in v13:
- Added change log
Changes in v12:
- None
Changes in v11:
- Changed the subject to dt-bindings
- Restuctured dt binings to represent periphe
Hi Linus,
On 2018-12-06 13:43, Linus Walleij wrote:
> Here is a fourth iteration of these fixups after fixing
> the (hopefullt last) bugs found in the v3 version.
>
> Also available in git branch
> gpio-descriptors-regulator-fixup in the GPIO git tree:
> https://git.kernel.org/pub/scm/linux/kernel
On 06/12/2018 14:23, David HERNANDEZ SANCHEZ wrote:
> Adding brackets allows to multiply the register value,
> masked by TS1_RAMP_COEFF_MASK, by an ADJUST value
> properly and not to multiply ADJUST by register value and
> then mask the whole.
>
> Signed-off-by: David Hernandez Sanchez
> Fixes: 1
On 06/12/2018 14:23, David HERNANDEZ SANCHEZ wrote:
> Calling stm_thermal_read_factory_settings before clocking
> internal peripheral causes bad register values and makes
> temperature computation wrong.
>
> Calling stm_thermal_read_factory_settings inside
> stm_thermal_prepare fixes this problem
On Thu, Dec 06, 2018 at 08:54:03AM +0100, Greg Kurz wrote:
> Commit 66ee620f06f9 ("idr: Permit any valid kernel pointer to
> be stored") changed the radix tree lookup so that it stops when
> reaching the bottom of the tree. But radix_tree_descend() may have
> changed the node variable to point to a
From: Stefan Popa
The AD5310R is a single channel DAC with 10-bit precision, which is
part of the same family as AD5311R, except that it uses the spi interface
instead of i2c. The device has a built-in 2.5V reference which is enabled
by default.
Another important difference is that the SPI write
Florian Weimer writes:
> * Jürg Billeter:
>
>> On Thu, 2018-12-06 at 13:30 +0100, Florian Weimer wrote:
>>> * Christian Brauner:
>>>
>>> > /* zombies */
>>> > Zombies can be signaled just as any other process. No special error will
>>> > be
>>> > reported since a zombie state is an unreliable s
This is an attempt to deal with i.MX SoC PWM HW limitation.
When a pad is configured as a PWM output the output level is always 0V
if the PWM block is disabled. This can cause problems when inverted PWM
signal is needed to drive the connected circuit. With inverted output
duty cycle = 0% correspond
On Thu, Dec 06 2018 at 1:21am -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
...
> Caused by commit
>
> 3a657cf59109 ("block: switch to per-cpu in-flight counters")
>
> This build do
Output of the PWM block on i.MX SoCs is always low when the block is
disabled. This can cause issues when inverted PWM polarity is needed.
With inverted polarity a duty cycle = 0% corresponds to high level on
the output. Now, when PWM is disabled its output instantly goes low
which corresponds to d
Normally the PWM output is held LOW when PWM is disabled. This can cause
problems when inverted PWM signal polarity is needed. With this behavior
the connected circuit is fed by 100% duty cycle instead of being shut-off.
Allow users to define a "pwm" and a "gpio" pinctrl states. The pwm pinctrl
st
* Eric W. Biederman:
> Floriam are you seeing a problem with this behavior or the way Christian
> was describing it?
My hope is that you could use taskfd_send_signal one day to send a
signal to a process which you *known* (based on how you've written your
application) should be running and not in
On Thu, Dec 06, 2018 at 02:27:03PM +0100, Marek Szyprowski wrote:
> On 2018-12-06 13:43, Linus Walleij wrote:
> One more thing - if I got everything right, gpiod_put() in
> *regulator_register() error path has to be removed also in
> wm8994-regulator.c and arizona-ldo1.c.
Indeed yes, good spot.
B
This patch solves the register readback issue with the bit shift. When the
dac resolution was lower than the register size (ex. 12 bits out of 16
bits) the readback value was not shifted with the difference in bits and
the value was higher. Also a mask is applied on the read value in order to
get t
On Wed, Dec 05, 2018 at 03:40:48PM -0800, Andy Lutomirski wrote:
> On Wed, Dec 5, 2018 at 3:20 PM Sean Christopherson
> wrote:
> > +notrace long __vdso_sgx_eenter(void *tcs, void *priv,
> > + struct sgx_eenter_fault_info *fault_info)
> > +{
> > + u32 trapnr, erro
On 05/12/2018 21:31, Linus Walleij wrote:
> On Thu, Nov 29, 2018 at 6:03 PM Thierry Reding
> wrote:
>
>> From: Thierry Reding
>>
>> Interrupt controllers in a hierarchy want to use this function to
>> propogate ->irq_set_wake() operations to their parent domains.
>>
>> Signed-off-by: Thierry Re
On Thu, Dec 06, 2018 at 01:41:31PM +, Vokáč Michal wrote:
> Normally the PWM output is held LOW when PWM is disabled. This can cause
> problems when inverted PWM signal polarity is needed. With this behavior
> the connected circuit is fed by 100% duty cycle instead of being shut-off.
>
> Allow
On 12/6/18 11:15 AM, Sebastian Andrzej Siewior wrote:
> There is a small window between setting t->task to NULL and waking the
> task up (which would set TASK_RUNNING). So the timer would fire, run and
> set ->task to NULL while the other side/do_nanosleep() wouldn't enter
> freezable_schedule()
On Wed, Dec 05, 2018 at 10:42:06PM +0100, Christian Brauner wrote:
> On Wed, Dec 05, 2018 at 09:01:45PM +0100, Greg KH wrote:
> > > /* binder-control */
> > > Each new binderfs instance comes with a binder-control device. No other
> > > devices will be present at first. The binder-control device ca
On Wed, Dec 05, 2018 at 05:32:19PM -0500, Sven Van Asbroeck wrote:
> Thanks :)
>
> On Wed, Dec 5, 2018 at 2:17 PM Greg KH wrote:
> >
> > Great, then call it a 'fieldbus' class, not "fieldbus_dev' class.
>
> Small nit:
>
> Hardware connected to a fieldbus comes in two distinct flavours:
> - clie
Currently showing content of /sys/kernel/debug/device_component/*
works partially, in case one of the components is not available this and
all remaining components have status not-registered, but the problem
is only with the first one.
Allowing to finish lookup for other components in case one is m
On Thu, Dec 06, 2018 at 05:55:47AM -0800, Sean Christopherson wrote:
> On Wed, Dec 05, 2018 at 03:40:48PM -0800, Andy Lutomirski wrote:
> > On Wed, Dec 5, 2018 at 3:20 PM Sean Christopherson
> > wrote:
> > > +notrace long __vdso_sgx_eenter(void *tcs, void *priv,
> > > +
On 12/06/2018 03:15 AM, Petr Mladek wrote:
> On Wed 2018-12-05 14:02:20, Joe Lawrence wrote:
>> On Thu, Nov 29, 2018 at 10:44:23AM +0100, Petr Mladek wrote:
>>> The code for freeing livepatch structures is a bit scattered and tricky:
>>>
>>> [ ... snip ... ]
>>>
>>> +static int klp_init_patch(struc
On 2018-12-06, Florian Weimer wrote:
> > Floriam are you seeing a problem with this behavior or the way Christian
> > was describing it?
>
> My hope is that you could use taskfd_send_signal one day to send a
> signal to a process which you *known* (based on how you've written your
> application)
On 12/06/2018 07:37 AM, Petr Mladek wrote:
> On Thu 2018-12-06 11:15:55, Petr Mladek wrote:
>> On Thu 2018-12-06 10:32:00, Miroslav Benes wrote:
>>>
> I don't have many code comments as the changes appear to safely and
> correctly do what the say. (We are at v14 after all :) I mainly
Since __sanitizer_cov_trace_const_cmp4 is marked as notrace, the
function called from __sanitizer_cov_trace_const_cmp4 shouldn't be
traceable either. ftrace_graph_caller() gets called every time func
write_comp_data() gets called if it isn't marked 'notrace'. This is the
backtrace from gdb:
#0
On Thu, 6 Dec 2018 at 14:19, Will Deacon wrote:
>
> On Wed, Dec 05, 2018 at 12:48:54PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > It has been reported that ftrace_replace_code() which is called by
> > ftrace_modify_all_code() can cause a soft lockup warning for an
>
On Wed, 5 Dec 2018 at 19:33, Steven Rostedt wrote:
>
> From: "Steven Rostedt (VMware)"
>
> The function ftrace_replace_code() is the ftrace engine that does the
> work to modify all the nops into the calls to the function callback in
> all the functions being traced.
>
> The generic version which
On 12/06/2018 05:14 AM, Petr Mladek wrote:
> On Thu 2018-12-06 10:23:40, Miroslav Benes wrote:
>> On Thu, 6 Dec 2018, Petr Mladek wrote:
>>
>>> On Wed 2018-12-05 14:32:53, Joe Lawrence wrote:
> diff --git a/kernel/livepatch/core.c b/kernel/livepatch/core.c
> index 972520144713..e01dfa3b58d2
On Thu, 29 Nov 2018 14:29:54 +0800
Ryder Lee wrote:
> From: Guochun Mao
>
> Replace mtd_device_register with mtd_device_parse_register for
> parsing partitions and add ofpart support.
What's the problem with the default partition parser table [1]?
[1]https://elixir.bootlin.com/linux/latest/so
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit ffe81d45322cc3cb140f0db080a4727ea284661e upstream.
If we attempt a direct issue to a SCSI device, and it returns BUSY, then
we queue the request up normally. However, the SCS
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lyude Paul
commit 04ac4b0ed412f65230b456fcd9aa07e13befff89 upstream.
Path property is used for userspace to know what MST connector goes to what
actual DRM DisplayPort connector, the tiling p
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Kresin
commit 7d35baa4e9ec4b717bc0e58a39cdb6a1c50f5465 upstream.
In case the nd_sd group is set to the sd-card function, Pins 45 + 46 are
configured as GPIOs. If they are blocked by th
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry V. Levin
commit c50cbd85cd7027d32ac5945bb60217936b4f7eaf upstream.
When checking for TIF_32BIT_REGS flag, mips_get_syscall_arg() should
use the task specified as its argument instead of
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Neil Armstrong
commit 2bcd3ecab773f73211c45bb1430bb52ac641f271 upstream.
Since Linux 4.17, calls to drm_crtc_vblank_on/off are mandatory, and we get
a warning when ctrc is disabled :
" driver
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lyude Paul
commit c9e0ab86b2e03154bb898cd2f851827783224727 upstream.
The change fixed huge delay in SST daisy chain and S3 soft hang
observed in 4.19 kernel rebase.
Regression point in drm:
d
>
> On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote:
> >
> > > qxl surfaces (used for framebuffers and gem objects) can live in both
> > > VRAM and PRIV ttm domains. Update placement setup to include both. Put
> > > PRIV first in the list so it is preferred, so VRAM will have mo
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Sam Bobroff
commit dc25ab067645eabd037f1a23d49a666f9e0b8c68 upstream.
If the platform has no IO space, ioregs is placed next to the already
allocated regs. In this case, it should not be separ
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lyude Paul
commit 995b278e4723b26f8ebf0e7c119286d16c712747 upstream.
Seeing as we use this registermap in the context of our IRQ handlers, we
need to be using spinlocks for reading/writing reg
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit b1286ed7158e9b62787508066283ab0b8850b518 upstream.
New versions of gcc reasonably warn about the odd pattern of
strncpy(p, q, strlen(q));
which really doesn't m
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Arcangeli
commit e2a50c1f64145a04959df2442305d57307e5395a upstream.
With MAP_SHARED: recheck the i_size after taking the PT lock, to
serialize against truncate with the PT lock. Delete
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit 1cd25cbb2fedbc777f3a8c3cb1ba69b645aeaa64 upstream.
After 2dd453168643 ("kgdboc: Fix restrict error"), kgdboc_option_setup is
now only used when built in, resulting in a war
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lihong Yang
commit eab077aa84331afbda071a213925d4cdbca58941 upstream.
In __i40e_del_filter function, the flag __I40E_MACVLAN_SYNC_PENDING for
the PF state is wrongly set for the VSI. Deleting
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Pavankumar Kondeti
commit 3054426dc68e5d63aa6a6e9b91ac4ec78e3f3805 upstream.
commit 3f5fe9fef5b2 ("sched/debug: Fix task state recording/printout")
tried to fix the problem introduced by a pre
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Cameron Gutman
commit a6754fae1e66e9a40fed406290d7ca3f2b4d227c upstream.
Since we continue to find tons of new variants [0,1,2,3,4,5,6] that
need the PDP quirk, let's just quirk all devices fr
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
commit 24c3456c8d5ee6fc1933ca40f7b4406130682668 upstream.
If for some reason we failed to query the mr status, we need to make sure
to provide sufficient information for an ambig
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
commit 598e1a42e9626213565d3b22ea948ce78556512a upstream.
Commit 32a4f5ecd738 ("net: sched: introduce chain object to uapi")
added new RTM_* definitions without properly updating SE
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Arcangeli
commit dcf7fe9d89763a28e0f43975b422ff141fe79e43 upstream.
Set the page dirty if VM_WRITE is not set because in such case the pte
won't be marked dirty and the page would be re
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Zenghui Yu
commit 0c7a52e4d4b5c4d35b31f3c3ad32af814f1bf491 upstream.
After enabling KVM event tracing, almost all of trace_kvm_exit()'s
printk shows
"kvm_exit: IRQ: ..."
even if the
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lyude Paul
commit 97b2a3180a559a33852ac0cd77904166069484fd upstream.
Currently on driver bringup with KASAN enabled, meson triggers an OOB
memory access as shown below:
[ 117.904528]
==
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Wilck
commit dfb7513374c1f8e7cd595106fbdba3fd07ebaf30 upstream.
Since f44ac12f1dcc, BG enablement is tracked with the LPFC_SLI3_BG_ENABLED
bit, which is set in lpfc_get_cfgparam before
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Parri
commit 09d3f015d1e1b4fee7e9bbdcf54201d239393391 upstream.
Commit:
142b18ddc8143 ("uprobes: Fix handle_swbp() vs unregister() + register() race")
added the UPROBE_COPY_INSN fla
This is the start of the stable review cycle for the 4.19.8 release.
There are 41 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 Dec 8 14:29:30 UTC 2018.
Anything receive
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Frieder Schrempf
commit 40b412897ccb4b98b2cfb2a0aaabed58dd9e2086 upstream.
Fix the size of the buffer allocated to store the in-memory BBT.
This bug was previously hidden by a different bug, t
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Arcangeli
commit 5b51072e97d587186c2f5390c8c9c1fb7e179505 upstream.
Userfaultfd did not create private memory when UFFDIO_COPY was invoked
on a MAP_PRIVATE shmem mapping. Instead it wr
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Brian Norris
commit ac5722c1643a2fb75224c79b578214956d34f989 upstream.
The cros_ec_keyb_bs array lists buttons and switches together, expecting
that its users will match the appropriate type a
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Patrick Gaskin
commit 3ed64da3b790be7c63601e8ca6341b7dff74a660 upstream.
Add ELAN0620 to the ACPI table to support the elan touchpad in
the Lenovo IdeaPad 130-15IKB.
Signed-off-by: Patrick Ga
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Hilman
commit b7cc40c32a8bfa6f2581a71747f6a7d491fe43ba upstream.
Change the default defconfig (used with 'make defconfig') to the ARCv2
nsim_hs_defconfig, and also switch the default Kco
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Wong
commit bf87ade0dd7f8cf19dac4d3161d5e86abe0c062b upstream.
Added the ability to detect the ELAN0621 touchpad found in some Lenovo
laptops.
Signed-off-by: Adam Wong
Cc: sta...@vger.k
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 58930cced012adb01bc78b3687049b17ef44d0a3 upstream.
As gcc-8 points out, the bit mask check makes no sense here:
drivers/staging/rts5208/sd.c: In function 'ext_sd_send_cmd
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
commit 24c3456c8d5ee6fc1933ca40f7b4406130682668 upstream.
If for some reason we failed to query the mr status, we need to make sure
to provide sufficient information for an ambig
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 8c5a50e8e7ad812a62f7ccf28d9a5e74fddf3000 upstream.
The bfa driver has a number of real issues with string termination
that gcc-8 now points out:
drivers/scsi/bfa/bfad_bsg
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Lyude Paul
commit 9df39bedbf292680655c6a947c77d6562c693d4a upstream.
Noticed the other day the trackpoint felt different on my P50, then
realized it was because rmi4 wasn't loading for this ma
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Brodkin
commit 6b04114f6fae5e84d33404c2970b1949c032546e upstream.
By default NFSv3 doesn't support ACL (Access Control Lists)
which might be quite convenient to have so that
mounted NFS
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit b1286ed7158e9b62787508066283ab0b8850b518 upstream.
New versions of gcc reasonably warn about the odd pattern of
strncpy(p, q, strlen(q));
which really doesn't m
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry V. Levin
commit c50cbd85cd7027d32ac5945bb60217936b4f7eaf upstream.
When checking for TIF_32BIT_REGS flag, mips_get_syscall_arg() should
use the task specified as its argument instead of
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sultan Alsawaf
commit 000ade8016400d93b4d7c89970d96b8c14773d45 upstream.
By passing a limit of 2 bytes to strncat, strncat is limited to writing
fewer bytes than what it's supposed to append t
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit c288248f5b26cd5563112fcdc077bf44964a942d upstream.
hdmi_lpe_audio_probe() copies the pcm name string via strncpy(), but
as a gcc8 warning suggests, it misses a NUL terminat
201 - 300 of 1420 matches
Mail list logo
