On Fri, 12 May 2017, Florian Fainelli wrote:
> On 05/12/2017 09:22 AM, David Miller wrote:
> > From: Julia Lawall
> > Date: Fri, 12 May 2017 22:54:23 +0800 (SGT)
> >
> >> Device node iterators put the previous value of the index variable, so an
> >> explicit put causes a double put.
> > ...
>
On Fri, May 12, 2017 at 05:46:06PM +0200, Matthias Brugger wrote:
On 12/05/17 12:46, kbuild test robot wrote:
Hi John,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.11 next-20170512]
[if your patch is applied to the wrong git tree, please drop us a note to help
On Sat, May 13, 2017 at 12:53:57AM +0100, Ian Campbell wrote:
> It not necessary and counter to how all the other files are done.
>
> It also happens to break the build in the split device tree repo
> https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/
>
> Signed-o
merged into cifs-2.6.git for-next
On Tue, May 9, 2017 at 11:26 PM, Shirish Pargaonkar
wrote:
> Looks correct.
>
> Acked-by: Shirish Pargaonkar
>
> On Sun, May 7, 2017 at 3:31 AM, Joe Perches via samba-technical
> wrote:
>> Create an ops variable to store tcon->ses->server->ops and cache
>> indi
So I should have asked earlier, but I was feeling rather busy during
the early merge window..
On Sun, Apr 30, 2017 at 8:45 PM, Al Viro wrote:
> uaccess unification pile. It's _not_ the end of uaccess work, but
> the next batch of that will go into the next cycle. This one mostly takes
>
sched_find_first_bit() is in fact the unrolled version of
find_first_bit(), which is theoretically faster in some cases.
But in the kernel it is called only in couple places in
kernel/sched/rt.c, and both of them are not looking like hot
paths that will doubtly achieve measurable benefit from usin
Hi Linu,
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on v4.11 next-20170512]
[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/Geetha-sowjanya/Cavium-ThunderX2-SMMUv3
merged into cifs-2.6.git for-next
On Thu, May 11, 2017 at 6:53 PM, Karim Eshapa wrote:
> Use time_after kernel macro for time comparison
> that has safety check.
>
> Signed-off-by: Karim Eshapa
> ---
> fs/cifs/transport.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/
Merged into cifs-2.6.git for-next
On Fri, May 12, 2017 at 10:59 AM, Christophe JAILLET
wrote:
> In fs/cifs/smb2pdu.h, we have:
> #define SMB2_SHARE_TYPE_DISK0x01
> #define SMB2_SHARE_TYPE_PIPE0x02
> #define SMB2_SHARE_TYPE_PRINT 0x03
>
> Knowing that, with the current code, the SMB2_SHA
Fixes a 'code indent should use tabs where possible' checkpatch code
style error by changing whitespace into tabs.
Signed-off-by: Remco Verhoef
---
Changes in v2:
- More expressive commit message and subject
drivers/staging/rtl8188eu/hal/rtl8188e_rxdesc.c | 2 +-
1 file changed, 1 insertion(+
On Sat, May 13, 2017 at 01:53:40AM +0300, Cyrill Gorcunov wrote:
> On Sat, May 13, 2017 at 12:41:30AM +0200, Jann Horn wrote:
> > [resending as plaintext]
> >
> > I realize that the existing kcmp code has the same issue, but:
> >
> > Why are you not taking a reference to filp or filp_tgt? This ca
fs/overlayfs/namei.c now calls exportfs_decode_fh() and
fs/overlayfs/copy_up.c calls exportfs_encode_fh() but misses an EXPORTFS
select which results in the following build error:
fs/built-in.o: In function `ovl_get_origin':
/home/florian/dev/linux/fs/overlayfs/namei.c:141: undefined reference to
I run kernel 4.11.0-4 on a Supermicro X10SAT motherboard.
HPET's enabled in BIOS, and apparently firmware table data is available.
But, hpet is not an available_clocksource.
Where's this need to be addressed/fixed? In my config, in kernel code, &/or in
BIOS?
info:
@ the mobo,
dmidec
On 05/11/2017 07:11 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.28 release.
There are 103 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/mmc/core/block.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c
index 8273b07..47ccb2a 100644
---
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
security/keys/keyctl.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/security/keys/keyctl.c b/security/keys/keyctl.c
index dd0da25..ce1574a 100644
--- a/securit
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/usb/misc/iowarrior.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/misc/iowarrior.c b/drivers/usb/misc/iowarrior.c
index 7756953..816afad 10
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/usb/gadget/function/f_fs.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/gadget/function/f_fs.c
b/drivers/usb/gadget/function/f_fs.c
index
On Sat, May 13, 2017 at 6:03 AM, kbuild test robot wrote:
> Hi Linu,
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on v4.11 next-20170512]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
&g
We use a directory under arch/$ARCH/boot/dts as an include path
that has links outside of the subtree to find dt-bindings from under
include/dt-bindings. That's been working well, but new DT architectures
haven't been adding them by default.
Recently there's been a desire to share some of the DT m
For EFI with 'efi=old_map' kernel option specified, Kernel will panic
when kaslr is enabled.
The back trace is:
BUG: unable to handle kernel paging request at 7febd57e
IP: 0x7febd57e
PGD 1025a067
PUD 0
Oops: 0010 [#1] SMP
[ ... ]
Call Trace:
? efi_call+0x58/0x90
? printk+0x58/0x6f
efi
Rob Landley writes:
> On 05/12/2017 09:45 AM, Eric W. Biederman wrote:
>> Thomas Gleixner writes:
>>
>>> On Fri, 12 May 2017, Michael Ellerman wrote:
Fixes: BKrev: 3e8e57a1JvR25MkFRNzoz85l2Gzccg ("[PATCH]
linux-2.5.66-signal-cleanup.patch")
In your tree that is c3c1070516
Braces around the error patch for metadata pre-allocation are wrongly
placed. This causes a memory leak in case of a memory allocation
failure. Fix it
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-init.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletio
Hi, Omar!
> On Fri, 12 May 2017 15:23:07 -0700, Omar Sandoval wrote:
> Hi,
> Linux kernel commit 4027494ae6e3 ("ARM: dts: add arm/arm64 include
> symlinks") introduced a couple of symlink cycles:
> $ ls -al arch/arm{,64}/boot/dts/include
> arch/arm64/boot/dts/include:
> total 12
> dr
On Fri, May 12, 2017 at 04:38:31PM -0700, Josh Zimmerman wrote:
> The TPM class has some common shutdown code that must be executed for
> all drivers. This adds some needed functionality for that.
>
> (In addition, update a comment to reflect an out-of-date path.)
Change that in a different patch
People reported kernel panic occurs during system boots up with mem boot option.
After checking code, several problems are found about memmap= and mem= in boot
stage
kaslr.
*) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only
one memmap
entry is considered and only th
Option mem= will limit the max address a system can use and any memory
region above the limit will be removed.
Furthermore, memmap=nn[KMG] which has no offset specified has the same
behaviour as mem=.
KASLR needs to consider this when choosing the random position for
decompressing the kernel. Do
In commit:
f28442497b5c ("x86/boot: Fix KASLR and memmap= collision")
... the memmap= option is parsed so that KASLR can avoid those reserved
regions. It uses cmdline_find_option() to get the value if memmap=
is specified, however the problem is that cmdline_find_option() can only
find the last
In commit:
9710f581bb4c ("x86, mm: Let "memmap=" take more entries one time")
... 'memmap=' was changed to adopt multiple, comma delimited values in a
single entry, so update the related description.
In the special case of only specifying size value without an offset,
like memmap=nn[KMG], memm
Fixed coding style issues.
Signed-off-by: Alberto Ladron
---
drivers/usb/class/usblp.c | 32 +---
1 file changed, 21 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/class/usblp.c b/drivers/usb/class/usblp.c
index fb87c17..b1879ff 100644
--- a/drivers/usb/clas
On Sat, May 13, 2017 at 5:17 AM, Florian Fainelli wrote:
> fs/overlayfs/namei.c now calls exportfs_decode_fh() and
> fs/overlayfs/copy_up.c calls exportfs_encode_fh() but misses an EXPORTFS
> select which results in the following build error:
>
Arnd has already sent that patch 2 days ago, but Tha
On Fri, May 12, 2017 at 06:45:09PM -0700, Andrei Vagin wrote:
> On Sat, May 13, 2017 at 01:53:40AM +0300, Cyrill Gorcunov wrote:
> > On Sat, May 13, 2017 at 12:41:30AM +0200, Jann Horn wrote:
> > > [resending as plaintext]
> > >
> > > I realize that the existing kcmp code has the same issue, but:
Hi Mauro,
[auto build test WARNING on linus/master]
[also build test WARNING on next-20170512]
[cannot apply to v4.11]
[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/Mauro-Carvalho-Chehab/docs
On Fri, May 12, 2017 at 06:00:44PM -0700, Linus Torvalds wrote:
> So I should have asked earlier, but I was feeling rather busy during
> the early merge window..
> So I'm actually more interested to hear if you have any pending work
> on cleaning up the __get/put_user() mess we have. Is that on yo
601 - 634 of 634 matches
Mail list logo
