The third argument of devm_request_threaded_irq() is the primary
handler. It is called in hardirq context and checks whether the
interrupt is relevant to the device. If the primary handler returns
IRQ_WAKE_THREAD, the secondary handler (a.k.a. handler thread) is
scheduled to run in process context.
On Kernel 4.10.14. The X windows screen garbage.
At that time, I have two different users login on two different
virtual consoles. Both are using X windows. One of them is idle (X
windows screen locked).
May 16 01:08:39 home kernel: [25854.797258] WARNING: CPU: 9 PID: 2480 at
drivers/gpu/drm/radeo
On Fri, May 12, 2017 at 10:25:30AM -0400, Steven Rostedt wrote:
> On Fri, 12 May 2017 14:48:45 +0900
> Byungchul Park wrote:
>
> > cpudl.elements is an instance that should be protected with a spin lock.
> > Without it, the code would be insane.
>
> And how much contention will this add? Spin lo
Eric,
Am 16.05.2017 um 01:25 schrieb Eric Biggers:
> On Mon, May 15, 2017 at 09:51:03PM +0200, Richard Weinberger wrote:
>>>
>>> The test is repeatedly creating and removing a directory "dir" while
>>> lookups are
>>> being done in it. It seems the problem is that many dentries are being
>>> cr
I'm announcing the release of the 3.18.53 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 8cd44350423b..274ec43fc6ba 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 52
+SUBLEVEL = 53
EXTRAVERSION =
NAME = Diseased Newt
diff --git a/arch/arm/kernel/Makefile b/arch/arm/kernel/Makefile
index 2ecc7d15b
On 16 May 2017 at 07:22, Viresh Kumar wrote:
> The pm_domain_data (pdd) pointer is set from genpd_alloc_dev_data() and
> pdd->dev is guaranteed to be valid. There is no need to check pdd and
> pdd->dev in rest of the code as pdd->dev will always be valid for a non
> NULL pdd pointer.
>
> Signed-of
On Tue, May 16, 2017 at 09:08:27AM +0300, Baruch Siach wrote:
> Hi Greg,
>
> On Tue, May 16, 2017 at 08:01:10AM +0200, Greg KH wrote:
> > On Tue, May 16, 2017 at 11:19:32AM +0530, Raveendra Padasalagi wrote:
> > > The third argument of devm_request_threaded_irq() is the primary
> > > handler. It i
2017-05-12T04:46:36.373001+08:00[[32m OK [0m] Reached target System
Initialization.
2017-05-12T04:46:36.385253+08:00[[32m OK [0m] Reached target Basic System.
2017-05-12T04:46:43.049936+08:00[ 25.839157] BUG: unable to handle kernel [
25.841509] floppy0: no floppy controllers found
20
> On Mon, May 15, 2017 at 04:27:25PM -0700, Darren Hart wrote:
> > > In light of the above, I still feel the split is worth going through
> > > with. The question is whether Jonathan feels the same :)
> >
> > In the interest of keeping this moving... As I'm not sure there is a "right
> > answer"
On 15/05/17 22:35, Stefano Stabellini wrote:
> The pvcalls backend has one ioworker per cpu: the ioworkers are
> implemented as a cpu bound workqueue, and will deal with the actual
> socket and data ring reads/writes.
>
> ioworkers are global: we only have one set for all the frontends. They
> pro
Hi Chen-Yu,
On 16/05/2017 07:18, Chen-Yu Tsai wrote:
> On Thu, May 11, 2017 at 9:42 PM, Quentin Schulz
> wrote:
>> This adds support in X-Powers AXP20X and AXP22X battery driver for a
>> fixed battery in DT.
>>
>> It will take the minimum supported voltage by the battery as defined in
>> the batt
Hi Matthias,
Sorry for my late reply.
2017-05-09 8:18 GMT+09:00 Matthias Kaehlcke :
> Hi Masahiro,
>
> El Sun, May 07, 2017 at 01:52:25AM +0900 Masahiro Yamada ha dit:
>
>> 2017-05-02 10:23 GMT+09:00 Matthias Kaehlcke :
>> > Hi Masahiro,
>> >
>> > El Sun, Apr 30, 2017 at 10:59:52PM +0900 Masahiro
leak
> >
> > Worked fine for me. Maybe your config is special?
>
> I don't think my config is special at all, here it is its just
> what I use for my qemu kvm guest image:
>
> http://drvbp1.linux-foundation.org/~mcgrof/2017/05/15/configs/piggy-x86_64_qemu_fork_km
Remove the restart handler registered in probe on device remove.
Fixes: a370f60a58ec ("mfd: rn5t618: Register restart handler")
Signed-off-by: Stefan Agner
---
drivers/mfd/rn5t618.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/rn5t618.c b/drivers/mfd/rn5t618.c
index 8131d197
Destroying a Xen guest domain while it was doing I/Os via xen-blkback
leaked several resources, including references of the guest's memory
pages.
This patch series addresses those leaks by correcting usage of
reference counts and the sequence when to free which resource.
The series applies on top
The be structure must nor be freed when freeing the blkif structure
isn't done. Otherwise a use-after-free of be when unmapping the ring
used for communicating with the frontend will occur in case of a
late call of xenblk_disconnect() (e.g. due to an I/O still active
when trying to disconnect).
Cc
On Mon, May 15, 2017 at 09:34:17PM -0700, Dmitry Vyukov wrote:
> On Mon, May 15, 2017 at 6:16 PM, wrote:
> > From: Joonsoo Kim
> >
> > Hello, all.
> >
> > This is an attempt to recude memory consumption of KASAN. Please see
> > following description to get the more information.
> >
> > 1. What i
Today disconnecting xen-blkback is broken in case there are still
I/Os in flight: xen_blkif_disconnect() will bail out early without
releasing all resources in the hope it will be called again when
the last request has terminated. This, however, won't happen as
xen_blkif_free() won't be called on t
There is no need to use xen_blkif_get()/xen_blkif_put() in the kthread
of xen-blkback. Thread stopping is synchronous and using the blkif
reference counting in the kthread will avoid to ever let the reference
count drop to zero at the end of an I/O running concurrent to
disconnecting and multiple r
* Paul E. McKenney wrote:
> Hello!
>
> The question of the use case for TASKS_RCU came up, and here is my
> understanding. Steve will not be shy about correcting any misconceptions
> I might have. ;-)
>
> The use case is to support freeing of trampolines used in tracing/probing
> in CONFIG_P
Currently, the xenon_clean_phy() is only used for freeing phy_params.
The phy_params is allocated by devm_kzalloc(), there's no need to free
is explicitly.
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci-xenon-phy.c | 14 +-
drivers/mmc/host/sdhci-xenon.c | 6 +-
dri
When using the resource managed version of pinctrl, resources
might already been freed when pinctrl_unregister is called by the
devres framework. When calling devm_kfree on such a already freed
resource, devres prints a warning:
WARNING: CPU: 0 PID: 1 at drivers/base/devres.c:891
pinmux_generic_
=== Binoy Jayan ===
=== Highlights ===
dm-crypt optimization
- No progress
dm-crypt:store keys in secure storage
- Read OPTEE ClientAPI specification to figure out how to
communicate with optee from a client application
- No examples available for using client api from kernel
so need to
Hi Greg,
On Tue, May 16, 2017 at 08:01:10AM +0200, Greg KH wrote:
> On Tue, May 16, 2017 at 11:19:32AM +0530, Raveendra Padasalagi wrote:
> > The third argument of devm_request_threaded_irq() is the primary
> > handler. It is called in hardirq context and checks whether the
> > interrupt is releva
On Mon, May 15, 2017 at 10:53:50PM -0700, Steven Pease wrote:
> Is there any particular reason that the CVE appears to be filed
> against 4.4.60? Or is this just a mistake?
>
> http://www.cvedetails.com/cve/CVE-2016-10229/
I have no idea why. Maybe they mentionned the current version at the
momen
On Tue, May 16, 2017 at 11:19:32AM +0530, Raveendra Padasalagi wrote:
> The third argument of devm_request_threaded_irq() is the primary
> handler. It is called in hardirq context and checks whether the
> interrupt is relevant to the device. If the primary handler returns
> IRQ_WAKE_THREAD, the sec
Is there any particular reason that the CVE appears to be filed
against 4.4.60? Or is this just a mistake?
http://www.cvedetails.com/cve/CVE-2016-10229/
- Steven
On Mon, May 15, 2017 at 10:20 PM, Willy Tarreau wrote:
> On Mon, May 15, 2017 at 06:09:53PM -0700, Steven Pease wrote:
>> Hi,
>>
>> T
The third argument of devm_request_threaded_irq() is the primary
handler. It is called in hardirq context and checks whether the
interrupt is relevant to the device. If the primary handler returns
IRQ_WAKE_THREAD, the secondary handler (a.k.a. handler thread) is
scheduled to run in process context.
Hi,
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Zheng,
> Lv
> Subject: RE: [PATCH 2/2] Revert "ACPI / button: Change default behavior to
> lid_init_state=open"
>
> Hi, Guys
>
> > From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.co
> + struct sem sems[0];
I can't contribute much to the code itself, but [0] is an old
GCC extension, for modern code sems[] should do the same things
but is standard C.
On (05/16/17 14:26), Minchan Kim wrote:
[..]
> > + /*
> > +* Free memory associated with this sector
> > +* before overwriting unused sectors.
> > +*/
> > + zram_slot_lock(zram, index);
> > + zram_free_page(zram, index);
>
> Hmm, zram_free should happen on
Hi Alberto,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.12-rc1 next-20170515]
[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/Alberto-Ladron/usb-class-usblp-Fixed
Hi Linus,
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:
* Convert the debug feature to refcount_t
* Reduce the copy size for strncpy_from_user
* 8 bug fixes
Elena Reshetova (1):
This test checks two behaviour cases:
When a mount is propagated to a place which is already busy, the new
mount is inserted between parent and old mount.
When a mount that is being unmounted due to propagation has another
mount on top of it, it is replaced by the top mount.
Cc: Shuah Khan
Sign
On Mon, 2017-05-01 at 17:30 -0400, Roy Pledge wrote:
> This patch series enables DPAA1 QBMan devices for ARM and
> ARM64 architectures. This allows the LS1043A and LS1046A to use
> QBMan functionality.
>
> Changes since v2:
> Fixed some misspellings
> Added 'no-map' constraint to device tree bindi
Hi, Guys
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: Re: [PATCH 2/2] Revert "ACPI / button: Change default behavior to
> lid_init_state=open"
>
> On May 15 2017 or thereabouts, Rafael J. Wysocki wrote:
> > On Mon, May 15, 2017 at 11:37 AM, Benjamin Tissoires
> >
Hi,
On Wed, May 10, 2017 at 2:58 PM, Mylene Josserand
wrote:
> Hi Chen-Yu,
>
> Thank you for the review!
>
>
> On 03/05/2017 19:13, Chen-Yu Tsai wrote:
>>
>> Hi,
>>
>> On Wed, May 3, 2017 at 9:56 PM, Mylène Josserand
>> wrote:
>>>
>>> Add ADC support for the sun8i-codec driver.
>>>
>>> This driv
On Tue, May 16, 2017 at 11:36:15AM +0900, Sergey Senozhatsky wrote:
> > > > @@ -794,7 +801,15 @@ static int __zram_bvec_write(struct zram *zram,
> > > > struct bio_vec *bvec, u32 index)
> > > > entry = zram_dedup_find(zram, page, &checksum);
> > > > if (entry) {
> > > >
While returning EPROBE_DEFER for iommu masters
take in to account of iommu nodes that could be
marked in DT as 'status=disabled', in which case
simply return NULL and let the master's probe
continue rather than deferring.
Signed-off-by: Sricharan R
Tested-by: Will Deacon
Acked-by: Will Deacon
-
On Sat, May 6, 2017 at 11:00 AM, Oza Oza wrote:
> On Fri, May 5, 2017 at 8:55 PM, Robin Murphy wrote:
>> On 04/05/17 19:41, Oza Oza wrote:
>> [...]
> 5) leaves scope of adding PCI flag handling for inbound memory
> by the new function.
Which flags would ever actually matter? DMA
this patch reserves the IOVA for PCI masters.
ARM64 based SOCs may have scattered memory banks.
such as iproc based SOC has
<0x 0x8000 0x0 0x8000>, /* 2G @ 2G */
<0x0008 0x8000 0x3 0x8000>, /* 14G @ 34G */
<0x0090 0x 0x4 0x>, /* 16G @ 576G */
<0x
The pm_domain_data (pdd) pointer is set from genpd_alloc_dev_data() and
pdd->dev is guaranteed to be valid. There is no need to check pdd and
pdd->dev in rest of the code as pdd->dev will always be valid for a non
NULL pdd pointer.
Signed-off-by: Viresh Kumar
---
drivers/base/power/domain.c | 2
It is possible that PCI device supports 64-bit DMA addressing,
and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64),
however PCI host bridge may have limitations on the inbound
transaction addressing.
This is particularly problematic on ARM/ARM64 SOCs where the
IOMMU (i.e. SMMU) trans
current device framework and OF framework integration assumes
dma-ranges in a way where memory-mapped devices define their
dma-ranges. (child-bus-address, parent-bus-address, length).
of_dma_configure is specifically written to take care of memory
mapped devices. but no implementation exists for p
current device framework and OF framework integration assumes
dma-ranges in a way where memory-mapped devices define their
dma-ranges. (child-bus-address, parent-bus-address, length).
of_dma_configure is specifically written to take care of memory
mapped devices. but no implementation exists for p
On Mon, May 15, 2017 at 06:09:53PM -0700, Steven Pease wrote:
> Hi,
>
> This is my first post - not currently subscribed so please CC me. :) I
> searched a bit for this question, but couldn't find an answer (Googled
> '2016-10229 site:lkml.org').
>
> Does CVE-2016-10229 affect the newest version
On Thu, May 11, 2017 at 9:42 PM, Quentin Schulz
wrote:
> This adds support in X-Powers AXP20X and AXP22X battery driver for a
> fixed battery in DT.
>
> It will take the minimum supported voltage by the battery as defined in
> the battery DT node and set the V_OFF register to this value, telling
>
Since commit 61562f981e92 ("uapi: export all arch specifics
directories"), "make INSTALL_HDR_PATH=$root/usr headers_install"
deletes standard glibc headers and others in $root/usr/include.
The cause of the issue is that headers_install now starts descending
from arch/$(hdr-arch)/include/uapi with
Hi Laurent,
On 15-05-2017 08:05, Laurent Pinchart wrote:
> On Monday 15 May 2017 08:47:49 Daniel Vetter wrote:
>> On Sun, May 14, 2017 at 02:04:24PM +0300, Laurent Pinchart wrote:
>>> On Friday 12 May 2017 17:06:14 Jose Abreu wrote:
On 12-05-2017 10:35, Laurent Pinchart wrote:
> On Tuesd
Hi, Benjamin
I reordered the discussion to collect topics and delete things to make
discussion shorter.
1. root caused issue:
> > It seems we just need to determine the following first:
> > 1. Who should be responsible for solving bugs triggered by the conflict
> > between bios and linux user
On Mon, May 15, 2017 at 9:35 PM, Masahiro Yamada
wrote:
> Since commit 61562f981e92 ("uapi: export all arch specifics
> directories"), "make INSTALL_HDR_PATH=${root}/usr headers_install"
> deletes standard glibc headers and others in ${root}/usr/include.
>
> The cause of the issue is that headers_
Hi
I hit the following issue by runing /proc/vmallocinfo. The kernel is 4.1
stable and
32 bit to be used. after I expand the vamlloc area, the issue is not occur
again.
it is related to the overflow. but I do not see any problem so far.
cat /proc/vmallocinfo
0xf158-0xf160 524288 ra
On 05/16, Al Viro wrote:
>On Tue, May 16, 2017 at 09:19:57AM +0800, kernel test robot wrote:
>>
>> FYI, we noticed the following commit:
>>
>> commit: c1aad8dcc49382399f48541dc47b6e30b0ef1b62 ("asm-generic: zero in
>> __get_user(), not __get_user_fn()")
>> https://git.kernel.org/cgit/linux/kerne
Hi Dan,
2017-05-16 10:15 GMT+09:00 Dan Williams :
> On Mon, May 15, 2017 at 6:02 PM, Dan Williams
> wrote:
>> On Mon, Mar 27, 2017 at 5:20 AM, Nicolas Dichtel
>> wrote:
>>> This patch removes the need of subdir-y. Now all files/directories under
>>> arch//include/uapi/ are exported.
>>>
>>> Th
On Mon, May 15, 2017 at 9:34 PM, Dmitry Vyukov wrote:
> On Mon, May 15, 2017 at 6:16 PM, wrote:
>> From: Joonsoo Kim
>>
>> Hello, all.
>>
>> This is an attempt to recude memory consumption of KASAN. Please see
>> following description to get the more information.
>>
>> 1. What is per-page shado
On 05/15/2017 12:13 PM, Matthias Kaehlcke wrote:
El Mon, May 15, 2017 at 10:02:15AM -0700 Guenter Roeck ha dit:
Hi all,
frv fails to build in mainline with the following build errors.
kernel/built-in.o: In function `__do_softirq':
(.text+0x6460): relocation truncated to fit: R_FRV_GPREL12 aga
Since commit 61562f981e92 ("uapi: export all arch specifics
directories"), "make INSTALL_HDR_PATH=${root}/usr headers_install"
deletes standard glibc headers and others in ${root}/usr/include.
The cause of the issue is that headers_install now starts descending
from arch/$(hdr-arch)/include/uapi w
On Mon, May 15, 2017 at 6:16 PM, wrote:
> From: Joonsoo Kim
>
> Hello, all.
>
> This is an attempt to recude memory consumption of KASAN. Please see
> following description to get the more information.
>
> 1. What is per-page shadow memory
Hi Joonsoo,
First I need to say that this is great wor
On Mon, May 15, 2017 at 10:34:51AM +0530, Anup Patel wrote:
> The Broadcom SBA RAID is a stream-based device which provides
> RAID5/6 offload.
>
> It requires a SoC specific ring manager (such as Broadcom FlexRM
> ring manager) to provide ring-based programming interface. Due to
> this, the Broadc
On Mon, May 15, 2017 at 05:09:13PM +0200, Takashi Iwai wrote:
> On Mon, 15 May 2017 16:49:40 +0200,
> Vinod Koul wrote:
> >
> > On Mon, May 15, 2017 at 11:43:11AM +0300, Andy Shevchenko wrote:
> > > On Sun, 2017-05-14 at 18:34 +0530, Vinod Koul wrote:
> > > > On Tue, May 09, 2017 at 07:18:37PM +03
Hi,
With 4.12-rc1 (Linus git), booting fails due to kernel panic, at
intel_pstate_register_driver+0x56/0x110.
I can't copy the whole trace from the graphic console, it looks like below.
Call Trace:
intel_pstate_init
intel_pstate_setup
do_one_initcall
set_debug_rodata
kernel_init_f
Hi Al,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc1 next-20170515]
[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/Al-Viro/move-compat-wait4-and-waitid-next-to
On 05/15/2017 07:10 PM, Peter Dolding wrote:
On Tue, May 16, 2017 at 6:57 AM, Alan Cox wrote:
O> I'm not implying that my patch is supposed to provide safety for
"hundreds of other" issues. I'm looking to provide a way to lock down a
single TTY ioctl that has caused real security issues to ari
Hi Al,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc1 next-20170515]
[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/Al-Viro/move-compat-wait4-and-waitid-next-to
The function x25_init is not properly unregister related resources
on error handler.It is will result in kernel oops if x25_init init
failed, so add properly unregister call on error handler.
Also, i adjust the coding style and make x25_register_sysctl properly
return failure.
Signed-off-by: linz
On 05/15/2017 06:50 AM, Marc Kleine-Budde wrote:
On 05/12/2017 08:37 AM, Quentin Schulz wrote:
Hi all,
On 05/05/2017 15:50, Quentin Schulz wrote:
To avoid possible ECC/parity checksum errors when reading an
uninitialized buffer, the entire Message RAM is initialized when probing
the driver.
On 2017/5/15 17:17, Lorenzo Pieralisi wrote:
> On Mon, May 15, 2017 at 02:13:47PM +0800, Zhou Wang wrote:
>> On 2017/4/26 18:06, Lorenzo Pieralisi wrote:
>>> The introduction of pci_bus_find_numa_node(pci_bus) allows at PCI
>>> host bridge registration to detect the NUMA node for a given
>>> struct
Good day
I av' been trying to reach you, contact me --> jeanettewon...@outlook.com
for details
On 05/15/2017 04:36 PM, Stefano Stabellini wrote:
Allocate a socket. Keep track of socket <-> ring mappings with a new data
structure, called sock_mapping. Implement the connect command by calling
inet_stream_connect, and mapping the new indexes page and data ring.
Associate the socket to an io
On 05/16/17 at 09:43am, Dou Liyang wrote:
>
>
> At 05/16/2017 09:12 AM, Baoquan He wrote:
> > On 05/16/17 at 08:56am, Dou Liyang wrote:
> > > Hi Baoquan,
> > >
> > > At 05/13/2017 01:46 PM, Baoquan He wrote:
> > > > Option mem= will limit the max address a system can use and any memory
> > > > r
From: Wei-Ning Huang
Some EC chip has larger flash sector size which requires longer erase
time. During erase the CPU is usually stalled and can't even respond to
interrupts. We sleep a while to block any EC command from executing
during the flash erase period.
Signed-off-by: Wei-Ning Huang
---
Hello Minchan,
On (05/16/17 10:59), Minchan Kim wrote:
> Hi Sergey,
>
[..]
> You mean this?
>
> static void zram_free_page(..) {
> if (zram_test_flag(zram, index, ZRAM_SAME))
> ...
>
> if (!entry)
> return;
>
> if (zram_dedup_enabled(zram
On Fri, May 12, 2017 at 07:00:29PM -0500, Rob Herring wrote:
> On Tue, May 09, 2017 at 11:20:20AM -0700, Moritz Fischer wrote:
> > This adds a binding for the Maxim/Dallas DS1374 MFD.
> >
> > Signed-off-by: Moritz Fischer
> > ---
> >
> > Hi all,
> >
> > I'm not entirely sure aobut the binding,
On 05/15/2017 04:35 PM, Stefano Stabellini wrote:
Just reply with success to the other end for now. Delay the allocation
of the actual socket to bind and/or connect.
Signed-off-by: Stefano Stabellini
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
---
drivers/xen/pvcalls-back.c | 31 +
On Sun, 14 May 2017 01:01:02 +0530
"Naveen N. Rao" wrote:
> If instance directories are deleted while there are registered function
> triggers:
>
> # cd /sys/kernel/debug/tracing/instances
> # mkdir test
> # echo "schedule:enable_event:sched:sched_switch" > test/set_ftrace_filter
> # rmd
On 05/15/2017 04:35 PM, Stefano Stabellini wrote:
When the other end notifies us that there are commands to be read
(pvcalls_back_event), wake up the backend thread to parse the command.
The command ring works like most other Xen rings, so use the usual
ring macros to read and write to it. The
On Sat, May 13, 2017 at 05:10:18PM -0700, Randy Dunlap wrote:
Hi robby,
Too much automation maybe??
Yeah sorry for the noises!
See the commit message:
avr32: remove support for AVR32
and then the error message...
On 05/13/17 17:05, kbuild test robot wrote:
The 2 patches to remove
On 05/15/2017 04:35 PM, Stefano Stabellini wrote:
Introduce a per-frontend data structure named pvcalls_back_priv. It
contains pointers to the command ring, its event channel, a list of
active sockets and a tree of passive sockets (passing sockets need to be
looked up from the id on listen, acc
Hi Sergey,
On Tue, May 16, 2017 at 10:30:22AM +0900, Sergey Senozhatsky wrote:
> On (05/15/17 16:41), Minchan Kim wrote:
> [..]
> > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> > index b885356551e9..8152e405117b 100644
> > --- a/drivers/block/zram/zram_drv.c
> > +++
On Mon, May 15, 2017 at 05:13:06PM +0200, Milian Wolff wrote:
> On Monday, May 15, 2017 5:04:44 PM CEST Milian Wolff wrote:
> > As the documentation for dwfl_frame_pc says, frames that
> > are no activation frames need to have their program counter
> > decremented by one to properly find the functi
Hey Ivan,
Please use j...@jms.id.au when you cc me on patches. That other
address won't work for most people.
Cheers,
Joel
On Mon, May 15, 2017 at 10:37 PM, Ivan Mikhaylov wrote:
> This adds support for the FSP2 (476fpe) board. This includes code in
> arch/powerpc/platforms/44x for board initi
On Mon, May 15, 2017 at 6:46 PM, Joel Fernandes wrote:
> From: Jamie Gennis
>
> The tgids are tracked along side the saved_cmdlines tracking, and can be
> included in trace output by enabling the 'print-tgid' trace option. This is
> useful when doing post-processing of the trace data, as it allow
On 05/15/2017 04:35 PM, Stefano Stabellini wrote:
Introduce the code to handle xenbus state changes.
Implement the probe function for the pvcalls backend. Write the
supported versions, max-page-order and function-calls nodes to xenstore,
as required by the protocol.
Introduce stub functions f
From: Jamie Gennis
The tgids are tracked along side the saved_cmdlines tracking, and can be
included in trace output by enabling the 'print-tgid' trace option. This is
useful when doing post-processing of the trace data, as it allows events to be
grouped by tgid.
Cc: Steven Rostedt
Cc: kernel-t
At 05/16/2017 09:12 AM, Baoquan He wrote:
On 05/16/17 at 08:56am, Dou Liyang wrote:
Hi Baoquan,
At 05/13/2017 01:46 PM, Baoquan He wrote:
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 o
any comments?
On 2017/5/4 10:31, Zefan Li wrote:
> It is assumed that the head of cache_groups always has valid RMID,
> which isn't true.
>
> When we deallocate RMID from conflicting events currently we don't
> move them to the tail, and one of those events can happen to be in
> the head. Another
On 05/15/2017 04:35 PM, Stefano Stabellini wrote:
The pvcalls backend has one ioworker per cpu: the ioworkers are
implemented as a cpu bound workqueue, and will deal with the actual
socket and data ring reads/writes.
ioworkers are global: we only have one set for all the frontends. They
proces
On Mon, May 15, 2017 at 12:21:15PM +0300, Madalin Bucur wrote:
> Madalin Bucur (3):
> arm64: dts: add DPAA QBMan portals
> arm64: dts: add LS1043A DPAA QBMan nodes
> arm64: dts: add LS1046A DPAA QBMan nodes
Applied all, thanks.
On May 15, 2017, at 5:46 PM, Johannes Weiner wrote:
>
> We have observed across several workloads situations where kswapd and
> direct reclaimers get stuck in the inode shrinker of the ext4 / mount,
> causing allocation latencies across tasks in the system, while there
> are dozens of gigabytes o
On (05/15/17 16:41), Minchan Kim wrote:
[..]
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index b885356551e9..8152e405117b 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -624,15 +624,22 @@ static void zram_free_page(struct z
On Tue, May 16, 2017 at 09:19:57AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> commit: c1aad8dcc49382399f48541dc47b6e30b0ef1b62 ("asm-generic: zero in
> __get_user(), not __get_user_fn()")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
Sorry for a noise.
Failure is due to suspicious subject.
Change it and resend.
-->8---
>From 989d7b079c1fd0b934d98d738cbecf7a56f8c6e6 Mon Sep 17 00:00:00 2001
From: Joonsoo Kim
Date: Fri, 3 Feb 2017 12:52:13 +0900
Subject: [PATCH v1 01/11] mm/kasan: rename _is_
cto-ia32-5/trinity-300s-yocto-tiny-i386-2016-04-22.cgz-c1aad8dcc49382399f48541dc47b6e30b0ef1b62-20170515-127570-ve362v-0.cgz
/lkp/lkp/lkp-i386.cgz
To reproduce:
git clone https://github.com/01org/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k job-script # job-script i
Hi all,
Changes since 20170515:
The akpm tree lost a patch that turned up elsewhere.
Non-merge commits (relative to Linus' tree): 1064
1008 files changed, 26929 insertions(+), 14343 deletions(-)
I have cr
From: Joonsoo Kim
Original shadow memory is only used when it is used by specific types
of access. We can distinguish them and can allocate actual shadow memory
on-demand to reduce memory consumption.
There is a problem on this on-demand shadow memory. After setting up
new mapping, we need to fl
From: Joonsoo Kim
This patch enables for x86 to use per-page shadow memory.
Most of initialization code for per-page shadow memory is
copied from the code for original shadow memory.
There are two things that aren't trivial.
1. per-page shadow memory for global variable is initialized
as the byp
From: Joonsoo Kim
Enable on-demand shadow mapping in x86.
x86 uses separate per-cpu kernel stack for interrupt/exception context.
We need to populate shadow memory for them before they are used.
And, there are two possible problems due to stable TLB entry when using
on-demand shadow mapping sin
From: Joonsoo Kim
Majority of access in the kernel is an access to slab objects.
In current implementation, we checks two types of shadow memory
in this case and it causes performance regression.
kernel build (2048 MB QEMU)
Base vs per-page
219 sec vs 238 sec
Although current per-page shadow im
From: Joonsoo Kim
Now, we have the per-page shadow. The purpose of the per-page shadow is
to check the page that is just used/checked in page size granularity.
File cache pages/anonymous page are in this category. The other
category is for being used by byte size granularity. Global variable,
ker
1 - 100 of 1000 matches
Mail list logo
