On Wed, May 08, 2019 at 10:36:48PM +0800, Wei Li wrote:
> After thread is added to machine->threads[i].dead in
> __machine__remove_thread, the machine->threads[i].dead is freed
> when calling free(session) in perf_session__delete(). So it get a
> Segmentation fault when accessing it in thread__put(
On 5/21/19 8:15 PM, Vandana BN wrote:
> SyzKaller hit the null pointer deref while reading from uninitialized
> udev->product in zr364xx_vidioc_querycap().
> ==
> BUG: KASAN: null-ptr-deref in read_word_at_a_time+0xe/0x20
> include/lin
> -Original Message-
> From: Chuanhua Han
> Sent: Wednesday, May 22, 2019 1:26 AM
> To: Leo Li ; Shawn Guo
> Cc: mark.rutl...@arm.com; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; Ying Zhang
>
> Subject: RE: [EXT] Re: [PATCH] arm64: d
unsubscribe morea...@gmail.com
Perf report fails to display s390 specific event numbered bd000
on an x86 platform. For example on s390 this works without error:
[root@m35lp76 perf]# uname -m
s390x
[root@m35lp76 perf]# ./perf record -e rbd000 -- find / >/dev/null
[ perf record: Woken up 3 times to write data ]
[ perf record: Cap
Thanks, a bunch Greg!
On 08:34 Wed 22 May , Greg KH wrote:
I'm announcing the release of the 5.1.4 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
Hi Vasily,
> This reverts commit d5bb334a8e171b262e48f378bd2096c0ea458265.
>
> This commit breaks some HID devices, see [1] for details
>
> https://bugzilla.kernel.org/show_bug.cgi?id=203643
>
> Signed-off-by: Vasily Khoruzhick
> Cc: sta...@vger.kernel.org
let me have a look at this. Maybe th
Hi!
On Wednesday 22 May 2019 02:53:18 Xiaoxiao Liu wrote:
> Hi Pali,
>
> Why it does not report input data?
> --> The alps devices which detected to use the ALPS_PROTO_V8 contains ALPS
> touchpad and ALPS track point.
> But the ALPS_PROTO_V8 do not support the track point device process.
On Wed, 2019-05-22 at 13:32 +0900, Masahiro Yamada wrote:
> On Tue, May 21, 2019 at 10:34 PM Greg KH wrote:
[]
> > - Add GPL-2.0-only or GPL-2.0-or-later tags to files where our scan
> > tools can determine the license text in the file itself. Where this
> > happens, the license text is
diff --git a/Documentation/x86/mds.rst b/Documentation/x86/mds.rst
index 534e9baa4e1d..5d4330be200f 100644
--- a/Documentation/x86/mds.rst
+++ b/Documentation/x86/mds.rst
@@ -142,45 +142,13 @@ Mitigation points
mds_user_clear.
The mitigation is invoked in prepare_exit_to_usermode() which
I'm announcing the release of the 5.0.18 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:
I'm announcing the release of the 5.1.4 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:
I'm announcing the release of the 4.14.121 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 browser
I'm announcing the release of the 4.19.45 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 browser:
diff --git a/Documentation/x86/mds.rst b/Documentation/x86/mds.rst
index 534e9baa4e1d..5d4330be200f 100644
--- a/Documentation/x86/mds.rst
+++ b/Documentation/x86/mds.rst
@@ -142,45 +142,13 @@ Mitigation points
mds_user_clear.
The mitigation is invoked in prepare_exit_to_usermode() which
Hi Vinod,
Thank for you reply.
the registers (CHCFG0 - CHCFG15) on big endian socs as fallows:
CHCFG0 0x0
CHCFG1 0x1
CHCFG2 0x2
CHCFG3 0x3
..
CHCFG12 0xC
CHCFG13 0xD
CHCFG14 0xE
CHCFG15 0xF
On little endian socs as fallows:
C
I'm announcing the release of the 4.9.178 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:
diff --git a/Documentation/x86/mds.rst b/Documentation/x86/mds.rst
index 534e9baa4e1d..5d4330be200f 100644
--- a/Documentation/x86/mds.rst
+++ b/Documentation/x86/mds.rst
@@ -142,45 +142,13 @@ Mitigation points
mds_user_clear.
The mitigation is invoked in prepare_exit_to_usermode() which
On Di, 2019-05-21 at 10:00 -0400, Alan Stern wrote:
>
> Changing configurations amounts to much the same as disconnecting,
> because both operations destroy all the existing interfaces.
>
> Disconnect can arise in two different ways.
>
> Physical hot-unplug: All I/O operations will fail.
On Wed, May 22, 2019 at 10:00:37AM +0800, Li Zhijian wrote:
> Looks good
>
> but the following place should be considered as well i think
> 342 vcollected = kstrdup(collected,
> GFP_KERNEL);
> 343 state = CopyFile;
>
>
> Thanks
> Z
> -Original Message-
> From: Leo Li
> Sent: 2019年5月22日 4:15
> To: Chuanhua Han ; Shawn Guo
>
> Cc: mark.rutl...@arm.com; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; Ying Zhang
>
> Subject: RE: [EXT] Re: [PATCH] arm64: dts: ls1028a: f
Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce
driver dependency into Kconfig as CONFIG_IMX_SCU must be
selected to support i.MX SCU SoC driver, also need to use
platform driver model to make sure IMX_SCU driver is probed
before i.MX SCU SoC driver.
With this patch, SoC info can b
This patch selects CONFIG_IMX_SCU_SOC by default to support
i.MX system controller unit SoC info driver.
Signed-off-by: Anson Huang
---
No changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
ind
On 22/05/2019 07.42, Andrew Morton wrote:
> On Tue, 14 May 2019 20:31:58 -0700 Nathan Chancellor
> wrote:
>
>> On Tue, May 14, 2019 at 04:16:19PM -0700, 'Nick Desaulniers' via Clang Built
>> Linux wrote:
>>> do we know if
>>> https://lkml.org/lkml/2019/4/29/743
>>> https://lkml.org/lkml/2019/4/
Don't prune master node in the hsr_prune_nodes function.
Neither time_in[HSR_PT_SLAVE_A], nor time_in[HSR_PT_SLAVE_B],
will ever be updated by hsr_register_frame_in for the master port.
Thus the master node will be repeatedly pruned leading to
repeated packet loss.
This bug never appeared because t
Hi Kees,
> Am 21.05.2019 um 22:36 schrieb Kees Cook :
>
> On Tue, May 21, 2019 at 01:23:36PM +0200, H. Nikolaus Schaller wrote:
> HOSTLLD -shared scripts/gcc-plugins/arm_ssp_per_task_plugin.so - due to
> target missing
> Undefined symbols for architecture x86_64:
> "gen_reg_rtx(m
Hi Måns
On 2019-05-21 15:30, Måns Rullgård wrote:
> Marek Szyprowski writes:
>> Dear All,
>>
>> Commit 69bec7259853 ("USB: core: let USB device know device node") added
>> support for attaching devicetree node for USB devices. Those nodes are
>> children of their USB host controller. However Exyn
On 22.05.19 02:06, Chris Packham wrote:
Because PPB unlocking unlocks the whole chip cfi_ppb_unlock() needs to
remember the locked status for each sector so it can re-lock the
unaddressed sectors. Dynamically calculate the maximum number of sectors
rather than using a hardcoded value that is too
On Tue, 21 May 2019, Benson Leung wrote:
> Hi Lee,
>
> On Sat, May 18, 2019 at 07:39:49AM +0100, Lee Jones wrote:
> > On Fri, 17 May 2019, Gwendal Grignou wrote:
> >
> > > Lee,
> > >
> > > I verified and merged the changes on the kernels (3.18, 4.4 and 4.14)
> > > used on chromebook using a squ
On Tue, 21 May 2019, Fabien Lahoudere wrote:
> Le jeudi 09 mai 2019 à 14:13 -0700, Gwendal Grignou a écrit :
> > The interface between CrosEC embedded controller and the host,
> > described by cros_ec_commands.h, as diverged from what the embedded
> > controller really support.
> >
> > The source
On Wed, May 22, 2019 at 11:01:15AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the pidfd tree got a conflict in:
>
> tools/testing/selftests/pidfd/Makefile
>
> between commit:
>
> ec8f24b7faaf ("treewide: Add SPDX license identifier - Makefile/Kconfig")
>
> fro
On Mon, 20 May 2019, Amelie Delaunay wrote:
> When CONFIG_GPIO_OF is not defined, struct gpio_chip 'of_node' member does
> not exist:
> drivers/pinctrl/pinctrl-stmfx.c: In function 'stmfx_pinctrl_probe':
> drivers/pinctrl/pinctrl-stmfx.c:652:17: error: 'struct gpio_chip' has no
> member named 'of
1) Clear up some recent tipc regressions because of registration ordering.
Fix from Junwei Hu.
2) tipc's TLV_SET() can read past the end of the supplied buffer during the
copy. From Chris Packham.
3) ptp example program doesn't match the kernel, from Richard Cochran.
4) Outgoing message
On Tue, 21 May 2019, Jacek Anaszewski wrote:
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git
On Wed, May 22, 2019 at 10:33:06AM +0530, Naresh Kamboju wrote:
> On Mon, 20 May 2019 at 18:03, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.1.4 release.
> > There are 128 patches in this series, all will be posted as a response
> > to this one. If an
On Tue, May 21, 2019 at 03:11:15PM -0600, shuah wrote:
> On 5/20/19 6:13 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.1.4 release.
> > There are 128 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with t
On Tue, 2019-05-21 at 21:47 -0700, Paul Walmsley wrote:
> On Tue, 21 May 2019, Andrew Morton wrote:
>
> > On Sun, 19 May 2019 11:24:22 -0700 (PDT) Paul Walmsley
> > wrote:
> >
> > > On Sat, 18 May 2019, Joe Perches wrote:
> > >
> > > > On Sat, 2019-05-18 at 14:00 -0700, Paul Walmsley wrote:
>
It seems that the current code lacks holding the namespace lock in
thread__namespaces(). Otherwise it can see inconsistent results.
Signed-off-by: Namhyung Kim
---
tools/perf/util/thread.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/threa
Hello,
These are some missing pieces that I found during the code-reading.
Thanks,
Namhyung
Namhyung Kim (3):
perf tools: Protect reading thread's namespace
perf tools: Add missing swap ops for namespace events
perf top: Enable --namespaces option
tools/perf/Documentation/perf-top.txt
In case it's recorded from other arch.
Signed-off-by: Namhyung Kim
---
tools/perf/util/session.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
index 2310a1752983..54cf163347f7 100644
--- a/tools/perf/util/session.
Since perf record already have the option, let's have it for perf top
as well.
Signed-off-by: Namhyung Kim
---
tools/perf/Documentation/perf-top.txt | 5 +
tools/perf/builtin-top.c | 5 +
2 files changed, 10 insertions(+)
diff --git a/tools/perf/Documentation/perf-top.txt
On Fri, 2019-05-17 at 15:36 +0800, Long Cheng wrote:
> 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
>
On Tue, May 21, 2019 at 05:48:11PM -0400, Steven Rostedt wrote:
> On Tue, 21 May 2019 14:43:26 -0700
> Alexei Starovoitov wrote:
>
> > Steve,
> > sounds like you've missed all prior threads.
>
> I probably have missed them ;-)
>
> > The feedback was given to Kris it was very clear:
> > implemen
This reverts commit d5bb334a8e171b262e48f378bd2096c0ea458265.
This commit breaks some HID devices, see [1] for details
https://bugzilla.kernel.org/show_bug.cgi?id=203643
Signed-off-by: Vasily Khoruzhick
Cc: sta...@vger.kernel.org
---
include/net/bluetooth/hci_core.h | 3 ---
net/bluetooth/hci_
> From: Stephen Hemminger
> Sent: Tuesday, May 21, 2019 9:40 PM
>
> Thanks for working this out with the host team.
> Now if we could just get some persistent slot information it would make udev
> in systemd happy.
The slot info comes from the serial number "hpdev->desc.ser", which may not
gua
On Tue, May 21, 2019 at 4:39 AM Christian Brauner wrote:
>
> On Tue, May 21, 2019 at 01:30:29PM +0200, Christian Brauner wrote:
> > On Tue, May 21, 2019 at 08:05:52PM +0900, Minchan Kim wrote:
> > > On Tue, May 21, 2019 at 10:42:00AM +0200, Christian Brauner wrote:
> > > > On Mon, May 20, 2019 at
On Chuwi Hi10 Plus, the Silead device id is MSSL0017.
Signed-off-by: Danct12
---
drivers/input/touchscreen/silead.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/touchscreen/silead.c
b/drivers/input/touchscreen/silead.c
index 09241d4cdebc..06f0eb04a8fd 100644
--- a/drivers/i
On Tue, May 21, 2019 at 11:27:21PM +0530, Naresh Kamboju wrote:
> Steps to reproduce is,
> running LTP three test cases in sequence on x86 device.
> # cd ltp/runtest
> # cat syscalls ( only three test case)
> open12 open12
> madvise06 madvise06
> poll02 poll02
> #
>
> as Dan referring to,
>
> LTP
On Mon, 20 May 2019 at 17:51, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.45 release.
> There are 105 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.
>
> Re
On Mon, 20 May 2019 at 18:03, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.1.4 release.
> There are 128 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.
>
> Resp
On Mon, 20 May 2019 at 17:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.0.18 release.
> There are 123 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.
>
> Res
On 11/05/19 8:12 AM, Ravi Bangoria wrote:
Consider a scenario where user creates two events:
1st event:
attr.sample_type |= PERF_SAMPLE_BRANCH_STACK;
attr.branch_sample_type = PERF_SAMPLE_BRANCH_ANY;
fd = perf_event_open(attr, 0, 1, -1, 0);
This sets cpuhw->bhrb_filter to
Hi Andrew,
On Tue, May 21, 2019 at 7:24 PM Andrew Lunn wrote:
>
> > static void ocores_process_polling(struct ocores_i2c *i2c)
> > {
> > + const struct of_device_id *match;
> > +
> > + match = of_match_node(ocores_i2c_match, i2c->adap.dev.of_node);
> > +
> > while (1) {
> >
Hi Andrew,
On Tue, May 21, 2019 at 7:26 PM Andrew Lunn wrote:
>
> > Required properties:
> > -- compatible : "opencores,i2c-ocores" or "aeroflexgaisler,i2cmst"
> > +- compatible : "opencores,i2c-ocores",
> > + "aeroflexgaisler,i2cmst",
> > +"sifive,f
On 05/22/19 at 11:20am, Dave Young wrote:
> How about the userspace kexec-tools? It needs a similar detection, but
> I'm not sure how to detect paging mode, maybe some sysfs entry or
> vmcoreinfo in /proc/vmcore
In usersapce, I plan to parse /proc/kcore to get the starting address
of page_offset
On Tue, 21 May 2019, Andrew Morton wrote:
> On Sun, 19 May 2019 11:24:22 -0700 (PDT) Paul Walmsley
> wrote:
>
> > On Sat, 18 May 2019, Joe Perches wrote:
> >
> > > On Sat, 2019-05-18 at 14:00 -0700, Paul Walmsley wrote:
> > > > The RISC-V architecture has a register named the "Supervisor Excep
Prior to [1], all non-GPL modules were able to make use of SIMD on x86
by making use of the __kernel_fpu_* API. Given that __kernel_fpu_* were
both EXPORT_SYMBOL'd and kernel_fpu_* are such trivial wrappers around
the now-static __kernel_fpu_*, it seems to me that there is no reason to
have differe
On Tue, May 21, 2019 at 10:34 PM Greg KH wrote:
>
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
>
Le 20/05/2019 à 16:10, Bartlomiej Zolnierkiewicz a écrit :
'default n' is the default value for any bool or tristate Kconfig
setting so there is no need to write it explicitly.
Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
is not set' for visible symbols") the Kconfig beh
On 22. 05. 19, 3:40, Gen Zhang wrote:
> In alloc_tty_struct(), tty->dev is assigned by tty_get_device(). And it
> calls class_find_device(). And class_find_device() may return NULL.
> And tty->dev is dereferenced in the following codes. When
> tty_get_device() returns NULL, dereferencing this tty-
To expand on the ChromeOS use case we're in a very similar situation
to Android. For example, the Chrome browser uses a separate process
for each individual tab (with some exceptions) and over time many tabs
remain open in a back-grounded or idle state. Given that we have a lot
of information about
On Tue, May 21, 2019 at 04:26:19PM -0700, Alexei Starovoitov wrote:
> On Tue, May 21, 2019 at 05:36:49PM -0400, Kris Van Hees wrote:
> > On Tue, May 21, 2019 at 01:55:34PM -0700, Alexei Starovoitov wrote:
> > > On Tue, May 21, 2019 at 02:41:37PM -0400, Kris Van Hees wrote:
> > > > On Tue, May 21, 2
On Thu 16 May 04:54 PDT 2019, Amit Kucheria wrote:
> (cc'ing Andy's correct email address)
>
> On Wed, May 15, 2019 at 2:46 AM Stephen Boyd wrote:
> >
> > Quoting Amit Kucheria (2019-05-13 04:54:12)
> > > On Mon, May 13, 2019 at 4:31 PM Amit Kucheria
> > > wrote:
> > > >
> > > > On Tue, Jan 15
On Tue 21 May 02:35 PDT 2019, Amit Kucheria wrote:
> From: "Raju P.L.S.S.S.N"
>
> Add device bindings for cpuidle states for cpu devices.
>
> Cc:
> Signed-off-by: Raju P.L.S.S.S.N
> Reviewed-by: Evan Green
> [amit: rename the idle-states to more generic names and fixups]
> Signed-off-by: Ami
On Tue 21 May 02:35 PDT 2019, Amit Kucheria wrote:
> msm8996 features 4 cpus - 2 in each cluster. However, all cpus implement
> the same microarchitecture and the two clusters only differ in the
> maximum frequency attainable by the CPUs.
>
> Add capacity-dmips-mhz property to allow the topology
On Tue 21 May 02:35 PDT 2019, Amit Kucheria wrote:
> Add device bindings for cpuidle states for cpu devices.
>
> msm8996 features 4 cpus - 2 in each cluster. However, all cpus implement
> the same microarchitecture and the two clusters only differ in the
> maximum frequency attainable by the CPUs
at 6:23 AM, Bjorn Helgaas wrote:
[+cc Mathias, linux-usb]
On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
There's an xHC device that doesn't wake when a USB device gets plugged
to its USB port. The driver's own runtime suspend callback was called,
PME signaling was enabled, but
Hi all,
Changes since 20190521:
The imx-mxs tree lost its build failure.
The scsi tree gained conflicts against Linus' tree.
The pidfd tree gained a conflict against Linus' tree.
The akpm-current tree gained a conflict against the pidfd tree.
Non-merge commits (relative to Linus
On Tue, 2019-05-21 at 13:33 +0300, Heikki Krogerus wrote:
> On Tue, May 21, 2019 at 03:35:04PM +0800, Chunfeng Yun wrote:
> > Hi,
> > On Mon, 2019-05-20 at 09:45 +, Biju Das wrote:
> > >
> > > Hi Heikki,
> > >
> > > Thanks for the feedback.
> > >
> > > > Subject: Re: [PATCH v5 4/6] usb: role
On Tue 21 May 02:35 PDT 2019, Amit Kucheria wrote:
> From: Niklas Cassel
>
> Add device bindings for cpuidle states for cpu devices.
>
> Signed-off-by: Niklas Cassel
> Reviewed-by: Vinod Koul
> [rename the idle-states to more generic names and fixups]
> Signed-off-by: Amit Kucheria
> Acked-b
On Tue 21 May 02:35 PDT 2019, Amit Kucheria wrote:
> Instead of using Qualcomm-specific terminology, use generic node names
> for the idle states that are easier to understand. Move the description
> into the "idle-state-name" property.
>
> Signed-off-by: Amit Kucheria
> Reviewed-by: Niklas Cass
On Tue 21 May 02:35 PDT 2019, Amit Kucheria wrote:
> The idle-states binding documentation[1] mentions that the
> 'entry-method' property is required on 64-bit platforms and must be set
> to "psci".
>
> [1] Documentation/devicetree/bindings/arm/idle-states.txt (see
> idle-states node)
>
> Signed
It is set before entering idle and cleared when quitting idle, though
it seems to be a complete duplicate of tick_sched.idle_active. We
should probably be able to use any one of them to replace the other.
CC: Frederic Weisbecker
CC: Thomas Gleixner
CC: Ingo Molnar
CC: linux-kernel@vger.kernel.
CMD of Source/Destination descriptor format should be lower of
struct fsl_qdma_engine number data address.
Signed-off-by: Peng Ma
---
changed for V3:
- Delete macro to simplify code.
drivers/dma/fsl-qdma.c | 18 ++
1 files changed, 10 insertions(+), 8 deletions(-)
dif
When an error occurs we should clean the error register then to return
Signed-off-by: Peng Ma
---
changed for V3:
- no changed.
drivers/dma/fsl-qdma.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/fsl-qdma.c b/drivers/dma/fsl-qdma.c
index da8fdf
On 5/22/19 9:23 AM, Huang, Ying wrote:
Yang Shi writes:
Since commit bd4c82c22c36 ("mm, THP, swap: delay splitting THP after
swapped out"), THP can be swapped out in a whole. But, nr_reclaimed
and some other vm counters still get inc'ed by one even though a whole
THP (512 pages) gets swapp
On 5/22/19 12:00 AM, Johannes Weiner wrote:
On Tue, May 21, 2019 at 05:40:42PM +0800, Yang Shi wrote:
Since commit bd4c82c22c36 ("mm, THP, swap: delay splitting THP after
swapped out"), THP can be swapped out in a whole. But, nr_reclaimed
and some other vm counters still get inc'ed by one ev
On 05/22/19 at 11:20am, Dave Young wrote:
> On 05/09/19 at 09:36am, Baoquan He wrote:
> > If the running kernel has 5-level paging activated, the 5-level paging
> > mode is preserved across kexec. If the kexec'ed kernel does not contain
> > support for handling active 5-level paging mode in the dec
A regression caused by 854a6ed56839 ("signal: Add restore_user_sigmask()")
caused users of epoll_pwait, io_pgetevents, and ppoll to notice a
latent problem in signal handling during these syscalls.
That patch (854a6ed56839) moved the signal_pending() check closer
to restoring of the user sigmask.
On 05/09/19 at 09:36am, Baoquan He wrote:
> If the running kernel has 5-level paging activated, the 5-level paging
> mode is preserved across kexec. If the kexec'ed kernel does not contain
> support for handling active 5-level paging mode in the decompressor, the
> decompressor will crash with #GP.
On Tue, May 21, 2019 at 08:59:47PM +0530, Anirudh Gupta wrote:
> Family of src/dst can be different from family of selector src/dst.
> Use xfrm selector family to validate address prefix length,
> while verifying new sa from userspace.
>
> Validated patch with this command:
> ip xfrm state add src
On 05/22/19 at 11:11am, Dave Young wrote:
> Hi Baoquan,
>
> A few nitpicks, otherwise
> Acked-by: Dave Young
>
> On 05/09/19 at 09:36am, Baoquan He wrote:
> > Restrict kdump to only reserve crashkernel below 64TB.
> >
> > The reaons is that the kdump may jump from 5-level to 4-level, and if
> >
> From: linux-hyperv-ow...@vger.kernel.org
> Sent: Sunday, May 19, 2019 3:29 PM
>
> Due to Azure host agent settings, the device instance ID's bytes 8 and 9
> are no longer unique. This causes some of the PCI devices not showing up
> in VMs with multiple passthrough devices, such as GPUs. So, as r
Hi Baoquan,
A few nitpicks, otherwise
Acked-by: Dave Young
On 05/09/19 at 09:36am, Baoquan He wrote:
> Restrict kdump to only reserve crashkernel below 64TB.
>
> The reaons is that the kdump may jump from 5-level to 4-level, and if
> the kdump kernel is put above 64TB, then the jumping will fai
Hi Marcel,
at 5:25 PM, Kai-Heng Feng wrote:
LE Advertising may wake up system during system-wide sleep, disable it
to prevent this issue from happening.
Do the reverse in hci_resume_dev().
Do you have any suggestion for this patch?
Kai-Heng
Signed-off-by: Kai-Heng Feng
---
v2:
- Abstra
Hi Pali,
Why it does not report input data?
--> The alps devices which detected to use the ALPS_PROTO_V8 contains ALPS
touchpad and ALPS track point.
But the ALPS_PROTO_V8 do not support the track point device process.
When the track point was detected to use ALPS_PROTO_V8 ,the v8
p
On Tue, 21 May 2019, Matthew Garrett wrote:
> + int (*locked_down)(const char *where, enum lockdown_level level);
> +static int lockdown_is_locked_down(const char *what, enum lockdown_level
> level)
I'm guessing 'what' is the best option here.
--
James Morris
On Tue, 21 May 2019, Gen Zhang wrote:
> On Tue, May 21, 2019 at 12:30:38AM -0400, Nicolas Pitre wrote:
> > Now imagine that MIN_NR_CONSOLES is defined to 10 instead of 1.
> >
> > What happens with allocated memory if the err_vc condition is met on the
> > 5th loop?
> Yes, vc->vc_screenbuf from t
On Tue, 21 May 2019, Matthew Garrett wrote:
> Hi James,
>
> This is a quick attempt to integrate lockdown into the existing LSM
> framework. It adds a new lockdown security hook and an LSM that defines
> the existing coarse-grained policy, and also adds a new
> DEFINE_EARLY_LSM() definition in or
On Thu, 16 May 2019 12:20:50 +0200 Roman Penyaev wrote:
> On 2019-05-16 12:03, Arnd Bergmann wrote:
> > On Thu, May 16, 2019 at 10:59 AM Roman Penyaev
> > wrote:
> >>
> >> epoll_create2() is needed to accept EPOLL_USERPOLL flags
> >> and size, i.e. this patch wires up polling from userspace.
>
We are now providing business & personal loans:
-Rate starting at: 2.05%.
-Flexible repayment: up to 30 years.
For more information and application, please reply.
> To unsubscribe please reply with "unsubscribe" as subject.
On Sun, 19 May 2019 04:48:21 +0800 kbuild test robot wrote:
> Hi Marco,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v5.1 next-20190517]
> [if your patch is applied to the wrong git tree, please drop us a
On Wed, 22 May 2019 at 09:15, Chunyan Zhang wrote:
>
> The function devm_regmap_init_mmio() wouldn't return NULL pointer for
> now, so only need to ensure the return value is not an error code.
>
> Signed-off-by: Chunyan Zhang
Reviewed-by: Baolin Wang
> ---
> drivers/clk/sprd/common.c | 2 +-
On Wed, 22 May 2019 at 09:15, Chunyan Zhang wrote:
>
> devm_ioremap_resources() automatically requests resources and devm_ wrappers
> do better error handling and unmapping of the I/O region when needed,
> that would make drivers more clean and simple.
>
> Signed-off-by: Chunyan Zhang
Reviewed-b
On Wed, May 22, 2019 at 10:00:37AM +0800, Li Zhijian wrote:
>
> On 5/22/19 09:04, Gen Zhang wrote:
> >In dir_add(), de and de->name are allocated by kmalloc() and kstrdup().
> >And de->name is dereferenced in the following codes. However, memory
> >allocation functions such as kmalloc() and kstrdu
From: Huang Ying
When swapin is performed, after getting the swap entry information from
the page table, system will swap in the swap entry, without any lock held
to prevent the swap device from being swapoff. This may cause the race
like below,
CPU 1 CPU 2
-
The reg property represents the address and size on the bus that a
device lives, but for APR the parent is a rpmsg bus, which does not have
numerical addresses. Simply defining #address/#size-cells to 1 and 0,
respectively, to silence the compiler is not an appropriate solution.
Replace the use of
On Tue, May 21, 2019 at 01:44:33PM -0700, Kees Cook wrote:
> This doesn't look safe to me: p->uni_pgdir[n] will still have a handle
> to the freed memory, won't it?
>
Thanks for your reply, Kees!
I think you are right. Maybe we should do this:
kfree(p1);
p->uni_pgdir[n] = NULL;
Is
On Tue, May 21, 2019 at 11:33:10AM -0400, Johannes Weiner wrote:
> On Tue, May 21, 2019 at 11:55:33AM +0900, Minchan Kim wrote:
> > On Mon, May 20, 2019 at 11:28:01AM +0200, Michal Hocko wrote:
> > > [cc linux-api]
> > >
> > > On Mon 20-05-19 12:52:54, Minchan Kim wrote:
> > > > System could have
Hi Srinivas,
> Subject: Re: [PATCH V3 2/4] nvmem: imx: add i.MX8 nvmem driver
>
>
>
> On 15/05/2019 08:53, Peng Fan wrote:
> > This patch adds i.MX8 nvmem ocotp driver to access fuse via RPC to
> > i.MX8 system controller.
> >
> > Cc: Srinivas Kandagatla
> > Cc: Shawn Guo
> > Cc: Sascha Hauer
1 - 100 of 937 matches
Mail list logo