Remove memfd and file sealing routines from shmem.c and enable the
use of the new files (memfd.c and memfd.h). A new config option
MEMFD_CREATE is defined that is enabled if TMPFS -or- HUGETLBFS is
defined.
Signed-off-by: Mike Kravetz
---
fs/Kconfig | 3 +
fs/fcntl.c
HUGETLBFS_I will be referenced but not used in code outside #ifdef
CONFIG_HUGETLBFS. Move the definition to prevent compiler errors.
Signed-off-by: Mike Kravetz
---
include/linux/hugetlb.h | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/include/
When memfd_create support was originally written, it only provided
suport for tmpfs. Support has recently been added for hugetlbfs.
memfd originally depended on tmpfs. In an effort to make it depend
on tmpfs -or- hugetlbfs, split out the required code to separate
files.
Signed-off-by: Mike Krave
The way people generally use netlink_dump is that they fill in the skb
as much as possible, breaking when nla_put returns an error. Then, they
get called again and start filling out the next skb, and again, and so
forth. The mechanism at work here is the ability for the iterative
dumping function t
On Wed, Nov 08, 2017 at 08:46:26PM +0100, Luis R. Rodriguez wrote:
> On Wed, Nov 08, 2017 at 03:15:54PM +0900, AKASHI, Takahiro wrote:
> > Luis,
> >
> > Thank you for this heads-up.
> >
> > On Wed, Nov 08, 2017 at 12:07:00AM +0100, Luis R. Rodriguez wrote:
> > > On Thu, Nov 02, 2017 at 06:10:41PM
FYI, we noticed the following commit (built with gcc-5):
commit: 8e5bf9759a06be2251fa96cfd8b412f1808c62f9 ("net: dsa: simplify tree
reference counting")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu
Currently if a pointer is printed using %p[ssB] and the symbol is not
found (kallsyms_lookup() fails) then we print the actual address. This
leaks kernel addresses. We should instead print something _safe_.
Print "" instead of kernel address.
Signed-off-by: Tobin C. Harding
---
kernel/kallsyms.
From: Wanpeng Li
PV-Flush guest would indicate to flush on enter, flush the TLB before
entering and exiting the guest.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/x86.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/x8
Remote flushing api's does a busy wait which is fine in bare-metal
scenario. But with-in the guest, the vcpus might have been pre-empted
or blocked. In this scenario, the initator vcpu would end up
busy-waiting for a long amount of time.
This patch set implements para-virt flush tlbs making sure t
From: Wanpeng Li
Remote flushing api's does a busy wait which is fine in bare-metal
scenario. But with-in the guest, the vcpus might have been pre-empted
or blocked. In this scenario, the initator vcpu would end up
busy-waiting for a long amount of time.
This patch set implements para-virt flush
From: Wanpeng Li
This patch reuses the preempted field in kvm_steal_time, and will export
the vcpu running/pre-empted information to the guest from host. This will
enable guest to intelligently send ipi to running vcpus and set flag for
pre-empted vcpus. This will prevent waiting for vcpus tha
Hi Alexandre,
On 9 November 2017 at 09:26, Alexandre Belloni
wrote:
> Hi,
>
> On 08/11/2017 at 17:16:15 +0800, Baolin Wang wrote:
>> +static int sprd_rtc_read_time(struct device *dev, struct rtc_time *tm)
>> +{
>> + struct sprd_rtc *rtc = dev_get_drvdata(dev);
>> + time64_t secs;
>> +
On Wed, Nov 08, 2017 at 11:58:13AM +0530, Lingutla Chandrasekhar wrote:
> khungtask by default monitors all tasks for long unterruptible sleep.
> This change introduces a sysctl option, /proc/sys/kernel/
> hung_task_selective_monitoring, to enable monitoring selected tasks.
> If this sysctl option
From: Wanpeng Li
This patch reuses the preempted field in kvm_steal_time, and will export
the vcpu running/pre-empted information to the guest from host. This will
enable guest to intelligently send ipi to running vcpus and set flag for
pre-empted vcpus. This will prevent waiting for vcpus tha
Remote flushing api's does a busy wait which is fine in bare-metal
scenario. But with-in the guest, the vcpus might have been pre-empted
or blocked. In this scenario, the initator vcpu would end up
busy-waiting for a long amount of time.
This patch set implements para-virt flush tlbs making sure t
From: Wanpeng Li
PV-Flush guest would indicate to flush on enter, flush the TLB before
entering and exiting the guest.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/x86.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/x8
On Thu, 2017-11-09 at 10:42 +0900, Jason A. Donenfeld wrote:
> +++ b/net/netlink/af_netlink.c
> @@ -2136,7 +2136,7 @@ static int netlink_dump(struct sock *sk)
> struct sk_buff *skb = NULL;
> struct nlmsghdr *nlh;
> struct module *module;
> - int len, err = -ENOBUFS;
> + in
From: Wanpeng Li
Remote flushing api's does a busy wait which is fine in bare-metal
scenario. But with-in the guest, the vcpus might have been pre-empted
or blocked. In this scenario, the initator vcpu would end up
busy-waiting for a long amount of time.
This patch set implements para-virt flush
On 2017/11/8 22:30, Andrew Lunn wrote:
On Wed, Nov 08, 2017 at 03:52:22PM +0800, Lipeng wrote:
From: Fuyun Liang
Driver gets phy address from NCL_config file and uses the phy address
to initialize phydev. There are 5 bits for phy address. And C22 phy
address has 5 bits. So 0-31 are all valid
On Thu, Nov 09, 2017 at 11:49:52AM +1100, Michael Ellerman wrote:
> "Tobin C. Harding" writes:
>
> > On Wed, Nov 08, 2017 at 11:10:56PM +1100, Michael Ellerman wrote:
> >> "Tobin C. Harding" writes:
> > [snip]
> >
> > Hi Michael,
> >
> > I'm working an adding support for ppc64 to leaking_address
On Wed, 2017-11-08 at 19:10 -0600, Rob Herring wrote:
> Add a check warning if SPDX-License-Identifier tags are not used in
> newly added files.
If this is to be done, and I think it's not a great idea,
there are better ways of doing this that emit this warning
on a per-file basis instead of a per
> > IMHO that should just fail then, ie, a "locked down" kernel should not want
> > to
> > *pass* a firmware signature if such thing could not be done.
> >
> > Its no different than trying to verify a signed module on a "locked down"
> > for
> > which it has no signature.
> >
> > But perhaps I'
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
arch/arm64/boot/dts/allwinner/Makefile
between commit:
d7341305863b ("arm64: allwinner: h5: add NanoPi NEO Plus2 DT support")
from the arm-soc tree and commit:
4408a86af32e ("kbuild: handle dtb-y and CONFIG_OF_AL
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
arch/arm64/boot/dts/amlogic/Makefile
between commit:
593d311d9f17 ("ARM64: dts: meson-gxm: Add Vega S96 board")
from the arm-soc tree and commit:
4408a86af32e ("kbuild: handle dtb-y and CONFIG_OF_ALL_DTBS nativel
On Wed, Nov 8, 2017 at 4:43 PM, Patrick McLean wrote:
> As of 4.13.11 (and also with 4.14-rc) we have an issue where when
> serving nfs4 sometimes we get the following BUG. When this bug happens,
> it usually also causes the motherboard to no longer POST until we
> externally re-flash the BIOS (us
Of course, if it's bisectable, that would be great too.
Yes, bisect is on the way. So far it's bisecting in the 4.12 commits.
The bisect was unsuccessful due to an unrelated DRM_BOCHS oops in 4.11.
Disabling the buggy driver, I managed to reproduce the
vlan_device_event bug in 4.11. However on
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 703509
Addresses-Coverity-ID: 703510
Addresses-Coverity-ID: 703511
Addresses-Coverity-ID: 703512
Addresses-Coverity-ID: 703513
Signed-off-by: Gustavo A. R. Silva
---
From: Wanpeng Li
watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185]
CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE 4.14.0-rc4+
#4
RIP: 0010:kvm_get_time_scale+0x4e/0xa0 [kvm]
Call Trace:
? get_kvmclock_ns+0xa3/0x140 [kvm]
get_time_ref_counter+0x5
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114767
Addresses-Coverity-ID: 114768
Addresses-Coverity-ID: 114769
Signed-off-by: Gustavo A. R. Silva
---
drivers/input/joystick/spaceball.c | 4
1 file change
On Thu, Nov 9, 2017 at 11:02 AM, Johannes Berg
wrote:
> nit: I think your line got a little long here :)
Ack. For v4.
> and here
Ack. For v4.
>
>> + nlk->dump_done_errno = INT_MAX;
>
> I guess positive values aren't really returned from dump?
When a positive value is returned, the API use
Allow sched_clock() to be used before schec_clock_init() and
sched_clock_init_late() are called. This provides us with a way to get
early boot timestamps on machines with unstable clocks.
Signed-off-by: Pavel Tatashin
---
kernel/sched/clock.c | 10 --
1 file changed, 8 insertions(+), 2 d
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114763
Addresses-Coverity-ID: 114764
Addresses-Coverity-ID: 114765
Addresses-Coverity-ID: 114766
Signed-off-by: Gustavo A. R. Silva
---
drivers/input/joystick/sidew
changelog
-
v8 - v7
- Addressed comments from Dou Liyang:
- Moved tsc_early_init() and tsc_early_fini() to be all inside
tsc.c, and changed them to be static.
- Removed warning when notsc parameter is used.
- Merged with:
https://git.kerne
Hi Ingo,
On Wed, 8 Nov 2017 10:18:28 +0100 Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > On Wed, Nov 08, 2017 at 01:47:17PM +1100, Stephen Rothwell wrote:
> >
> > Does this fix it?
> >
> > diff --git a/tools/objtool/Makefile b/tools/objtool/Makefile
> > index 6aaed251b4ed..0f94af3cca
tsc_disabled is set when notsc is passed as kernel parameter. The reason we
have notsc is to avoid timing problems on multi-socket systems. We already
have a mechanism, however, to detect and resolve these issues by invoking
tsc unstable path. Thus, make notsc to behave the same as tsc=unstable.
read_boot_clock64() returns time of when system was started. Now, that
early boot clock is going to be available on x86 it is possible to
implement x86 specific version of read_boot_clock64() that takes advantage
of this new feature.
Signed-off-by: Pavel Tatashin
---
arch/x86/kernel/time.c | 30
Early boot clock might differ from the clock that is used later on,
therefore add a new field to pv_time_ops, that shows currently active
clock. If platform supports early boot clock, this field will be changed
to use that clock early in boot, and later will be replaced with the
permanent clock.
S
read_boot_clock64() returns a boot start timestamp from epoch. Some arches
may need to access the persistent clock interface in order to calculate the
epoch offset. The resolution of the persistent clock, however, might be
low. Therefore, in order to avoid time discrepancies a new argument 'now'
i
This patch adds early clock feature to x86 platforms.
tsc_early_init():
Determines offset, shift and multiplier for the early clock based on the
TSC frequency.
tsc_early_fini()
Implement the finish part of early tsc feature, prints message about the
offset, which can be useful to find out how muc
Hi Changcheng,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.14-rc8]
[cannot apply to next-20171108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
This patch adds following related changes:
- defines pulse event related registers
- enables and handles single pulse interrupt for fxls8471
- handles IIO_EV_DIR_EITHER in read/write callbacks (because
event direction for pulse is either rising or falling)
- configures read/write event value for
Hi Martin,
Thanks for publishing the patch.
I will work on it, but unfortunately I can't promise anything before 11/27.
Thanks,
Harinath
On Mon, Nov 6, 2017 at 2:19 AM, Martin Kepplinger wrote:
> This adds the power_mode sysfs interface to the device as documented in
> sysfs-bus-iio.
>
> ---
>
From: Qiuyang Sun
Currently, a multi-device F2FS only has superblocks written in its start
device, but not the others. Thus, we cannot tell if a single device is part
of a F2FS by reading itself only, which may be unsafe in scenarios like
transferring devices between computer systems. This patch
On Thu, Nov 09, 2017 at 09:55:41AM +0900, Mahesh Bandewar (महेश बंडेवार) wrote:
> On Thu, Nov 9, 2017 at 4:02 AM, Christian Brauner
> wrote:
> > On Wed, Nov 08, 2017 at 03:09:59AM -0800, Mahesh Bandewar (महेश बंडेवार)
> > wrote:
> >> Sorry folks I was traveling and seems like lot happened on this
Hi Changcheng,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.14-rc8]
[cannot apply to next-20171108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
The synchronize_rcu() in namespace_unlock() is called every time
a filesystem is unmounted. If a great many filesystems are mounted,
this can cause a noticable slow-down in, for example, system shutdown.
The sequence:
mkdir -p /tmp/Mtest/{0..5000}
time for i in /tmp/Mtest/*; do mount -t tmpfs
Hi
these three patches are all completely separate, but are
all related to the VFS. I've posted them all previously
but with, as yet, no response (except an ack from Paul McKenney
for the RCU one). One was, admitted, posted early last year...
I would appreciate review and, hopefully, accept
bit-spin-locks, as used for dcache hash chains, are not fair.
This is not a problem for the dcache hash table as different CPUs are
likely to access different entries in the hash table so high contention
is not expected.
However anonymous dentryies (created by NFSD) all live on a single hash
chain
d_move() will call __d_drop() and then __d_rehash()
on the dentry being moved. This creates a small window
when the dentry appears to be unhashed. Many tests
of d_unhashed() are made under ->d_lock and so are safe
from racing with this window, but some aren't.
In particular, getcwd() calls d_unli
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114761
Addresses-Coverity-ID: 114762
Signed-off-by: Gustavo A. R. Silva
---
drivers/input/joystick/gamecon.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/
ing to improve:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v4.14-rc8]
> [cannot apply to next-20171108]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0d
On Thu, 9 Nov 2017 09:56:35 +0900
Sergey Senozhatsky wrote:
> Hello Steven,
>
> On (11/08/17 09:29), Steven Rostedt wrote:
> > On Wed, 8 Nov 2017 14:19:55 +0900
> > Sergey Senozhatsky wrote:
> >
> > > the change goes further. I did express some of my concerns during the KS,
> > > I'll just b
On Thu, Nov 09, 2017 at 10:02:37AM +0800, lipeng (Y) wrote:
>
>
> On 2017/11/8 22:30, Andrew Lunn wrote:
> >On Wed, Nov 08, 2017 at 03:52:22PM +0800, Lipeng wrote:
> >>From: Fuyun Liang
> >>
> >>Driver gets phy address from NCL_config file and uses the phy address
> >>to initialize phydev. There
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:29 EET H. Nikolaus Schaller wrote:
> The vendor name was "toppoly" but other panels and the vendor list
> have defined it as "tpo". So let's fix it in driver and bindings.
>
> Signed-off-by: H. Nikolaus Schaller
> ---
>
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:31 EET H. Nikolaus Schaller wrote:
> We can remove the "omapdss," prefix.
I agree but you should explain why.
> Signed-off-by: H. Nikolaus Schaller
> ---
> arch/arm/boot/dts/omap3-pandora-common.dtsi | 2 +-
> 1 file ch
On Thu, 9 Nov 2017 12:50:29 +1100
"Tobin C. Harding" wrote:
> Currently if a pointer is printed using %p[ssB] and the symbol is not
> found (kallsyms_lookup() fails) then we print the actual address. This
> leaks kernel addresses. We should instead print something _safe_.
>
> Print "" instead o
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 115106
Signed-off-by: Gustavo A. R. Silva
---
net/decnet/dn_table.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/decnet/dn_table.c b/net/decnet/dn_table.
This patch adds the Spreadtrum RTC driver, which embedded in the
Spreadtrum SC27xx series PMICs.
Signed-off-by: Baolin Wang
---
Changes since v2:
- Add checking if RTC values are valid.
Changes since v1:
- Change file name.
- Should depend on the MFD parent.
- Add more help documentation.
-
This patch adds the binding documentation for Spreadtrum SC27xx series
RTC device.
Signed-off-by: Baolin Wang
---
Changes since v2:
- No updates.
Changes since v1:
- Use a specific chip name as compatible string.
- Remove useless alias.
- Add the parent MFD node.
---
.../devicetree/bindings
On Wed, Nov 8, 2017 at 12:56 PM, Andi Kleen wrote:
>> diff --git a/tools/perf/Documentation/perf-record.txt
>> b/tools/perf/Documentation/perf-record.txt
>> index 5a626ef666c2..3b156fa03c99 100644
>> --- a/tools/perf/Documentation/perf-record.txt
>> +++ b/tools/perf/Documentation/perf-record.txt
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114891
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/8390/pcnet_cs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/8390/pcn
On Wed, Nov 08, 2017 at 06:40:22PM -0800, Linus Torvalds wrote:
> > Here is the BUG we are getting:
> >> [ 58.962528] BUG: unable to handle kernel NULL pointer dereference at
> >> 0230
> >> [ 58.963918] IP: vfs_statfs+0x73/0xb0
>
> The code disassembles to
>
>0: 83 c9 08
On Thu, Nov 09, 2017 at 09:36:39AM +0900, Joonsoo Kim wrote:
> On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote:
> > * Joonsoo Kim [171109 00:05]:
> > > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote:
> > > > * Joonsoo Kim [171108 07:43]:
> > > > > On Tue, Nov 07, 2017
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:32 EET H. Nikolaus Schaller wrote:
> commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to
> dpi code")
>
> introduced a new match table which turned out to be wrong, at least
> for the 600 MHz OpenPan
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114888
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/3com/3c574_cs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/3com/3c5
Hi Linus,
On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell
wrote:
>
> After merging the gpio tree, yesterday's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
>
> arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_property): Missing
> property '#phy-cells' in node /phy o
On Thursday, November 9, 2017 4:03:06 AM IST Stephen Rothwell wrote:
> Hi Miklos,
>
> After merging the overlayfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/overlayfs/super.c: In function 'ovl_fill_super':
> fs/overlayfs/super.c:1070:25: warning: 'num
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/pi433/pi433_if.c
between commit:
f81f0b5c9a30 ("pi433: sanitize ioctl")
from the vfs tree and commit:
69af5d92da20 ("Staging: pi433: Fix the position of brace after if")
from the staging tree.
I f
The way people generally use netlink_dump is that they fill in the skb
as much as possible, breaking when nla_put returns an error. Then, they
get called again and start filling out the next skb, and again, and so
forth. The mechanism at work here is the ability for the iterative
dumping function t
On Thu, Nov 09, 2017 at 11:12:06AM +0800, Fengguang Wu wrote:
Hi Alex,
So looking over the trace the panic seems to be happening after a
decnet interface is getting deleted. Is there any chance we could try
compiling the kernel without decnet support to see if that is the
source of these issues
2017-11-08 2:37 GMT+09:00 Nick Desaulniers :
> On Sat, Nov 4, 2017 at 8:06 PM, Masahiro Yamada
> wrote:
>> ld-option is only used for arch/{arm64,powerpc}/Makefile
>>
>> arch/arm64/Makefile: ifeq ($(call ld-option, --fix-cortex-a53-843419),)
>> arch/powerpc/Makefile:LDFLAGS_vmlinux += $(call
>> l
On (11/08/17 22:35), Steven Rostedt wrote:
> On Thu, 9 Nov 2017 12:50:29 +1100
> "Tobin C. Harding" wrote:
>
> > Currently if a pointer is printed using %p[ssB] and the symbol is not
> > found (kallsyms_lookup() fails) then we print the actual address. This
> > leaks kernel addresses. We should
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114928
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/wan/x25_asy.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wan/x25_asy.c b/drivers/net/
On Wed, Nov 08, 2017 at 10:33:51PM +0900, Jaewon Kim wrote:
> 2017-11-08 16:52 GMT+09:00 Joonsoo Kim :
> > On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote:
> >> online_page_ext and page_ext_init allocate page_ext for each section, but
> >> they do not allocate if the first PFN is !pfn_pr
On Wed, Nov 08, 2017 at 03:21:06PM +0100, Michal Hocko wrote:
> On Wed 08-11-17 16:59:56, Joonsoo Kim wrote:
> > On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote:
> > > [CC Joonsoo]
> > >
> > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote:
> > > > online_page_ext and page_ext_init alloca
Hi Nick
2017-11-08 4:46 GMT+09:00 Nick Desaulniers :
> From: Chris Fries
>
> Set the clang KBUILD_CFLAGS up before including arch/ Makefiles,
> so that ld-options (etc.) can work correctly.
>
> This fixes errors with clang such as ld-options trying to CC
> against your host architecture, but LD t
On Thu, Oct 26, 2017 at 6:16 PM, Martin Schwidefsky
wrote:
> On Thu, 26 Oct 2017 17:47:39 +0800
> Li Wang wrote:
>
>> On Thu, Oct 26, 2017 at 5:26 PM, Martin Schwidefsky
>> wrote:
>> > On Thu, 26 Oct 2017 15:36:10 +0800
>> > Li Wang wrote:
>> >
>> > The code in mmap.c checks for the per-task li
On Wed, Nov 08, 2017 at 06:52:12PM -0800, Wanpeng Li wrote:
> From: Wanpeng Li
>
> watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185]
> CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE
> 4.14.0-rc4+ #4
> RIP: 0010:kvm_get_time_scale+0x4e/0xa0 [kvm]
> C
Mimi,
On Wed, Nov 08, 2017 at 09:17:37PM -0500, Mimi Zohar wrote:
> > > IMHO that should just fail then, ie, a "locked down" kernel should not
> > > want to
> > > *pass* a firmware signature if such thing could not be done.
> > >
> > > Its no different than trying to verify a signed module on a
> But I don't know if there is anything else than the profiling code
> that _really_ wants access to /proc/kallsyms in user space as a
> regular user.
Am unsure about this, but kprobes? (/jprobes/kretprobes), and by
extension, wrappers over this infra (like SystemTap)?
I (hazily) recollect a scrip
On (11/08/17 22:29), Steven Rostedt wrote:
> > On (11/08/17 09:29), Steven Rostedt wrote:
> > > On Wed, 8 Nov 2017 14:19:55 +0900
> > > Sergey Senozhatsky wrote:
> > >
> > > > the change goes further. I did express some of my concerns during the
> > > > KS,
> > > > I'll just bring them to the
> On Nov 9, 2017, at 3:02 AM, Andi Kleen wrote:
>
>> There's the series from Andi Kleen that enables LTO for Linux on x86:
>> https://lwn.net/Articles/512548/
>> https://github.com/andikleen/linux-misc/tree/lto-411-1
>>
>> It has solved many problems you also try to solve, and some patches
>> ar
There is no way a timer used as broadcast clockevent device is also used as
percpu tick clockevent device currently.
It's better to put related code in tick_install_broadcast_device(), but I feel
it's harmless to give it back to the clockevents layer. Pls correct me if I'm
wrong.
Signed-off-by: Z
On Thu, Nov 9, 2017 at 10:13 AM, Kaiwan N Billimoria
wrote:
>> But I don't know if there is anything else than the profiling code
>> that _really_ wants access to /proc/kallsyms in user space as a
>> regular user.
>
Front-ends to ftrace, like trace-cmd?
[from the trace-cmd git repo (Steve Rostedt
On Thu, 9 Nov 2017 13:45:48 +0900
Sergey Senozhatsky wrote:
>
> so what we are looking at
>
>a) we take over printing. can be from safe context to unsafe context
> [well, bad karma]. can be from unsafe context to a safe one. or from
> safe context to another safe context... or fr
1) Fix use-after-free in IPSEC input parsing, desintation address
pointer was loaded before pskb_may_pull() which can change the
SKB data pointers. From Florian Westphal.
2) Stack out-of-bounds read in xfrm_state_find(), from Steffen
Klassert.
3) IPVS state of SKB is not properly reset
This series adds summary reporting to the script. First we do some clean
up. Then we implement changes that were first posted as
[PATCH v4] scripts: add leaking_addresses.pl
Additionally; files (and paths) to skip is amended, thanks to Michael
Ellerman and Kees Cook.
Support for scanning PowerPC
Current code uses spaces instead of tabs in places.
Use tabs instead of spaces.
Signed-off-by: Tobin C. Harding
---
scripts/leaking_addresses.pl | 54 ++--
1 file changed, 27 insertions(+), 27 deletions(-)
diff --git a/scripts/leaking_addresses.pl b/scri
There are a couple more files that cause the script to stall.
/sys/firmware/devicetree and its symlink /proc/device-tree, reported by
Michael Ellerman.
usbmon should be skipped were ever it appears. Reported by Kees Cook
Add files to be excluded from parsing.
Signed-off-by: Tobin C. Harding
--
Currently script just dumps all results found. Potentially, this risks
losing single results among multiple duplicate results. We need some
way of restricting duplicates to assist users of the script. It would
also be nice if we got a report instead of raw results.
Duplicates can be defined in var
Currently script accepts files to skip. This was added to make running
the script faster (for repeat runs). We can remove this functionality in
preparation for adding sub commands (scan and format) to the script.
Remove command line options.
Signed-off-by: Tobin C. Harding
---
scripts/leaking_a
Currently script is targeted at x86_64. We can support other
architectures by using the correct regular expressions for each
architecture.
Add the infrastructure to support multiple architectures. Add support
for ppc64.
Signed-off-by: Tobin C. Harding
---
scripts/leaking_addresses.pl | 66 +
Currently script can stall if we read certain files (like
/proc/kmsg). While we have a mechanism to skip these files once they are
discovered it would be nice to not stall on as yet undiscovered files of
this kind.
Set a timer before each file is parsed, warn user if timer expires.
Suggested-by:
Fix typo in comment string.
Signed-off-by: Tobin C. Harding
---
scripts/leaking_addresses.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/leaking_addresses.pl b/scripts/leaking_addresses.pl
index 719ed0aaede7..3f8c6e230962 100755
--- a/scripts/leaking_addresses.pl
debug_arrays is not called. Also, %seen hash is not used. We should
remove unused code.
Remove dead code.
Signed-off-by: Tobin C. Harding
---
scripts/leaking_addresses.pl | 9 -
1 file changed, 9 deletions(-)
diff --git a/scripts/leaking_addresses.pl b/scripts/leaking_addresses.pl
inde
Hi Masahiro.
Thanks for picking this up.
> A key point is, the parent Makefile knows whether built-in.o is needed
> or not. If a subdirectory needs to create built-in.o, its parent can
> tell the fact when Kbuild descends into it.
Good observation!
>
> diff --git a/Makefile b/Makefile
> index 0
On (11/09/17 00:06), Steven Rostedt wrote:
> What does safe context mean?
"safe" means that we don't cause lockups, stalls, sched throttlings, etc.
by doing console_unlock() from that context [task].
> Do we really want to allow the printk thread to sleep when there's more
> to print? What happe
Are there any issues with this patch
(https://patchwork.kernel.org/patch/9938919/) that Pavel Tikhomirov submitted
back in September? I am willing to help if there's anything I can do to help
get it accepted.
The failing case I'm working on involves lots of servers with disk read/write
activ
Hi Russel,
> Am 08.11.2017 um 23:38 schrieb Russell King - ARM Linux
> :
>
> On Wed, Nov 08, 2017 at 10:36:04PM +, Russell King - ARM Linux wrote:
>> We don't need a compiler warning there, we probably need better help
>> text against DEBUG_LL and against EARLY_PRINTK.
>
> Actually, this is
On Wed, Nov 08, 2017 at 10:35:55PM -0500, Steven Rostedt wrote:
> On Thu, 9 Nov 2017 12:50:29 +1100
> "Tobin C. Harding" wrote:
>
> > Currently if a pointer is printed using %p[ssB] and the symbol is not
> > found (kallsyms_lookup() fails) then we print the actual address. This
> > leaks kernel
501 - 600 of 1209 matches
Mail list logo
