On Wed, Jun 03, 2020 at 03:21:47PM +0200, Andrew Lunn wrote:
> On Tue, Jun 02, 2020 at 11:50:17PM +0100, Russell King - ARM Linux admin
> wrote:
> > On Fri, May 29, 2020 at 06:33:40PM +0200, Andrew Lunn wrote:
> > > Given the current code, you cannot. Now we understand the
> > > requirements, we
On Wed, 3 Jun 2020 at 12:10, Mel Gorman wrote:
>
> On Wed, Jun 03, 2020 at 10:29:22AM +0200, Patrick Bellasi wrote:
> >
> > Hi Dietmar,
> > thanks for sharing these numbers.
> >
> > On Tue, Jun 02, 2020 at 18:46:00 +0200, Dietmar Eggemann
> > wrote...
> >
> > [...]
> >
> > > I ran these tests
On 03.06.2020 16:33, Lukas Straub wrote:
> On Mon, 29 Apr 2019 18:16:51 +0200
> "Maciej S. Szmigiero" wrote:
>
>> This series adds support for analog part of Medion 95700 in the cxusb
>> driver.
>>
(..)
> Hi,
> Any status on this?
It has been merged already a year ago.
> Regards,
> Lukas
IORING_SETUP_IOPOLL is defined only for read/write, other opcodes should
be disallowed, otherwise it'll get an error as below. Also refuse
open/cloes with SQPOLL, as the polling thread wouldn't know which file
table to use.
RIP: 0010:io_iopoll_getevents+0x111/0x5a0
Call Trace:
?
The first one adds checks {SQPOLL,IOPOLL}. IOPOLL check can be
moved in the common path later, or rethinked entirely, e.g.
not io_iopoll_req_issued()'ed for unsupported opcodes.
3 others are just cleanups on top.
v2: add IOPOLL to the whole bunch of opcodes in [1/4].
dirty and effective.
Fail recv/send in case of IORING_SETUP_IOPOLL earlier during prep,
so it'd be done only once. Removes duplication as well
Signed-off-by: Pavel Begunkov
---
fs/io_uring.c | 18 ++
1 file changed, 6 insertions(+), 12 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index
Hi Reinette,
> -Original Message-
> From: Reinette Chatre
> Sent: Tuesday, June 2, 2020 6:28 PM
> To: Moger, Babu ; fenghua...@intel.com;
> t...@linutronix.de; mi...@redhat.com; b...@alien8.de; x...@kernel.org;
> h...@zytor.com; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH]
io_openat_prep() and io_openat2_prep() are identical except for how
struct open_how is built. Deduplicate it with a helper.
Signed-off-by: Pavel Begunkov
---
fs/io_uring.c | 55 ++-
1 file changed, 19 insertions(+), 36 deletions(-)
diff --git
build_open_how() is just adjusting open_flags/mode. Do it once during
prep. It looks better than storing raw values for the future.
Signed-off-by: Pavel Begunkov
---
fs/io_uring.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
On 03/06/2020 11:42, Jon Hunter wrote:
>
> On 02/06/2020 19:13, 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
Linus,
please pull the latest x86/timers branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-timers-2020-06-03
up to: bd35c77e32e4: x86/tsc: Add tsc_early_khz command line parameter
X86 timer specific updates:
- Add TPAUSE based delay which allows the CPU to
On 03/06/2020 15:45, Dan Carpenter wrote:
> On Wed, Jun 03, 2020 at 03:18:46PM +0100, Colin Ian King wrote:
>> On 03/06/2020 15:09, Dan Carpenter wrote:
>>> On Wed, Jun 03, 2020 at 02:51:02PM +0100, Colin King wrote:
From: Colin Ian King
The variable error is being initialized with
Hi,
On Wed, 2020-06-03 at 17:42 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (htmldocs)
> failed like this:
>
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage:
>
Hi,
we need to decide how to continue with the lan743x patch for fixed phy support.
Thanks everyone for the valuable time.
Summary of the development steps so far:
The patch initially had low influence on the installed base, but lacked some
compatibility to Linux best practices. During the
This patch prevents the following oops:
[ 10.771813] BUG: kernel NULL pointer dereference, address: 0
[...]
[ 10.779790] RIP: 0010:ima_match_policy+0xf7/0xb80
[...]
[ 10.798576] Call Trace:
[ 10.798993] ? ima_lsm_policy_change+0x2b0/0x2b0
[ 10.799753] ?
Fix the SCS debug usage check so that we report the number of bytes
usedm, rather than the number of entries.
Fixes: 5bbaf9d1fcb9 ("scs: Add support for stack usage debugging")
Reported-by: Sami Tolvanen
Signed-off-by: Will Deacon
---
kernel/scs.c | 2 +-
1 file changed, 1 insertion(+), 1
If the template field 'd' is chosen and the digest to be added to the
measurement entry was not calculated with SHA1 or MD5, it is
recalculated with SHA1, by using the passed file descriptor. However, this
cannot be done for boot_aggregate, because there is no file descriptor.
This patch adds a
Not sure how this strange cv subject got copy-pasted, but
hopefully it's clear what it does from the description.
On 03/06/2020 18:03, Pavel Begunkov wrote:
> The first one adds checks {SQPOLL,IOPOLL}. IOPOLL check can be
> moved in the common path later, or rethinked entirely, e.g.
> not
On 2020-06-02 19:47, Saidi, Ali wrote:
[...]
Looks like the x86 apic set_affinity call explicitly checks for if
it’s activated in the managed case which makes sense given the code
Ben posted above:
/*
* Core code can call here for inactive interrupts. For
inactive
On Tue, May 19, 2020 at 09:58:18AM -0400, Brian Gerst wrote:
> On Tue, Apr 28, 2020 at 11:28 AM Joerg Roedel wrote:
> The proper fix would be to initialize MSR_GS_BASE earlier.
That'll mean to initialize it two times during boot, as the first C
function with stack-protection is called before
On Tue, May 19, 2020 at 11:15:26AM +0200, Borislav Petkov wrote:
> On Tue, Apr 28, 2020 at 05:16:45PM +0200, Joerg Roedel wrote:
> > From: Joerg Roedel
> >
> > The code inserted by the stack protector does not work in the early
> > boot environment because it uses the GS segment, at least with
On Wed, Jun 3, 2020 at 8:12 AM Greg KH wrote:
>
> 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
From: Colin Ian King
Currently the assignment of -ENOMEM to error is redudant because error
is not being read and -ENOMEM is being hard coded as an error return.
Fix this by returning the error code in variable 'error'; this also
allows the error code from a failed call to input_register_device
This fixes the Sphinx parallel build error when building htmldocs:
docutils.utils.SystemMessage:
/home/sfr/next/next/Documentation/trace/histogram-design.rst:219: (SEVERE/4)
Unexpected section title.
It also fixes a bunch of other warnings I noticed when fixing the
above, caused by mixing
On Wed, 3 Jun 2020 17:42:53 +1000
Stephen Rothwell wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (htmldocs)
> failed like this:
>
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage:
>
Hi Steve,
On Wed, 2020-06-03 at 11:22 -0400, Steven Rostedt wrote:
> On Wed, 3 Jun 2020 17:42:53 +1000
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the ftrace tree, today's linux-next build (htmldocs)
> > failed like this:
> >
> >
> > Sphinx parallel build error:
> >
On Wed, May 20, 2020 at 10:39:16AM +0200, Borislav Petkov wrote:
> On Tue, Apr 28, 2020 at 05:16:48PM +0200, Joerg Roedel wrote:
> > +bool sev_es_active(void)
> > +{
> > + return !!(sev_status & MSR_AMD64_SEV_ES_ENABLED);
> > +}
> > +EXPORT_SYMBOL_GPL(sev_es_active);
>
> I don't see this being
On 03/06/20 13:45, Benjamin Gaignard wrote:
> +static void dcmi_set_min_frequency(struct stm32_dcmi *dcmi, u64 freq)
> +{
> + struct cpufreq_policy *p;
> + int cpu;
> +
> + for_each_cpu(cpu, irq_get_affinity_mask(dcmi->irq)) {
> + p = per_cpu(policy, cpu);
> +
Use kstrdup() instead of opencoded alloc and copy. kzalloc() is
excessive here.
Signed-off-by: Denis Efremov
---
drivers/net/xen-netback/xenbus.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/xen-netback/xenbus.c b/drivers/net/xen-netback/xenbus.c
index
Hi Maxime,
Am 03.06.20 um 15:14 schrieb Maxime Ripard:
> Hi Stefan,
>
> On Tue, Jun 02, 2020 at 10:03:13PM +0200, Stefan Wahren wrote:
>> Am 02.06.20 um 21:31 schrieb Eric Anholt:
>>> On Tue, Jun 2, 2020 at 8:02 AM Dave Stevenson
>>> wrote:
Hi Maxime and Eric
On Tue, 2 Jun 2020 at
On Tue, May 26, 2020 at 10:13:50AM +0200, Peter Zijlstra wrote:
> On Tue, May 26, 2020 at 02:52:31AM +0200, Ahmed S. Darwish wrote:
> > Peter Zijlstra wrote:
>
> > > +#define lockdep_assert_irqs_enabled()
> > > \
> > > +do {
On 6/2/2020 11:33 PM, Vinod Koul wrote:
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
Hi Pradeep,
On Wed, Jun 03, 2020 at 02:39:35PM +0530, Pradeep P V K wrote:
> Interconnect bandwidth scaling support is now added as a
> part of OPP [1]. So, make sure interconnect driver is ready
> before handling interconnect scaling.
>
> This change is based on
> [1] [Patch v8] Introduce OPP
On Wed, 03 Jun 2020 10:24:36 -0500
Tom Zanussi wrote:
> > It appears to be the ascii art that is causing the issue. I have no
> > idea
> > how to fix it. If someone has a patch they would like to submit, I
> > will
> > take it before I push it off to Linus.
> >
> > -- Steve
>
> I just sent
> A deadlock caused by logbuf_lock occurs when panic:
I suggest a few wording adjustments for this change description.
Would you like to omit an extra space character at the beginning of this
sentence?
> we try to re-init …
We …
> … deadlock, but it … here, because :
… deadlock. But it …
Hello,
syzbot found the following crash on:
HEAD commit:2089c6ed usb: core: kcov: collect coverage from usb comple..
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=17cf6bd610
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:2089c6ed usb: core: kcov: collect coverage from usb comple..
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=12576bd610
kernel config:
> On Jun 3, 2020, at 8:20 AM, chenzhou wrote:
>
> Hi,
>
>
> On 2020/6/3 19:47, Prabhakar Kushwaha wrote:
>> Hi Chen,
>>
>> On Tue, Jun 2, 2020 at 8:12 PM John Donnelly
>> wrote:
>>>
>>>
On Jun 2, 2020, at 12:38 AM, Prabhakar Kushwaha
wrote:
On Tue, Jun 2, 2020 at
On Wed, Jun 03, 2020 at 10:06:07PM +0800, Wangshaobo (bobo) wrote:
> Today I test your fix, but arch_stack_walk_reliable() still return failed
> sometimes, I
>
> found one of three scenarios mentioned failed:
>
>
> 1. user task (just fork) but not been scheduled
>
> test FAILED
>
> it
This small patchset intends to use PUD/PGDIR entries for linear mapping
in order to better utilize TLB.
At the moment, only PMD entries can be used since on common platforms
(qemu/unleashed), the kernel is loaded at DRAM + 2MB which dealigns virtual
and physical addresses and then prevents the
On Fri, Mar 27, 2020 at 11:31:08PM +, Al Viro wrote:
> From: Al Viro
>
> Just inline the call and use memcpy() instead of __copy_from_user() and
> note that the tail is precisely ia64 csum_partial().
>
> Signed-off-by: Al Viro
This patch results in:
arch/ia64/lib/csum_partial_copy.c: In
Early page table uses the kernel load address as mapping for PAGE_OFFSET:
that makes memblock remove any memory below the kernel which results in
using only PMD entries for the linear mapping.
By setting MIN_MEMBLOCK_ADDR to 0, we allow this memory to be present
when creating the kernel page
On 6/3/20 4:03 AM, Masami Hiramatsu wrote:
Hi Stephen,
On Wed, 3 Jun 2020 18:29:01 +1000
Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
tools/testing/selftests/sysctl/sysctl.sh
between commit:
eee470e0739a ("selftests/sysctl:
Improve best_map_size so that PUD or PGDIR entries are used for linear
mapping when possible as it allows better TLB utilization.
Signed-off-by: Alexandre Ghiti
---
arch/riscv/mm/init.c | 45 +---
1 file changed, 34 insertions(+), 11 deletions(-)
diff
On 6/3/20 3:12 AM, Tada, Kenta (Sony) wrote:
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
Miklos Szeredi writes:
> On Fri, May 29, 2020 at 2:31 PM Miklos Szeredi wrote:
>
>> > Can you please describe the setup of this test?
>> >
>> > - Host kernel version
>
> 5.5.16-100.fc30.x86_64
>
>> > - Guest kernel version
>
> 75caf310d16c ("Merge branch 'akpm' (patches from Andrew)")
>
>> >
The existing driver is expecting the Versaclock to be pre-programmed,
and only sets the output frequency. Unfortunately, not all devices
are pre-programmed, and the Versaclock chip has more options beyond
just the frequency.
This patch enables the following additional features:
-
Currently, the Versaclock driver is only expecting one instance and
uses hard-coded names for the various clock names. Unfortunately,
this is a problem when there is more than one instance of the driver,
because the subsequent instantiations of the driver use the identical
name. Each clock after
The VersaClock driver now supports some additional bindings to support
child nodes which can configure optional settings like mode, voltage
and slew.
This patch updates the binding document to describe what is available
in the driver.
Signed-off-by: Adam Ford
Reviewed-by: Rob Herring
---
V3:
On 3/06/20 3:52 pm, Alexey Budankov wrote:
>
> On 03.06.2020 15:05, Adrian Hunter wrote:
>> On 25/05/20 5:23 pm, Alexey Budankov wrote:
>>>
>>> Introduce --ctl-fd[-ack] options to pass open file descriptors numbers
>>> from command line. Extend perf-record.txt file with --ctl-fd[-ack]
>>> options
Thomas Gleixner writes:
> Miklos Szeredi writes:
>> On Fri, May 29, 2020 at 2:31 PM Miklos Szeredi wrote:
>>
>>> > Can you please describe the setup of this test?
>>> >
>>> > - Host kernel version
>>
>> 5.5.16-100.fc30.x86_64
>>
>>> > - Guest kernel version
>>
>> 75caf310d16c ("Merge branch
From: Colin Ian King
There are two error return paths where the call to path_put is
dereferencing the null pointer 'stack'. Fix this by avoiding the
error exit path via label 'out_err' that will lead to the path_put
calls and instead just return the error code directly.
Addresses-Coverity:
Changes in v7:
- added missing perf-record.txt changes
- adjusted docs wording for --ctl-fd,ctl-fd-ack options
to additionally mention --delay=-1 effect
v6:
https://lore.kernel.org/lkml/f8e3a714-d9b1-4647-e1d2-9981cbaa8...@linux.intel.com/
Changes in v6:
- split re-factoring of events
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d6f9469a03d832dcd17041ed67774ffb5f3e73b3
commit: 78ed001d9e7106171e0ee761cd854137dd731302 compat: scsi: sg: fix v3
compat read/write interface
date: 5 months ago
config: sh-randconfig-s031-20200603
On 2020-06-03 5:44 a.m., Piotr Stankiewicz wrote:
> When debugging an issue where I was asking the PCI machinery to enable a
> set of MSI-X vectors, without falling back on MSI, I ran across a
> behaviour which seems odd. The pci_alloc_irq_vectors_affinity() will
> always return -ENOSPC on
On 5/11/20 10:59 PM, tip-bot2 for Joel Fernandes (Google) wrote:
> The following commit has been merged into the core/rcu branch of tip:
>
> Commit-ID: 9154244c1ab6c9db4f1f25ac8f73bd46dba64287
> Gitweb:
> https://git.kernel.org/tip/9154244c1ab6c9db4f1f25ac8f73bd46dba64287
> Author:
When we are in the interrupt context, it is irrelevant to the
current task context. If we use current task's mems_allowed, we
can fair to alloc pages in the fast path and fall back to slow
path memory allocation when the current node(which is the current
task mems_allowed) does not have enough
On Wed, Jun 03, 2020 at 06:26:43PM +0300, Denis Efremov wrote:
> Use kstrdup() instead of opencoded alloc and copy. kzalloc() is
> excessive here.
>
> Signed-off-by: Denis Efremov
Acked-by: Wei Liu
> ---
> drivers/net/xen-netback/xenbus.c | 3 +--
> 1 file changed, 1 insertion(+), 2
On 03.06.2020 18:44, Adrian Hunter wrote:
> On 3/06/20 3:52 pm, Alexey Budankov wrote:
>>
>> On 03.06.2020 15:05, Adrian Hunter wrote:
>>> On 25/05/20 5:23 pm, Alexey Budankov wrote:
Introduce --ctl-fd[-ack] options to pass open file descriptors numbers
from command line. Extend
Implement adding of file descriptors by fdarray__add_stat() to
fix-sized (currently 1) stat_entries array located at struct fdarray.
Append added file descriptors to the array used by poll() syscall
during fdarray__poll() call. Copy poll() result of the added
descriptors from the array back to
Define and initialize control file descriptors.
Signed-off-by: Alexey Budankov
---
tools/perf/util/evlist.c | 3 +++
tools/perf/util/evlist.h | 5 +
2 files changed, 8 insertions(+)
diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
index 173b4f0e0e6e..47541b5cab46 100644
On 3/06/20 3:52 pm, Alexey Budankov wrote:
>
> On 03.06.2020 15:30, Hunter, Adrian wrote:
>>
>>
>>> -Original Message-
>>> From: Hunter, Adrian
>>> Sent: Wednesday, June 3, 2020 3:24 PM
>>> To: Alexey Budankov
>>> Cc: Arnaldo Carvalho de Melo ; Jiri Olsa
>>> ; Namhyung Kim ; Alexander
Implement functions of initialization, finalization and processing
of control command messages coming from control file descriptors.
Allocate control file descriptor as a static descriptor at struct
pollfd object of evsel_list using perf_evlist__add_pollfd_stat().
Signed-off-by: Alexey Budankov
Introduce process_interval() and process_timeout() functions that
factor out body of event handling loop for attach and system wide
monitoring use cases.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-stat.c | 28
1 file changed, 20 insertions(+), 8
Check for target existence in loop control statement jointly with 'stop'
indicator based on command line values and external asynchronous 'done'
signal.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-stat.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
Factor out body of event handling loop for fork case reusing
process_timeout() function.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-stat.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
index
Consolidate event dispatching loops for fork, attach and system
wide monitoring use cases into common dispatch_events() function.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-stat.c | 35 ---
1 file changed, 24 insertions(+), 11 deletions(-)
diff
Extend -D,--delay option with -1 value to start monitoring with
events disabled to be enabled later by enable command provided
via control file descriptor.
Signed-off-by: Alexey Budankov
---
tools/perf/Documentation/perf-stat.txt | 5 +++--
tools/perf/builtin-stat.c | 18
Implement handling of 'enable' and 'disable' control commands
coming from control file descriptor. process_evlist() function
checks for events on static fds and makes required operations.
If poll event splits initiated timeout interval then the reminder
is calculated and still waited in the
On Wed, Jun 03, 2020 at 04:52:32PM +0200, Roelof Berg wrote:
> TEST REPORT: BROKEN PATCH
>
> Thanks to everyone for working on the fixed link feature of lan743x eth
> driver.
>
> I received more test hardware today, and one piece of hardware
> (EVBlan7430) becomes incompatible by the patch. We
Introduce --ctl-fd[-ack] options to pass open file descriptors numbers
from command line. Extend perf-stat.txt file with --ctl-fd[-ack] options
description. Document possible usage model introduced by --ctl-fd[-ack]
options by providing example bash shell script.
Signed-off-by: Alexey Budankov
Extend -D,--delay option with -1 to start collection with events
disabled to be enbled later by enable command provided via control
file descriptor.
Signed-off-by: Alexey Budankov
---
tools/perf/Documentation/perf-record.txt | 5 +++--
tools/perf/builtin-record.c | 12
Implement handling of 'enable' and 'disable' control commands
coming from control file descriptor.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-record.c | 16
1 file changed, 16 insertions(+)
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
Introduce --ctl-fd[-ack] options to pass open file descriptors numbers
from command line. Extend perf-record.txt file with --ctl-fd[-ack]
options description. Document possible usage model introduced by
--ctl-fd[-ack] options by providing example bash shell script.
Signed-off-by: Alexey
From: Colin Ian King
Currently if an xa_insert fails then there is a memory lead of the
recently allocated zone object. Fix this by kfree'ing zone before
returning on the error return path.
Addresses-Coverity: ("Resource leak")
Fixes: 1a311efa3916 ("dm zoned: convert to xarray")
Signed-off-by:
> -Original Message-
> From: Logan Gunthorpe
> Sent: Wednesday, June 3, 2020 5:48 PM
>
>
>
> On 2020-06-03 5:44 a.m., Piotr Stankiewicz wrote:
> > When debugging an issue where I was asking the PCI machinery to enable a
> > set of MSI-X vectors, without falling back on MSI, I ran
On Wed, Jun 03, 2020 at 04:47:54PM +0200, Marco Elver wrote:
> This is fun: __always_inline functions inlined into
> __no_sanitize_undefined *do* get instrumented because apparently UBSan
> passes must run before the optimizer (before inlining), contrary to
> what [ATM]SAN instrumentation does.
On 03.06.20 16:11, SeongJae Park wrote:
> From: SeongJae Park
>
> This commit implements the four callbacks (->init_target_regions,
> ->update_target_regions, ->prepare_access_check, and ->check_accesses)
> for the basic access monitoring of the physical memory address space.
> By setting the
On Wed, Jun 03, 2020 at 10:06:31AM +0530, Anshuman Khandual wrote:
> Does this look okay and sufficient ?
>
> --- a/Documentation/vm/page_migration.rst
> +++ b/Documentation/vm/page_migration.rst
> @@ -253,5 +253,20 @@ which are function pointers of struct
> address_space_operations.
>
max_pfn is uesd to get the highest pfn in the system. Drivers like
drivers/iommu/mtk_iommu.c checks max_pfn to see if it should enable
its "4GB mode".
This patch exports the max_pfn symbol, so we can build the driver as
a kernel module.
Signed-off-by: Miles Chen
---
mm/memblock.c | 1 +
1 file
On Wed, Jun 3, 2020 at 6:46 PM Colin King wrote:
>
> From: Colin Ian King
>
> There are two error return paths where the call to path_put is
> dereferencing the null pointer 'stack'. Fix this by avoiding the
> error exit path via label 'out_err' that will lead to the path_put
> calls and
Hi Chuhong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v5.7 next-20200603]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base
On 03/06/2020 17:11, Amir Goldstein wrote:
> On Wed, Jun 3, 2020 at 6:46 PM Colin King wrote:
>>
>> From: Colin Ian King
>>
>> There are two error return paths where the call to path_put is
>> dereferencing the null pointer 'stack'. Fix this by avoiding the
>> error exit path via label
On Wed, Jun 3, 2020 at 5:59 AM Anson Huang wrote:
>
> Convert the i.MXDI RTC binding to DT schema format using json-schema
>
> Signed-off-by: Anson Huang
> ---
> .../devicetree/bindings/rtc/imxdi-rtc.txt | 20 ---
> .../devicetree/bindings/rtc/imxdi-rtc.yaml | 42
>
On 03.06.20 18:11, Miles Chen wrote:
> max_pfn is uesd to get the highest pfn in the system. Drivers like
> drivers/iommu/mtk_iommu.c checks max_pfn to see if it should enable
> its "4GB mode".
>
> This patch exports the max_pfn symbol, so we can build the driver as
> a kernel module.
Please add
On Tue, Aug 27, 2019 at 07:17:55PM +0800, Jonathan Cameron wrote:
> On Thu, 22 Aug 2019 15:42:14 +0100
> Raphael Gault wrote:
>
> > This test relies on the fact that the PMU registers are accessible
> > from userspace. It then uses the perf_event_mmap_page to retrieve
> > the counter index and
On Wed, Jun 03, 2020 at 04:49:45PM +0200, Ahmed S. Darwish wrote:
> Commit bf7afb29d545 ("phy: improve safety of fixed-phy MII register
> reading") protected the fixed PHY status with a sequence counter.
>
> Two years later, commit d2b977939b18 ("net: phy: fixed-phy: remove
>
On Wed, Jun 3, 2020 at 7:15 PM Colin Ian King wrote:
>
> On 03/06/2020 17:11, Amir Goldstein wrote:
> > On Wed, Jun 3, 2020 at 6:46 PM Colin King wrote:
> >>
> >> From: Colin Ian King
> >>
> >> There are two error return paths where the call to path_put is
> >> dereferencing the null pointer
dev_err() needs a terminating newline.
Signed-off-by: Luca Ceresoli
---
drivers/power/reset/gpio-poweroff.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/reset/gpio-poweroff.c
b/drivers/power/reset/gpio-poweroff.c
index 6a4bbb506551..c5067eb75370 100644
---
On 2020-06-03 10:04 a.m., Stankiewicz, Piotr wrote:
>> -Original Message-
>> From: Logan Gunthorpe
>> Sent: Wednesday, June 3, 2020 5:48 PM
>>
>>
>>
>> On 2020-06-03 5:44 a.m., Piotr Stankiewicz wrote:
>>> When debugging an issue where I was asking the PCI machinery to enable a
>>> set
On Wed, 2020-06-03 at 16:05 +0200, Arnd Bergmann wrote:
> I don't know if you can just run 'make headers_install' without configuring
> first, or if that is something that can be easily changed if it doesn't
> already
> work.
It would be kind of wrong for the exported ABI headers to depend on
This patch introduces CAP_CHECKPOINT_RESTORE, a new capability facilitating
checkpoint/restore for non-root users.
Over the last years, The CRIU (Checkpoint/Restore In Userspace) team has been
asked numerous times if it is possible to checkpoint/restore a process as
non-root. The answer usually
From: Nicolas Viennot
The current process is authorized to change its /proc/self/exe link via
two policies:
1) The current user can do checkpoint/restore In other words is
CAP_SYS_ADMIN or CAP_CHECKPOINT_RESTORE capable.
2) The current user can use ptrace.
With access to ptrace facilities, a
Hi John,
On 6/3/20 4:59 AM, John Garry wrote:
> On 02/06/2020 07:17, Dongli Zhang wrote:
>> When scheduler is set, we hit below page fault when we offline cpu.
>>
>> [ 1061.007725] BUG: kernel NULL pointer dereference, address:
>> 0040
>> [ 1061.008710] #PF: supervisor read access in
This is v2 of the 'Introduce CAP_CHECKPOINT_RESTORE' patchset. The
difference from v1 are:
* Renamed CAP_RESTORE to CAP_CHECKPOINT_RESTORE
* Added a test
* Added details about CRIU's use of map_files
* Allow changing /proc/self/exe link with CAP_CHECKPOINT_RESTORE
The biggest difference is
This adds a test that changes its UID, uses capabilities to
get CAP_CHECKPOINT_RESTORE and uses clone3() with set_tid to
create a process with a given PID as non-root.
Signed-off-by: Adrian Reber
---
tools/testing/selftests/clone3/Makefile | 4 +-
Hi! Was going through my email and found this from last month, it's a bit late
and someone might have reviewed/pushed this already but just in case:
Reviewed-by: Lyude Paul
On Wed, 2020-05-20 at 18:47 +0800, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
On Wed, 3 Jun 2020 01:24:43 -0400
Yan Zhao wrote:
> On Tue, Jun 02, 2020 at 09:55:28PM -0600, Alex Williamson wrote:
> > On Tue, 2 Jun 2020 23:19:48 -0400
> > Yan Zhao wrote:
> >
> > > On Tue, Jun 02, 2020 at 04:55:27PM -0600, Alex Williamson wrote:
> > > > On Wed, 29 Apr 2020 20:39:50
On Wed, Jun 03, 2020 at 05:27:07PM +0800, Chuhong Yuan wrote:
> xfs_ifree_cluster() calls xfs_perag_get() at the beginning, but forgets to
> call xfs_perag_put() in one failed path.
> Add the missed function call to fix it.
>
> Fixes: ce92464c180b ("xfs: make xfs_trans_get_buf return an error
Hello,
On Mon, Jun 01, 2020 at 10:50:36AM +0530, Sandipan Patra wrote:
> diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c
> index d26ed8f..1daf591 100644
> --- a/drivers/pwm/pwm-tegra.c
> +++ b/drivers/pwm/pwm-tegra.c
> @@ -4,8 +4,36 @@
> *
> * Tegra pulse-width-modulation
601 - 700 of 1155 matches
Mail list logo
