From: Dave Martin
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7195ee3120d878259e8d94a5d9f808116f34d5ea upstream.
It's not clear what behaviour is sensible when doing partial write of
NT_METAG_RPIPE, so just don't bother.
This patch assum
From: Peter Xu
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit df630b8c1e851b5e265dc2ca9c87222e342c093b upstream.
When releasing the bus, let's clear the bus pointers to mark it out. If
any further device unregister happens on this bus, we kn
From: Uwe Kleine-König
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit f87e904ddd8f0ef120e46045b0addeb1cc88354e upstream.
There are several issues fixed in this patch:
- When alarm isn't enabled, set .enabled to zero instead of returning
From: Naoya Horiguchi
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit c9d398fa237882ea07167e23bcfc5e6847066518 upstream.
I found the race condition which triggers the following bug when
move_pages() and soft offline are called on a single hug
From: Uwe Kleine-König
3.12-stable review patch. If anyone has any objections, please let me know.
===
The rtc core calls the .read_alarm with all fields initialized to 0. As
the s35390a driver doesn't touch some fields the returned date is
interpreted as a date in January 1900. So
From: Uwe Kleine-König
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 8e6583f1b5d1f5f129b873f1428b7e414263d847 upstream.
There were two deviations from the reference manual: you have to wait
half a second when POC is active and you might hav
From: Uwe Kleine-König
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 3bd32722c827d00eafe8e6d5b83e9f3148ea7c7e upstream.
On some QNAP NAS devices the rtc can wake the machine. Several people
noticed that once the machine was woken this way i
On Mon 2017-02-13 19:42:28, Josh Poimboeuf wrote:
> For live patching and possibly other use cases, a stack trace is only
> useful if it can be assured that it's completely reliable. Add a new
> save_stack_trace_tsk_reliable() function to achieve that.
>
> Note that if the target task isn't the c
From: Alan Stern
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 1633682053a7ee8058e10c76722b9b28e97fb73f upstream.
Using KASAN, Dmitry found a bug in the rh_call_control() routine: If
buffer allocation fails, the routine returns immediately
From: David Hildenbrand
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 90db10434b163e46da413d34db8d0e77404cc645 upstream.
No caller currently checks the return value of
kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on
From: "Rafael J. Wysocki"
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit d4faadd5d5b368a7051fef374ee933ec3606713b upstream.
Commit 2167e2399dc5 (cpufreq: fix garbage kobjects on errors during
suspend/resume) breaks suspend/resume on Martin Z
From: Josh Poimboeuf
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 61b79e16c68d703dde58c25d3935d67210b7d71b upstream.
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functi
From: Hugh Dickins
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit ab3f5faa6255a0eb4f832675507d9e295ca7e9ba upstream.
Sometimes the cleanup after memcg hierarchy testing gets stuck in
mem_cgroup_reparent_charges(), unable to bring non-kmem us
From: "Rafael J. Wysocki"
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 0f1b414d190724617eb1cdd615592fa8cd9d0b50 upstream.
Commit b9a5e5e18fbf "ACPI / init: Fix the ordering of
acpi_reserve_resources()" overlooked the fact that the memory
a
From: Viresh Kumar
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 92c14bd9477a20a83144f08c0ca25b0308bf0730 upstream.
This is only relevant to implementations with multiple clusters, where clusters
have separate clock lines but all CPUs withi
From: "Rafael J. Wysocki"
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 0294112ee3135fbd15eaa70015af8283642dd970 upstream.
This effectively reverts the following three commits:
7bc10388ccdd ACPI / resources: free memory on error in add_re
From: Takashi Iwai
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit f363a06642f28caaa78cb6446bbad90c73fe183c upstream.
In the commit [15c75b09f8d1: ALSA: ctxfi: Fallback DMA mask to 32bit],
I forgot to put "!" at dam_set_mask() call check in c
From: Alan Stern
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7d8021c967648accd1b78e5e1ddaad655cd2c61f upstream.
This patch fixes a bug introduced by commit 977dcfdc6031 ("USB: OHCI:
don't lose track of EDs when a controller dies"). The c
From: Takashi Iwai
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 2d7d54002e396c180db0c800c1046f0a3c471597 upstream.
When a new event is queued while processing to resize the FIFO in
snd_seq_fifo_clear(), it may lead to a use-after-free, as
From: Takashi Iwai
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 15c75b09f8d190f89ab4db463b87d411ca349dfe upstream.
Currently ctxfi driver tries to set only the 64bit DMA mask on 64bit
architectures, and bails out if it fails. This causes
From: Colin Ian King
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit ed9ab4287f96e66340e0390e2c583f2f9110cba0 upstream.
Quirking the following AMI USB device with ALWAYS_POLL fixes an AMI
virtual keyboard and mouse from not responding and tim
From: Brendan McGrath
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit a89af4abdf9b353cdd6f61afc0eaaac403304873 upstream.
Support for the Asus Touchpad was recently added. It turns out this
device can fail initialisation (and become unusable)
From: Ardinartsev Nikita
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 877a021e08ccb6434718c0cc781fdf943c884cc0 upstream.
With NOGET quirk Logitech F510 is now fully workable in dinput mode including
rumble effects (according to fftest).
B
From: Maxime Ripard
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 259b77ef853cc375a5c9198cf81f9b79fc19413c upstream.
The TCA8418 might be used using different interrupt triggers on various
boards. This is not working so far because the curr
From: Akinobu Mita
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 08fea55e37f58371bffc5336a59e55d1f155955a upstream.
This driver reports input events on their interrupts which are triggered
by the sensor's status register changes. But only
From: Raphael Assenat
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 45536d373a21d441bd488f618b6e3e9bfae839f3 upstream.
Postpone axis initialization to the first open instead of doing it
in joydev_connect. This is to make sure the generated
From: Dan Carpenter
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7bc10388ccdd79b3d20463151a1f8e7a590a775b upstream.
There is a small memory leak on error.
Fixes: 0f1b414d1907 (ACPI / PNP: Avoid conflicting resource reservations)
Signed-of
From: Akinobu Mita
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 9723ddc8fe0d76ce41fe0dc16afb241ec7d0a29d upstream.
This driver reports misc scan input events on the sensor's status
register changes. But the event capability for them was n
From: Richard Genoud
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 31ca2c63fdc0aee725cbd4f207c1256f5deaabde upstream.
If uart_flush_buffer() is called between atmel_tx_dma() and
atmel_complete_tx_dma(), the circular buffer has been cleared,
From: "Jason A. Donenfeld"
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit de5540d088fe97ad583cc7d396586437b32149a5 upstream.
Under extremely heavy uses of padata, crashes occur, and with list
debugging turned on, this happens instead:
[8748
From: Andrew Lunn
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 4eba7bb1d72d9bde67d810d09bf62dc207b63c5c upstream.
When a multicast group is joined on a socket, a struct ip_mc_socklist
is appended to the sockets mc_list containing informati
From: Ludovic Desroches
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit a9bed6b10bd117a300cceb9062003f7a2761ef99 upstream.
In some cases, we could start a new i2c transfer with the RXRDY flag
set. It is not a clean state and it leads to print
From: Eric Biggers
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit b9cf625d6ecde0d372e23ae022feead72b4228a6 upstream.
If ext4_convert_inline_data() was called on a directory with inline
data, the filesystem was left in an inconsistent state (
From: Johan Hovold
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 4ce362711d78a4999011add3115b8f4b0bc25e8c upstream.
Make sure to check the number of endpoints to avoid dereferencing a
NULL-pointer should a malicious device lack endpoints.
From: Johan Hovold
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 181302dc7239add8ab1449c23ecab193f52ee6ab upstream.
Make sure to check the number of endpoints to avoid dereferencing a
NULL-pointer should a malicious device lack endpoints.
From: Dan Williams
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 6e9f44eaaef0df7b846e9316fa9ca72a02025d44 upstream.
Add Quectel UC15, UC20, EC21, and EC25. The EC20 is handled by
qcserial due to a USB VID/PID conflict with an existing Acer
From: Mathias Nyman
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 98d74f9ceaefc2b6c4a6440050163a83be0abede upstream.
PCI hotpluggable xhci controllers such as some Alpine Ridge solutions will
remove the xhci controller from the PCI bus when
From: "Darrick J. Wong"
3.12-stable review patch. If anyone has any objections, please let me know.
===
Commit ef388e2054feedaeb05399ed654bdb06f385d294 upstream.
The on-disk field di_size is used to set i_size, which is a signed
integer of loff_t. If the high bit of di_size is se
From: Mikulas Patocka
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit d67a5f4b5947aba4bfe9a80a2b86079c215ca755 upstream.
Commit df2cb6daa4 ("block: Avoid deadlocks with bio allocation by
stacking drivers") created a workqueue for every bio se
From: Keno Fischer
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 8310d48b125d19fcd9521d83b8293e63eb1646aa upstream.
In commit 19be0eaffa3a ("mm: remove gup_flags FOLL_WRITE games from
__get_user_pages()"), the mm code was changed from unset
This is the start of the stable review cycle for the 3.12.73 release.
There are 142 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 made by Wed Apr 12 17:33:10 CEST 2017.
Anything rece
On Mon 10-04-17 17:22:28, Michal Hocko wrote:
[...]
> Heh, this one is embarrassing
> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
> index 1c6fdacbccd3..9677b6b711b0 100644
> --- a/drivers/base/memory.c
> +++ b/drivers/base/memory.c
> @@ -402,7 +402,7 @@ static ssize_t show_valid_zone
On Sun, Apr 09, 2017 at 09:02:03PM +0200, Greg KH wrote:
On Sun, Apr 09, 2017 at 04:28:12PM +0200, Arthur Brainville (Ybalrid) wrote:
> According to checkpatch.pl, comedi_lrange should be declared as `const
> struct` instead of `struct` in driver/staging/comedidev.h
>
> Signed-off-by: Arthur Brai
Hi Yongjun,
On 2017/2/5 16:32, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return error code -ENODEV from the of_find_compatible_node()
> error handling case instead of 0, as done elsewhere in this function.
>
> Signed-off-by: Wei Yongjun
Thanks!
Applied to the hisilicon soc tree.
Best
This patch-set handles the Serial Audio Interface (SAI) IP on STM32 platforms.
The SAI IP is composed of two Sub-block A and B. (see the figure below)
Each sub-block makes use of individual and shared resources.
Shared resources:
- Reset line. Reset common and sub-block registers.
This patch implements SAI ASoC driver for STM32.
Signed-off-by: olivier moysan
---
sound/soc/Kconfig | 1 +
sound/soc/Makefile| 1 +
sound/soc/stm/Kconfig | 8 +
sound/soc/stm/Makefile| 6 +
sound/soc/stm/stm32_sai.c | 115 ++
sound/soc/stm
This patch adds documentation of device tree bindings for the
STM32 SAI ASoC driver.
Signed-off-by: olivier moysan
---
.../devicetree/bindings/sound/st,stm32-sai.txt | 89 ++
1 file changed, 89 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/st,s
[dropping Lai Jiangshan whose email bounces]
On Mon 10-04-17 16:56:39, Michal Hocko wrote:
> On Mon 10-04-17 16:27:49, Igor Mammedov wrote:
> [...]
> > Hi Michal,
> >
> > I've given series some dumb testing, see below for unexpected changes I've
> > noticed.
> >
> > Using the same CLI as above
If we set a kprobe on a 'stdu' instruction on powerpc64, we see a kernel
OOPS:
[ 1275.165932] Bad kernel stack pointer cd93c840 at c0009868
[ 1275.166378] Oops: Bad kernel stack pointer, sig: 6 [#1]
...
GPR00: c01fcd93cb30 cd93c840 c15c5e00 cd93c840
.
On Tue, Apr 04, 2017 at 05:44:31PM +0200, Hugues Fruchet wrote:
> This adds documentation of device tree bindings for the STM32 DCMI
> (Digital Camera Memory Interface).
>
> Signed-off-by: Hugues Fruchet
> ---
> .../devicetree/bindings/media/st,stm32-dcmi.txt| 46
> ++
>
From: Mathias Krause
vdso_enabled can be set to arbitrary integer values via the kernel command
line 'vdso32=' parameter or via 'sysctl abi.vsyscall32'.
load_vdso32() only maps VDSO if vdso_enabled == 1, but ARCH_DLINFO_IA32
merily checks for vdso_enabled != 0. As a consequence the AT_SYSINFO_EH
The vsyscall32 sysctl can racy against a concurrent fork when it switches
from disabled to enabled:
arch_setup_additional_pages()
if (vdso32_enabled)
--> No mapping
sysctl.vsysscall32()
--> vds
vdso*_enabled is conceptionally a boolean. Though there are leftovers from
the original implementation which required an int. That's just confusing
and error prone.
Convert evrything to boolean and correct stale comments.
Signed-off-by: Thomas Gleixner
Cc: Andy Lutomirski
Cc: Mathias Krause
--
On Friday, April 7, 2017 6:16:08 PM EDT Tyler Hicks wrote:
> On 02/22/2017 12:46 PM, Kees Cook wrote:
> > On Thu, Feb 16, 2017 at 3:29 PM, Kees Cook wrote:
> >> On Wed, Feb 15, 2017 at 7:24 PM, Andy Lutomirski
wrote:
> >>> On Mon, Feb 13, 2017 at 7:45 PM, Tyler Hicks
wrote:
> This patch s
The following series is a collection of Mathias enable fix, the plug of the
sysctl race and a cleanup of the vdso*_enable handling.
Thanks,
tglx
On Wed, Apr 05, 2017 at 08:23:29AM +0200, Richard Leitner wrote:
> On 04/05/2017 06:40 AM, Jaehoon Chung wrote:
> > Hi,
> >
> > On 04/04/2017 11:16 PM, Richard Leitner wrote:
> >> Some eMMCs disable their hardware reset line (RST_N) by default. To enable
> >> it the host must set the corresponding
On Mon, 10 Apr 2017, Felipe Balbi wrote:
> Hi,
>
> Alan Stern writes:
> > On Wed, 5 Apr 2017, Felipe Balbi wrote:
> >
> >> >> >> --- a/drivers/usb/gadget/udc/core.c
> >> >> >> +++ b/drivers/usb/gadget/udc/core.c
> >> >> >> @@ -1273,6 +1273,7 @@ void usb_del_gadget_udc(struct usb_gadget
> >> >>
On Mon, 2017-04-10 at 11:55 +0200, Paolo Valente wrote:
> That said, if you do always want maximum throughput, even at the
> expense of latency, then just switch off low-latency heuristics, i.e.,
> set low_latency to 0. Depending on the device, setting slice_ilde to
> 0 may help a lot too (as well
On 30 March 2017 at 17:22, Gregory CLEMENT
wrote:
> Hello,
>
> This the seventh version of the series adding support for the SDHCI
> Xenon controller. It can be currently found on the Armada 37xx and the
> Armada 7K/8K but will be also used in more Marvell SoC (and not only
> the mvebu ones actual
On Mon, Apr 10, 2017 at 02:06:38PM +0200, Jan Kara wrote:
> On Mon 10-04-17 02:22:33, alexander.le...@verizon.com wrote:
> > On Fri, Dec 05, 2014 at 09:52:44AM -0500, Johannes Weiner wrote:
> > > Tejun, while reviewing the code, spotted the following race condition
> > > between the dirtying and tr
From: Markus Elfring
Date: Mon, 10 Apr 2017 17:00:13 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle software.
On Mon, 10 Apr 2017 16:17:27 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > which software have you used as representative of "reality"?
>
> ppc64 (big endian) virtual machine, running with qemu stdvga & bochs-drm
> driver. Xorg with modesetting driver uses DRM_FORMAT_XRGB (one and
> only form
On Mon, Apr 10, 2017 at 04:35:58PM +0200, Boris Brezillon wrote:
> On Mon, 10 Apr 2017 17:20:20 +0300
> Claudiu Beznea wrote:
>
> > Implement suspend and resume power management specific
> > function to allow PWM controller to correctly suspend
> > and resume.
> >
> > Signed-off-by: Claudiu Bezn
On 04/08/2017 11:12 AM, Emil Velikov wrote:
> Hi Laura,
>
> Couple of trivial nitpicks below.
>
> On 3 April 2017 at 19:57, Laura Abbott wrote:
>
>> --- a/drivers/staging/android/ion/ion.h
>> +++ b/drivers/staging/android/ion/ion.h
>> @@ -1,5 +1,5 @@
>> /*
>> - * drivers/staging/android/ion/io
On (04/10/17 13:54), Petr Mladek wrote:
[..]
> > > that works with my proposal, but not with yours. Seen it happen many
> > > times before.
> >
> > I see your point, sure.
> > I can't completely agree on "that works with my proposal, but not with
> > yours."
> >
> > on SMP system this would be t
From: Jesper Dangaard Brouer
IRQ context were excluded from using the Per-Cpu-Pages (PCP) lists caching
of order-0 pages in commit 374ad05ab64d ("mm, page_alloc: only use per-cpu
allocator for irq-safe requests").
This unfortunately also included excluded SoftIRQ. This hurt the performance
for
On Mon, Mar 27, 2017 at 02:18:16PM +0100, Juri Lelli wrote:
> arm and arm64 topology.c share a lot of code related to parsing of capacity
> information. This is v3 of a solution [1] (based on Will's, Catalin's and
> Mark's off-line suggestions) to move such common code in a single place:
> drivers/
On Mon, Apr 03, 2017 at 03:23:47PM -0500, David Lechner wrote:
> This add a new device tree binding for LEGO MINDSTORMS EV3 battery. The EV3
> has some built-in capability for monitoring the attached battery.
>
> Signed-off-by: David Lechner
> ---
> .../bindings/power/supply/lego_ev3_battery.txt
On Fri, Apr 07, 2017 at 05:27:40AM +0200, Jason A. Donenfeld wrote:
> Given that the below commit isn't very big and adds a nice security
> property (in addition to performance), it might be worthwhile to
> backport this to 4.9 stable. It's not a candidate for 4.4, since that
> kernel doesn't use c
On Mon, Apr 03, 2017 at 06:44:46PM +0200, Enric Balletbo i Serra wrote:
> Allow the possibility to configure the charge and the current voltage of
> the charger and also the NTC type for battery temperature measurement.
>
> Signed-off-by: Enric Balletbo i Serra
> ---
> .../bindings/power/supply/
sparse says
warning: incorrect type in assignment (different base types)
expected unsigned short [unsigned] [usertype] offset
got restricted __be16 [usertype]
for every usage of cpu_to_be16 in yealink.c. Defining it __be16 in the
first place shouldn't hurt.
Signed-off-by: Martin Keppli
On Mon, 10 Apr 2017, 冯伟linux wrote:
> > --- a/drivers/mfd/rtsx_pcr.c
> > +++ b/drivers/mfd/rtsx_pcr.c
> > @@ -30,6 +30,7 @@
> > #include
> > #include
> > #include
> > +#include
> > Why is this required?
> >
> The UHS_SER104_MAX_DTR which is in "card_clock = UHS_SER104_MAX_DTR
> - (pcr->dma
On Mon, Apr 10, 2017 at 03:39:55PM +0200, Thomas Gleixner wrote:
> Notifiers? You mean a proper NMI handler, right?
I mean notifiers in the sense, the NMI handler should queue the logged
error on the decoding chain x86_mce_decoder_chain like the rest of RAS
code does instead of calling straight in
On Mon, 10 Apr 2017, Quentin Schulz wrote:
> Hi Lee,
>
> Just to make sure you didn't miss that patch (can't find it in
> for-mfd-next and for-mfd-next-next).
It has not been missed, but is yet to be reviewed.
> On 04/04/2017 08:34, Quentin Schulz wrote:
> > The X-Powers AXP20X and AXP22X PMICs
On Mon, Apr 10, 2017 at 7:22 AM, tedheadster wrote:
> On Sat, Apr 8, 2017 at 6:23 AM, Francois Romieu wrote:
>> David Miller :
>> [...]
>>> One theory is that the interrupt masking isn't working properly
>>> and interrupts are still arriving and hitting the NAPI state even
>>> when we are active
Hi.
2017-04-06 4:11 GMT+09:00 Michael Davidson :
> It "works" for the cases that I currently care about but I have to say
> that I am uneasy about adding -Werror to the cc-option test in this
> way.
>
> Suppose that one of the *other* flags that is implicitly passed to the
> compiler by cc-option
On Mon, Apr 03, 2017 at 05:02:28PM +0300, Todor Tomov wrote:
> Add the document for ov5645 device tree binding.
>
> Signed-off-by: Todor Tomov
> Reviewed-by: Laurent Pinchart
> ---
> .../devicetree/bindings/media/i2c/ov5645.txt | 54
> ++
> 1 file changed, 54 insertio
On Mon 10-04-17 16:27:49, Igor Mammedov wrote:
[...]
> Hi Michal,
>
> I've given series some dumb testing, see below for unexpected changes I've
> noticed.
>
> Using the same CLI as above plus hotpluggable dimms present at startup
> (it still uses hotplug path as dimms aren't reported in e820)
>
On 04/10/2017 08:11 AM, Masami Hiramatsu wrote:
On Wed, 5 Apr 2017 22:30:03 -0500
Paul Clarke wrote:
Symbol versioning, as in glibc, results in symbols being defined as:
@[@]
(Note that "@@" identifies a default symbol, if the symbol name
is repeated.)
perf is currently unable to deal with thi
Currently the sram-exec functionality, which allows allocation of
executable memory and provides an API to move code to it, is only
selected in configs for the ARM architecture. Based on commit
5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol manipulation macros for
function body copying") simply copyin
While playing with the resctrl interface I found it much
easier to deal with cpumask list rather than just regular
cpumask.
Adding cpus_list file to provide cpumask list interface
to define group's cpus.
# cd /sys/fs/resctrl/
# echo 1-10 > krava/cpus_list
# cat krava/cpus_list
1-10
# ca
On 04/05/2017 05:14 PM, Russell King - ARM Linux wrote:
> On Wed, Apr 05, 2017 at 10:02:42AM -0600, Shuah Khan wrote:
>> When coherent DMA memory without struct page is shared, importer
>> fails to find the page and runs into kernel page fault when it
>> tries to dmabuf_ops_attach/map_sg/map_page t
On 05/04/17 03:21, Chanwoo Choi wrote:
> Hi Enric,
>
> On 2017년 03월 02일 16:29, Chanwoo Choi wrote:
>> Hi,
>>
>> On 2017년 03월 01일 20:19, Enric Balletbo i Serra wrote:
>>> From: Benson Leung
>>>
>>> This is the driver for the USB Type C cable detection mechanism
>>> built into the ChromeOS Embedd
On 30 March 2017 at 17:31, Jan Glauber wrote:
> Hi Ulf,
>
> we have a bug on some Octeon plattforms so I removed the Octeon driver for now
> (but kept the DT bindings for it). We'll submit the Octeon driver later when
> we've fixed the issue.
>
> Changes to v12:
> - dts: use generic "mmc-slot" for
On sama5d2, VDD core may be cut while suspending to RAM. This means the
AIC5 registers content is lost. Restore it at resume time.
Signed-off-by: Alexandre Belloni
---
Changes in v2:
- smr_cache is now static and is allocated at init time
- saving SMR and restoring it only happens when smr_cach
On Mon, Apr 10, 2017 at 10:17 AM, Gerd Hoffmann wrote:
> Hi,
>
>> which software have you used as representative of "reality"?
>
> ppc64 (big endian) virtual machine, running with qemu stdvga & bochs-drm
> driver. Xorg with modesetting driver uses DRM_FORMAT_XRGB (one and
> only format supp
Vitaly Kuznetsov writes:
> Jork Loeser writes:
>
[snip]
>
>>> + }
>>> +#else
>>> + {
>>> + u32 hv_status_hi, hv_status_lo;
>>> +
>>> + __asm__ __volatile__ ("call *%6"
>>> + : "=d"(hv_status_hi),
>>> + "=
On Mon, Apr 10, 2017 at 10:33:56PM +0800, zhong jiang wrote:
> On 2017/4/10 22:13, Willy Tarreau wrote:
> > On Mon, Apr 10, 2017 at 10:06:59PM +0800, zhong jiang wrote:
> >> On 2017/4/10 20:48, Michal Hocko wrote:
> >>> On Mon 10-04-17 20:10:06, zhong jiang wrote:
> On 2017/4/10 16:56, Mel Gor
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Friday, April 7, 2017 4:27 AM
>> To: de...@linuxdriverproject.org; x...@kernel.org
>> Cc: linux-kernel@vger.kernel.org; KY Srinivasan ;
>> Haiyang Zhang ; Stephen Hemminger
>> ; Tho
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6).
Unfortunately it's not reproducible.
BUG: KASAN: use-after-free in ip_select_ttl include/net/dst.h:176
[inline] at addr 88006ab3602c
BUG: KASAN: us
On Fri, Feb 24, 2017 at 5:06 PM, Aniroop Mathur wrote:
>> Hi
>>
>> On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote:
>>> On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann
>>> wrote:
On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur
wrote:
> continue;
>>>
To fix following build error when SOFTWARE_REBOOT is defined:
CC [M] driver/watchdog/wdt_pci.o
driver/watchdog/wdt_pci.c: In function 'wdtpci_interrupt':
driver/watchdog/wdt_pci.c:335:3: error: too many arguments to function
'emergency_restart'
emergency_restart(NULL);
^
In file included
On (04/10/17 14:20), Petr Mladek wrote:
[..]
> > Sergey has mentioned it already:
> > "at some point freezes user space and kernel threads".
> > Well, this is the action which is *itself* causing thoroughly disrupting
> > consequences,
> > which I'd think thus ought to be responsible to
> > ensure
On 2017/4/10 22:13, Willy Tarreau wrote:
> On Mon, Apr 10, 2017 at 10:06:59PM +0800, zhong jiang wrote:
>> On 2017/4/10 20:48, Michal Hocko wrote:
>>> On Mon 10-04-17 20:10:06, zhong jiang wrote:
On 2017/4/10 16:56, Mel Gorman wrote:
> On Sat, Apr 08, 2017 at 09:39:42PM +0800, zhong jiang
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6).
Unfortunately it's not reproducible.
==
BUG: KASAN: use-after-free in __read_once_size
On Mon, 10 Apr 2017 17:20:20 +0300
Claudiu Beznea wrote:
> Implement suspend and resume power management specific
> function to allow PWM controller to correctly suspend
> and resume.
>
> Signed-off-by: Claudiu Beznea
> ---
> drivers/pwm/pwm-atmel.c | 81
>
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6).
Unfortunately it's not reproducible.
BUG: KASAN: use-after-free in ip_check_mc_rcu+0x805/0x8b0
net/ipv4/igmp.c:2645 at addr 880065b21cb8
Read of si
On Thu, Apr 06, 2017 at 11:47:37AM +0100, Russell King - ARM Linux wrote:
> On Thu, Apr 06, 2017 at 11:26:36AM +0100, Lorenzo Pieralisi wrote:
> > On Wed, Apr 05, 2017 at 01:38:12PM +0100, Lorenzo Pieralisi wrote:
> > > eg: openrisc
> > >
> > > >> include/asm-generic/io.h:922:9: error: implicit de
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6).
Unfortunately it's not reproducible.
==
BUG: KASAN: use-after-free in ipv6_sock_ac_clos
Hi Lee,
On Mon, Apr 03, 2017 at 11:26:15AM +0100, Lee Jones wrote:
> On Wed, 29 Mar 2017, Sebastian Reichel wrote:
>
> > CPCAP can sense if IRQ is currently set or not. This
> > functionality is required for a few subdevices, such
> > as the power button and usb phy modules.
> >
> > Acked-by: To
901 - 1000 of 1311 matches
Mail list logo
