On 19 October 2018 at 00:51, Rob Herring wrote:
> On Mon, Oct 15, 2018 at 04:09:22PM +0800, Baolin Wang wrote:
>> Some battery driver will use the open circuit voltage (OCV) value to look
>> up the corresponding battery capacity percent in one certain degree Celsius.
>> Thus this patch provides so
On Fri, Oct 12, 2018 at 09:29:56AM +0530, Anshuman Khandual wrote:
> During huge page allocation it's migratability is checked to determine if
> it should be placed under movable zones with GFP_HIGHUSER_MOVABLE. But the
> movability aspect of the huge page could depend on other factors than just
>
On Wed, Oct 17, 2018 at 01:49:17PM +0530, Anshuman Khandual wrote:
>
>
> On 10/12/2018 09:29 AM, Anshuman Khandual wrote:
> > This patch series enables HugeTLB migration support for all supported
> > huge page sizes at all levels including contiguous bit implementation.
> > Following HugeTLB migr
When /tmp is mounted with noexec, mksyscalltbl fails.
[snip]
|perf-1.0/tools/perf/arch/arm64/entry/syscalls//mksyscalltbl:
/tmp/create-table-6VGPSt: Permission denied
[snip]
Add variable TMPDIR as prefix dir of the temporary file, if it is set,
replace default /tmp
Remove extra slash from `syscal
On Tue, 28 Aug 2018 13:22:49 -0400 Johannes Weiner wrote:
> This version 4 of the PSI series incorporates feedback from Peter and
> fixes two races in the lockless aggregator that Suren found in his
> testing and which caused the sample calculation to sometimes underflow
> and record bogusly larg
syzbot has found a reproducer for the following crash on:
HEAD commit:fa520c47eaa1 fscache: Fix out of bound read in long cookie..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=130da8ee40
kernel config: https://syzkaller.appspot.com/x/.config?x=b3f55c
On Wed, 26 Sep 2018 16:22:27 +0200 Michal Hocko wrote:
> > MPOL_PREFERRED is handled by policy_node() before we call
> > __alloc_pages_nodemask.
> > __GFP_THISNODE is applied only when we are not using
> > __GFP_DIRECT_RECLAIM which is handled in alloc_hugepage_direct_gfpmask
> > now.
> > Lastly
On Thu, Oct 18, 2018 at 09:31:35AM -0500, Rob Herring wrote:
> On Tue, 16 Oct 2018 10:58:37 +0800, Guo Ren wrote:
> > This patch adds the documentation to describe that how to add cpu nodes in
> > dts for SMP.
> >
> > Signed-off-by: Guo Ren
> > Cc: Rob Herring
> > ---
> > Changelog:
> > - Add c
On Thu, Oct 18, 2018 at 1:15 PM Bart Van Assche wrote:
>
> On Thu, 2018-10-18 at 12:38 -0700, Alexander Duyck wrote:
> > Basically if somebody loads a driver the dev->driver becomes set. If a
> > driver is removed it will clear dev->driver and set driver_data to
> > 0/NULL. That is what I am using
On Oct 18, 2018, at 7:11 AM, Miklos Szeredi wrote:
>
> Constants of the *_ALL type can be actively harmful due to the fact that
> developers will usually fail to consider the possible effects of future
> changes to the definition.
>
> Remove STATX_ALL from the uapi, while no damage has been done
On 10/18/18 7:20 PM, Alexander Duyck wrote:
I see what you are talking about now. Actually I think this was an
existing issue before my patch even came into play. Basically the code
as it currently stands is device specific in terms of the attach and
release code.
I wonder if we shouldn't have t
On 10/19/2018 07:29 AM, Naoya Horiguchi wrote:
> On Fri, Oct 12, 2018 at 09:29:56AM +0530, Anshuman Khandual wrote:
>> During huge page allocation it's migratability is checked to determine if
>> it should be placed under movable zones with GFP_HIGHUSER_MOVABLE. But the
>> movability aspect of t
On Fri, Oct 19, 2018 at 1:53 AM Borislav Petkov wrote:
>
> On Fri, Oct 19, 2018 at 01:39:21AM +0900, Masahiro Yamada wrote:
> > It is not realistic to enable this warning option by default.
>
> I believe the question is whether to enable that warning by default in
> KBUILD_HOSTCFLAGS. Enabling it
On Thu, Oct 18, 2018 at 11:04 AM Leonardo Bras wrote:
>
> Hello Helen,
>
> On Wed, Oct 17, 2018 at 12:06 AM Helen Koike wrote:
> >
> > Hi Leonardo,
> >
> > On 10/16/18 9:09 PM, Leonardo Brás wrote:
> > > Removes an unnecessary shadowed local variable (start).
> > > Optimize test of isdigi
On Thu, Oct 18, 2018 at 11:42 PM Masahiro Yamada
wrote:
> Adding -Wshadow to KBUILD_HOSTCFLAGS emits another warning in Kconfig.
> Of course, it is easy to fix.
For v2, I already replaced '-Wshadow=local' for '-Wshadow' and fixed this
warning.
> But, I just started to think this option is a kind
On 10/18/18 10:37, Wenwen Wang wrote:
> In coreboot_table_init(), a for loop is used to copy the entries of the
> coreboot table. For each entry, the header of the entry, which is a
> structure coreboot_table_entry and includes the size of the entry, is
> firstly copied from the IO region 'ptr_entr
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
tools/include/uapi/linux/kvm.h
between commit:
25fe15e54fe5 ("tools headers uapi: Sync kvm.h copy")
from the tip tree and commit:
c939989d74e2 ("tools/headers: update kvm.h")
from the kvm tree.
I fixed it up (the latt
On Thu, Oct 18, 2018 at 09:17:06AM -0400, Steven Rostedt wrote:
> On Thu, 18 Oct 2018 10:51:18 +0530
> Sai Prakash Ranjan wrote:
>
> > > So something else is causing an issue besides just msm_read.
> > >
> > > Can you do an objdump -dr of the entire vmlinux binary and gzip it and
> > > post it s
Jann Horn writes:
> On Wed, Oct 17, 2018 at 2:10 PM Michael Ellerman wrote:
>> Currently seq_buf_puts() will happily create a non NULL terminated
>> string for you in the buffer. This is particularly dangerous if the
>> buffer is on the stack.
>>
>> For example:
>>
>> char buf[8];
>> char sec
Currently seq_buf_puts() will happily create a non null-terminated
string for you in the buffer. This is particularly dangerous if the
buffer is on the stack.
For example:
char buf[8];
char secret = "secret";
struct seq_buf s;
seq_buf_init(&s, buf, sizeof(buf));
seq_buf_puts(&s, "foo")
Jann Horn points out that we're using unsigned int for len in
seq_buf_puts(), which could potentially overflow if we're passed a
UINT_MAX sized string.
The rest of the code already uses size_t, so we should also use that
in seq_buf_puts() to avoid any issues.
Suggested-by: Jann Horn
Signed-off-b
> On Oct 18, 2018, at 6:08 PM, Nadav Amit wrote:
>
> at 10:00 AM, Andy Lutomirski wrote:
>
>>
>>
>>> On Oct 18, 2018, at 9:47 AM, Nadav Amit wrote:
>>>
>>> at 8:51 PM, Andy Lutomirski wrote:
>>>
> On Wed, Oct 17, 2018 at 8:12 PM Nadav Amit wrote:
> at 6:22 PM, Andy Lutomirski wrote:
>
Hi Stefan,
I love your patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v4.19-rc8 next-20181018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
at 9:29 PM, Andy Lutomirski wrote:
>> On Oct 18, 2018, at 6:08 PM, Nadav Amit wrote:
>>
>> at 10:00 AM, Andy Lutomirski wrote:
>>
On Oct 18, 2018, at 9:47 AM, Nadav Amit wrote:
at 8:51 PM, Andy Lutomirski wrote:
>> On Wed, Oct 17, 2018 at 8:12 PM Nadav Amit wrote:
On 10/17/2018 10:02 PM, Tomas Winkler wrote:
diff --git a/drivers/char/tpm/tpm_i2c_nuvoton.c
b/drivers/char/tpm/tpm_i2c_nuvoton.c
index caa86b19c76d..f74f451baf6a 100644
--- a/drivers/char/tpm/tpm_i2c_nuvoton.c
+++ b/drivers/char/tpm/tpm_i2c_nuvoton.c
@@ -369,6 +369,7 @@ static int i2c_nuvoto
Hi James,
After merging the scsi tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/scsi/lpfc/lpfc_debugfs.c: In function 'lpfc_debugfs_nodelist_open':
drivers/scsi/lpfc/lpfc_debugfs.c:706:17: warning: 'nrport' may be used
uninitialized in this function [-Wma
On 10/18/18 6:47 PM, Andrew Morton wrote:
> On Thu, 18 Oct 2018 20:46:21 -0400 Andrea Arcangeli
> wrote:
>
>> On Thu, Oct 18, 2018 at 04:16:40PM -0700, Mike Kravetz wrote:
>>> I was not sure about this, and expected someone could come up with
>>> something better. It just seems there are filesy
On Fri, 2018-10-19 at 15:50 +1100, Stephen Rothwell wrote:
> Hi James,
>
> After merging the scsi tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/scsi/lpfc/lpfc_debugfs.c: In function
> 'lpfc_debugfs_nodelist_open':
> drivers/scsi/lpfc/lpfc_debugfs.c:
Commit 4d3ebd3658d8 ("coreisght: tmc: Claim device before use") uses
CLAIM tag to validate if the device is available, it needs to pass
the device base address to access related registers.
In the function tmc_etb_disable_hw() it wrongly passes the driver data
pointer as register base address, thus
Hi James,
On Thu, 18 Oct 2018 21:54:03 -0700 James Bottomley
wrote:
>
> It's the merge commit ... it was obviously the wrong choice; I'll fix
> it.
OK, thanks.
--
Cheers,
Stephen Rothwell
pgpS8HDlYzZFg.pgp
Description: OpenPGP digital signature
>
> >
> > Another example is __BPF_PROG_RUN_ARRAY(), which also uses
> > preempt_enable_no_resched().
>
> Alexei, I think this code is just wrong.
why 'just wrong' ?
> Do you know why it uses
> preempt_enable_no_resched()?
dont recall precisely.
we could be preemptable at the point where macro
This RFC provides implementation of WhiteEgret.
Signed-off-by: Shinya Takumi
---
security/Kconfig | 1 +
security/Makefile | 2 +
security/whiteegret/Kconfig| 82 +++
security/whiteegret/Makefile | 2 +
security/whiteegret/init.c
Hi Daniel,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.19-rc8 next-20181018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
A user application is required to use WhiteEgret.
This RFC provides a sample user application program.
Usage
sample-we-user
WhiteEgret is an LSM to simply provide a whitelisting-type
execution control.
An execution-whitelist, simply called whitelist, is a list
of executable components (e.g., applications, libraries)
that are approved to run on a host. The whitelist is used
to decide whether executable components are pe
On Tue, Oct 16, 2018 at 05:14:43PM -0700, Dmitry Torokhov wrote:
> synaptics_detect() does not check whether sending commands to the
> device succeeds and instead relies on getting unique data from the
> device. Let's make sure we seed entire buffer with zeroes to make sure
> we not use garbage on
Hi Daniel,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.19-rc8 next-20181018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Commit-ID: 485734f3fc77c1eb77ffe138c027b9a4bf0178f3
Gitweb: https://git.kernel.org/tip/485734f3fc77c1eb77ffe138c027b9a4bf0178f3
Author: Christoph Hellwig
AuthorDate: Sun, 14 Oct 2018 09:52:08 +0200
Committer: Ingo Molnar
CommitDate: Fri, 19 Oct 2018 07:49:32 +0200
x86/swiotlb: Enable s
On Thu, Oct 18, 2018 at 12:16:32PM +0100, Mel Gorman wrote:
> On Wed, Oct 17, 2018 at 10:59:04PM +0800, Aaron Lu wrote:
> > > Any particuular reason why? I assume it's related to the number of zone
> > > locks with the increase number of zones and the number of threads used
> > > for the test.
> >
* Eric W. Biederman wrote:
> tip-bot for Dave Hansen writes:
>
> > Commit-ID: aa37c51b9421d66f7931c5fdcb9ce80c450974be
> > Gitweb:
> > https://git.kernel.org/tip/aa37c51b9421d66f7931c5fdcb9ce80c450974be
> > Author: Dave Hansen
> > AuthorDate: Fri, 28 Sep 2018 09:02:23 -0700
> > Com
Hi Josh,
On Wed, Oct 17, 2018 at 1:16 AM Josh Poimboeuf wrote:
>
> On Wed, Oct 17, 2018 at 12:51:40AM +0900, Masahiro Yamada wrote:
> > > ifdef CONFIG_UNWINDER_ORC
> > >
> > > chk_unwinder_orc = echo "int main() {}" | $(HOSTCC) -xc -o /dev/null
> > > -lelf -
> > > msg_unwinder_orc = "Cannot bui
Hi, Sudeep,
I use MIPS, and there is no "size" in
/sys/devices/system/cpu/cpuX/cache/indexX/ file after your patch. Because the
DT node only has "next-level-cache = <&L2>;" but has no "size" information.
Huacai
-- Original --
From: "Sudeep Holla";
Date: Th
On 10/19/2018 9:47 AM, Joel Fernandes wrote:
On Thu, Oct 18, 2018 at 09:17:06AM -0400, Steven Rostedt wrote:
On Thu, 18 Oct 2018 10:51:18 +0530
Sai Prakash Ranjan wrote:
So something else is causing an issue besides just msm_read.
Can you do an objdump -dr of the entire vmlinux binary and gz
There is no point in taking the page table lock as pte_frag or
pmd_frag are always NULL when we have only one fragment.
Reviewed-by: Aneesh Kumar K.V
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/pgtable-book3s64.c | 3 +++
arch/powerpc/mm/pgtable-frag.c | 3 +++
2 files changed, 6 in
Hi Marcin,
Thank you for the patch! Perhaps something to improve:
url:
https://github.com/0day-ci/linux/commits/Marcin-Ciupak/staging-nrf24-add-new-driver-for-2-4GHz-radio-transceiver/20181018-164230
smatch warnings:
drivers/staging/nrf24/nrf24_if.c:538 nrf24_create_pipe() error: 'p
701 - 745 of 745 matches
Mail list logo