Attention: Friend,
How are you, I am Dr. Philippe Don Siaka, a medical doctor working with Gabriel
Toure Hospital Bamako Mali, please don't be upset by the way i am sending this
message to you without knowing you before, i only trying to render help that
is needed from me by someone who is no
To link KCOV to the kasan-dev@ mailing list.
Signed-off-by: Andrey Konovalov
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d53db30d1365..eec0b687eb08 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9305,6 +9305,15 @@ F: Document
On Sat, Jul 18, 2020 at 10:58:53AM +0800, Macpaul Lin wrote:
> On Sat, 2020-07-18 at 10:45 +0800, Macpaul Lin wrote:
> > From: Eddie Hung
> >
>
> Well, it's strange, I simply replaced the uploader's name to my
> colleague, git send-email pop up this line automatically.
>
> Shouldn't I do that k
Hi!
> commit e7b931bee739e8a77ae216e613d3b99342b6dec0 upstream.
>
> The driver would happily overwrite its write buffer with user data in
> 256 byte increments due to a removed buffer-space sanity check.
> +++ b/drivers/usb/serial/iuu_phoenix.c
> @@ -697,14 +697,16 @@ static int iuu_uart_write(s
Minas Harutyunyan writes:
> Hi Felipe,
>
> On 7/21/2020 1:43 PM, Felipe Balbi wrote:
>> Minas Harutyunyan writes:
>>
>>> On 7/15/2020 1:32 PM, Lee Jones wrote:
The value obtained from GINTSTS2 should be masked with the GINTMSK2
value. Looks like this has been broken since
dwc2_g
On Tue, Jul 21, 2020 at 02:35:09PM +0800, Xiongfeng Wang wrote:
> When I cat some ipmi_watchdog parameters by sysfs, it displays as
> follows. It's better to add a newline for easy reading.
>
> root@(none):/# cat /sys/module/ipmi_watchdog/parameters/action
> resetroot@(none):/# cat /sys/module/ipm
On 2020/07/21 20:09, Maxim Levitsky wrote:
> On Tue, 2020-07-21 at 11:05 +, Damien Le Moal wrote:
>> On 2020/07/21 19:53, Maxim Levitsky wrote:
>>> Kernel block layer has never supported logical block
>>> sizes less that SECTOR_SIZE nor larger that PAGE_SIZE.
>>>
>>> Some drivers have runtime c
On SC7180 the MBA firmware stores the bootup text logs in a 4K segment
at the beginning of the MBA region. Add support to extract the logs
which will be useful to debug mba boot/authentication issues.
Signed-off-by: Sibi Sankar
---
V2:
* Don't dump logs in mba_reclaim path [Bjorn]
* Move has_m
Hi Tudor,
On 07/07/20 05:37PM, tudor.amba...@microchip.com wrote:
> Hi, Pratyush,
>
> On 6/23/20 9:30 PM, Pratyush Yadav wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> > content is safe
> >
> > Double Transfer Rate (DTR) is SPI protocol in which data is
The series adds support for the following modem debug features:
* Modem debug policy which enables coredumps/live debug on secure devices
* MBA text logs extraction on SC7180 SoCs
V2:
* Use request_firmware_direct [Bjorn]
* Use Bjorn's template to show if debug policy is present
* Add size ch
On Fri, Jul 17, 2020 at 11:03 PM Doug Anderson wrote:
>
> Hi,
>
Thanks for the review!
> On Fri, Jul 17, 2020 at 5:02 AM Cheng-Yi Chiang wrote:
> >
> > Add devicetree bindings documentation file for sc7180 sound card.
> >
> > Signed-off-by: Cheng-Yi Chiang
> > ---
> > .../bindings/sound/qcom,
Add modem debug policy support which will enable coredumps and live
debug support when the msadp firmware is present on secure devices.
Signed-off-by: Sibi Sankar
---
v2:
* Use request_firmware_direct [Bjorn]
* Use Bjorn's template to show if debug policy is present
* Add size check to preven
Ravi Bangoria writes:
> On 7/17/20 11:14 AM, Jordan Niethe wrote:
>> On Fri, Jul 17, 2020 at 2:10 PM Ravi Bangoria
>> wrote:
>>>
>>> Add new device-tree feature for 2nd DAWR. If this feature is present,
>>> 2nd DAWR is supported, otherwise not.
>>>
>>> Signed-off-by: Ravi Bangoria
>>> ---
>>>
Hi!
> > > >After some investigations, we concluded the following:
> > > > - the issue does not exist in vanilla v5.8-rc4+
> > > > - [bisecting shows that] the panic on v4.14.186 is caused by the lack
> > > > of v5.6-rc1 commit 987351e1ea7772 ("phy: core: Add consumer device
> > > > link suppor
On 2020/07/21 19:55, Maxim Levitsky wrote:
> Plus some tiny refactoring.
>
> Signed-off-by: Maxim Levitsky
> ---
> drivers/scsi/sr.c | 31 +--
> 1 file changed, 13 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/scsi/sr.c b/drivers/scsi/sr.c
> index 0c4aa4665
Hi Guenter,
Thank you for work on this. Cc'ing Gwendal as he has a deep knowledge of the EC
and their errors.
On 20/7/20 22:22, Guenter Roeck wrote:
> The EC reports a variety of error codes. Most of those, with the exception
> of EC_RES_INVALID_VERSION, are converted to -EPROTO. As result, the a
On Tue, Jul 21, 2020 at 01:15:23PM +0200, Nicolas Saenz Julienne wrote:
> I'm at loss at what could be failing here. Your device should be able
> to address the whole 8GB memory space, which AFAIK is the max available
> on that smartphone family. But maybe the device-tree is lying, who
> knows...
Can you pich the patches up in the nds32 tree for Linus? There are
not short-term dependencies on them.
On 2020/7/21 16:18, Michael S. Tsirkin wrote:
On Tue, Jul 21, 2020 at 03:00:13PM +0800, Shile Zhang wrote:
Use alloc_pages_node() allocate memory for vring queue with proper
NUMA affinity.
Reported-by: kernel test robot
Suggested-by: Jiang Liu
Signed-off-by: Shile Zhang
Do you observe a
Hi!
> On Mon, Jul 20, 2020 at 12:15:22PM +0200, Pavel Machek wrote:
> > This is queued for 4.19.134-stable, reverting 3 patches. But it seems
> > better alternative is available...
> >
> > commit f3e697b7b6f5e2c570226f8f8692fb7db57215ec
> > Author: Sasha Levin
> > Date: Fri Jul 17 12:58:32 202
On Sun, 19 Jul 2020, Joe Lawrence wrote:
> On 7/17/20 2:29 PM, Josh Poimboeuf wrote:
> > Use of the new -flive-patching flag was introduced with the following
> > commit:
> >
> >43bd3a95c98e ("kbuild: use -flive-patching when CONFIG_LIVEPATCH is
> >enabled")
> >
> > This flag has several
On 7/17/20 2:54 PM, Helen Koike wrote:
> From: Hans Verkuil
>
> Those extended buffer ops have several purpose:
> 1/ Fix y2038 issues by converting the timestamp into an u64 counting
>the number of ns elapsed since 1970
> 2/ Unify single/multiplanar handling
> 3/ Add a new start offset fie
On Tue, 2020-07-21 at 11:40 +0200, Matthias Brugger wrote:
>
> On 21/07/2020 04:16, Miles Chen wrote:
> > In previous discussion [1] and [2], we found that it is risky to
> > use max_pfn or totalram_pages to tell if 4GB mode is enabled.
> >
> > Check 4GB mode by reading infracfg register, remove
On 2020/07/21 19:55, Maxim Levitsky wrote:
> Use blk_is_valid_logical_block_size instead of hardcoded list
s/hardcoded list/hardcoded checks./
>
> Signed-off-by: Maxim Levitsky
> ---
> drivers/scsi/sd.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/
On Tue 21-07-20 07:10:14, Qian Cai wrote:
>
>
> > On Jul 21, 2020, at 2:33 AM, Michal Hocko wrote:
> >
> > on a large ppc machine. The very likely cause is a suboptimal
> > configuration when systed-udev spawns way too many workders to bring the
> > system up.
>
> This is strange. The problem
> -Original Message-
> From: Peter Oh
> Sent: Tuesday, July 21, 2020 7:03 AM
> To: Kalle Valo
> Cc: Brian Norris ; Doug Anderson
> ; linux-wireless wirel...@vger.kernel.org>; Rakesh Pillai ; ath10k
> ; LKML
> Subject: Re: [PATCH] ath10k: Add interrupt summary based CE processing
>
>
The driver pretty much uses device managed functions. The only left-over is
the iio_device_register() function, which also requires an action-or-reset
hook to disable the regulator on the remove and error path.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/frequency/ad9523.c | 60 +++
On 2020/07/21 19:55, Maxim Levitsky wrote:
> This replaces manual checking in the driver
>
> Signed-off-by: Maxim Levitsky
> ---
> drivers/nvme/host/core.c | 17 -
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/cor
Set the timeout value as per cfg80211's set_power_mgmt() request. If the
requested value value is left undefined we set it to 2 seconds, the
maximum supported value.
Signed-off-by: Nicolas Saenz Julienne
---
Changes since v1:
- Use min_t()
.../net/wireless/broadcom/brcm80211/brcmfmac/cfg80211
From: Joerg Roedel
Building a kernel for the CSKY architecture with CONFIG_FRAME_POINTER
set requires a gcc supporting the non-upstream '-mbacktrace' option.
Check for the '-mbacktrace' option before enabling CONFIG_FRAMEPOINTER
and fix building CSKY with an upstream gcc compiler.
Signed-off-by:
Cc: Johannes Weiner ; Michal Hocko ;
Vladimir Davydov
Thanks.
---
PROBLEM: cgroup cost too much memory when transfer small files to tmpfs.
keywords: cgroup PERCPU/memory cost too much.
description:
We send small files from node-A to node-B tmpfs /tmp directory using sftp. On
node-B the syst
Excerpts from Peter Zijlstra's message of July 9, 2020 6:31 pm:
> On Wed, Jul 08, 2020 at 07:54:34PM -0400, Waiman Long wrote:
>> On 7/8/20 4:41 AM, Peter Zijlstra wrote:
>> > On Tue, Jul 07, 2020 at 03:57:06PM +1000, Nicholas Piggin wrote:
>> > > Yes, powerpc could certainly get more performance o
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an
issue:
general protection fault in kernfs_find_ns
pvrusb2: Invalid write control endpoint
pvrusb2: Invalid write control endpoint
pvrusb2: Invalid write control endpoint
pvrusb2: Invalid write control endpoint
On Mon, Jul 20, 2020 at 01:44:47PM +0200, Christoph Hellwig wrote:
> dump_inst has a return before actually doing anything, so just drop the
> whole thing.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/nds32/kernel/traps.c | 35 ---
> 1 file changed, 35 deleti
On Mon, Jul 20, 2020 at 01:44:48PM +0200, Christoph Hellwig wrote:
> Use the proper get_kernel_nofault helper to access an unsafe kernel
> pointer without faulting instead of playing with set_fs and get_user.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/nds32/kernel/traps.c | 15 +++
From: Qiwu Huang
Reports the kind of quick charge type based on
different adapter power.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 21 +
drivers/power/supply/power_supply_sysfs.c | 1 +
include/linux/power_supply.h| 10 ++
From: Qiwu Huang
Reports what type of wireless adapter connection is
currently active for the supply.
for example it can show if ADAPTER_PD capable source is attached.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 28 +
drivers/power/supply/pow
From: Qiwu Huang
Interface to control wireless reverse charge.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 14 ++
drivers/power/supply/power_supply_sysfs.c | 1 +
include/linux/power_supply.h| 1 +
3 files changed, 16 insertions(+
From: Qiwu Huang
reports wireless signal strength.
The value show degree of coupling between tx and rx.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 22 +
drivers/power/supply/power_supply_sysfs.c | 1 +
include/linux/power_supply.h
From: Qiwu Huang
This patchset aims to provide power supply properties about wireless/wired
charging.
"quick_charge_type" reports different types of quick charge based on the
charging power;
"tx_adapter" shows" the type of wireless charging adapter;
"signal_strength" shows the coupling level be
On 2020/07/21 19:55, Maxim Levitsky wrote:
> Signed-off-by: Maxim Levitsky
> ---
> drivers/memstick/core/mspro_block.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/memstick/core/mspro_block.c
> b/drivers/memstick/core/mspro_block.c
> index cd6b8d4f23350..86c9eb0aef512
On Fri, 17 Jul 2020, Josh Poimboeuf wrote:
> Use of the new -flive-patching flag was introduced with the following
> commit:
>
> 43bd3a95c98e ("kbuild: use -flive-patching when CONFIG_LIVEPATCH is
> enabled")
>
> This flag has several drawbacks:
>
> - It disables some optimizations, so it ca
On 2020/07/21 19:54, Maxim Levitsky wrote:
> Signed-off-by: Maxim Levitsky
> ---
> drivers/memstick/core/ms_block.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/memstick/core/ms_block.c
> b/drivers/memstick/core/ms_block.c
> index d9ee8e3dc72da..e4df03e10fb46
On 2020/07/21 19:54, Maxim Levitsky wrote:
> This slightly changes the behavier of the driver,
s/behavier/behavior
> when given invalid block size (non power of two, or below 512 bytes),
> but shoudn't matter.
>
> Signed-off-by: Maxim Levitsky
> ---
> drivers/block/null_blk_main.c | 6 +++---
>
Hello Helen,
Just a few drive-by comments.
On Fri, 17 Jul 2020 08:54:29 -0300
Helen Koike wrote:
> Hi,
>
> I'm sorry for taking too long to submit v4.
>
> It is not perfect, not all v4l2-compliance tests passes, but I'd like a
> review,
> specially on the API and potential problems, so I can
On Tue, 2020-07-21 at 14:24 +0530, Amit Pundir wrote:
> On Tue, 21 Jul 2020 at 14:09, Nicolas Saenz Julienne
> wrote:
> > Hi Amit,
> > > Hi Nicolas,
> > >
> > > I see a boot regression with this commit d9765e41d8e9 "dma-pool:
> > > Do not allocate pool memory from CMA" on my Xiaomi Poco F1
> > >
On Mon, Jul 20, 2020 at 04:51:44PM -0700, Andrew Morton wrote:
> On Sun, 19 Jul 2020 14:10:19 -0700 syzbot
> wrote:
>
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit:4c43049f Add linux-next specific files for 20200716
> > git tree: linux-next
> > cons
From: Thomas Gleixner
64bit and 32bit entry code have the same open coded syscall entry handling
after the bitwidth specific bits.
Move it to a helper function and share the code.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c | 93 +--
Replace the x86 variant with the generic version. Provide the relevant
architecture specific helper functions and defines.
Use a temporary define for idtentry_exit_user which will be cleaned up
seperately.
Signed-off-by: Thomas Gleixner
---
V4: Drop a pointless define
Adjust to moved TIF_USE
#syz test: https://github.com/google/kasan.git usb-fuzzer
fix WARNING in pvr2_i2c_core_done by
unregistering device in the release handler
instead of the disconnect handler.
Reported-by: syzbot+e74a998ca8f1df9cc...@syzkaller.appspotmail.com
Signed-off-by: B K Karthik
---
drivers/i2c/i2c-core-ba
From: Thomas Gleixner
Like the syscall entry/exit code interrupt/exception entry after the real
low level ASM bits should not be different accross architectures.
Provide a generic version based on the x86 code.
irqentry_enter() is called after the low level entry code and
irqentry_exit() must b
From: Thomas Gleixner
Entering a guest is similar to exiting to user space. Pending work like
handling signals, rescheduling, task work etc. needs to be handled before
that.
Provide generic infrastructure to avoid duplication of the same handling
code all over the place.
The exit to guest mode
> On Jul 21, 2020, at 2:33 AM, Michal Hocko wrote:
>
> on a large ppc machine. The very likely cause is a suboptimal
> configuration when systed-udev spawns way too many workders to bring the
> system up.
This is strange. The problem description is missing quite a few important
details. For
Like syscall entry all architectures have similar and pointlessly different
code to handle pending work before returning from a syscall to user space.
1) One-time syscall exit work:
- rseq syscall exit
- audit
- syscall tracing
- tracehook (single stepping)
2) Preparat
Replace the syscall entry work handling with the generic version. Provide
the necessary helper inlines to handle the real architecture specific
parts, e.g. ptrace.
Use a temporary define for idtentry_enter_user which will be cleaned up
seperately.
Signed-off-by: Thomas Gleixner
---
V4: Drop the
On Tue, 2020-07-21 at 11:05 +, Damien Le Moal wrote:
> On 2020/07/21 19:53, Maxim Levitsky wrote:
> > Kernel block layer has never supported logical block
> > sizes less that SECTOR_SIZE nor larger that PAGE_SIZE.
> >
> > Some drivers have runtime configurable block size,
> > so it makes sense
Excerpts from Peter Zijlstra's message of July 8, 2020 6:41 pm:
> On Tue, Jul 07, 2020 at 03:57:06PM +1000, Nicholas Piggin wrote:
>> Yes, powerpc could certainly get more performance out of the slow
>> paths, and then there are a few parameters to tune.
>
Sorry for the delay, got bogged down and
Replace the x86 code with the generic variant. Use temporary defines for
idtentry_* which will be cleaned up in the next step.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c | 167
arch/x86/include/asm/idtentry.h | 10 --
2 files ch
Remove the temporary defines and fixup all references.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c |6 +++---
arch/x86/include/asm/idtentry.h | 33 ++---
arch/x86/kernel/kvm.c |6 +++---
arch/x86/kernel/traps.c |6
On 2020/07/21 19:54, Maxim Levitsky wrote:
> This allows to remove nbd's own check for valid block size
>
> Signed-off-by: Maxim Levitsky
> ---
> drivers/block/nbd.c | 12 ++--
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
Cleanup the temporary defines and use irqentry_ instead of idtentry_.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/idtentry.h |4
arch/x86/kernel/cpu/mce/core.c |4 ++--
arch/x86/kernel/traps.c | 18 +-
3 files changed, 11 insertions(+), 15 dele
Use the generic infrastructure to check for and handle pending work before
entering into guest mode.
This now handles TIF_NOTIFY_RESUME as well which was ignored so
far. Handling it is important as this covers task work and task work will
be used to offload the heavy lifting of POSIX CPU timers to
On 2020/07/21 19:54, Maxim Levitsky wrote:
> This allows to remove loop's own check for supported block size
>
> Signed-off-by: Maxim Levitsky
> ---
> drivers/block/loop.c | 23 +--
> 1 file changed, 5 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/block/loop.c b/dr
On syscall entry certain work needs to be done:
- Establish state (lockdep, context tracking, tracing)
- Conditional work (ptrace, seccomp, audit...)
This code is needlessly duplicated and different in all
architectures.
Provide a generic version based on the x86 implementation which has
From: Thomas Gleixner
The user register sanity check is sprinkled all over the place. Move it
into enter_from_user_mode().
Signed-off-by: Thomas Gleixner
Reviewed-by: Kees Cook
---
arch/x86/entry/common.c | 24 +---
1 file changed, 9 insertions(+), 15 deletions(-)
--- a
Guests and user space share certain MSRs. KVM sets these MSRs to guest
values once and does not set them back to user space values on every VM
exit to spare the costly MSR operations.
User return notifiers ensure that these MSRs are set back to the correct
values before returning to user space in
From: Thomas Gleixner
As a preparatory step for moving the syscall and interrupt entry/exit
handling into generic code, provide a pt_regs helper which retrieves the
interrupt state from pt_regs. This is required to check whether interrupts
are reenabled by return from interrupt/exception.
Signed
To avoid #ifdeffery in the upcoming generic syscall entry work code provide
a stub for __secure_computing() as this is preferred over
secure_computing() because the TIF flag is already evaluated.
Signed-off-by: Thomas Gleixner
---
V4: New patch
---
include/linux/seccomp.h |1 +
1 file change
This is the 4rd version of generic entry/exit functionality for host and
guest.
The 3rd version is available here:
https://lore.kernel.org/r/20200716182208.180916...@linutronix.de
Changes vs. V3:
- Drop the architecture wrappers for seccomp and audit (Kees)
- Move the user return notifi
From: Jian Shen
Currently, PF queries the MAC link status per second by calling
function hclge_get_mac_link_status(). It return the error code
when failed to send cmdq command to firmware. It's incorrect,
because this return value is used as the MAC link status, which
0 means link down, and none-
There are some bugfixes for the HNS3 ethernet driver.
Jian Shen (1):
net: hns3: fix return value error when query MAC link status fail
Yunsheng Lin (3):
net: hns3: fix for not unmapping TX buffer correctly
net: hns3: fix for not calculating TX BD send size correctly
net: hns3: fix error h
On 2020/07/21 19:54, Maxim Levitsky wrote:
> Linux kernel only supports logical block sizes which are power of two,
> at least 512 bytes and no more that PAGE_SIZE.
>
> Check this instead of crashing later on.
>
> Note that there is no need to check physical block size since it is
> only a hint,
From: Yunsheng Lin
The content of the TX desc is automatically cleared by the HW
when the HW has sent out the packet to the wire. When desc filling
fails in hns3_nic_net_xmit(), it will call hns3_clear_desc() to do
the error handling, which miss zeroing of the TX desc and the
checking if a unmapp
> On 21 Jul 2020, at 1:14 pm, Jerome Brunet wrote:
>
> On Sun 19 Jul 2020 at 16:10, Christian Hewitt
> wrote:
>
>> HardKernel ODROID-N2+ uses an Amlogic S922X rev. C chip capable of higher
>> clock speeds than the original ODROID-N2. Hardkernel supports the big cpu
>> cluster at 2.4GHz and t
From: Yunsheng Lin
With GRO and fraglist support, the SKB can be aggregated to
a total size of 65535, and when that SKB is forwarded through
a bridge, the size of the SKB may be pushed to exceed the size
of 65535 when br_dev_queue_push_xmit() is called.
The max send size of BD supported by the H
From: Yunsheng Lin
When a big TX buffer is sent using multi BD, the driver maps the
whole TX buffer, and unmaps it using info in desc_cb corresponding
to each BD, but only the info in the desc_cb of first BD is correct,
other info in desc_cb is wrong, which causes TX unmapping problem
when SMMU i
On Tue, Jul 21, 2020 at 12:30PM +0200, Marco Elver wrote:
[...]
> diff --git a/lib/Kconfig.kcsan b/lib/Kconfig.kcsan
> index 3d282d51849b..cde5b62b0a01 100644
> --- a/lib/Kconfig.kcsan
> +++ b/lib/Kconfig.kcsan
> @@ -40,6 +40,11 @@ menuconfig KCSAN
>
> if KCSAN
>
> +# Compiler capabilities tha
On 2020/07/21 19:53, Maxim Levitsky wrote:
> Kernel block layer has never supported logical block
> sizes less that SECTOR_SIZE nor larger that PAGE_SIZE.
>
> Some drivers have runtime configurable block size,
> so it makes sense to have common helper for that.
...common helper to check the valid
Hi all,
Changes since 20200720:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
The net-next tree gained a conflict against the net tree.
The bpf-next tree gained conflicts against the net-next tree.
The security tree still had its build failure for wh
> This is fine as is in all three aspects.
I have tried again to point specific data processing consequences out
for operation modes of scripts in the semantic patch language.
Regards,
Markus
> https://github.com/ereshetova/linux-stable/commits/refcount_t_fs
Looking at "fs, cachefiles: convert cachefiles_object.usage from atomic_t to
refcount_t", I see:
- u = atomic_inc_return(&object->usage);
+ refcount_inc(&object->usage);
trace_cachefiles_ref(object, _object->co
On 17/07/2020 09:50, Anup Patel wrote:
> We add a separate CLINT timer driver for Linux RISC-V M-mode (i.e.
> RISC-V NoMMU kernel).
>
> The CLINT MMIO device provides three things:
> 1. 64bit free running counter register
> 2. 64bit per-CPU time compare registers
> 3. 32bit per-CPU inter-processor
Hi Mike,
On Mon, 20 Jul 2020 at 11:26, Mike Rapoport wrote:
>
> From: Mike Rapoport
>
> Introduce "secretmemfd" system call with the ability to create memory areas
> visible only in the context of the owning process and not mapped not only
> to other processes but in the kernel page tables as we
From: "hongbo.wang"
the following command will be supported:
Add VLAN:
ip link add link swp1 name swp1.100 type vlan protocol 802.1ad id 100
Delete VLAN:
ip link del link swp1 name swp1.100
when adding vlan, this patch only set protocol for user port,
cpu port don't care it, so set param
On 7/21/2020 12:37 PM, Stephen Boyd wrote:
Quoting Stephen Boyd (2020-07-20 22:59:14)
I worry that we also need a dmb() here to make sure the dma buffer is
properly mapped before this write to the device is attempted. But it may
only matter to be before the I2C_READ.
I'm suggesting this patc
ジョブドラフトセミナー運営室より
高校新卒採用の最前線セミナーのご案内です。
〜オンライン座談会〜
就職担当の先生へ直撃質問!!
コロナで変わった、高校現場の“リアル”
▼ 詳細 ▼
https://hr-saiyo.work/200727/
コロナウイルスにより、高校生の就職活動の現場では
企業・生徒・教員それぞれにかつて無いほどの混乱が起きています。
そこでこの度、お互いの認識のズレを解消すべく
現役の就
Hi all,
After merging the akpm-current tree, today's linux-next build
(sparc64 defconfig) failed like this:
mm/hugetlb.c: In function 'free_gigantic_page':
mm/hugetlb.c:1233:18: error: 'hugetlb_cma' undeclared (first use in this
function); did you mean 'hugetlb_lock'?
cma_release(hugetlb_c
Plus some tiny refactoring.
Signed-off-by: Maxim Levitsky
---
drivers/scsi/sr.c | 31 +--
1 file changed, 13 insertions(+), 18 deletions(-)
diff --git a/drivers/scsi/sr.c b/drivers/scsi/sr.c
index 0c4aa4665a2f9..0e96338029310 100644
--- a/drivers/scsi/sr.c
+++ b/driv
Thanks, my comments below.
On Tue, Jul 21, 2020 at 1:41 PM Abanoub Sameh wrote:
Commit message is missed on why you did all these changes.
...
> if (pin <= 255) {
> char ev_name[5];
> +
> sprintf(ev_name, "_%c%02hhX",
> agpio->tr
Use blk_is_valid_logical_block_size instead of hardcoded list
Signed-off-by: Maxim Levitsky
---
drivers/scsi/sd.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index d90fefffe31b7..f012e7397b058 100644
--- a/drivers/scsi/sd.c
+++ b/
Signed-off-by: Maxim Levitsky
---
drivers/memstick/core/mspro_block.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/memstick/core/mspro_block.c
b/drivers/memstick/core/mspro_block.c
index cd6b8d4f23350..86c9eb0aef512 100644
--- a/drivers/memstick/core/mspro_block.c
+++ b/driv
Signed-off-by: Maxim Levitsky
---
drivers/memstick/core/ms_block.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memstick/core/ms_block.c b/drivers/memstick/core/ms_block.c
index d9ee8e3dc72da..e4df03e10fb46 100644
--- a/drivers/memstick/core/ms_block.c
+++ b/drivers
This replaces manual checking in the driver
Signed-off-by: Maxim Levitsky
---
drivers/nvme/host/core.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index add040168e67e..8014b3046992a 100644
--- a/drivers
This allows to remove nbd's own check for valid block size
Signed-off-by: Maxim Levitsky
---
drivers/block/nbd.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index ce7e9f223b20b..2cd9c4e824f8b 100644
--- a/drivers/blo
This slightly changes the behavier of the driver,
when given invalid block size (non power of two, or below 512 bytes),
but shoudn't matter.
Signed-off-by: Maxim Levitsky
---
drivers/block/null_blk_main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/block/nul
Linux kernel only supports logical block sizes which are power of two,
at least 512 bytes and no more that PAGE_SIZE.
Check this instead of crashing later on.
Note that there is no need to check physical block size since it is
only a hint, and virtio-blk already only supports power of two values.
This allows to remove loop's own check for supported block size
Signed-off-by: Maxim Levitsky
---
drivers/block/loop.c | 23 +--
1 file changed, 5 insertions(+), 18 deletions(-)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 475e1a738560d..9984c8f824271 10064
Kernel block layer has never supported logical block
sizes less that SECTOR_SIZE nor larger that PAGE_SIZE.
Some drivers have runtime configurable block size,
so it makes sense to have common helper for that.
Signed-off-by: Maxim Levitsky
---
block/blk-settings.c | 18 ++
inc
This patch series aims to move the logical block size checking to the
block code.
This was inspired by missing check for valid logical block size in
virtio-blk which causes the kernel to crash in a weird way later on
when it is invalid.
I added blk_is_valid_logical_block_size which returns true i
On Mon, Jul 20, 2020 at 05:58:47PM -0300, Daniel Gutson wrote:
> On Fri, Jul 17, 2020 at 11:57 AM Greg Kroah-Hartman <
> gre...@linuxfoundation.org> wrote:
>
> > On Fri, Jul 17, 2020 at 11:46:39AM -0300, Daniel Gutson wrote:
> > > On Fri, Jul 17, 2020 at 11:41 AM Arnd Bergmann wrote:
> > >
> > >
1101 - 1200 of 1486 matches
Mail list logo
