* Masami Hiramatsu wrote:
> Hi,
>
> Here is the v9 series of probe-event to support user-space access.
> Previous version is here.
>
> https://lkml.kernel.org/r/155741476971.28419.15837024173365724167.stgit@devnote2
>
> In this version, I fixed more typos/style issues.
>
> Changes in v9:
>
Hi Jones,
> > +
> > +struct rpc_spi {
> > + struct rpc_mfd *mfd;
>
> The term MFD isn't a real thing. What you're obtaining below is
> driver data and is normally articulated as 'ddata' in drivers.
yes, it's just imply that data is from MFD.
Should I rename "mfd" ?
>
> > + u32
Since commit 350e88bad496 ("mm: memblock: make keeping memblock memory
opt-in rather than opt-out") the default behaviour is to discard memblock
data after init and the ARCH_DISCARD_MEMBLOCK is obsolete.
Remove it.
Signed-off-by: Mike Rapoport
---
arch/parisc/Kconfig | 1 -
1 file changed, 1
On 14.05.2019 23:04, Arnaldo Carvalho de Melo wrote:
> Em Mon, Mar 18, 2019 at 08:44:42PM +0300, Alexey Budankov escreveu:
>>
>> Implemented -z,--compression_level[=] option that enables compression
>> of mmaped kernel data buffers content in runtime during perf record
>> mode collection. Default
Add user memory access attribute for kprobe event arguments.
If a given 'local variable' is in user-space, User can
specify memory access method by '@user' suffix. This is
not only for string but also for data structure.
If we access a field of data structure in user memory from
kernel on some
Add a user-memory access syntax testcase which checks
new user-memory access syntax and ustring type.
Signed-off-by: Masami Hiramatsu
Acked-by: Steven Rostedt (VMware)
---
Changes in v6:
- Add $argN availability check
---
.../ftrace/test.d/kprobe/kprobe_args_user.tc | 32
Add probe_user_read(), strncpy_from_unsafe_user() and
strnlen_unsafe_user() which allows caller to access user-space
in IRQ context.
Current probe_kernel_read() and strncpy_from_unsafe() are
not available for user-space memory, because it sets
KERNEL_DS while accessing data. On some arch, user
Add "ustring" type for fetching user-space string from kprobe event.
User can specify ustring type at uprobe event, and it is same as
"string" for uprobe.
Note that probe-event provides this option but it doesn't choose the
correct type automatically since we have not way to decide the address
is
Support user-space dereference syntax for probe event arguments
to dereference the data-structure or array in user-space.
The syntax is just adding 'u' before an offset value.
+|-u()
e.g. +u8(%ax), +u0(+0(%si))
For example, if you probe do_sched_setscheduler(pid, policy,
param) and record
WARN_ON_IN_IRQ() assumes that the access_ok() and following
user memory access can sleep. But this assumption is not
always correct; when the pagefault is disabled, following
memory access will just returns -EFAULT and never sleep.
Add pagefault_disabled() check in WARN_ON_ONCE() so that
it can
Hi,
Here is the v9 series of probe-event to support user-space access.
Previous version is here.
https://lkml.kernel.org/r/155741476971.28419.15837024173365724167.stgit@devnote2
In this version, I fixed more typos/style issues.
Changes in v9:
[3/6]
- Fix other style & coding issues
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch aims to suppress 3 missing-break-in-switch false positives
on some architectures.
Acked-by: Arnd Bergmann
Cc: Deepa Dinamani
Cc: Gustavo A. R. Silva
Cc: Kees Cook
Cc: Jann
Hi Kairui,
On 5/13/19 5:02 PM, Baoquan He wrote:
> On 05/13/19 at 09:50am, Borislav Petkov wrote:
>> On Mon, May 13, 2019 at 03:32:54PM +0800, Baoquan He wrote:
>> So we're going to try it again this cycle and if there's no fallout, it
>> will go upstream. If not, it will have to be fixed. The
On Wed, May 15, 2019 at 02:22:06PM +0930, Joel Stanley wrote:
> This fixes a build break introduced in with the recent round of CPU
> bug patches.
>
> arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
> arch/powerpc/kernel/security.c:59:21: error: implicit declaration of
>
Hi Florian,
On 5/14/19 7:38 PM, Florian Fainelli wrote:
> When building on a 64-bit host, we will get warnings like those:
>
> drivers/firmware/broadcom/bcm47xx_nvram.c:103:3: note: in expansion of macro
> 'pr_err'
>pr_err("nvram on flash (%i bytes) is bigger than the reserved space in
>
On Tue, 14 May 2019 16:58:24 -0500, Xing, Cedric
wrote:
Hi Everyone,
I think we are talking about 2 different kinds of criteria for
determining the sanity of an enclave.
The first kind determines an enclave's sanity by generally accepted good
practices. For example, no executable
On Wed, May 15, 2019 at 12:34:00AM +, Jason Gunthorpe wrote:
> On Tue, May 14, 2019 at 12:45:10PM -0700, Nathan Chancellor wrote:
> > DIV_ROUND_UP is u64 / u32 in this case. I think DIV_ROUND_UP_ULL is
> > needed but I am not sure if that has any unintended side effects so I
> > didn't want to
Ah, I think I see the problem. Sorry, this one was my fault. Does
this fix things for you?
- Ted
>From 0c72924ef346d54e8627440e6d71257aa5b56105 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o
Date: Wed, 15 May 2019 00:51:19 -0400
Subject: [PATCH]
This fixes a build break introduced in with the recent round of CPU
bug patches.
arch/powerpc/kernel/security.c: In function ‘setup_barrier_nospec’:
arch/powerpc/kernel/security.c:59:21: error: implicit declaration of
function ‘cpu_mitigations_off’ [-Werror=implicit-function-declaration]
The top level Makefile adds -Wall globally:
KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
For riscv, I see two "-Wall" added for compiling each object.
Signed-off-by: Masahiro Yamada
---
arch/riscv/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git
Hi,
Am 14.05.2019 um 13:22 schrieb Michael Schmitz:
Stephen,
I wasn't aware of the other asix module when submitting the phy driver.
The phy module gets autoloaded based on the PHY ID, so there's no reason
why it couldn't be renamed.
May I suggest ax88796b for the new module name?
I've got
On 05/15/2019 05:21 AM, Roman Gushchin wrote:
> __vunmap() calls find_vm_area() twice without an obvious reason:
> first directly to get the area pointer, second indirectly by calling
> vm_remove_mappings()->remove_vm_area(), which is again searching
> for the area.
>
> To remove this
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190514:
The thermal-soc tree lost its build failure but gained conflicts against
Linus' tree.
The akpm-current tree gained a conflict against the pidfd
New display port clock ops supported for display port clocks.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/Kconfig| 1 +
drivers/clk/qcom/clk-rcg.h | 1 +
drivers/clk/qcom/clk-rcg2.c | 81 -
3 files changed, 82 insertions(+), 1 deletion(-)
SDM845 dispcc supports RCG and CBCRs for display port, so add support for
the same.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/dispcc-sdm845.c | 216 -
include/dt-bindings/clock/qcom,dispcc-sdm845.h | 13 +-
2 files changed, 227 insertions(+), 2
[v2]
* Update KCONFIG to select RATIONAL
* Clean up redundant code from dp_set_rate/dp_set_rate_and_parent
* Update the disp_cc_mdss_dp_link_clk_src to use the byte2_ops instead
of defining the frequencies in KHz.
* Clean up CLK_GET_RATE_NOCACHE from various RCGs of DP.
[v1]
On Mon, May 13, 2019 at 3:48 PM Doug Anderson wrote:
>
> Hi,
>
> On Thu, May 9, 2019 at 11:44 AM Rob Clark wrote:
>
> > From: Douglas Anderson
> >
> > Let's fixup the reserved memory to re-add the things we deleted in
> > ("CHROMIUM: arm64: dts: qcom: sdm845-cheza: Temporarily delete
> >
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of vmentry which is
merged both patches into cifs-2.6.git for-next
On Mon, May 13, 2019 at 11:02 PM wrote:
>
> From: Long Li
>
> When sending data, use the DMA_TO_DEVICE to map buffers. Also log the number
> of requests in a compounding request from upper layer.
>
> Signed-off-by: Long Li
> ---
>
From: Wanpeng Li
Extract adaptive tune timer advancement logic to a single function.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Sean Christopherson
Cc: Liran Alon
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 57 ++--
1 file changed, 33
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of vmentry which is
From: Wanpeng Li
After commit c3941d9e0 (KVM: lapic: Allow user to disable adaptive tuning of
timer advancement), '-1' enables adaptive tuning starting from default
advancment of 1000ns. However, we should expose an int instead of an overflow
uint module parameter.
Before patch:
From: Wanpeng Li
Expose the per-vCPU advancement information to the user via per-vCPU debugfs
entry. wait_lapic_expire() call was moved above guest_enter_irqoff() because
of its tracepoint, which violated the RCU extended quiescent state invoked
by guest_enter_irqoff()[1][2]. This patch
From: Wanpeng Li
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of
On Mon, May 13, 2019 at 11:24 PM Oliver wrote:
>
> On Mon, May 13, 2019 at 9:23 PM Masahiro Yamada
> wrote:
> >
> > Commit 5e9dcb6188a4 ("powerpc/boot: Expose Kconfig symbols to wrapper")
> > was wrong, but commit e41b93a6be57 ("powerpc/boot: Fix build failures
> > with -j 1") was also wrong.
>
The pull request you sent on Wed, 15 May 2019 00:46:58 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5ac94332248ee017964ba368cdda4ce647e3aba7
Thank you!
--
Deet-doot-dot, I am a
From: Ashish Kumar
This patch is to add esdhc node and enable SD UHS-I,
eMMC HS200 for ls1028ardb/ls1028aqds board.
Signed-off-by: Ashish Kumar
Signed-off-by: Yangbo Lu
Signed-off-by: Yinbo Zhu
---
Change in v2:
Update the patch title
Add a commont in dts code
Hi Xiang:
Thanks for your reply, I will have a stress test on my device later.
I didn't have chance to test LZ4 with clang build because of device limitation.
I think I could do it later.
I guess the clang performance downgrade is caused by some compiler optimization
options.
I will double
> -Original Message-
> From: Yinbo Zhu
> Sent: 2019年5月5日 14:07
> To: Rob Herring
> Cc: Shawn Guo ; Leo Li ; Xiaobo
> Xie ; Mark Rutland ;
> linux-arm-ker...@lists.infradead.org; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; Y.b. Lu
> ; Jiafei Pan
As noted in commit 84b40e3b57ee ("serial: 8250: omap: Disable DMA for
console UART"), UART console lines use low-level PIO only access functions
which will conflict with use of the line when DMA is enabled, e.g. when
the console line is also used for systemd messages. So disable DMA
support for
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
include/linux/pid.h
between commit:
51f1b521a515 ("pidfd: add polling support")
from the pidfd tree and commit:
c02e28a1bb18 ("kernel/pid.c: convert struct pid:count to refcount_t")
from the akpm-current
On 14 May 2019 11:29:37 am ACST, Arthur Marsh
wrote:
>Apologies, I had forgotten to
>
>git bisect - - hard origin/master
>
>I am still seeing the corruption leading to the invalid block error on
>5.1.0+ kernels on both my machines.
>
>Arthur.
After the mm commits, the 32 bit kernel on
From: Jiri Kosina
The only purpose of klp_check_compiler_support() is to make sure that we
are not using ftrace on x86 via mcount (because that's executed only after
prologue has already happened, and that's too late for livepatching
purposes).
Now that mcount is not supported by ftrace any
From: "Steven Rostedt (VMware)"
User Mode Linux does not have access to the ip or sp fields of the pt_regs,
and accessing them causes UML to fail to build. Hide the int3_emulate_jmp()
and int3_emulate_call() instructions from UML, as it doesn't need them
anyway.
Reported-by: kbuild test robot
From: Linus Torvalds
Peter Zijlstra noticed that with CONFIG_PROFILE_ALL_BRANCHES, the "if"
macro converts the conditional to an array index. This can cause GCC
to create horrible code. When there are nested ifs, the generated code
uses register values to encode branching decisions.
Josh
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 693713cbdb3a4bda5a8a678c31f06560bbb14657
Jiri Kosina (1):
livepatch: Remove klp_check_compiler_support()
Linus Torvalds (1):
tracing: Simplify "if" macro code
Steven Rostedt (VMware) (3):
From: "Steven Rostedt (VMware)"
When DYNAMIC_FTRACE is enabled in the kernel, all the functions that can be
traced by the function tracer have a "nop" placeholder at the start of the
function. When function tracing is enabled, the nop is converted into a call
to the tracing infrastructure where
From: "Steven Rostedt (VMware)"
There's two methods of enabling function tracing in Linux on x86. One is
with just "gcc -pg" and the other is "gcc -pg -mfentry". The former will use
calls to a special function "mcount" after the frame is set up in all C
functions. The latter will add calls to a
Hi Chenxi,
On 2019/5/15 8:43, Chenxi Mao wrote:
> FAST_DEC_LOOP was introduced from LZ4 1.9.
> This change would be introduce 10% on decompress operation
> according to LZ4 benchmark result on X86 devices.
> Meanwhile, LZ4 with FAST_DEC_LOOP could get improvements,
> however clang compiler has
On Wed, 15 May 2019 at 02:20, Marcelo Tosatti wrote:
>
> On Tue, May 14, 2019 at 11:20:15AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, May 14, 2019 at 10:50:23AM -0300, Marcelo Tosatti wrote:
> > > On Mon, May 13, 2019 at 05:20:37PM +0800, Wanpeng Li wrote:
> > > > On Wed, 8 May 2019 at
On 05/14/2019 09:10 PM, Mark Rutland wrote:
> On Tue, May 14, 2019 at 02:30:05PM +0530, Anshuman Khandual wrote:
>> The arm64 pagetable dump code can race with concurrent modification of the
>> kernel page tables. When a leaf entries are modified concurrently, the dump
>> code may log stale or
On 05/08/19 at 05:47pm, Kirill A. Shutemov wrote:
> On Wed, May 08, 2019 at 05:35:20PM +0800, Baoquan He wrote:
> > On 05/08/19 at 11:04am, Borislav Petkov wrote:
> > > On Wed, May 08, 2019 at 04:24:18PM +0800, Baoquan He wrote:
> > > > I think this's worth noticing stable tree:
> > > >
> > > >
On Mon, 13 May 2019 at 19:52, Raslan, KarimAllah wrote:
>
> On Mon, 2019-05-13 at 07:31 -0400, Konrad Rzeszutek Wilk wrote:
> > On May 13, 2019 5:20:37 AM EDT, Wanpeng Li wrote:
> > >
> > > On Wed, 8 May 2019 at 02:57, Marcelo Tosatti
> > > wrote:
> > > >
> > > >
> > > >
> > > > Certain
i.MX8MM has clock gate for SNVS module, add it into clock tree
for SNVS RTC driver to manage.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx8mm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/imx/clk-imx8mm.c b/drivers/clk/imx/clk-imx8mm.c
index 733ca20..7ffbd6e3
i.MX8MM has clock gate for SNVS module, add clock info to SNVS
RTC node for clock management.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi
Hi Thomas,
>
> > > >
---
> > > > static void macronix_nand_onfi_init(struct nand_chip *chip)
> > > > {
> > > > struct nand_parameters *p = >parameters;
> > > > struct nand_onfi_vendor_macronix *mxic = (void
On Tue, May 14, 2019 at 02:27:08PM -0700, Andy Lutomirski wrote:
> On Tue, May 14, 2019 at 1:45 PM Sean Christopherson
> wrote:
> >
> > On Tue, May 14, 2019 at 08:13:36AM -0700, Andy Lutomirski wrote:
> > > On Tue, May 14, 2019 at 3:43 AM Jarkko Sakkinen
> > > wrote:
> > > >
> > > > On Mon, May
Add macro for the SNVS clock of the i.MX8MM.
Signed-off-by: Anson Huang
---
This patch is based on patch: https://patchwork.kernel.org/patch/10939997/
---
include/dt-bindings/clock/imx8mm-clock.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Add macro for the SNVS clock of the i.MX8MQ.
Signed-off-by: Anson Huang
---
include/dt-bindings/clock/imx8mq-clock.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/dt-bindings/clock/imx8mq-clock.h
b/include/dt-bindings/clock/imx8mq-clock.h
index 6677e92..0233bb1
i.MX8MQ has clock gate for SNVS module, add it into clock tree
for SNVS RTC driver to manage.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx8mq.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/imx/clk-imx8mq.c b/drivers/clk/imx/clk-imx8mq.c
index daf1841..24c3464 100644
i.MX8MQ has clock gate for SNVS module, add clock info to SNVS
RTC node for clock management.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
Since lo_ioctl() is calling sb_set_blocksize() immediately after udf_load_vrs()
called sb_set_blocksize(), udf_tread() can't use expected i_blkbits settings...
[ 48.685672][ T7322] fs/block_dev.c:135 bdev=14fa0ec2 12 -> 9
[ 48.694675][ T7322] CPU: 4 PID: 7322 Comm: a.out Not tainted
On Tue, May 14, 2019 at 07:44:42PM +0200, Roberto Sassu wrote:
> On 5/14/2019 5:57 PM, Arvind Sankar wrote:
> > On Tue, May 14, 2019 at 11:27:04AM -0400, Arvind Sankar wrote:
> >> It's also much easier to change/customize it for the end
> >> system's requirements rather than setting the process in
There is a race condition between removing glue directory and adding a new
device under the glue directory. It can be reproduced in following test:
path 1: Add the child device under glue dir
device_add()
get_device_parent()
mutex_lock(_mutex);
/*find parent from
FAST_DEC_LOOP was introduced from LZ4 1.9.
This change would be introduce 10% on decompress operation
according to LZ4 benchmark result on X86 devices.
Meanwhile, LZ4 with FAST_DEC_LOOP could get improvements,
however clang compiler has downgrade if FAST_DEC_LOOP enabled.
So FAST_DEC_LOOP only
LGTM for whole series
Reviewed-by: Timofey Titovets
вт, 14 мая 2019 г. в 16:17, Oleksandr Natalenko :
>
> Document respective sysfs knob.
>
> Signed-off-by: Oleksandr Natalenko
> ---
> Documentation/admin-guide/mm/ksm.rst | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
On Tue, May 14, 2019 at 04:54:12PM -0700, James Bottomley wrote:
> On Tue, 2019-05-14 at 18:39 -0500, Rob Landley wrote:
> > On 5/14/19 2:18 PM, James Bottomley wrote:
> > > > I think Rob is right here. If /init was statically built into
> > > > the kernel image, it has no more ability to
LGTM
Reviewed-by: Timofey Titovets
вт, 14 мая 2019 г. в 16:22, Aaron Tomlin :
>
> On Tue 2019-05-14 15:16 +0200, Oleksandr Natalenko wrote:
> > Present a new sysfs knob to mark task's anonymous memory as mergeable.
> >
> > To force merging task's VMAs, its PID is echoed in a write-only file:
>
Hi Linus,
These are the 2nd proposed RDMA patches for 5.2.
As requested the main reason to send this is to fix the gcc 9.1
warnings that many people may hit now that FC30 is out.
Thanks,
Jason
The following changes since commit b79656ed44c6865e17bcd93472ec39488bcc4984:
RDMA/ipoib: Allow
Hi Eduardo,
On Tue, 14 May 2019 07:15:33 -0700 Eduardo Valentin wrote:
>
> On Tue, May 14, 2019 at 02:40:06PM +1000, Stephen Rothwell wrote:
> > Hi Eduardo,
> >
> > On Mon, 13 May 2019 20:44:11 -0700 Eduardo Valentin
> > wrote:
> > >
> > > Thanks for spotting this. I am re-doing the branch
On Tue, May 14, 2019 at 12:45:10PM -0700, Nathan Chancellor wrote:
> DIV_ROUND_UP is u64 / u32 in this case. I think DIV_ROUND_UP_ULL is
> needed but I am not sure if that has any unintended side effects so I
> didn't want to send a patch.
Hmm. Most likely those u64 length's should really be
In perf_output_put_handle(), an IRQ/NMI can happen in below location and
write records to the same ring buffer:
...
local_dec_and_test(>nest)
... <-- an IRQ/NMI can happen here
rb->user_page->data_head = head;
...
In this case, a
On Tue, May 14, 2019 at 07:20:15PM +0200, Roberto Sassu wrote:
> On 5/14/2019 6:58 PM, Greg KH wrote:
> > On Tue, May 14, 2019 at 06:33:29PM +0200, Roberto Sassu wrote:
> >> Right, the measurement/signature verification of the kernel image is
> >> sufficient.
> >>
> >> Now, assuming that we defer
Jerome Brunet writes:
> This patchset adds the MMC controller B and C to the g12a SoC as well
> as the u200 and sei510 boards.
>
> MMC controller A has been left out on purpose. This controller is
> special on this SoC family and will be added later on.
>
> Notice the use of the pinconf DT
Jerome Brunet writes:
> Now that the AO clock controller is available, make the uarts of the
> always-on domain claim the appropriate peripheral clock.
>
> Signed-off-by: Jerome Brunet
Queued for v5.3 with tags from Neil and Martin,
Thanks,
Kevin
From: Roman Gushchin
Date: Tue, May 14, 2019 at 2:54 PM
To: Andrew Morton, Shakeel Butt
Cc: , ,
, Johannes Weiner, Michal Hocko, Rik van Riel,
Christoph Lameter, Vladimir Davydov, , Roman
Gushchin
> Switching to an indirect scheme of getting mem_cgroup pointer for
> !root slab pages broke
Jerome Brunet writes:
> Add UHS ddr50 mode to the nanopi k2
>
> Signed-off-by: Jerome Brunet
Queued for v5.3,
Thanks,
Kevin
From: Roman Gushchin
Date: Tue, May 14, 2019 at 2:54 PM
To: Andrew Morton, Shakeel Butt
Cc: , ,
, Johannes Weiner, Michal Hocko, Rik van Riel,
Christoph Lameter, Vladimir Davydov, , Roman
Gushchin
> Let's reparent memcg slab memory on memcg offlining. This allows us
> to release the memory
Jerome Brunet writes:
> On Sat, 2019-05-11 at 19:06 +0200, Martin Blumenstingl wrote:
>> Hi Jerome,
>>
>> On Fri, May 10, 2019 at 6:49 PM Jerome Brunet wrote:
>> > Add the ethernet pinctrl settings for RMII, RGMII and internal phy leds
>> >
>> > Signed-off-by: Jerome Brunet
>> > ---
>> >
From: Roman Gushchin
Date: Tue, May 14, 2019 at 2:55 PM
To: Andrew Morton, Shakeel Butt
Cc: , ,
, Johannes Weiner, Michal Hocko, Rik van Riel,
Christoph Lameter, Vladimir Davydov, , Roman
Gushchin
> This commit makes several important changes in the lifecycle
> of a non-root kmem_cache, which
Hi all,
Today's linux-next merge of the thermal-soc tree got a conflict in:
drivers/hwmon/pwm-fan.c
between commits:
6b1ec4789fb1 ("hwmon: (pwm-fan) Add RPM support via external interrupt")
841cf6767bf6 ("hwmon: (pwm-fan) Report probe errors consistently")
from Linus' tree and commit:
Martin Blumenstingl writes:
> Amlogic's vendor kernel defines an OPP for the GPU on Meson8b boards
> with a voltage of 1.15V. It turns out that the vendor kernel relies on
> the bootloader to set up the voltage. The bootloader however sets a
> fixed voltage of 1.10V.
>
> Amlogic's patched u-boot
On Tue, 2019-05-14 at 18:39 -0500, Rob Landley wrote:
> On 5/14/19 2:18 PM, James Bottomley wrote:
> > > I think Rob is right here. If /init was statically built into
> > > the kernel image, it has no more ability to compromise the kernel
> > > than anything else in the kernel. What's the
Vmalloc() is getting more and more used these days (kernel stacks,
bpf and percpu allocator are new top users), and the total %
of memory consumed by vmalloc() can be pretty significant
and changes dynamically.
/proc/meminfo is the best place to display this information:
its top goal is to show
__vunmap() calls find_vm_area() twice without an obvious reason:
first directly to get the area pointer, second indirectly by calling
vm_remove_mappings()->remove_vm_area(), which is again searching
for the area.
To remove this redundancy, let's split remove_vm_area() into
__remove_vm_area(struct
On Thu, Apr 25, 2019 at 4:22 PM Yang Shi wrote:
>
> The commit 6b4c9f446981 ("filemap: drop the mmap_sem for all blocking
> operations") changed when mmap_sem is dropped during filemap page fault
> and when returning VM_FAULT_RETRY.
>
> Correct the comment to reflect the change.
>
> Cc: Josef
On 5/14/19 2:18 PM, James Bottomley wrote:
>> I think Rob is right here. If /init was statically built into the
>> kernel image, it has no more ability to compromise the kernel than
>> anything else in the kernel. What's the problem here?
>
> The specific problem is that unless you own the
On 5/11/19 11:04 PM, Kelsey Skunberg wrote:
Create /selftests/drivers/.gitignore which holds the following file name
created after compiling:
Thanks for the patch.
Ran into the same relative path WARN from checkpatch for the commit
log. Fixed it and applied.
thanks,
-- Shuah
Hi Kelsey,
On 5/11/19 10:57 PM, Kelsey Skunberg wrote:
Create /selftests/pidfd/.gitignore which holds the following file name
created after compiling:
This patch generates the following checkpatch warning.
WARNING: use relative pathname instead of absolute in changelog text
#85:
Create
On Sun, May 12, 2019 at 02:28:07AM +0530, Jeffrin Thalakkottoor wrote:
> Hi Pablo,
>
> Please follow up on the mail you sent.
> This is for my interest to see my patch upstream
Please, pick a shorter patch subject, I'd suggest something like:
"selftests: netfilter: missing error check when
--
I need your cooperation to transfer $7 million in your bank account
and you will be entitled to 40% of the money, kindly reply me for more
details if you are interested.
On Tue, May 14, 2019 at 02:25:27PM -0700, Andrew Morton wrote:
> On Tue, 9 Jan 2018 02:10:50 -0800 Yu Zhao wrote:
>
> > > Also what prevents reordering here? There do not seem to be any barriers
> > > to prevent __SetPageSwapBacked leak after set_pte_at with your patch.
> >
> > I assumed
Parameters passed to check helpers are now obtained by dereferencing
unverified pointer arguments. Check validity of those pointers first.
Signed-off-by: Janusz Krzysztofik
---
drivers/media/v4l2-core/v4l2-subdev.c | 27 +++
1 file changed, 27 insertions(+)
diff --git
Extend parameter checks performed by v4l2_subdev_call() with a check for
a non-NULL pad config pointer if V4L2_SUBDEV_FORMAT_TRY format type is
requested so drivers don't need to care.
Signed-off-by: Janusz Krzysztofik
---
drivers/media/v4l2-core/v4l2-subdev.c | 27 +--
Correctness of format type (try or active) and pad number parameters
passed to subdevice operation callbacks is now verified only for IOCTL
calls. However, those callbacks are also used by drivers, e.g., V4L2
host interfaces.
Since both subdev_do_ioctl() and drivers are using v4l2_subdev_call()
Correctness of format type (try or active) and pad ID parameters passed
to subdevice operation callbacks is now verified only for IOCTL calls.
However, those callbacks are also used by drivers, e.g., V4L2 host
interfaces.
Since both subdev_do_ioctl() and drivers are using v4l2_subdev_call()
Hi Josef,
Any comment on this patch? I switched to my personal email since the
mail may get bounced back with my work email sometime.
On Wed, May 8, 2019 at 9:55 AM Yang Shi wrote:
>
> Ping.
>
>
> Josef, any comment on this one?
>
>
> Thanks,
>
> Yang
>
>
>
> On 4/25/19 4:22 PM, Yang Shi
From: Raphael Gault
The directive specified in the documentation to add an exception
for a single file in a Makefile was inverted.
Signed-off-by: Raphael Gault
Signed-off-by: Josh Poimboeuf
---
tools/objtool/Documentation/stack-validation.txt | 2 +-
1 file changed, 1 insertion(+), 1
.On Tue, May 14, 2019 at 3:41 PM Nathan Chancellor
wrote:
>
> Currently, this Makefile hardcodes GNU ar, meaning that if it is not
> available, there is no way to supply a different one and the build will
> fail.
>
> $ make AR=llvm-ar CC=clang LD=ld.lld HOSTAR=llvm-ar HOSTCC=clang \
>
Running "make kselftest" or building selftests when KBUILD_OUTPUT
is set, will create selftest objects in the KBUILD_OUTPUT directory.
This could be undesirable especially when user didn't intend to
relocate selftest objects.
Use KBUILD_OUTPUT/kselftest to create selftest objects instead of
1 - 100 of 664 matches
Mail list logo
