On Tue, Jun 02, 2020 at 01:43:20PM -0700, Linus Torvalds wrote:
> On Tue, Jun 2, 2020 at 1:33 PM Michael S. Tsirkin wrote:
> >
> > Hmm are you sure we can drop it? access_ok is done in the context
> > of the process. Access itself in the context of a kernel thread
> > that borrows the same mm.
On Tue, 2 Jun 2020 at 15:54, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.183 release.
> There are 76 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.
>
>
On Wed, 03 Jun 2020 07:41:05 +0900,
Stephen Rothwell wrote:
>
> [1 ]
> Hi Rich,
>
> On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker wrote:
> >
> > On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote:
> > > Hi Rich,
> > >
> > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker wrote:
On Wed, Jun 03, 2020 at 02:27:33AM +, Rajat Jain wrote:
> On Mon, Jun 1, 2020 at 10:06 PM Greg Kroah-Hartman
> wrote:
> >
> > On Mon, Jun 01, 2020 at 06:25:42PM -0500, Bjorn Helgaas wrote:
> > > [+cc Greg, linux-kernel for wider exposure]
> >
> > Thanks for the cc:, missed this...
> >
> > >
>
When build perf with ASan or UBSan, if libasan or libubsan can not find,
the feature-glibc is 0 and there exists the following error log which is
wrong, because we can find gnu/libc-version.h in /usr/include, glibc-devel
is also installed.
[yangtiezhu@linux perf]$ make DEBUG=1
Remove Andreas Werner as Maintainer of the F21 BMC driver, as he is no
longer with the company and add Andreas Geissler as additional
Maintainer for all MEN Hardware.
Acked-by: Johannes Thumshirn
Acked-by: Andreas Werner
Signed-off-by: AGeissler
---
MAINTAINERS | 12 +++-
1 file
On Tue, Jun 02, 2020 at 10:41:16PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit:1ee08de1 Merge tag 'for-5.8/io_uring-2020-06-01' of git://..
> git tree: upstream
> console output:
On Tue, 2 Jun 2020 at 23:44, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.226 release.
> There are 55 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.
>
>
On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote:
>
> 在 2020/6/3 1:20, Markus Elfring 写道:
> > > Fix it by adding a call to kobject_put() in the error path of
> > > kobject_init_and_add().
> > Thanks for another completion of the exception handling.
> >
> > Would an other patch subject
On Tue, 2 Jun 2020 at 15:46, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.226 release.
> There are 47 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.
>
>
> -Original Message-
> From: Christoph Hellwig
> Sent: Wednesday, June 3, 2020 7:27 AM
> To: Stankiewicz, Piotr
> Cc: Hunter, Adrian ; Ulf Hansson
> ; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH 11/15] mmc: sdhci: use PCI_IRQ_MSI_TYPES where
>
patch #1: support to set and get pause params with
"ethtool -A/a" cmd
patch #2: support to set and get irq coalesce params with
"ethtool -C/c" cmd
patch #3: support to do self test with "ethtool -t" cmd
patch #4: support to identify physical device with "ethtool -p" cmd
patch
add support to get eeprom information from the plug-in module
with ethtool -m cmd.
Signed-off-by: Luo bin
---
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 68
.../net/ethernet/huawei/hinic/hinic_hw_dev.h | 4 +
.../net/ethernet/huawei/hinic/hinic_port.c| 78
add support to excute internal and external loopback test with
ethtool -t cmd.
Signed-off-by: Luo bin
---
drivers/net/ethernet/huawei/hinic/hinic_dev.h | 6 +
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 178 ++
.../net/ethernet/huawei/hinic/hinic_hw_dev.h | 3 +
add support to set TX/RX irq coalesce params with ethtool -C and
get these params with ethtool -c.
Signed-off-by: Luo bin
---
drivers/net/ethernet/huawei/hinic/hinic_dev.h | 8 +
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 294 ++
add support to set pause params with ethtool -A and get pause
params with ethtool -a. Also remove set_link_ksettings ops for VF
and enable pause by default.
Signed-off-by: Luo bin
---
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 100 +-
add support to identify physical device by flashing an LED
attached to it with ethtool -p cmd.
Signed-off-by: Luo bin
---
.../net/ethernet/huawei/hinic/hinic_ethtool.c | 41 ++
.../net/ethernet/huawei/hinic/hinic_hw_dev.c | 2 +
.../net/ethernet/huawei/hinic/hinic_hw_dev.h | 1 +
On 2020/6/3 下午1:46, Michael S. Tsirkin wrote:
On Wed, Jun 03, 2020 at 01:18:54PM +0800, Jason Wang wrote:
On 2020/6/3 下午12:18, Al Viro wrote:
On Wed, Jun 03, 2020 at 11:57:11AM +0800, Jason Wang wrote:
How widely do you hope to stretch the user_access areas, anyway?
To have best
Convert the MXS SPI binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
Documentation/devicetree/bindings/spi/mxs-spi.txt | 26 --
Documentation/devicetree/bindings/spi/mxs-spi.yaml | 55 ++
2 files changed, 55 insertions(+), 26 deletions(-)
Convert the i.MX CSPI binding to DT schema format using json-schema,
update compatible, remove obsolete properties "fsl,spi-num-chipselects"
and update the example based on latest DT file.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/spi/fsl-imx-cspi.txt | 56 -
This patch series converts mxs/imx spi/cspi/lpspi binding to json-schema.
In fsl-imx-cspi.yaml, also update compatible, remove obsolete properties
"fsl,spi-num-chipselects" and update the example based on latest DT file;
In spi-fsl-lpspi.yaml, the original maintainer's email address
Convert the i.MX LPSPI binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
.../devicetree/bindings/spi/spi-fsl-lpspi.txt | 29 ---
.../devicetree/bindings/spi/spi-fsl-lpspi.yaml | 60 ++
2 files changed, 60 insertions(+), 29
On Wed, Jun 03, 2020 at 05:18:49AM +0100, Al Viro wrote:
> On Wed, Jun 03, 2020 at 11:57:11AM +0800, Jason Wang wrote:
>
> > > How widely do you hope to stretch the user_access areas, anyway?
> >
> >
> > To have best performance for small packets like 64B, if possible, we want to
> > disable
On Wed, 03 Jun 2020 05:05:15 +0200,
Macpaul Lin wrote:
>
> On Tue, 2020-06-02 at 14:46 +0200, Takashi Iwai wrote:
> > On Tue, 02 Jun 2020 13:53:41 +0200,
> > Macpaul Lin wrote:
> > >
> > > This patch fix incorrect power state changed by usb_audio_suspend()
> > > when CONFIG_PM is enabled.
> > >
> Additionally, there's no point copying param->string in
> exfat_parse_param() - just steal it, leaving NULL in param->string.
> That's independent from the leak or fix thereof - it's simply
> avoiding an extra copy.
I find it clearer to provide such a source code adjustment
by a separate update
On Wed, Jun 03, 2020 at 02:23:08PM +0800, Jason Wang wrote:
> >
> > BTW now I re-read it I don't understand __vhost_get_user_slow:
> >
> >
> > static void __user *__vhost_get_user_slow(struct vhost_virtqueue *vq,
> >void __user *addr, unsigned int
>
On Wed, Jun 3, 2020 at 1:44 PM Eric Dumazet wrote:
>
> On Tue, Jun 2, 2020 at 10:05 PM Jason Xing wrote:
> >
> > Hi Eric,
> >
> > I'm still trying to understand what you're saying before. Would this
> > be better as following:
> > 1) discard the tcp_internal_pacing() function.
> > 2) remove
在 2020/6/3 14:14, Greg Kroah-Hartman 写道:
On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote:
在 2020/6/3 1:20, Markus Elfring 写道:
Fix it by adding a call to kobject_put() in the error path of
kobject_init_and_add().
Thanks for another completion of the exception handling.
Would an
Hi Dave,
On 01-06-20, 15:09, Dave Jiang wrote:
> Vinod,
> Obviously this series won't make it for 5.8 due to being blocked by
> Fenghua's PASID series. Do you think you can take patches 4 and 5
> independently? I think these can go into 5.8 and is not dependent on
> anything. Thanks.
I was out
On Wed, Jun 03, 2020 at 12:18:44PM +0800, Jason Wang wrote:
>
> On 2020/6/2 下午9:31, Michael S. Tsirkin wrote:
> > On Tue, Jun 02, 2020 at 02:49:38PM +0800, Jason Wang wrote:
> > > On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
> > > > On Tue, Jun 02, 2020 at 03:22:49AM +0800, kbuild test robot
On 2020/6/3 下午2:30, Michael S. Tsirkin wrote:
On Wed, Jun 03, 2020 at 02:23:08PM +0800, Jason Wang wrote:
BTW now I re-read it I don't understand __vhost_get_user_slow:
static void __user *__vhost_get_user_slow(struct vhost_virtqueue *vq,
void
Add missing line breaks on pr_warn().
Signed-off-by: Chen Tao
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index cef05d3a23f5..0b0f05e1e49e 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -7123,7 +7123,7 @@
On 2020/6/3 下午2:34, Michael S. Tsirkin wrote:
On Wed, Jun 03, 2020 at 12:18:44PM +0800, Jason Wang wrote:
On 2020/6/2 下午9:31, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at 02:49:38PM +0800, Jason Wang wrote:
On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at
a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Andrei-Vagin/arm64-add-the-time-namespace-support/20200603-020504
base
In previous patch, using return -EBUSY in really_probe() instead WARN_ON()
only. The following is the partial code.
...
atomic_inc(_count);
pr_debug("bus: '%s': %s: probing driver %s with device %s\n",
drv->bus->name, __func__, drv->name, dev_name(dev));
On Wed, 3 Jun 2020 at 07:34, Masahiro Yamada wrote:
>
> Documentation/kbuild/makefiles.rst says:
>
> Use of lib-y is normally restricted to `lib/` and `arch/*/lib`.
>
> I want to disallow lib-y outside of them.
>
Why?
> Add a custom rule to build lib.a, which is linked to the decompressor
>
> Please note that you are responding to someone that a lot of kernel
> developers and maintainers have blacklisted as being very annoying
I can understand that you can occasionally become annoyed.
> and not helpful at all.
I got the impression that some contributors (including you)
found also
Hi Ritesh,
On 20.05.2020 08:40, Ritesh Harjani wrote:
> There could be a race in function ext4_mb_discard_group_preallocations()
> where the 1st thread may iterate through group's bb_prealloc_list and
> remove all the PAs and add to function's local list head.
> Now if the 2nd thread comes in to
On Wed, Jun 03, 2020 at 02:34:07PM +0800, wanghai (M) wrote:
>
> 在 2020/6/3 14:14, Greg Kroah-Hartman 写道:
> > On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote:
> > > 在 2020/6/3 1:20, Markus Elfring 写道:
> > > > > Fix it by adding a call to kobject_put() in the error path of
> > > > >
There is no way to set up the defrag options in boot time. And it's
useful to set it up by default instead of making it work by a
systemd/upstart service or put the command to set up defrag inside
/etc/rc.local.
Signed-off-by: Gavin Guo
---
.../admin-guide/kernel-parameters.txt | 18
在 2020/6/3 14:50, Greg Kroah-Hartman 写道:
On Wed, Jun 03, 2020 at 02:34:07PM +0800, wanghai (M) wrote:
在 2020/6/3 14:14, Greg Kroah-Hartman 写道:
On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote:
在 2020/6/3 1:20, Markus Elfring 写道:
Fix it by adding a call to kobject_put() in the
On Wed, 03 Jun 2020 08:28:09 +0200,
Takashi Iwai wrote:
>
> And, the most suspicious case is the last one,
> chip->num_suspended-intf. It means that the device has multiple
> USB interfaces and they went to suspend, while the resume isn't
> performed for the all suspended interfaces in return.
The seg6_validate_srh() is used to validate SRH for three cases:
case1: SRH of data-plane SRv6 packets to be processed by the Linux kernel.
Case2: SRH of the netlink message received from user-space (iproute2)
Case3: SRH injected into packets through setsockopt
In case1, the SRH can be encoded
On Tue, 2 Jun 2020, Shuah Khan wrote:
> I changed the logic to read config to get max banks and counters
> before checking if counters are writable and tried writing to all.
> The result is the same and all of them aren't writable. However,
> when disable the writable check and assume they are, I
the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub
> Okay, so I don’t have to send the v2 patch.
It will become more interesting under which circumstances the presented
software development concerns will be taken better into account.
Regards,
Markus
On 02.06.20 17:48:43, Borislav Petkov wrote:
> On Thu, May 28, 2020 at 12:13:06PM +0200, Robert Richter wrote:
> > v4:
> >
> > * dimm->label: Only update dimm->label in if bank/device is found in
> >the SMBIOS table, this keeps current behavior for machines that do
> >not provide this
On 2020/6/2 20:41, Sahitya Tummala wrote:
> In case a compressed file is getting overwritten, the current retry
> logic doesn't include the current page to be retried now as it sets
> the new start index as 0 and new end index as writeback_index - 1.
> This causes the corresponding cluster to be
On 2020/6/1 11:03, Daeho Jeong wrote:
> From: Daeho Jeong
>
> Found a new segemnt allocation without f2fs_lock_op() in
> expand_inode_data(). So, when we do fallocate() for a pinned file
> and trigger checkpoint very frequently and simultaneously. F2FS gets
> stuck in the below code of
There's a hack at the driver that selects a different table
for a BYT tablet, which sets the maximum frequency to 320 MHz,
instead of 400 MHz.
After looking at the Intel Aero Yocto's version from:
https://download.01.org/aero/deb/pool/main/l/linux-4.4.76-aero-1.3/
It was noticed that
When an IRQ is not handled, it is nice to know what's the
reason.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/atomisp_cmd.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/atomisp_cmd.c
Replace usages of strcpy(), strlcpy() and strncpy() in favor
of strscpy().
Suggested-by: Hans Verkuil
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/atomisp_file.c | 2 +-
.../media/atomisp/pci/atomisp_gmin_platform.c| 2 +-
Instead of having a static var to detect it, let's use the
already-existing arch-specific bytes, as this is how other
parts of the code also checks when it needs to do something
different, depending on an specific chipset version.
Signed-off-by: Mauro Carvalho Chehab
---
Most of the code here is meant to make the IRQ handling code clearer,
and the ISP frequency setting (DFS).
There's a fix there at the DFS setting: right now, if the sensor doesn't
provide the number of frames per second, DFS is kept on its minimal
value, with will likely fail. The logic at patch
Some parts of the driver have their own implementation of
memcpy() & friends. Replace all of them by strscpy().
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_include/string_support.h | 165 --
.../ctc/ctc_1.0/ia_css_ctc_table.host.c | 3 +-
There are some ifdefs there that end doing the same thing.
Get rid of them.
Signed-off-by: Mauro Carvalho Chehab
---
.../atomisp/pci/isp2400_input_system_local.h | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git
There are several parts of the driver that could produce
a "dfs failed!" message. Change the texts, in order to help
identifying from where they're coming.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/atomisp_cmd.c | 4 ++--
Instead of hardcoding the intel family values there, use
the already defined ones from asm/intel-family.h.
Signed-off-by: Mauro Carvalho Chehab
---
.../media/atomisp/include/linux/atomisp_platform.h | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
The contents of hive_isp_css_2401_irq_types_hrt.h and
hive_isp_css_common/irq_global.h are identical, except for
one unused enum:
On isp2401, this IRQ line has this name:
hrt_isp_css_irq_is2401 = HIVE_GP_DEV_IRQ_ISP_PMEM_ERROR_BIT_ID,
While the same bit is named as:
As both isp2400 and isp2401 files are identical, remove one
of them and remove the test for ISP variant.
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_common/isp_global.h | 6 +-
.../atomisp/pci/isp2401_mamoiada_params.h | 211 --
If the sensor doesn't implement support for g_frame_interval,
it won't return the expected fps rate.
Instead of keeping DFS on its minimal value (which will likely
not work), set it to the max.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/atomisp_cmd.c | 8
- Get rid of typedefs;
- Get rid of a duplicated enum type with different names for
ISP2400 and ISP2401;
- adjust indentation on the touched code.
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_common/host/irq.c| 29 +--
There are some parameters that are different between
isp2400 and isp2401. None of those are actually used.
So, get rid of them.
Signed-off-by: Mauro Carvalho Chehab
---
.../hrt/isp2400_mamoiada_params.h | 20 +--
.../atomisp/pci/isp2401_mamoiada_params.h | 20
The logic which sets the hpll_freq for BYT sets hpll_freq
to 1600MHz, but ignores it, and sets it again after reading
from-device-specific EFI vars (this time, using a default
of 2000MHz).
Remove the first set, as this will be overriden anyway.
While here, do minor adjustments on comments and on
There are lots of mess with IRQ ifdef settings. As the
*_global.h will already detect the type of IRQ system at
compile time, we can get rid of them, replacing by just
one ifdef for ISP2401.
Signed-off-by: Mauro Carvalho Chehab
---
.../pci/hive_isp_css_common/isp_global.h | 10 ++
On Thu, Apr 23, 2020 at 4:58 AM Zhe Li wrote:
>
> Mounting jffs2 on nand flash will get message "failed: I/O error"
> with the steps listed below.
> 1.erase nand flash
> 2.mount jffs2 on it (this mounting operation will be successful)
> 3.do chown or chmod to the mount point directory
> 4.umount
Oh, thanks for notification!
2020년 6월 3일 (수) 오후 3:59, Chao Yu 님이 작성:
>
> On 2020/6/1 11:03, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > Found a new segemnt allocation without f2fs_lock_op() in
> > expand_inode_data(). So, when we do fallocate() for a pinned file
> > and trigger checkpoint
[resend; because of missing cc]
Remove Andreas Werner as Maintainer of the F21 BMC driver, as he is no
longer with the company and add Andreas Geissler as additional
Maintainer for all MEN Hardware.
Acked-by: Johannes Thumshirn
Acked-by: Andreas Werner
Signed-off-by: AGeissler
---
From: SeongJae Park
DAMON[1] can be used as a primitive for data access awared memory management
optimizations. For that, users who want such optimizations should run DAMON,
read the monitoring results, analyze it, plan a new memory management scheme,
and apply the new scheme by themselves.
From: SeongJae Park
This commit exports 'do_madvise()' to external GPL modules, so that
other modules including DAMON could use the function.
Signed-off-by: SeongJae Park
---
mm/madvise.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/madvise.c b/mm/madvise.c
index
Once PR_SPEC_FORCE_DISABLE is set, users cannot set PR_SPEC_ENABLE.
This commit checks whether PR_SPEC_FORCE_DISABLE was previously set.
Signed-off-by: Kenta Tada
---
arch/x86/kernel/cpu/bugs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/kernel/cpu/bugs.c
Hi Ji-Ze,
On Wed, Jun 3, 2020 at 8:45 AM Ji-Ze Hong (Peter Hong) wrote:
> In previous patch, using return -EBUSY in really_probe() instead WARN_ON()
> only. The following is the partial code.
>
> ...
> atomic_inc(_count);
> pr_debug("bus: '%s': %s: probing driver %s with
From: SeongJae Park
DAMON can be used as a primitive for data access pattern aware memory
management optimizations. However, users who want such optimizations
should run DAMON, read the monitoring results, analyze it, plan a new
memory management scheme, and apply the new scheme by themselves.
On 2020/6/2 下午9:05, Michael S. Tsirkin wrote:
The idea is to support multiple ring formats by converting
to a format-independent array of descriptors.
This costs extra cycles, but we gain in ability
to fetch a batch of descriptors in one go, which
is good for code cache locality.
When used,
From: SeongJae Park
In many cases, users might use DAMON for simple data access aware
memory management optimizations such as applying an operation scheme to
a memory region of a specific size having a specific access frequency
for a specific time. For example, "page out a memory region larger
From: SeongJae Park
This commit implements a debugfs interface for the data access
monitoring oriented memory management schemes. It is supposed to be
used by administrators and/or privileged user space programs. Users can
read and update the rules using ``/damon/schemes`` file. The
format
From: SeongJae Park
To tune the DAMON-based operation schemes, knowing how many and how
large regions are affected by each of the schemes will be helful. Those
stats could be used for not only the tuning, but also monitoring of the
working set size and the number of regions, if the scheme does
On 2020/6/2 下午9:05, Michael S. Tsirkin wrote:
As testing shows no performance change, switch to that now.
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Eugenio Pérez
Link: https://lore.kernel.org/r/20200401183118.8334-3-epere...@redhat.com
Signed-off-by: Michael S. Tsirkin
---
From: SeongJae Park
This commit adds simple selftets for 'schemes' debugfs file of DAMON.
Signed-off-by: SeongJae Park
---
.../testing/selftests/damon/debugfs_attrs.sh | 29 +++
1 file changed, 29 insertions(+)
diff --git a/tools/testing/selftests/damon/debugfs_attrs.sh
From: SeongJae Park
This commit documents DAMON-based operation schemes in the DAMON
document.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/guide.rst | 35 +
Documentation/admin-guide/mm/damon/usage.rst | 127 +--
2 files changed, 152 insertions(+),
From: SeongJae Park
This commit implements 'schemes' subcommand of the damon userspace tool.
It can be used to describe and apply the data access monitoring-based
operation schemes in more human friendly fashion.
Signed-off-by: SeongJae Park
---
tools/damon/_convert_damos.py | 128
On Tue, Jun 02, 2020 at 04:36:22PM -0400, Kyungtae Kim wrote:
> We report a bug (in linux-5.6.11) found by FuzzUSB (a modified version
> of syzkaller)
>
> The buf of an usbtest_dev instance (dev->buf) allocated in
> usbtest_probe() leaked.
>
> The usbtest_dev instance holding the buf is attached
Hi
Am 02.06.20 um 23:56 schrieb Linus Torvalds:
> On Tue, Jun 2, 2020 at 2:21 PM Linus Torvalds
> wrote:
>>
>> I'm still working through the rest of the merge, so far that was the
>> only one that made me go "Whaa?".
>
> Hmm. I'm also ending up effectively reverting the drm commit
>
On Fri, May 29, 2020 at 5:38 AM Zhe Li wrote:
>
> Recently I find a bug that I get nothing with shell
> command "ls". The test steps are listed below.
> 1. cd $JFFS2_MOUNT_DIR
> 2. touch file
> 3. ls
>
> Finally I find that when command "ls" going into
> function jffs2_readdir(), it get non-zero
On Tue, Jun 02, 2020 at 04:35:33PM -0400, Kyungtae Kim wrote:
> We report a bug (in linux-5.6.11) found by FuzzUSB (a modified version
> of syzkaller)
>
> This bug happened when accessing a deallocated instance in printer_read().
>
> printer_read() tries to access lock_printer_io of the
Signed-off-by: kbuild test robot
---
contiguous.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c
index 4b10d0ca0456d..2094c8e0590ac 100644
--- a/kernel/dma/contiguous.c
+++ b/kernel/dma/contiguous.c
@@ -37,7 +37,7 @@
Hi!
On 5/31/20 12:47 PM, John Paul Adrian Glaubitz wrote:
> Changes since v1:
> - Replace single mov instruction for exception handling
>in case of invalid load
Yutaka Niibe has had a look at my patch and he says, we might have to add
an entry for the fault handling of the upper word.
This patch-set is aimed to improve console handling especially when kdb
operates in NMI context.
Brief description of enhancements:
- Add status check for console prior to invoking corresponding handler.
- Fixup to avoid possible deadlock in NMI context due to usage of locks
in the console
also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CMA-for-ARM-server/20200603-104821
base: https://git.kernel.org/pub/scm/linux/kernel/git
On 2 June 2020 11:03:03 PM IST, Amit Singh Tomar wrote:
>At the moment, Driver uses bit fields to describe registers of the DMA
>descriptor structure that makes it less portable and maintainable, and
>Andre suugested(and even sketched important bits for it) to make use of
>array to describe
Re-factor kdb_printf() message write code in order to avoid duplication
of code and thereby increase readability.
Signed-off-by: Sumit Garg
Reviewed-by: Douglas Anderson
---
kernel/debug/kdb/kdb_io.c | 57 +++
1 file changed, 28 insertions(+), 29
In kgdb context, calling console handlers aren't safe due to locks used
in those handlers which could in turn lead to a deadlock. Although, using
oops_in_progress increases the chance to bypass locks in most console
handlers but it might not be sufficient enough in case a console uses
more locks
Check if a console is enabled prior to invoking corresponding write
handler.
Suggested-by: Sergey Senozhatsky
Signed-off-by: Sumit Garg
Reviewed-by: Daniel Thompson
Reviewed-by: Douglas Anderson
---
kernel/debug/kdb/kdb_io.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
While rounding up CPUs via NMIs, its possible that a rounded up CPU
maybe holding a console port lock leading to kgdb master CPU stuck in
a deadlock during invocation of console write operations. A similar
deadlock could also be possible while using synchronous breakpoints.
So in order to avoid
Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for
subscribing to the service. It has been a long time we use both kbuild test
robot and kernel test robot to send out report. From now on, we want to
combine two mails to kernel test robot, which is a single voice for the
On Tue Jun 02 20, Joerg Roedel wrote:
Hi,
two small patches to move the Intel and AMD IOMMU drivers into their own
subdirectory under drivers/iommu/ to make the file structure a bit less
cluttered.
Regards,
Joerg
Joerg Roedel (2):
iommu/amd: Move AMD IOMMU driver into subdirectory
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
With this patch applied, new and old code perform identically.
Lots of extra optimizations are now possible, e.g.
we can fetch multiple heads with copy_from/to_user now.
We can get rid of maintaining the log array. Etc etc.
Signed-off-by:
Hi Rich!
On 6/2/20 3:33 AM, Rich Felker wrote:
> Hmm, it looks like Andrew Morton just pulled most of these into -mm,
> apparently independently of me getting them in my for-next a few hours
> ago, since his versions lack my signed-off-by. That's ok though, as
> long as they go up. Some details
On Tue, 2020-06-02 at 21:02 +0800, Marc Zyngier wrote:
> On 2020-06-02 13:14, Ard Biesheuvel wrote:
> > On Tue, 2 Jun 2020 at 10:15, Neal Liu wrote:
> >>
> >> These patch series introduce a security random number generator
> >> which provides a generic interface to get hardware rnd from Secure
>
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
Return code of fetch_buf is confusing, so callers resort to
tricks to get to sane values. Let's switch to something standard:
0 empty, >0 non-empty, <0 error.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/vhost.c | 24
1 - 100 of 1155 matches
Mail list logo
