On Mon, Nov 13, 2017 at 07:02:21AM +0100, Michael Kerrisk (man-pages) wrote:
> Hello Ram,
>
> Long ago (2.6.29) you added the /proc/PID/mountinfo file and
> associated documentation in Documentation/filesystems/proc.txt. Later,
> I pasted much of that documentation into the proc(5) manual page.
>
Linus,
Please pull the latest ras-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus
# HEAD: 783ca517bfd62ca516178712775e4b273292d5b1 x86/MCE/AMD: Fix
mce_severity_amd_smca() signature
Two minor updates to AMD SMCA support, plus a t
Marc-Andre,
It looks to me that the 4th and 5th patches somehow has not been sent.
Could you send them, too?
I'd like them to actually build and run the kernel for testing.
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org
> [mailto:linux-kernel-ow...@vger.kernel.org] On Beh
Linus,
Please pull the latest perf-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-for-linus
# HEAD: fcdfafcb73be8fa45909327bbddca46fb362a675 kprobes: Don't spam the
build log with deprecation warnings
The main changes in this cycle were:
Perf tool fails with following build failure when AUXTRACE is
not set:
$ make NO_AUXTRACE=1
builtin-script.c: In function 'perf_script__process_auxtrace_info':
util/auxtrace.h:608:44: error: called object is not a function or function
pointer
#define perf_event__process_auxtrace_info 0
On Sun, Nov 12, 2017 at 11:09:23AM -0800, Milind Chabbi wrote:
> ,
>
> On Thu, Nov 9, 2017 at 10:59 AM, Milind Chabbi
> wrote:
> > SNIP
> >
> > On Thu, Nov 9, 2017 at 5:12 AM, Jiri Olsa wrote:
> >>
> >>
> >> how about something like below (untested)
> >>
> >> looks like there's no irq caller f
Hi Linus:
Here is the crypto update for 4.15:
API:
- Disambiguate EBUSY when queueing crypto request by adding ENOSPC.
This change touches code outside the crypto API.
- Reset settings when empty string is written to rng_current.
Algorithms:
- Add OSCCA SM3 secure hash.
Drivers:
- Remove
The driver as well as the controller support the SPI lsb first
mode. However, it's not possible to configure it e.g. when using
spidev. Adding this flag to mode_bits resolves the issue and lsb first
mode can be used.
Signed-off-by: Kurt Kanzenbach
---
drivers/spi/spi-fsl-dspi.c | 2 +-
1 file ch
Hi Kevin & others
I'd like to just re-send the patch [4/4] (while leave others[1-3/4]
unchanged), to have separated DT patch the for 32bit / 64bit platform.
is this ok for you?
On 11/12/17 09:33, Martin Blumenstingl wrote:
> Hi Yixun,
>
> On Tue, Nov 7, 2017 at 3:10 PM, Yixun Lan wrote:
>>
Hello Michal,
> Date: Fri, 13 Oct 2017 14:00:12 +0200
>
> From: Michal Hocko
>
> Michael has noticed that the memory offline tries to migrate kernel code
> pages when doing echo 0 > /sys/devices/system/memory/memory0/online
>
> The current implementation will fail the operation after severa
Linus,
Please pull the latest locking-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-core-for-linus
# HEAD: 450cbdd0125cfa5d7bbf9e2a6b6961cc48d29730 locking/x86: Use LOCK ADD
for smp_mb() instead of MFENCE
The main changes in this cycle a
Hi,
Please pull these hardened usercopy whitelisting changes for v4.15-rc1.
This significantly narrows the areas of memory that can be copied to/from
userspace in the face of usercopy bugs.
Thanks!
-Kees
The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:
Linux 4.14-
Hi Cao,
2017-11-10 19:58 GMT+09:00 Cao jin :
> Masahiro-san
>
> On 11/09/2017 11:41 PM, Masahiro Yamada wrote:
>> The previous commit largely optimized the object directory creation.
>> We can optimize it more for incremental build.
>>
>> There are already *.cmd files in the output directory. Th
On 2017-11-11 17:43, Johan Hovold wrote:
> Fix child-node lookup during probe, which ended up searching the whole
> device tree depth-first starting at parent rather than just matching on
> its children.
>
> Later sanity checks on node properties (which would likely be missing)
> should prevent
On 2017-11-11 17:43, Johan Hovold wrote:
> A helper purported to look up a child node based on its name was using
> the wrong of-helper and ended up prematurely freeing the parent of-node
> while searching the whole device tree depth-first starting at the parent
> node.
>
> Fixes: 64b9e4d803b1 (
2017-11-10 17:49 GMT+08:00 Paolo Bonzini :
> Sometimes, a processor might execute an instruction while another
> processor is updating the page tables for that instruction's code page,
> but before the TLB shootdown completes. The interesting case happens
> if the page is in the TLB.
>
> In genera
Linus,
Please pull the latest core-rcu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus
# HEAD: 72bc286b81d21404cdfecddf76b64c7163aac764 Merge branch 'for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into co
* Sergey Senozhatsky wrote (on 2017-11-10
08:48:27 +0900):
> We are moving towards separate kernel and module function descriptor
> dereference callbacks. This patch enables it for powerpc64.
>
> For pointers that belong to the kernel
> - Added __start_opd and __end_opd pointers, to track the
On Mon, Nov 13, 2017 at 11:38 AM, Tobin C. Harding wrote:
> On Mon, Nov 13, 2017 at 11:16:28AM +0530, kaiwan.billimo...@gmail.com wrote:
>> On Mon, 2017-11-13 at 09:21 +1100, Tobin C. Harding wrote:
>> > On Fri, Nov 10, 2017 at 07:26:34PM +0530, kaiwan.billimo...@gmail.com
>> > wrote:
>> > > On T
From: Wanpeng Li
There is a logic to handle first-time write when updating the
pvclock/wall clock/steal time shared memory pages each time,
actually we should do this logic during pv stuffs setup if we
suspect the version-field can't be guranteed to be initialized
to an even number by the gue
Hello Linus,
since Martin is on vacation you get the s390 pull request for the v4.15
merge window this time from me.
Please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Besides a lot of cleanups
sysfs: cannot create duplicate filename '/devices/platform/vpd'
on the second load of this driver. I.e.,
modprobe vpd-sysfs
rmmod vpd-sysfs
modprobe vpd-sysfs
[boom]
on 4.14-rc8
--
~Randy
Hi,
these patches address the following issue, raised and
discussed in [1].
BFQ provides a proportional share policy for the blkio controller. In
this respect, BFQ updates the I/O accounting related to its policy,
i.e., the statistics contained in the special files blkio.bfq.* in
blkio groups (th
From: Luca Miccio
bfqg_stats_update_io_add and bfqg_stats_update_io_remove are to be
invoked, respectively, when an I/O request enters and when an I/O
request exits the scheduler. Unfortunately, bfq does not fully comply
with this scheme, because it does not invoke these functions for
requests th
From: Luca Miccio
BFQ currently creates, and updates, its own instance of the whole
set of blkio statistics that cfq creates. Yet, from the comments
of Tejun Heo in [1], it turned out that most of these statistics
are meant/useful only for debugging. This commit makes BFQ create
the latter, debug
We have investigated more deeply the performance of BFQ, in terms of
number of IOPS that can be processed by the CPU when BFQ is used as
I/O scheduler. In more detail, using the script [1], we have measured
the number of IOPS reached on top of a null block device configured
with zero latency, as a
bfq invokes various blkg_*stats_* functions to update the statistics
contained in the special files blkio.bfq.* in the blkio controller
groups, i.e., the I/O accounting related to the proportional-share
policy provided by bfq. The execution of these functions takes a
considerable percentage, about
Hi all,
Please do not add any v4.16 material to your linux-next included trees
until v4.15-rc1 has been released.
Changes since 20171110:
The powerpc tree still had its build failure for which I applied a
patch
The keys tree gained a build failure so I used the version from
next-20171110.
Non-
Hi all,
On Wed, 1 Nov 2017 07:57:23 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the arm64 tree got a conflict in:
>
> drivers/acpi/arm64/iort.c
>
> between commit:
>
> 37f6b42e9c29 ("ACPI/IORT: Fix PCI ACS enablement")
>
> from Linus' tree and commit:
>
> 896dd2c324
On Mon, Nov 13, 2017 at 11:16:28AM +0530, kaiwan.billimo...@gmail.com wrote:
> On Mon, 2017-11-13 at 09:21 +1100, Tobin C. Harding wrote:
> > On Fri, Nov 10, 2017 at 07:26:34PM +0530, kaiwan.billimo...@gmail.com
> > wrote:
> > > On Tue, 2017-11-07 at 21:32 +1100, Tobin C. Harding wrote:
> > > > Cu
Hello Ram,
Long ago (2.6.29) you added the /proc/PID/mountinfo file and
associated documentation in Documentation/filesystems/proc.txt. Later,
I pasted much of that documentation into the proc(5) manual page.
That documentation says of the second field in the file:
[[
This file contains lines of
Hi all,
On Mon, 30 Oct 2017 20:55:47 + Mark Brown wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> net/ipv4/tcp_output.c
>
> between commit:
>
> 6aa7de059173a ("locking/atomics: COCCINELLE/treewide: Convert trivial
> ACCESS_ONCE() patterns to READ_ONCE()/WRIT
Hi all,
On Mon, 30 Oct 2017 20:37:56 + Mark Brown wrote:
>
> Today's linux-next merge of the devicetree tree got a conflict in:
>
> drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c
>
> between commit:
>
> 44cd3939c111b7 ("drm/tilcdc: Remove redundant OF_DETACHED flag setting")
>
> from th
Hi all,
On Mon, 30 Oct 2017 14:48:04 + Mark Brown wrote:
>
> Today's linux-next merge of the ext4 tree got a conflict in:
>
> fs/ext4/inode.c
>
> between commit:
>
> 2ee6a576be564272 ("fs, fscrypt: add an S_ENCRYPTED inode flag")
>
> from the fscrypt tree and commit:
>
> d4e50e6d43
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/printk.h:7:0,
from include/linux/kernel.h:14,
from lib/test_find_bit.c:28:
lib/test_find_bit.c: In function '
Adding two #define constants is less common than performing & and |
operations on them, so put the addition first to reduce the set of cases
that have to be considered in detail. At the same time, add & and |
patterns for both arguments of +, to account for commutativity and obtain
more results.
Commit:
ba26621e63ce ("time: Remove duplicated code in ktime_get_raw_and_real()")
... got rid of ktime_get_raw_and_real_ts64(), but left its declaration
behind.
Remove it.
Signed-off-by: Dou Liyang
---
include/linux/timekeeping.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/incl
On Mon, 2017-11-13 at 09:21 +1100, Tobin C. Harding wrote:
> On Fri, Nov 10, 2017 at 07:26:34PM +0530, kaiwan.billimo...@gmail.com
> wrote:
> > On Tue, 2017-11-07 at 21:32 +1100, Tobin C. Harding wrote:
> > > Currently we are leaking addresses from the kernel to user space.
> > > This
> > > script
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
In file included from include/linux/mmzone.h:17:0,
from include/linux/mempolicy.h:10,
from mm/mempolicy.c:70:
mm/mempolicy.c: In function 'mp
In memory Collection (IMC) counter pmu driver controls the ucode's execution
state. At the system boot, IMC perf driver pause the ucode. Ucode state is
changed to "running" only when any of the nest units are monitored or profiled
using perf tool.
Hi,
Kindly ignore this version
Thanks,
Anju
On Monday 13 November 2017 11:06 AM, Anju T Sudhakar wrote:
In memory Collection (IMC) counter pmu driver controls the ucode's execution
state. At the system boot, IMC perf driver pause the ucode. Ucode state is
changed to "running" only when any of
Hi all,
On Mon, 30 Oct 2017 12:51:33 + Mark Brown wrote:
>
> Hi all,
>
> Today's linux-next merge of the powerpc tree got a conflict in:
>
> arch/powerpc/kvm/powerpc.c
>
> between commit:
>
> ac64115a66c1 ("KVM: PPC: Fix oops when checking KVM_CAP_PPC_HTM")
>
> from Linus' tree and c
In memory Collection (IMC) counter pmu driver controls the ucode's execution
state. At the system boot, IMC perf driver pause the ucode. Ucode state is
changed to "running" only when any of the nest units are monitored or profiled
using perf tool.
Hi all,
On Wed, 18 Oct 2017 11:50:25 +0100 Mark Brown wrote:
>
> Today's linux-next merge of the integrity tree got a conflict in:
>
> Documentation/ABI/testing/evm
>
> between commit:
>
> c7f66400f504fd5 ("Documentation: fix security related doc refs")
>
> from the jc-docs tree and commi
On Mon, Nov 13, 2017 at 10:05 AM, Tobin C. Harding wrote:
> On Mon, Nov 13, 2017 at 06:37:28AM +0300, Kirill A. Shutemov wrote:
>> On Mon, Nov 13, 2017 at 10:06:46AM +1100, Tobin C. Harding wrote:
>> > On Sun, Nov 12, 2017 at 02:10:07AM +0300, Kirill A. Shutemov wrote:
...
>> >
>> > Thanks for the
Hi Mark,
On Wed, 11 Oct 2017 17:10:35 +0100 Mark Brown wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> arch/s390/include/asm/spinlock.h
>
> between a series of commits adding wait queuing to s390 spinlocks
> from the s390 tree:
>
> eb3b7b848fb3dd00f7a57d633 s390/rw
Hi, Russell,
Have you any time to check this patch?
I found this issue/missing in my works, the application cannot mmap big
hugepage (about 360MB) due to no more contiguous vm from the default
"TASK_UNMMAPPED_AREA" by legacy bottom-up.
We need this patch to fix this issue.
Could you please help
Hi all,
On Wed, 11 Oct 2017 16:51:45 +0100 Mark Brown wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> arch/s390/include/asm/rwsem.h
>
> between commit:
>
>91a1fad759ffd ("s390: use generic rwsem implementation")
>
> from the s390 tree and commit:
>
>a61ba
Hi all,
On Mon, 9 Oct 2017 18:56:33 +0100 Mark Brown wrote:
>
> Today's linux-next merge of the drivers-x86 tree got a conflict in:
>
> Documentation/admin-guide/thunderbolt.rst
>
> between commit:
>
>e69b6c02b4c3b ("net: Add support for networking over Thunderbolt cable")
>
> from the
On 10/24/17 at 01:31pm, Dave Young wrote:
> Now crashkernel=X will fail if there's not enough memory at low region
> (below 896M) when trying to reserve large memory size. One can use
> crashkernel=xM,high to reserve it at high region (>4G) but it is more
> convinient to improve crashkernel=X to:
Hi Mark,
On Mon, 9 Oct 2017 19:38:36 +0100 Mark Brown wrote:
>
> Hi Tejun,
>
> Today's linux-next merge of the cgroup tree got a conflict in:
>
> kernel/cgroup/cgroup.c
>
> between commit:
>
> 324bda9e6c5ad ("bpf: multi program support for cgroup+bpf")
>
> from the net-next tree and comm
Hi Linus,
Can you please pull the m68knommu git tree, for-next branch.
The bulk of the changes are to support the ColdFire 5441x SoC family with
their MMU enabled. The parts have been supported for a long time now, but
only in no-MMU mode. Angelo Dureghello has a new board with a 5441x and
we hav
Hi all,
On Mon, 9 Oct 2017 19:26:54 +0100 Mark Brown wrote:
>
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css_firmware.c
>
> between commit:
>
>866af46e6ebbc ("media: Staging: atomisp: fix alloc
On Mon, Nov 13, 2017 at 11:33:43AM +0800, Peter Xu wrote:
> On Fri, Nov 10, 2017 at 09:05:20AM +0100, Peter Zijlstra wrote:
> > On Fri, Nov 10, 2017 at 03:10:17PM +0800, Peter Xu wrote:
> > > I came to this when reading kvm_vcpu_wake_up(), so that only affects
> > > some statistic which may not be
On Mon, 2017-10-30 at 16:32 +1030, Joel Stanley wrote:
> This registers the core clocks; those which are required to calculate
> the rate of the timer peripheral so the system can load a clocksource
> driver.
>
> Signed-off-by: Joel Stanley
>
> ---
> v5:
> - Add Andrew's Reviewed-by
Not quite
On Mon, 2017-10-30 at 16:32 +1030, Joel Stanley wrote:
> This registers a platform driver to set up all of the non-core
> clocks.
>
> The clocks that have configurable rates are now registered.
>
> Signed-off-by: Joel Stanley
Reviewed-by: Andrew Jeffery
> --
> v5:
> - Remove eclk configurati
On 11/07/2017 09:44 PM, Florian Fainelli wrote:
> In preparation for allowing BCM63xx to use this driver, we abstract I/O
> accessors such that we can easily change those later on.
>
> Signed-off-by: Florian Fainelli
> Reviewed-by: Eric Anholt
Reviewed-by: Philippe Mathieu-Daudé
> ---
> driv
Hi Andrew,
2017-10-13 22:03 GMT+09:00 Masahiro Yamada :
> This header contains references to spinlock_t and lockdep_is_held(),
> both of which are defined in
>
> Signed-off-by: Masahiro Yamada
I have not got any comment on this patch.
Could you take a look at it, please?
> ---
>
> include
On Mon, Nov 13, 2017 at 12:08:49PM +0800, Phil Reid wrote:
> On 12/11/2017 23:38, Pan Bian wrote:
> >Function devm_gpiod_get_optional() returns an ERR_PTR on failure. Its
> >return value should not be validated by a NULL check. Instead, use IS_ERR.
> >
> >Signed-off-by: Pan Bian
> >---
> > driver
On Sat, Nov 11, 2017 at 8:25 PM, Andy Lutomirski wrote:
> On Sat, Nov 11, 2017 at 6:59 PM, Andy Lutomirski wrote:
>> On Sat, Nov 11, 2017 at 2:58 AM, Borislav Petkov wrote:
>>> On Fri, Nov 10, 2017 at 08:05:19PM -0800, Andy Lutomirski wrote:
This isn't quite done (the TSS remap patch is bus
On Sun, Nov 12, 2017 at 6:08 PM, kernel test robot
wrote:
>
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: e04a713254ef50629d1ae9558ddd4c118b7cb807 ("x86/asm/64: Use a percpu
> trampoline stack for IDT entries")
> https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git
On Mon, Nov 13, 2017 at 06:37:28AM +0300, Kirill A. Shutemov wrote:
> On Mon, Nov 13, 2017 at 10:06:46AM +1100, Tobin C. Harding wrote:
> > On Sun, Nov 12, 2017 at 02:10:07AM +0300, Kirill A. Shutemov wrote:
> > > On Tue, Nov 07, 2017 at 09:32:11PM +1100, Tobin C. Harding wrote:
> > > > Currently w
Hi Julia,
2017-11-13 3:41 GMT+09:00 Julia Lawall :
> Adding two #define constants is less common than performing & and |
> operations on them, so put the addition first to reduce the set of cases
> that have to be considered in detail. At the same time, add & and |
> patterns for both arguments
On Fri, Nov 10, 2017 at 07:43:14AM -0800, Tejun Heo wrote:
> Hello, Shaohua.
>
> On Thu, Nov 09, 2017 at 08:27:13PM -0800, Shaohua Li wrote:
> > I think the absolute latency would only work for HD. For a SSD, a 4k latency
> > probably is 60us and 1M latency is 500us. The disk must be very contende
Hi,
On Sat, Nov 11, 2017 at 3:14 AM, Rob Herring wrote:
> On Wed, Nov 08, 2017 at 01:16:41PM +0530, Raveendra Padasalagi wrote:
>> Add devicetree binding document for broadcom's
>> Cygnus SoC specific usb phy controller driver.
>>
>> Signed-off-by: Raveendra Padasalagi
>> ---
>> .../bindings/ph
Hi Cao,
2017-11-10 16:35 GMT+09:00 Cao jin :
> commit
>
> cf4f21938e13e ("kbuild: Allow to specify composite modules with modname-m")
>
> add modname-m support, but miss to update the corresponding multi-objs-m
> defination.
Commit cf4f21938e13 ("kbuild: Allow to specify composite modules
wit
On 12/11/2017 23:38, Pan Bian wrote:
Function devm_gpiod_get_optional() returns an ERR_PTR on failure. Its
return value should not be validated by a NULL check. Instead, use IS_ERR.
Signed-off-by: Pan Bian
---
drivers/net/dsa/lan9303-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
On Sun, Nov 12, 2017 at 02:26:13PM -0800, Tejun Heo wrote:
> BIO_THROTTLED is used to mark already throttled bios so that a bio
> doesn't get throttled multiple times. The flag gets set when the bio
> starts getting dispatched from blk-throtl and cleared when it leaves
> blk-throtl.
>
> Unfortuna
> -Original Message-
> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> Sent: Friday, November 10, 2017 2:32 PM
> To: Xiaowei Bao ; robh...@kernel.org;
> mark.rutl...@arm.com; catalin.mari...@arm.com; will.dea...@arm.com;
> bhelg...@google.com; shawn...@kernel.org; Madalin-cristian B
On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen
wrote:
> On 11/10/2017 02:06 PM, Andy Lutomirski wrote:
>> On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen
>> wrote:
>>> On 11/09/2017 06:25 PM, Andy Lutomirski wrote:
Here are two proposals to address this without breaking vsyscalls.
1. Se
Hi Pavel,
At 11/09/2017 11:01 AM, Pavel Tatashin wrote:
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 p
Hi Pavel,
At 11/09/2017 11:02 AM, Pavel Tatashin wrote:
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 messag
Hi Pavel,
At 11/09/2017 11:01 AM, Pavel Tatashin wrote:
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,
We always poll tx for socket, this is sub optimal since this will
slightly increase the waitqueue traversing time and more important,
vhost could not benefit from commit 9e641bdcfa4e ("net-tun:
restructure tun_do_read for better sleep/wakeup efficiency") even if
we've stopped rx polling during hand
+ Horace
-Original Message-
From: Colin King [mailto:colin.k...@canonical.com]
Sent: 2017年11月11日 19:51
To: Deucher, Alexander ; Koenig, Christian
; David Airlie ; Liu, Monk
; Yu, Xiangliang ;
amd-...@lists.freedesktop.org; dri-de...@lists.freedesktop.org
Cc: kernel-janit...@vger.kernel
On Mon, Nov 13, 2017 at 10:06:46AM +1100, Tobin C. Harding wrote:
> On Sun, Nov 12, 2017 at 02:10:07AM +0300, Kirill A. Shutemov wrote:
> > On Tue, Nov 07, 2017 at 09:32:11PM +1100, Tobin C. Harding wrote:
> > > Currently we are leaking addresses from the kernel to user space. This
> > > script is
On Fri, Nov 10, 2017 at 09:05:20AM +0100, Peter Zijlstra wrote:
> On Fri, Nov 10, 2017 at 03:10:17PM +0800, Peter Xu wrote:
> > I came to this when reading kvm_vcpu_wake_up(), so that only affects
> > some statistic which may not be that critical. However I don't know
> > whether there would be an
Commit 6184fc0b8dd7 ("quota: Propagate error from ->acquire_dquot()")
missed to handle error from dquot_initialize in dquot_file_open, fix it.
Signed-off-by: Chao Yu
---
fs/quota/dquot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/quota/dquot.c b/fs/quota/dquot.c
index
Add documentation for the w83773g driver.
Signed-off-by: Lei YU
---
v2:
- Add notes for offset and update_interval
---
Documentation/hwmon/w83773g | 33 +
1 file changed, 33 insertions(+)
create mode 100644 Documentation/hwmon/w83773g
diff --git a/Documentation
Signed-off-by: Lei YU
---
Documentation/devicetree/bindings/trivial-devices.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/trivial-devices.txt
b/Documentation/devicetree/bindings/trivial-devices.txt
index af284fb..63ad2f1 100644
--- a/Documentation/devi
Nuvoton W83773G is a hardware monitoring chip, which integrates two remote
and one local temperature sensors.
---
v2:
- The driver is re-written as v1's comment, so the author is changed to me.
- Added the device to trivial-devices.txt
v3:
- Update the driver to use new API devm_hwmon_device_reg
Nuvoton W83773G is a hardware monitor IC providing one local
temperature and two remote temperature sensors.
Signed-off-by: Lei YU
---
v2:
- Rewrite the driver using regmap
- Add offset and update_interval
v3:
- Use devm_hwmon_device_register_with_info() with is_visible/read/write
functions
The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:
Linux 4.14-rc3 (2017-10-01 14:54:54 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/ext4_for_linus
for you to fetch changes up to 232530680290ba94ca
On 11/13/17 at 02:15P, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Even though aperfmperf_snapshot_khz() caches the samples.khz value
> to return if called again in a sufficiently short time, its caller,
> arch_freq_get_on_cpu(), still uses smp_call_function_single() to run
> it which
On 2017年11月10日 20:07, Enric Balletbo Serra wrote:
2017-10-04 19:53 GMT+02:00 Emil Renner Berthing :
On the Samsung Chromebook Plus I get this error with 4.14-rc3:
BUG: scheduling while atomic: kworker/3:1/50/0x0002
Modules linked in:
CPU: 3 PID: 50 Comm: kworker/3:1 Not tainted 4.14.0-0.rc3
UMIP does not incur in a significant performance penalty. Furthermore, it
is triggered only when a small group of instructions are used from user
space programs.
While here, provide more details on the benefits UMIP provides and the
behavior that can expect the few applications that use the instru
Let us have an indication that this feature has been enabled.
Cc: Andy Lutomirski
Cc: H. Peter Anvin
Cc: Borislav Petkov
Cc: Tony Luck
Cc: Paolo Bonzini
Cc: Ravi V. Shankar
Cc: x...@kernel.org
Suggested-by: Ingo Molnar
Signed-off-by: Ricardo Neri
---
arch/x86/kernel/cpu/common.c | 2 ++
1
Now that the support for UMIP [1], [2] has been merged in the tip tree,
this series add a couple of tweaks.
Ingo asked for two small additions to select UMIP by default when building
and inform of this feature being enabled [3].
Also, Linus suggested to issue a rate-limited warning whenever the a
The instructions str and sldt are not emulated in any case. Thus, it made
sense to not implement functionality to identify them. However, a
subsequent commit will introduce functionality to warn about the use of
all the instructions that UMIP protect, not only those that are emulated.
A first step
Issue a rate-limited warning whenever any of the instructions that UMIP
protects (i.e., sgdt, sidt, sldt, str and smsw) are used by user space
programs.
This is useful because, with UMIP enabled, the few programs that use such
instructions will start receiving a SIGSEGV signal. In the specific cas
On Fri, Nov 10, 2017 at 10:49 PM, Guenter Roeck wrote:
> On 11/08/2017 11:09 PM, Lei YU wrote:
>>
>> Nuvoton W83773G is a hardware monitor IC providing one local
>> temperature and two remote temperature sensors.
>>
>> Signed-off-by: Lei YU
>
>
> Nicely done. Couple of nitpicks left.
>
> Thanks!
>>On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote:
>> From: Greentime Hu
>
>> +#endif /* __ASM_NDS32_SYSCALLS_H */
>> diff --git a/arch/nds32/include/asm/unistd.h
>> b/arch/nds32/include/asm/unistd.h new file mode 100644 index
>> 000..b30adca
>> --- /dev/null
>> +++ b/arch/nds32/include/as
> -Original Message-
> From: Leo Li
> Sent: Saturday, November 11, 2017 5:21 AM
> To: Kishon Vijay Abraham I ; Xiaowei Bao
> ; robh...@kernel.org; mark.rutl...@arm.com;
> catalin.mari...@arm.com; will.dea...@arm.com; bhelg...@google.com;
> shawn...@kernel.org; Madalin-cristian Bucur ;
> S
>> +static int restore_sigframe(struct pt_regs *regs,
>> + struct rt_sigframe __user * sf) {
>
>[snip]
>
>> + err |= !valid_user_regs(regs);
>
>IDGI... Where do you modify ->ipsw at all and how can valid_user_regs() come
>to be false here?
>
Thanks.
This code is trivia
On 11/13/2017 10:59 AM, Chao Yu wrote:
> On 2017/11/13 9:35, Hyunchul Lee wrote:
>> On 11/13/2017 10:26 AM, Chao Yu wrote:
>>> On 2017/11/13 8:24, Hyunchul Lee wrote:
On 11/10/2017 03:42 PM, Chao Yu wrote:
> On 2017/11/10 8:23, Hyunchul Lee wrote:
>> Hello, Chao
>>
>> On 11/09/
[...]
> Oh - and talking about "big step forward" - does the 0day robot do
> any
> suspend/resume testing at all?
Yes, we do. CC Rui and Aaron on power testing.
yes, we have added suspend/resume test in 0day, including both
functionality and suspend/resume performance. It is not widely run
beca
Hi David,
After merging the keys tree, today's linux-next build (arm
multi_v7_defconfiga) produced these warning:
certs/system_keyring.c:39:23: warning: 'trusted_keyring_acl' defined but not
used [-Wunused-variable]
static struct key_acl trusted_keyring_acl = {
^
net/wire
FYI, we noticed the following commit (built with gcc-6):
commit: e04a713254ef50629d1ae9558ddd4c118b7cb807 ("x86/asm/64: Use a percpu
trampoline stack for IDT entries")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip
in testcase: boot
on test machine: qemu-system
FYI, we noticed the following commit (built with gcc-6):
commit: 66688e9d11455f15983d08e7c14733969cd25919 ("x86/entry/64: Create a
percpu SYSCALL entry trampoline")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip
in testcase: boot
on test machine: qemu-system-x8
Hi David,
After merging the keys tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/md/dm-crypt.c: In function 'crypt_set_keyring_key':
drivers/md/dm-crypt.c:2022:8: error: too few arguments to function 'request_key'
key = request_key(key_string[0] == 'l' ? &key_
1 - 100 of 323 matches
Mail list logo
