x86_64 randconfig-a004-20200507
x86_64 randconfig-a006-20200507
x86_64 randconfig-a002-20200507
i386 randconfig-a012-20200507
i386 randconfig-a016-20200507
i386 randconfig-a014-20200507
i386
i386 randconfig-a005-20200507
i386 randconfig-a004-20200507
i386 randconfig-a001-20200507
i386 randconfig-a002-20200507
i386 randconfig-a003-20200507
i386 randconfig-a006-20200507
x86_64
Fix sparse warning:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c:2206:5:
warning: symbol 'brcmf_p2p_get_conn_idx' was not declared. Should it be
static?
Reported-by: Hulk Robot
Signed-off-by: Chen Zhou
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c | 2 +-
1 file
On Tue, 05 May 2020 15:41:13 +0200
Thomas Gleixner wrote:
> --- a/arch/x86/kernel/ftrace_64.S
> +++ b/arch/x86/kernel/ftrace_64.S
> @@ -12,7 +12,7 @@
> #include
>
> .code64
> - .section .entry.text, "ax"
> + .section .text, "ax"
>
> #ifdef CONFIG_FRAME_POINTER
> /* Save
On 2020/5/7 21:52, Will Deacon wrote:
> On Thu, May 07, 2020 at 05:28:19PM +0800, Yunfeng Ye wrote:
>> diff --git a/arch/arm64/include/asm/stacktrace.h
>> b/arch/arm64/include/asm/stacktrace.h
>> index fdb913cc0bcb..b92bef2fb6cd 100644
>> --- a/arch/arm64/include/asm/stacktrace.h
>> +++
allnoconfig
i386 randconfig-a005-20200507
i386 randconfig-a004-20200507
i386 randconfig-a001-20200507
i386 randconfig-a002-20200507
i386 randconfig-a003-20200507
i386 randconfig-a006
All right，will fix.
On 2020/5/8 9:00, David Miller wrote:
From: Luo bin
Date: Thu, 7 May 2020 04:32:22 +
+ ulong timeo;
Please fully spell out "unsigned long" for this type.
The same problem exists in your net-next patch submission as well.
Thank you.
.
Hi Mimi,
On Thu, 07 May 2020 20:23:41 -0400 Mimi Zohar wrote:
>
> Sorry for the delay in pushing this and other fixes to the next-
> integrity branch. It's in my next-integrity-testing branch.
OK, thanks.
> This isn't a bug per-se, just annotating the reason for the lack of
> locking.
Yes,
On Tue, 5 May 2020 21:55:35 -0700, Can Guo wrote:
> During system resume, scsi_resume_device() decreases a request queue's
> pm_only counter if the scsi device was quiesced before. But after that,
> if the scsi device's RPM status is RPM_SUSPENDED, the pm_only counter is
> still held (non-zero).
During zstd compression, ZSTD_endStream() may return non-zero value
because distination buffer is full, but there is still compressed data
remained in intermediate buffer, it means that zstd algorithm can not
save at last one block space, let's just writeback raw data instead of
compressed one,
Hi all,
After merging the xfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
fs/xfs/xfs_buf.c: In function 'xfs_buf_bio_end_io':
fs/xfs/xfs_buf.c:1292:20: warning: unused variable 'mp' [-Wunused-variable]
1292 | struct xfs_mount *mp = bp->b_mount;
|
On Thu, May 7, 2020 at 3:16 PM Jim Quinlan wrote:
>
> From: Jim Quinlan
>
> For various reasons, one may want to disable the ASPM L0s
> capability.
>
> Signed-off-by: Jim Quinlan
> ---
> Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml | 2 ++
> 1 file changed, 2 insertions(+)
Hi Jiri,
On 5/7/2020 11:18 PM, Jiri Olsa wrote:
On Thu, May 07, 2020 at 02:58:22PM +0800, Jin Yao wrote:
Currently perf-stat supports to print counts at regular interval (-I),
but it's not very easy for user to get the overall statistics.
The patch uses 'evsel->prev_raw_counts' to get counts
From: Chuhong Yuan
Date: Thu, 7 May 2020 23:13:20 +0800
> This driver calls kthread_run() in probe, but forgets to call
> kthread_stop() in probe failure and remove.
> Add the missed kthread_stop() to fix it.
>
> Signed-off-by: Chuhong Yuan
Applied, thanks.
From: Colin King
Date: Thu, 7 May 2020 15:34:30 +0100
> From: Colin Ian King
>
> The unsigned variable val is being checked for an error by checking
> if it is less than zero. This can never occur because val is unsigned.
> Fix this by making val a plain int.
>
> Addresses-Coverity:
Hi Mike,
You are right.
I did not notice that the macro DMEMIT uses the sz variable.
Thanks.
On 2020/5/7 22:29, Mike Snitzer wrote:
On Thu, May 07 2020 at 8:26am -0400,
Samuel Zou wrote:
This patch fixes below warning reported by coccicheck:
allnoconfig
i386 randconfig-a005-20200507
i386 randconfig-a004-20200507
i386 randconfig-a001-20200507
i386 randconfig-a002-20200507
i386 randconfig-a003-20200507
i386 randconfig-a006-20200507
i386
On 2020-05-04 07:20, huob...@gmail.com wrote:
> From: Bean Huo
>
> Add HPB related parameters introduced in Unit Descriptor and
> Geometry Descriptor.
>
> Signed-off-by: Bean Huo
> ---
> drivers/scsi/ufs/ufs.h | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git
On 2020-05-04 07:20, huob...@gmail.com wrote:
> From: Bean Huo
>
> Make a copy of bUFSFeaturesSupport, name it ufs_features, add it
> to structure ufs_dev_info.
>
> Signed-off-by: Bean Huo
> ---
> drivers/scsi/ufs/ufs.h| 2 ++
> drivers/scsi/ufs/ufshcd.c | 2 ++
> 2 files changed, 4
From: Luo bin
Date: Thu, 7 May 2020 04:32:22 +
> + ulong timeo;
Please fully spell out "unsigned long" for this type.
The same problem exists in your net-next patch submission as well.
Thank you.
On 2020-05-04 07:20, huob...@gmail.com wrote:
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index 698e8d20b4ba..de13d2333f1f 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -6627,6 +6627,17 @@ static int ufs_get_device_desc(struct ufs_hba
Hi Kishon,
On Thu, May 07, 2020 at 10:14:45AM +0530, Kishon Vijay Abraham I wrote:
> On 4/2/2020 3:40 AM, Laurent Pinchart wrote:
> > From: Anurag Kumar Vulisha
> >
> > Xilinx ZynqMP SoCs have a Gigabit Transceiver with four lanes. All the
> > high speed peripherals such as USB, SATA, PCIE,
From: Grygorii Strashko
Date: Wed, 6 May 2020 21:13:58 +0300
> This series is follow update for TI A65x/J721E Common platform time sync
> (CPTS)
> driver [1] to implement DT bindings review comments from
> Rob Herring [2].
> - "reg" and "compatible" properties are made required for CPTS DT
/trace_hwlat.c:40:
include/linux/kthread.h:60:7: note: previous declaration of 'kthread_fn' was
here
60 | void *kthread_fn(struct task_struct *k);
| ^~
Caused by commit
7df082e85764 ("kthread: save thread function")
I have used the nfsd tree from next-20200507
On Thu, May 7, 2020 at 2:44 PM Guoqing Jiang
wrote:
>
> After introduce attach/detach_page_private in pagemap.h, we can remove
> the duplicat code and call the new functions.
>
> Cc: Song Liu
> Cc: linux-r...@vger.kernel.org
> Signed-off-by: Guoqing Jiang
Acked-by: Song Liu
All
On 5/7/20 4:47 PM, Dan Murphy wrote:
Fix build issue when CONFIG_TI_CPTS is defined in the defconfig but
CONFIG_TI_CPTS_MOD is not set.
I see this already has a pending patch to fix this so unless this
solution is better I will drop the patch
On Wed, Apr 29, 2020 at 8:30 AM Sean Christopherson
wrote:
>
> On Sun, Apr 26, 2020 at 11:57:53AM -0500, Dr. Greg wrote:
> > In closing, it is important to note that the proposed SGX driver is
> > not available as a module. This effectively excludes any alternative
> > implementations of the
From: Ioana Ciornei
Date: Tue, 5 May 2020 23:14:29 +0300
> Mask the consumer index before using it. Without this, we would be
> writing frame descriptors beyond the ring size supported by the QBMAN
> block.
>
> Fixes: 3b2abda7d28c ("soc: fsl: dpio: Replace QMAN array mode with ring mode
>
On Tue, 05 May 2020 15:16:34 +0200
Thomas Gleixner wrote:
> From: Peter Zijlstra
>
> SuperH is the last remaining user of arch_ftrace_nmi_{enter,exit}(),
> remove it from the generic code and into the SuperH code.
>
> Signed-off-by: Peter Zijlstra (Intel)
> Signed-off-by: Thomas Gleixner
>
Add Broadcom VK driver offload engine.
This driver interfaces to the VK PCIe offload engine to perform
should offload functions as video transcoding on multiple streams
in parallel. VK device is booted from files loaded using
request_firmware_into_buf mechanism. After booted card status is
Add maintainer entry for new Broadcom VK Driver
Signed-off-by: Scott Branden
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 88bf36ab2b22..63eec54250f0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3612,6 +3612,13 @@ L:
From: Arnd Bergmann
Date: Tue, 5 May 2020 19:22:14 +0200
> clang points out that building without IPv6 would lead to returning
> an uninitialized variable if a packet with family!=AF_INET is
> passed into bareudp_udp_encap_recv():
>
> drivers/net/bareudp.c:139:6: error: variable 'err' is used
> On May 7, 2020, at 7:36 PM, Rafael Aquini wrote:
>
> On Thu, May 07, 2020 at 07:07:20PM -0400, Qian Cai wrote:
>>
>>
>>> On May 7, 2020, at 6:15 PM, Rafael Aquini wrote:
>>>
>>> It's a reasonable and self-contained feature that we have a valid use for.
>>> I honestly fail to see it
Add additional hooks to test_firmware to pass in support
for partial file read using request_firmware_into_buf.
buf_size: size of buffer to request firmware into
partial: indicates that a partial file request is being made
file_offset: to indicate offset into file to request
Signed-off-by: Scott
Add user space api for bcm-vk driver.
Signed-off-by: Scott Branden
---
include/uapi/linux/misc/bcm_vk.h | 99
1 file changed, 99 insertions(+)
create mode 100644 include/uapi/linux/misc/bcm_vk.h
diff --git a/include/uapi/linux/misc/bcm_vk.h
Add firmware tests for partial file reads of request_firmware_into_buf.
Signed-off-by: Scott Branden
---
.../selftests/firmware/fw_filesystem.sh | 80 +++
1 file changed, 80 insertions(+)
diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh
Please consider this version series ready for upstream acceptance.
This patch series adds partial read support in request_firmware_into_buf.
In order to accept the enhanced API it has been requested that kernel
selftests and upstreamed driver utilize the API enhancement and so
are included in
Add offset to request_firmware_into_buf to allow for portions
of firmware file to be read into a buffer. Necessary where firmware
needs to be loaded in portions from file in memory constrained systems.
Signed-off-by: Scott Branden
---
drivers/base/firmware_loader/firmware.h | 5 +++
Add kernel_pread_file* support to kernel to allow for partial read
of files with an offset into the file. Existing kernel_read_file
functions call new kernel_pread_file functions with offset=0 and
flags=KERNEL_PREAD_FLAG_WHOLE.
Signed-off-by: Scott Branden
---
fs/exec.c | 96
On Thu, May 07, 2020 at 05:35:31PM -0500, Haitao Huang wrote:
> On Thu, 07 May 2020 14:34:59 -0500, Sean Christopherson
> wrote:
>
> >On Thu, May 07, 2020 at 12:49:15PM -0400, Nathaniel McCallum wrote:
> >>> For larger size mmap, I think it requires enabling vm overcommit mode
> >>1:
> >>> echo
On Fri, May 08, 2020 at 01:05:09AM +0100, Al Viro wrote:
> On Thu, May 07, 2020 at 05:57:09PM -0600, Shuah Khan wrote:
> > Fix ksys_sync_file_range() to avoid fdput() after a failed fdget().
> > fdput() doesn't do fput() on this file since FDPUT_FPUT isn't set
> > in fd.flags. Fix it anyway since
On Tue, 05 May 2020 15:16:26 +0200
Thomas Gleixner wrote:
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -3639,9 +3639,6 @@ static void __trace_hardirqs_on_caller(u
> {
> struct task_struct *curr = current;
>
> - /* we'll do an OFF -> ON transition: */
> -
Hi Stephen,
On Fri, 2020-05-08 at 10:14 +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 30 Apr 2020 21:32:05 +0530 madhuparnabhowmi...@gmail.com wrote:
> >
> > From: Madhuparna Bhowmik
> >
> > This patch fixes the following warning and few other
> > instances of traversal of
Hi all,
On Thu, 30 Apr 2020 21:32:05 +0530 madhuparnabhowmi...@gmail.com wrote:
>
> From: Madhuparna Bhowmik
>
> This patch fixes the following warning and few other
> instances of traversal of evm_config_xattrnames list:
>
> [ 32.848432] =
> [ 32.848707]
, May 7, 2020 at 11:26 AM syzbot
> > > wrote:
> > >>
> > >> =====
> > >> WARNING: suspicious RCU usage
> > >> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted
> > >> -
> > >> security/integ
On Thu, May 07, 2020 at 11:34:47AM -0700, Divya Indi wrote:
> This patch fixes commit -
> commit 3ebd2fd0d011 ("IB/sa: Put netlink request into the request list before
> sending")'
>
> Above commit adds the query to the request list before ib_nl_snd_msg.
>
> However, if there is a delay in
On Wed, 6 May 2020 10:18:24 +0800 Walter Wu wrote:
> On Wed, 2020-04-22 at 18:21 -0700, Bart Van Assche wrote:
> > On 4/20/20 6:35 PM, Walter Wu wrote:
> > > Modify the variable type of 'skip' member of struct stack_trace.
> > > In theory, the 'skip' variable type should be unsigned int.
> > >
On Thu, May 07, 2020 at 05:57:09PM -0600, Shuah Khan wrote:
> Fix ksys_sync_file_range() to avoid fdput() after a failed fdget().
> fdput() doesn't do fput() on this file since FDPUT_FPUT isn't set
> in fd.flags. Fix it anyway since failed fdget() doesn't require
> a fdput().
>
> This was
On Thu, May 07, 2020 at 04:16:10PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The variable rcqe_sz is being unnecessarily assigned twice, fix this
> by removing one of the duplicates.
>
> Addresses-Coverity: ("Evaluation order violation")
> Signed-off-by: Colin Ian King
> Acked-by:
On Wed, 6 May 2020 09:25:54 +0300 Vasily Averin wrote:
> new_pos should jump through hole of unused ids,
> pos can be updated inside "for" cycle.
>
> Cc: sta...@vger.kernel.org
> Fixes: 89163f93c6f9 ("ipc/util.c: sysvipc_find_ipc() should increase position
> index")
This:
> --- a/ipc/util.c
Fix kernel_read_file_from_fd() to avoid fdput() after a failed fdget().
fdput() doesn't do fput() on this file since FDPUT_FPUT isn't set
in fd.flags. Fix it anyway since failed fdget() doesn't require
a fdput().
This was introduced in a commit that added kernel_read_file_from_fd() as
a wrapper
While debugging an unrelated problem that got me down the path of
reviewing at all the fdget() and fdput() paths in the kernel.
While doing the review, I noticed these two places where fdput()
is called after failed fdget(). Fixing them in these two patches.
Shuah Khan (2):
fs: avoid fdput()
On Thu, May 07, 2020 at 06:22:23PM -0400, Peter Xu wrote:
> On Thu, May 07, 2020 at 04:03:34PM -0600, Alex Williamson wrote:
> > On Thu, 7 May 2020 17:47:44 -0400
> > Peter Xu wrote:
> >
> > > Hi, Alex,
> > >
> > > On Tue, May 05, 2020 at 03:54:53PM -0600, Alex Williamson wrote:
> > > > +/*
> >
On Thu, 7 May 2020 16:50:53 -0400
Steven Rostedt wrote:
> On Thu, 7 May 2020 21:30:08 +0200
> Julia Lawall wrote:
>
> > Elsewhere in the file, the function trace_kprobe_has_same_kprobe uses
> > a trace_probe_event.probes object as the second argument of
> > list_for_each_entry, ie as a list
Fix ksys_sync_file_range() to avoid fdput() after a failed fdget().
fdput() doesn't do fput() on this file since FDPUT_FPUT isn't set
in fd.flags. Fix it anyway since failed fdget() doesn't require
a fdput().
This was introdcued in a commit to add sync_file_range() helper.
Fixes: 22f96b3808c1
Recently a performance problem was reported for a process invoking a
non-trival ASL program. The method call in this case ends up
repetitively triggering a call path like:
acpi_ex_store
acpi_ex_store_object_to_node
acpi_ex_write_data_to_field
acpi_ex_insert_into_field
allnoconfig
i386 randconfig-a005-20200507
i386 randconfig-a004-20200507
i386 randconfig-a001-20200507
i386 randconfig-a002-20200507
i386 randconfig-a003-20200507
i386 randconfig-a006-20200507
i386
On Thu, May 07, 2020 at 05:24:43PM -0400, Peter Xu wrote:
> On Tue, May 05, 2020 at 03:54:44PM -0600, Alex Williamson wrote:
> > With conversion to follow_pfn(), DMA mapping a PFNMAP range depends on
> > the range being faulted into the vma. Add support to manually provide
> > that, in the same
Hi Avri,
On Mon, 2020-05-04 at 22:33 +0800, Stanley Chu wrote:
> Hi Avri,
>
> On Mon, 2020-05-04 at 10:37 +, Avri Altman wrote:
> > >
> > > static void ufshcd_wb_probe(struct ufs_hba *hba, u8 *desc_buf)
> > > {
> > > + if (!ufshcd_is_wb_allowed(hba))
> > > + return;
> >
Wei Yang writes:
> On Wed, May 06, 2020 at 04:22:54PM +0800, Huang, Ying wrote:
>>Wei Yang writes:
>>
>>> On Fri, May 01, 2020 at 03:48:53PM -0700, Andrew Morton wrote:
On Fri, 1 May 2020 01:52:59 + Wei Yang
wrote:
> When the condition is true, there are two
On Wed, 6 May 2020 14:21:28 +0800 Tan Hu wrote:
> If the given type has fraction smaller than max_frac/FPROP_FRAC_BASE,
> __fprop_inc_percpu_max should follow the design formula and aging
> fraction too.
>
> Signed-off-by: Tan Hu
> ---
> lib/flex_proportions.c | 7 +++
> 1 file changed, 3
Please pull this fix from KP Singh (several folks are reporting issues
around this):
The following changes since commit c45e8bccecaf633480d378daff11e122dfd5e96d:
Merge tag 'for-5.7/dm-fixes-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
(2020-04-30 16:45:08
On Tue, 05 May 2020 15:16:09 +0200
Thomas Gleixner wrote:
> Currently instrumentation of atomic primitives is done at the
> architecture level, while composites or fallbacks are provided at the
> generic level.
>
> The result is that there are no uninstrumented variants of the
> fallbacks.
Modern device tree bindings are supposed to be created as YAML-files
in accordance with dt-schema. This commit replaces SYSCON reboot-mode
legacy bare text bindings with YAML file. As before the bindings file
states that the corresponding dts node is supposed to be compatible
"syscon-reboot-mode"
Since normally syscon-reboot block is supposed to be a part of a system
controller, lets look for the syscon regmap in a parental DT node if
regmap property isn't specified. DT binding from now considers the regmap
property as deprecated.
Signed-off-by: Serge Semin
Cc: Alexey Malahov
Cc: Thomas
Hi Paul,
On 5/7/20 10:25 PM, Paul Kocialkowski wrote:
> Hi,
>
> On Fri 01 May 20, 00:05, Johan Jonker wrote:
>> Hi Paul,
>>
>>> The PX30 features a RGA block: add the necessary node to support it.
>>>
>>> Signed-off-by: Paul Kocialkowski
>>> ---
>>> arch/arm64/boot/dts/rockchip/px30.dtsi | 11
Since normally syscon-reboot block is supposed to be a part of a system
controller, lets mark the regmap property as deprecated and recommend the
syscon-reboot node to be a sub-node of SYSCON.
Signed-off-by: Serge Semin
Cc: Alexey Malahov
Cc: Thomas Bogendoerfer
Cc: Paul Burton
Cc: Ralf
This is a small patchset about tuning the syscon infrastructure a bit.
As it's going to be general in the framework of the Baikal-T1 SoC support
integration into the kernel, we suggest to replace the legacy text-based
syscon-reboot-mode dts-bindings file with yaml-based one. Then seeing a
syscon
On Thu, May 07, 2020 at 07:07:20PM -0400, Qian Cai wrote:
>
>
> > On May 7, 2020, at 6:15 PM, Rafael Aquini wrote:
> >
> > It's a reasonable and self-contained feature that we have a valid use for.
> > I honestly fail to see it causing that amount of annoyance as you are
> > suggesting here.
On Thu, May 07, 2020 at 05:03:17PM -0600, Jens Axboe wrote:
> On 5/7/20 4:44 PM, Al Viro wrote:
> > On Thu, May 07, 2020 at 04:25:24PM -0600, Jens Axboe wrote:
> >
> >> static int io_close(struct io_kiocb *req, bool force_nonblock)
> >> {
> >> + struct files_struct *files = current->files;
>
On Wed, May 06, 2020 at 04:07:25PM +0200, Arnd Bergmann wrote:
> Hi,
>
> During randconfig testing with clang-10 I came across a number
> of additional objtool warnings, I'll send another mail about those
> when I have collected more information and some object files.
>
> This one sticks out
allnoconfig
x86_64 randconfig-a004-20200507
x86_64 randconfig-a006-20200507
x86_64 randconfig-a002-20200507
i386 randconfig-a005-20200507
i386 randconfig-a004-20200507
i386 randconfig-a001
owing crash on:
> >>
> >> HEAD commit:6b43f715 Add linux-next specific files for 20200507
> >> git tree: linux-next
> >> console output: https://syzkaller.appspot.com/x/log.txt?x=16f6437010
> >> kernel config: https://syzkal
randconfig-a005-20200507
i386 randconfig-a004-20200507
i386 randconfig-a001-20200507
i386 randconfig-a002-20200507
i386 randconfig-a003-20200507
i386 randconfig-a006-20200507
x86_64 randconfig-a015
Hi,
On Tue, Mar 3, 2020 at 12:52 PM Doug Anderson wrote:
>
> Hi,
>
> On Thu, Feb 13, 2020 at 7:06 AM Daniel Thompson
> wrote:
> >
> > Currently the code to manage the kdb history buffer uses strncpy() to
> > copy strings to/and from the history and exhibits the classic "but
> > nobody ever told
Hello!
This pull request contains KCSAN updates for v5.8. These have been
subject to LKML review:
https://lore.kernel.org/lkml/20200415183343.GA12265@paulmck-ThinkPad-P72
https://lore.kernel.org/lkml/20200417025837.49780-1-weiyongj...@huawei.com
On Thu, May 7, 2020 at 2:25 AM Andy Shevchenko
wrote:
>
> On Thu, May 7, 2020 at 3:21 AM Dan Williams wrote:
> >
> > Recently a performance problem was reported for a process invoking a
> > non-trival ASL program. The method call in this case ends up
> > repetitively triggering a call path like:
>From code inspection the math in handle_ctrl_cmd() looks super sketchy
because it subjects -1 from cmdptr and then does a "%
KDB_CMD_HISTORY_COUNT". It turns out that this code works because
"cmdptr" is unsigned and KDB_CMD_HISTORY_COUNT is a nice power of 2.
Let's make this a little less
Aside from PCIe/SATA/DDR/I2C/CPU-reboot specific settings the Baikal-T1
system controller provides a MIPS P5600 CM2 L2-cache tuning block.
It is responsible for the setting up the Tag/Data/WS L2-to-RAM latencies.
This small patchset provides a driver and DT-schema-based binding for the
described
Baikal-T1 SoC provides a way to tune the MIPS P5600 CM2 L2-cache
performance up. It can be done by changing the L2-RAM Data/Tag/WS
latencies in a dedicated register exposed by the system controller.
The driver added by this commit provides a dts properties-based and
sysfs-based interface for it.
There is a single register provided by the SoC system controller,
which can be used to tune the L2-cache RAM up. It only provides a way
to change the L2-RAM access latencies. So aside from "be,bt1-l2-ctl"
compatible string the device node can be optionally equipped with the
properties of
> On May 7, 2020, at 6:15 PM, Rafael Aquini wrote:
>
> It's a reasonable and self-contained feature that we have a valid use for.
> I honestly fail to see it causing that amount of annoyance as you are
> suggesting here.
It is not a big trouble yet, but keeping an obsolete patch that not
On Thu, 7 May 2020 18:46:24 -0300 "Guilherme G. Piccoli"
wrote:
> After a recent change introduced by Vlastimil's series [0], kernel is
> able now to handle sysctl parameters on kernel command line; also, the
> series introduced a simple infrastructure to convert legacy boot
> parameters (that
On Thu, 7 May 2020 18:59:46 -0300 "Guilherme G. Piccoli"
wrote:
> Currently we have no way to determine if compaction was triggered
> by sysctl write, but this is an interesting information to have,
> specially in systems with high uptime that presents lots of
> fragmented memory. There's no
On 5/7/20 4:44 PM, Al Viro wrote:
> On Thu, May 07, 2020 at 04:25:24PM -0600, Jens Axboe wrote:
>
>> static int io_close(struct io_kiocb *req, bool force_nonblock)
>> {
>> +struct files_struct *files = current->files;
>> int ret;
>>
>> req->close.put_file = NULL;
>> -ret =
Hi Paul,
With help of enum each additional compatibility string with fall back
'rockchip,rk3288-rga' adds only 1 extra line instead of 3.
See my and Heiko's response at the review of 'rockchip-saradc.yaml'.
Re: [PATCH v1 1/3] dt-bindings: iio: adc: convert rockchip saradc
bindings to yaml
The pull request you sent on Thu, 7 May 2020 12:23:39 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-5.7-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9ecc4d775f61fb3fd26a1b8cc70a56a98b3b40d3
Thank you!
--
The pull request you sent on Thu, 7 May 2020 14:33:53 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.7-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/192ffb7515839b1cc8457e0a8c1e09783de019d3
Thank you!
--
On Thu, May 07, 2020 at 01:04:14PM -0600, Shuah Khan wrote:
> >
> > diff --git a/tools/testing/selftests/nsfs/pidns.c
> > b/tools/testing/selftests/nsfs/pidns.c
> > index e0d86e1668c0..e3c772c6a7c7 100644
> > --- a/tools/testing/selftests/nsfs/pidns.c
> > +++
On Thu, 7 May 2020 19:03:44 +0200 Bartosz Golaszewski wrote:
>> To implement Edwin's suggestion? Makes sense, but I'm no expert, let's
>> also CC Heiner since he was asking about it last time.
>
> Yes, because taking the last bit of priv_flags from net_device seems
> to be more controversial
At times when I'm using kgdb I see a splat on my console about
suspicious RCU usage. I managed to come up with a case that could
reproduce this that looked like this:
WARNING: suspicious RCU usage
5.7.0-rc4+ #609 Not tainted
-
kernel/pid.c:395
Hi all,
In commit
0f84d0247722 ("ARM: dts: am437x: fix networking on boards with ksz9031 phy")
Fixes tag
Fixes: commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support for the
KSZ9031 PHY")
has these problem(s):
- leading word 'commit' unexpected
In commit
3a78c16f67a0 ("ARM:
From: Ira Weiny
Most architectures define kmap_prot to be PAGE_KERNEL.
Let sparc and xtensa define there own and define PAGE_KERNEL as the
default if not overridden.
Suggested-by: Christoph Hellwig
Signed-off-by: Ira Weiny
---
Changes from V3:
Fix semicolon in macro
Changes from
On Thu, May 07, 2020 at 01:53:07PM -0700, Andrew Morton wrote:
> On Thu, 7 May 2020 08:00:03 -0700 ira.we...@intel.com wrote:
>
> > From: Ira Weiny
> >
> > Most architectures define kmap_prot to be PAGE_KERNEL.
> >
> > Let sparc and xtensa define there own and define PAGE_KERNEL as the
> >
On Wed, May 06, 2020 at 12:23:29PM -0700, Jakub Kicinski wrote:
> Please trim your replies.
>
> Off-topic.
>
> Is there any simple way to trim replies semi-automatically in VIM?
>
> Right now, I'm doing it manually, but maybe there is some better
> way to do it.
I'm also doing it manually :(
On Thu, May 07, 2020 at 01:52:58PM -0700, Andrew Morton wrote:
> On Thu, 7 May 2020 08:00:01 -0700 ira.we...@intel.com wrote:
>
> > parisc reimplements the kmap calls except to flush it's dcache. This is
> > arguably an abuse of kmap but regardless it is messy and confusing.
> >
> > Remove the
GCC 10 appears to have changed -O2 in order to make compilation time
faster when using -flto, seemingly at the expense of performance, in
particular with regards to how the inliner works. Since -O3 these days
shouldn't have the same set of bugs as 10 years ago, this commit
defaults new kernel
On Thu, May 07, 2020 at 05:58:13PM -0400, Richard Guy Briggs wrote:
> On 2020-05-07 13:50, Gustavo A. R. Silva wrote:
> > The current codebase makes use of the zero-length array language
> > extension to the C90 standard, but the preferred mechanism to declare
> > variable-length types such as
On 2020-05-07 20:53, Gustavo A. R. Silva wrote:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
> introduced in C99:
>
> struct
On Thu, May 07, 2020 at 04:25:24PM -0600, Jens Axboe wrote:
> static int io_close(struct io_kiocb *req, bool force_nonblock)
> {
> + struct files_struct *files = current->files;
> int ret;
>
> req->close.put_file = NULL;
> - ret = __close_fd_get_file(req->close.fd,
201 - 300 of 1840 matches
Mail list logo
