From: René van Dorst
in recent Kernel-Versions there are warnings about incorrect MTU-Size
like these:
mt7530 mdio-bus:00: nonfatal error -95 setting MTU on port x
eth0: mtu greater than device maximum
mtk_soc_eth 1b10.ethernet eth0: error -22 setting MTU to include DSA
overhead
Fixes:
Remove unneeded variable i in bch_dirty_init_thread().
Signed-off-by: Xu Wang
---
drivers/md/bcache/writeback.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/md/bcache/writeback.c b/drivers/md/bcache/writeback.c
index 1cf1e5016cb9..71801c086b82 100644
---
Hi,
> On Jul 3, 2020, at 20:27, Hans de Goede wrote:
>
> Hi,
>
> On 7/1/20 8:46 AM, Kai-Heng Feng wrote:
>>> On Jun 19, 2020, at 17:56, Hans de Goede wrote:
>>>
>>> Hi,
>>>
>>> On 6/19/20 6:16 AM, Kai-Heng Feng wrote:
Hi,
> On Jun 18, 2020, at 23:28, Hans de Goede wrote:
>
On Wed, Jul 08, 2020 at 04:13:54PM -0700, Nick Desaulniers wrote:
> On Thu, Jul 2, 2020 at 8:57 AM Kees Cook wrote:
> >
> > This looks good to me. Do you want me to carry it as part of the orphan
> > series? (It doesn't look like it'll collide, so that's not needed, but I
> > can if that makes
Dear Linux folks,
Building Linux v5.8-rc4-25-gbfe91da29bfad with Clang/LLD
1:11~++20200701093119+ffee8040534-1~exp1 from Debian experimental for
32-bit (`ARCH=i386`), starting Weston (Wayland) or X.Org Server results
in non-working screen, and Linux shows the trace below [1].
[
Remove unnecassary casts in the argument to kfree.
Signed-off-by: Xu Wang
---
fs/debugfs/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
index ae49a55bda00..3753c4c484fc 100644
--- a/fs/debugfs/file.c
+++ b/fs/debugfs/file.c
@@
On 07/09, Chao Yu wrote:
> On 2020/7/9 9:57, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > When end_addr comes to zero, it'll trigger different behaviour.
> > To prevent this, we need to ignore the case of that range.len is
> > zero in the function.
> >
> > Signed-off-by: Daeho Jeong
> >
On 07. 07. 20, 17:42, Dave Jiang wrote:
> On 7/6/2020 11:05 PM, Jiri Slaby wrote:
>> On 26. 06. 20, 20:09, Dave Jiang wrote:
>>> Check dma device list and channel list for empty before iterate as the
>>> iteration function assume the list to be not empty. With devices and
>>> channels now being
Use delayed timer as default instead of deferrable timer
in order to monitor the DMC status regardless of CPU idle.
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Lukasz Luba
Signed-off-by: Chanwoo Choi
---
drivers/memory/samsung/exynos5422-dmc.c | 1 +
1 file changed, 1 insertion(+)
diff
Until now, the devfreq driver using polling mode like simple_ondemand
governor have used only deferrable timer for reducing the redundant
power consumption. It reduces the CPU wake-up from idle due to polling mode
which check the status of Non-CPU device.
But, it has a problem for Non-CPU device
Add the delayed timer to devfreq framework in order to support
the periodical polling mode without stop caused by CPU idle state.
Some Non-CPU device must need to monitor the device status like
utilization regardless of CPU state.
- patch1 explains the detailed reason why the delayed timer is
Hi Krzysztof,
On 7/8/20 9:33 PM, Krzysztof Kozlowski wrote:
> On Fri, Jul 03, 2020 at 03:26:22PM +0900, Chanwoo Choi wrote:
>> Use delayed timer as default instead of deferrable timer
>> in order to monitor the DMC status regardless of CPU idle.
>>
>> Signed-off-by: Chanwoo Choi
>> ---
>>
Hi Guo,
Le 7/9/20 à 12:38 AM, guo...@kernel.org a écrit :
From: Guo Ren
Let riscv enable randomizes the stack, heap and binary images of
ELF binaries. Seems it's ok at all after qemu & chip test and
there is no founded side effect.
So just simply select ARCH_HAS_ELF_RANDOMIZE :)
On Wed, Jul 08, 2020 at 05:14:29PM -0600, Jens Axboe wrote:
> On 7/1/20 3:06 AM, Christoph Hellwig wrote:
> > Hi Jens,
> >
> > we have a lot of bdi congestion related code that is left around without
> > any use. This series removes it in preparation of sorting out the bdi
> > lifetime rules
Hi KP,
I love your patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url:
https://github.com/0day-ci/linux/commits/KP-Singh/Generalizing-bpf_local_storage/20200709-085810
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config:
It doesn't need to bypass flushing quota data in background.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 44645f4f914b6..72e8b50e588c1 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@
On Mon, Dec 02, 2019 at 11:07:26AM +0800, Dave.Wang wrote:
> Hi Dmitry,
>
> List device with its corresponding hardware ID as below patch,
> Please check , thanks!
>
> Add more hardware ID for Lenovo laptop.
>
> Signed-off-by: Dave Wang
Applied, thank you.
--
Dmitry
Very sorry for that, I will re-send v2 later.
Stephen Rothwell s...@canb.auug.org.auwrote:
> Hi all,
>
> After merging the spi tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/spi/spi-atmel.c: In function 'atmel_spi_probe':
>
While running LTP mm test suite on i386 or qemu_i386 this kernel warning
has been noticed from stable 5.4 to stable 5.7 branches and mainline 5.8.0-rc4
and linux next.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git commit:
Hi "Matthew,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on block/for-next]
[cannot apply to balbi-usb/testing/next cifs/for-next miklos-vfs/overlayfs-next
linus/master v5.8-rc4 next-20200708]
[If your patch is applied to the wrong git tree, kindly dr
Hi Florian,
On 2020-07-09 10:43, Florian Fainelli wrote:
When the erratum_1463225 array was introduced a sentinel at the end was
missing thus causing a KASAN: global-out-of-bounds in
is_affected_midr_range_list on arm64 error.
Link:
Check upon `num_rsp` is insufficient. A malformed event packet with a
large `num_rsp` number makes hci_extended_inquiry_result_evt() go out
of bounds. Fix it. Also, make `num_rsp` unsigned.
This patch fixes the following syzbot bug:
Enable ARCH_HAS_FAST_MULTIPLIER on RV64I
which works fine on GCC-9.3 and GCC-10.1
PS2: remove ARCH_SUPPORTS_INT128 because of RV64I already enabled.
Signed-off-by: Chenxi Mao
---
arch/riscv/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> Hello,
>
> Just a gentle reminder that I'd like some feedback.
> Any suggestions here?
If no-one objects, I think you can submit your patches for review as non-RFC.
Thanks,
Avri
>
> Thanks,
> Daejun
On 7/8/2020 9:36 PM, Naresh Kamboju wrote:
> While running LTP cpuhotplug test on mainline 5.8.0-rc4 the kernel BUG noticed
> on arm64 Juno-r2 KASAN config enabled kernel.
>
> steps to reproduce:
> - boot KASAN enabled Juno-r2 device
> - cd /opt/ltp
> - ./runltp -f cpuhotplug
>
> metadata:
>
When the erratum_1463225 array was introduced a sentinel at the end was
missing thus causing a KASAN: global-out-of-bounds in
is_affected_midr_range_list on arm64 error.
Link:
https://lore.kernel.org/linux-arm-kernel/ca+g9fys3eavpu89-rtqfqq9ggxamgmak7jiivrfp0yxj5s+...@mail.gmail.com/
Fixes:
Hi Dan
> -Original Message-
> From: Dan Williams
> Sent: Thursday, July 9, 2020 11:39 AM
> To: Justin He
> Cc: Catalin Marinas ; Will Deacon
> ; Tony Luck ; Fenghua Yu
> ; Yoshinori Sato ; Rich
> Felker ; Dave Hansen ; Andy
> Lutomirski ; Peter Zijlstra ;
> Thomas Gleixner ; Ingo Molnar
Hi Andrzej,
On Fri, Jun 19, 2020 at 06:28:19PM +0200, Andrzej Pietrasiewicz wrote:
> There exist machines which don't have SysRq key at all, e.g. chromebooks.
>
> This patch allows configuring an alternative key to act as SysRq. Devices
> which declare KEY_SYSRQ in their 'keybit' bitmap continue
On Sun, 07 Jun 2020 00:59:46 PDT (-0700), a...@ghiti.fr wrote:
This is a preparatory patch for relocatable kernel.
The kernel used to be linked at PAGE_OFFSET address and used to be loaded
physically at the beginning of the main memory. Therefore, we could use
the linear mapping for the kernel
Expose the SMR and S2CR structs in the header file, to allow platform
specific implementations to populate/initialize the smrs and s2cr
arrays.
Signed-off-by: Bjorn Andersson
---
drivers/iommu/arm-smmu.c | 14 --
drivers/iommu/arm-smmu.h | 15 +++
2 files changed, 15
Based on previous attempts and discussions this is the latest attempt at
inheriting stream mappings set up by the bootloader, for e.g. boot splash or
efifb.
The first patch is an implementation of Robin's suggestion that we should just
mark the relevant stream mappings as BYPASS. Relying on
Firmware that traps writes to S2CR to translate BYPASS into FAULT also
ignores writes of type FAULT. As such booting with "disable_bypass" set
will result in all S2CR registers left as configured by the bootloader.
This has been seen to result in indeterministic results, as these
mappings might
With many Qualcomm platforms not having functional S2CR BYPASS a
temporary IOMMU domain, without translation, needs to be allocated in
order to allow these memory transactions.
Unfortunately the boot loader uses the first few context banks, so
rather than overwriting a active bank the last
Turn all stream mappings marked as valid into BYPASS. This allows the
platform specific implementation to configure stream mappings to match
the boot loader's configuration for e.g. display to continue to function
through the reset of the SMMU.
Suggested-by: Robin Murphy
Signed-off-by: Bjorn
Some firmware found on various Qualcomm platforms traps writes to S2CR
of type BYPASS and writes FAULT into the register. This prevents us from
marking the streams for the display controller as BYPASS to allow
continued scanout of the screen through the initialization of the ARM
SMMU.
This adds a
While running LTP controllers on mainline 5.8.0-rc4 the kernel warning was
noticed on x86_64 KASAN enabled kernel.
steps to reproduce:
- boot KASAN enabled x86_64 device
- cd /opt/ltp
- ./runltp -f controllers
metadata:
git branch: master
git repo:
On Tue, Jul 07, 2020 at 01:41:20PM +0800, Feng Tang wrote:
> On Tue, Jul 07, 2020 at 12:00:09PM +0800, Huang, Ying wrote:
> > Feng Tang writes:
> >
> > > On Mon, Jul 06, 2020 at 06:34:34AM -0700, Andi Kleen wrote:
> > >> >ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> >
On Fri 03 Jul 05:31 PDT 2020, Will Deacon wrote:
> On Tue, Jun 09, 2020 at 03:40:18PM -0400, Jonathan Marek wrote:
> > Add dts nodes for apps_smmu and USB for both sm8150 and sm8250.
> >
> > Also add initial dts files for HDK855 and HDK865, based on mtp dts, with a
> > few changes. Notably, the
On Tue 09 Jun 12:40 PDT 2020, Jonathan Marek wrote:
> Use the qcom implementation for IOMMU hardware on sm8150 and sm8250 SoCs.
>
> Signed-off-by: Jonathan Marek
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> ---
> drivers/iommu/arm-smmu-impl.c | 4 +++-
> 1 file changed, 3 insertions(+), 1
From: Guo Ren
Let riscv enable randomizes the stack, heap and binary images of
ELF binaries. Seems it's ok at all after qemu & chip test and
there is no founded side effect.
So just simply select ARCH_HAS_ELF_RANDOMIZE :)
Signed-off-by: Guo Ren
Cc: Palmer Dabbelt
Cc: Paul Walmsley
Cc: Zong
在 2020/7/9 11:26, Stephen Rothwell 写道:
Hi all,
After merging the device-mapper tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from drivers/md/dm-dust.c:11:
drivers/md/dm-dust.c: In function 'dust_list_badblocks':
drivers/md/dm-dust.c:307:10:
Introduce a mechanism to quickly disable/enable syscall handling for a
specific process and redirect to userspace via SIGSYS. This is useful
for processes with parts that require syscall redirection and parts that
don't, but who need to perform this boundary crossing really fast,
without paying
While running LTP cpuhotplug test on mainline 5.8.0-rc4 the kernel BUG noticed
on arm64 Juno-r2 KASAN config enabled kernel.
steps to reproduce:
- boot KASAN enabled Juno-r2 device
- cd /opt/ltp
- ./runltp -f cpuhotplug
metadata:
git branch: master
git repo:
4 Patches of v3 has been queued into kvm/queue branch. This v4 contains
the rest to refactor the flow of KVM_SET_CPUID* as:
1. cpuid check: check if userspace provides legal CPUID settings;
2. cpuid update: Update userspace provided CPUID settings. It currently
only contains
Use kvm_check_cpuid() to validate if userspace provides legal cpuid
settings and call it before KVM take any action to update CPUID or
update vcpu states based on given CPUID settings.
Signed-off-by: Xiaoyao Li
---
arch/x86/kvm/cpuid.c | 55
The name of callback cpuid_update() is misleading that it's not about
updating CPUID settings of vcpu but updating the configurations of vcpu
based on the CPUIDs. So rename it to vcpu_after_set_cpuid().
Signed-off-by: Xiaoyao Li
---
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/cpuid.c
Now there is no updating CPUID bits behavior in kvm_update_cpuid(),
rename it to kvm_vcpu_after_set_cpuid().
Signed-off-by: Xiaoyao Li
---
arch/x86/kvm/cpuid.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
index
kvm_x86_ops.vcpu_after_set_cpuid() is used to update vmx/svm specific
vcpu settings based on updated CPUID settings. So it's supposed to be
called after CPUIDs are updated, i.e., kvm_update_cpuid_runtime().
Currently, kvm_update_cpuid_runtime() only updates CPUID bits of OSXSAVE,
APIC, OSPKE,
Beside called in kvm_vcpu_ioctl_set_cpuid*(), kvm_update_cpuid() is also
called 5 places else in x86.c and 1 place else in lapic.c. All those 6
places only need the part of updating guest CPUIDs (OSXSAVE, OSPKE, APIC,
KVM_FEATURE_PV_UNHALT, ...) based on the runtime vcpu state, so extract
them as
On 7/8/2020 8:10 PM, Paolo Bonzini wrote:
On 08/07/20 08:50, Xiaoyao Li wrote:
This serial is the extended version of
https://lkml.kernel.org/r/20200528151927.14346-1-xiaoyao...@intel.com
First two patches are bug fixing, and the others aim to refactor the flow
of SET_CPUID* as:
1. cpuid
I thought it's better to treat this as the error case, since the range
already passed out of the i_size range.
If we allow that, the user needs to send the range parameter being
aligned like start:0 and len: roundup(i_size, PAGE_SIZE), even if he
or she wants to erase the whole file.
2020년 7월 9일
This email is a detailed explanation of how to test the LAPB drivers,
just in case you have time to check. Thanks!
This email has 4 parts.
1) How to set up "lapbether" links (for comparison)
2) How to set up "x25_asy" links
3) How to test using AF_X25 sockets
4) How to test using
On 08.07.20 21:52, Thomas Gleixner wrote:
From: Thomas Gleixner
read/write_cr2() go throuh the paravirt XXL indirection, but nested VMX in
a XEN_PV guest is not supported.
Use the native variants.
Signed-off-by: Thomas Gleixner
Reviewed-by: Juergen Gross
Juergen
Hi all,
After merging the spi tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/spi/spi-atmel.c: In function 'atmel_spi_probe':
drivers/spi/spi-atmel.c:1680:1: warning: label 'out_free' defined but not used
[-Wunused-label]
1680 | out_free:
| ^~~~
On Mon, Jul 06, 2020 at 09:48:12PM -0300, Leonardo Bras wrote:
> On PAPR+ the hcall() on 0x1B0 is called H_DISABLE_AND_GET, but got
> defined as H_DISABLE_AND_GETC instead.
>
> This define was introduced with a typo in commit
> ("[PATCH] powerpc: Extends HCALL interface for InfiniBand usage"),
On 2020/7/9 11:39, Xu Wang wrote:
> Remove unneeded variable ret i.
>
I see 'i' is removed, where is 'ret' ?
Thanks.
Coly Li
> Signed-off-by: Xu Wang
> ---
> drivers/md/bcache/writeback.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/md/bcache/writeback.c
Issue:
When PEC is enabled, binding adm1272 to the adm1275 would
fail due to PEC error. See below:
adm1275: probe of failed with error -74
Diagnosis:
Per the datasheet of adm1272, adm1278, adm1293 and amd1294,
PMON_CONFIG (0xd4) is 16bits wide. On the other hand,
PMON_CONFIG (0xd4) for
On 7/8/20 8:30 PM, Chu Lin wrote:
> On Wed, Jul 8, 2020 at 5:33 PM Guenter Roeck wrote:
>>
>> On 7/8/20 4:53 PM, Chu Lin wrote:
>>> Issue:
>>> When binding adm1272 to the adm1275 driver, PEC error is reported.
>>> See blow:
>>
>> s/blow/below/
>>
>> Also, unless I am missing something, the error
On 07/09/2020 09:17 AM, Randy Dunlap wrote:
> On 7/8/20 7:29 PM, Andrew Morton wrote:
>> The mm-of-the-moment snapshot 2020-07-08-19-28 has been uploaded to
>>
>>http://www.ozlabs.org/~akpm/mmotm/
>>
>> mmotm-readme.txt says
>>
>> README for mm-of-the-moment:
>>
>>
Hi Lukasz,
On 7/9/20 12:34 AM, Lukasz Luba wrote:
> In order to react faster and make better decisions under some workloads,
> benchmarking the memory subsystem behavior, adjust the polling interval
> and upthreshold value used by the simple_ondemand governor.
>
> Reported-by: Willy Wolff
>
From: Tiezhu Yang
Fix the following checkpatch warnings and errors:
ERROR: do not initialise statics to 0
+static int csr_temp_enable = 0;
WARNING: Symbolic permissions 'S_IRUGO' are not preferred. Consider using octal
permissions '0444'.
+static SENSOR_DEVICE_ATTR(name, S_IRUGO,
From: Tiezhu Yang
Once the temperature of any CPUs is too high, it can power off immediately,
no need to check the rest of CPUs, and it is better to print a log before
power off, this is useful when analysis the abnormal issues.
Signed-off-by: Tiezhu Yang
Signed-off-by: Zhi Li
---
Replace hwmon_device_register() with hwmon_device_register_with_info()
to fix the following boot warning :
[9.029924] Loongson Hwmon Enter...
[9.106850] (NULL device *): hwmon_device_register() is deprecated. Please
convert the driver to use hwmon_device_register_with_info().
v2:
- Drop the patch "MIPS: Loongson: Add hwmon support for generic CPU"
- Reduce possible loop times in do_thermal_timer()
v3:
- Fix boot warning about hwmon_device_register()
Tiezhu Yang (2):
MIPS: Loongson: Cleanup cpu_hwmon.c
MIPS: Loongson: Reduce possible loop times and add log
On 7/8/20 7:29 PM, Andrew Morton wrote:
> The mm-of-the-moment snapshot 2020-07-08-19-28 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch
On 07/09/2020 06:44 AM, Tian Tao wrote:
> It is not possible to increase size with vmalloc= in arm64
Small nit. s/in arm64/on arm64/
In fact "vmalloc=" cmdline option is not available on many
platforms. Hence it is not something arm64 specific here, it is
a general problem.
> architecture
On 7/8/2020 10:20 PM, Mark Brown wrote:
On Wed, Jul 08, 2020 at 10:38:13AM +0530, Rohit kumar wrote:
From: Ajit Pandey
We are allocating dma memory for component->dev but trying to mmap
such memory for substream->pcm->card->dev. Replace device argument
in mmap with component->dev to fix
allnoconfig
i386 randconfig-a002-20200708
i386 randconfig-a001-20200708
i386 randconfig-a006-20200708
i386 randconfig-a005-20200708
i386 randconfig-a004-20200708
i386 randconfig-a003-20200708
i386
allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc rhel-kconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a002-20200708
i386
Hi KP,
I love your patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url:
https://github.com/0day-ci/linux/commits/KP-Singh/Generalizing-bpf_local_storage/20200709-085810
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config:
Remove unneeded variable ret i.
Signed-off-by: Xu Wang
---
drivers/md/bcache/writeback.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/md/bcache/writeback.c b/drivers/md/bcache/writeback.c
index 1cf1e5016cb9..71801c086b82 100644
--- a/drivers/md/bcache/writeback.c
+++
On Wed, Jul 8, 2020 at 7:07 PM Jia He wrote:
>
> numa_off is set unconditionally at the end of dummy_numa_init(),
> even with a fake numa node. ACPI detects node id as NUMA_NO_NODE(-1) in
> acpi_map_pxm_to_node() because it regards numa_off as turning off the numa
> node. Hence
Bonjour Chers Lauréat
Nous vous contactons par cette présente lettre pour vous informer que vous
venez de gagner la somme de 680.000€ (Six Cent Quatre Vingt Mille Euros) du
tirage au sort organisé par la Française des Jeux LOTERIE EURO MILLIONS .
Pour la réclamation du gain veuillez entrer
On Wed, Jul 8, 2020 at 5:33 PM Guenter Roeck wrote:
>
> On 7/8/20 4:53 PM, Chu Lin wrote:
> > Issue:
> > When binding adm1272 to the adm1275 driver, PEC error is reported.
> > See blow:
>
> s/blow/below/
>
> Also, unless I am missing something, the error is only seen if PEC is
> enabled.
This is
On 07/06/2020 08:26 AM, Anshuman Khandual wrote:
> This series enables vmemmap backing memory allocation from device memory
> ranges on arm64. But before that, it enables vmemmap_populate_basepages()
> and vmemmap_alloc_block_buf() to accommodate struct vmem_altmap based
> alocation requests.
>
Hi all,
After merging the device-mapper tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from drivers/md/dm-dust.c:11:
drivers/md/dm-dust.c: In function 'dust_list_badblocks':
drivers/md/dm-dust.c:307:10: warning: zero-length gnu_printf format string
2020년 7월 8일 (수) 오후 4:48, Michal Hocko 님이 작성:
>
> On Wed 08-07-20 16:19:17, Joonsoo Kim wrote:
> > On Tue, Jul 07, 2020 at 01:40:19PM +0200, Michal Hocko wrote:
> [...]
> > Subject: [PATCH] mm/migrate: clear __GFP_RECLAIM for THP allocation for
> > migration
> >
> > In migration target allocation
2020년 7월 8일 (수) 오전 1:34, Vlastimil Babka 님이 작성:
>
> On 7/7/20 9:44 AM, js1...@gmail.com wrote:
> > From: Joonsoo Kim
> >
> > To calculate the correct node to migrate the page for hotplug, we need
> > to check node id of the page. Wrapper for alloc_migration_target() exists
> > for this purpose.
>
On 7/8/20 4:26 PM, Matthew Wilcox (Oracle) wrote:
> +void unregister_kiocb_completion(int id)
> +{
> + ki_cmpls[id - 1] = NULL;
> +}
> +EXPORT_SYMBOL(unregister_kiocb_completion);
This should have a limit check (<= 0 || > max).
> void complete_kiocb(struct kiocb *iocb, long ret, long ret2)
Hi all,
Today's linux-next merge of the device-mapper tree got a conflict in:
drivers/md/dm-crypt.c
between commit:
ed00aabd5eb9 ("block: rename generic_make_request to submit_bio_noacct")
from the block tree and commit:
202b8d712016 ("dm crypt: add flags to optionally bypass kcryptd
On 2020/7/9 9:57, Daeho Jeong wrote:
> From: Daeho Jeong
>
> When end_addr comes to zero, it'll trigger different behaviour.
> To prevent this, we need to ignore the case of that range.len is
> zero in the function.
>
> Signed-off-by: Daeho Jeong
> ---
> fs/f2fs/file.c | 7 +++
> 1 file
Hi all,
Today's linux-next merge of the block tree got a conflict in:
fs/buffer.c
between commit:
4f74d15fe408 ("ext4: add inline encryption support")
from the fscrypt tree and commit:
ed9b3196d2b2 ("fs: remove a weird comment in submit_bh_wbc")
from the block tree.
I fixed it up
Use set_current_state macro instead of current->state = TASK_RUNNING.
Signed-off-by: Xu Wang
---
kernel/time/timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index 398e6eadb861..2bf78ecffebe 100644
--- a/kernel/time/timer.c
Hi all,
Today's linux-next merge of the block tree got a conflict in:
fs/btrfs/disk-io.c
between commit:
16e1dd6a777e ("btrfs: preallocate anon block device at first phase of
snapshot creation")
from the btrfs tree and commit:
21cf86614504 ("writeback: remove bdi->congested_fn")
from
From: Robbie Ko
When a migrate page occurs, we first create a migration entry
to replace the original pte, and then go to fallback_migrate_page
to execute a writeout if the migratepage is not supported.
In the writeout, we will clear the dirty bit of the page and use
page_mkclean to clear the
> -Original Message-
> From: Fabio Estevam
> Sent: 2020年7月9日 1:49
> To: Richard Zhu
> Cc: Shawn Guo ; dl-linux-imx ;
> moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
> ; linux-kernel
>
> Subject: Re: [PATCH] ARM: dts: imx6qdl: only enable pcie in the pcie dts
> file
>
> Hi
Hi, Dennis,
Thanks for this patch.
It's better to send another tree for this patch.
Because this tree is only for soc/mediatek.
Please do not forget to add the dependency information.
Bibby
On Tue, 2020-07-07 at 23:45 +0800, Dennis YC Hsieh wrote:
> No need to clear event again since event
The mm-of-the-moment snapshot 2020-07-08-19-28 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hi Kevin,
> From: Tian, Kevin
> Sent: Thursday, July 9, 2020 10:18 AM
>
> > From: Liu, Yi L
> > Sent: Thursday, July 9, 2020 10:08 AM
> >
> > Hi Kevin,
> >
> > > From: Tian, Kevin
> > > Sent: Thursday, July 9, 2020 9:57 AM
> > >
> > > > From: Liu, Yi L
> > > > Sent: Thursday, July 9, 2020
From: Guo Ren
This patch adds support for uprobes on riscv architecture.
Just like kprobe, it support single-step and simulate instructions.
Signed-off-by: Guo Ren
Reviewed-by: Pekka Enberg
Cc: Patrick Stählin
Cc: Masami Hiramatsu
Cc: Palmer Dabbelt
Cc: Björn Töpel
---
From: Guo Ren
This patch adds support for kprobes on ftrace call sites to avoids
much of the overhead with regular kprobes. Try it with simple
steps:
1. Get _do_fork ftrace call site.
Dump of assembler code for function _do_fork:
0xffe00020af64 <+0>: addisp,sp,-128
From: Guo Ren
For linux-5.8-rc1, enable ftrace of riscv will cause boot panic:
[2.388980] Run /sbin/init as init process
[2.529938] init[39]: unhandled signal 4 code 0x1 at 0x003ff449e000
[2.531078] CPU: 0 PID: 39 Comm: init Not tainted 5.8.0-rc1-dirty #13
[2.532719] epc:
From: Guo Ren
This patch enables "kprobe & kretprobe" to work with ftrace
interface. It utilized software breakpoint as single-step
mechanism.
Some instructions which can't be single-step executed must be
simulated in kernel execution slot, such as: branch, jal, auipc,
la ...
Some instructions
From: Patrick Stählin
Needed for kprobes support. Copied and adapted from arm64 code.
Guo Ren fixup pt_regs type for linux-5.8-rc1.
Signed-off-by: Patrick Stählin
Signed-off-by: Guo Ren
Reviewed-by: Pekka Enberg
Reviewed-by: Zong Li
---
arch/riscv/Kconfig | 1 +
From: Guo Ren
Unfortunately, the current code couldn't be compiled:
CC arch/riscv/kernel/patch.o
In file included from ./include/linux/kernel.h:11,
from ./include/linux/list.h:9,
from ./include/linux/preempt.h:11,
from
On 7/2/20 3:46 PM, Sibi Sankar wrote:
> Add OPP tables required to scale DDR/L3 per freq-domain on SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
Hi Sibi,
Bjorn asked me to give this patch a whirl, and I have to say, I like it
but I'm not sure if I'm missing a dependency somewhere...
From: Guo Ren
The patchset includes kprobe/uprobe support and some related fixups.
Patrick provides HAVE_REGS_AND_STACK_ACCESS_API support and some
kprobe's code. The framework of k/uprobe is from csky but also refers
to other arches'. kprobes on ftrace is also supported in the patchset.
There
> From: Liu, Yi L
> Sent: Thursday, July 9, 2020 10:08 AM
>
> Hi Kevin,
>
> > From: Tian, Kevin
> > Sent: Thursday, July 9, 2020 9:57 AM
> >
> > > From: Liu, Yi L
> > > Sent: Thursday, July 9, 2020 8:32 AM
> > >
> > > Hi Alex,
> > >
> > > > Alex Williamson
> > > > Sent: Thursday, July 9,
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
Hi Matthew
> -Original Message-
> From: Matthew Wilcox
> Sent: Thursday, July 9, 2020 10:11 AM
> To: Justin He
> Cc: Catalin Marinas ; Will Deacon
> ; Tony Luck ; Fenghua Yu
> ; Yoshinori Sato ; Rich
> Felker ; Dave Hansen ; Andy
> Lutomirski ; Peter Zijlstra ;
> Thomas Gleixner ; Ingo
1 - 100 of 1556 matches
Mail list logo
