From: Noam Camus
The reasons are:
1) speeding up boot time, becomes critical for many CPUs machine,
e.g. NPS400 with 4K CPUs
2) shorten kernel log at boot time, again easy to scan for large
scale machines such NPS400
Signed-off-by: Noam Camus
---
arch/arc/kernel/setup.c |6 +++---
ar
From: Noam Camus
Change Log
---
v1 --> v2:
Outcome of Alexey Brodkin comments
1) Turned mem_service into weak symbol, so it can be override
by any platform
2) remove ifedf wrapper on '88' lable at assembly of TLB exception.
With this patch set I continue the effort of upstreaming the
ez
From: Noam Camus
When HW threads are active we want CPU to enter idle state only
for the calling HW thread and not to put on sleep all HW threads
sharing this core. For this need the NPS400 got dedicated instruction
so only calling thread is entring sleep and all other are still awake
and can exe
From: Noam Camus
This counter represents threshold for consecutive stall that which
trigger HW threads scheduling.
When this feature is enabled low values of this counter cause
downgrade in performance and in the worst case even a livelock.
Remove those couple of lines and resort to HW reset val
From: Noam Camus
Signed-off-by: Noam Camus
Reviewed-by: Alexey Brodkin
---
arch/arc/plat-eznps/Kconfig |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arc/plat-eznps/Kconfig b/arch/arc/plat-eznps/Kconfig
index 1595a38..feaa471 100644
--- a/arch/arc/plat-eznps/K
From: Noam Camus
This way when we execute "ex" during trying to hold lock we can switch to
other HW thread and utilize the core intead of just spinning on a lock.
We noticed about 10% improvement of execution time with hackbench test.
Signed-off-by: Noam Camus
---
arch/arc/include/asm/spinloc
From: Noam Camus
Due to a HW bug in NPS400 we get from time to time false TLB miss.
Workaround this by validating each miss.
Signed-off-by: Noam Camus
---
arch/arc/mm/tlbex.S |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/arch/arc/mm/tlbex.S b/arch/arc/mm/tlbe
From: Noam Camus
For User Mode Memory Bus Error some platforms do not creat interrupt
level 2 e.g. nps400 creates machine check exception.
Turning mem_service into weak symbol allows each platform to override
mem_service with its own implementation.
Signed-off-by: Noam Camus
---
arch/arc/kerne
From: Liav Rehana
Signed-off-by: Liav Rehana
Signed-off-by: Noam Camus
Reviewed-by: Alexey Brodkin
---
arch/arc/mm/fault.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arc/mm/fault.c b/arch/arc/mm/fault.c
index 162c975..a0b7bd6 100644
--- a/arch/arc/mm/fault.
From: Noam Camus
This commit adds the configuration CONFIG_EZNPS_MEM_ERROR.
If set, it will cause the kernel to handle user memory error
as a machine check exception.
It is required in order to align the NPS simulator memory
error handling to the one of the NPS400 real chip behavior.
We override
From: Liav Rehana
Signed-off-by: Liav Rehana
Signed-off-by: Noam Camus
Reviewed-by: Alexey Brodkin
---
arch/arc/kernel/entry-compact.S | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arc/kernel/entry-compact.S b/arch/arc/kernel/entry-compac
From: Noam Camus
This patch is derived due to performance issue.
The use case is a page fault that resides on more than the local cpu.
Trying to broadcast all CPUs results on performance degradation.
So we try to avoid this by sending only to the relevant CPUs.
Signed-off-by: Noam Camus
Reviewe
Hi Xiaowei,
[auto build test ERROR on pci/next]
[also build test ERROR on v4.12-rc2 next-20170526]
[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/Xiaowei-Song/DT-and-Driver-review-comments-fix/2
These functions are only used by this driver, make them static.
Signed-off-by: Axel Lin
---
drivers/regulator/bd9571mwv-regulator.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/regulator/bd9571mwv-regulator.c
b/drivers/regulator/bd9571mwv-regulator.c
Hi Chris,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 249f1efd8e3d58f86469fc305b0eda39db18d7ce
commit: 894ccebee2b0e606ba9638d20dd87b33568482d7 drm/i915: Micro-optimise
gen8_ppgtt_insert_entries()
date: 3 mont
Hi Hans,
[auto build test ERROR on ljones-mfd/for-mfd-next]
[also build test ERROR on v4.12-rc2 next-20170526]
[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/Hans-de-Goede/mfd-intel_soc_pmic-Sel
Hi Chris,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 249f1efd8e3d58f86469fc305b0eda39db18d7ce
commit: b348090d6758cc391dc91f8a8233b18f0acc8458 drm/i915: Simple selftest to
exercise live requests
date: 3 month
On Sat, May 27, 2017 at 05:39:14PM -0700, Kees Cook wrote:
> Prepare to mark sensitive kernel structures for randomization by making
> sure they're using designated initializers. In this case, no initializers
> are needed (they can be NULL initialized and callers adjusted to check
> for NULL, which
On Sat, May 27, 2017 at 01:03:23PM -0700, Kees Cook wrote:
> On Sat, May 27, 2017 at 1:42 AM, Christoph Hellwig wrote:
> > On Fri, May 26, 2017 at 01:17:15PM -0700, Kees Cook wrote:
> >> Since the ACPICA source is maintained externally to the kernel, we can
> >> neither switch it to designated ini
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 249f1efd8e3d58f86469fc305b0eda39db18d7ce
commit: 7142afb3a186ed2cd028318205a4852f04283380 drm/panel: Add driver for
sitronix ST7789V LCD controller
date: 7 weeks ago
config: x86_64-randconfig-s3-05280946 (
On Sat, May 27, 2017 at 11:58:47AM +0200, Daniel Lezcano wrote:
> diff --git a/arch/arm/mach-imx/epit.c b/arch/arm/mach-imx/epit.c
> index fb9a73a..4a4d2e2 100644
> --- a/arch/arm/mach-imx/epit.c
> +++ b/arch/arm/mach-imx/epit.c
> @@ -39,7 +39,7 @@
> #define EPITCR_OM_TOGGLE (1 << 22)
Hi Kan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc2 next-20170526]
[cannot apply to tip/x86/core]
[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/kan-liang-intel-c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 249f1efd8e3d58f86469fc305b0eda39db18d7ce
commit: ed29f9426d9bf1b5ec7e79dfb28f39de7b3a0069 drm/panel: Add support for
S6E3HA2 panel driver on TM2 board
date: 7 weeks ago
config: x86_64-randconfig-s3-0528094
Hi Brian,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.12-rc2 next-20170526]
[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/Liviu-Dudau/drm-mali-dp-Add-support-for-writeb
+++ Luis R. Rodriguez [25/05/17 17:44 -0700]:
kmod <= v19 was broken -- it could return 0 to modprobe calls,
incorrectly assuming that a kernel module was built-in, whereas in
reality the module was just forming in the kernel. The reason for this
is an incorrect userspace heuristics. A userspace
+++ Masami Hiramatsu [26/05/17 09:24 +0900]:
On Thu, 25 May 2017 19:24:26 +0200
"Luis R. Rodriguez" wrote:
On Thu, May 25, 2017 at 07:38:17PM +0900, Masami Hiramatsu wrote:
> Fix kprobes to set(recover) RWX bits correctly on trampoline
> buffer before releasing it. Releasing readonly page to
>
Kees Cook wrote:
> On Sat, May 27, 2017 at 4:17 AM, Tetsuo Handa
> wrote:
> > Commit 3dfc9b02864b19f4 ("LSM: Initialize security_hook_heads upon
> > registration.") treats "struct security_hook_heads" as an implicit array
> > of "struct list_head" so that we can eliminate code for static
> > initi
On Sat, May 27, 2017 at 4:17 AM, Tetsuo Handa
wrote:
> Commit 3dfc9b02864b19f4 ("LSM: Initialize security_hook_heads upon
> registration.") treats "struct security_hook_heads" as an implicit array
> of "struct list_head" so that we can eliminate code for static
> initialization. Although we haven'
On Sat, May 27, 2017 at 3:04 PM, Tetsuo Handa
wrote:
> Kees Cook wrote:
>> On Sat, May 27, 2017 at 1:41 AM, Christoph Hellwig
>> wrote:
>> > On Fri, May 26, 2017 at 01:17:09PM -0700, Kees Cook wrote:
>> >> The LSM initialization routines walk security_hook_heads as an array
>> >> of struct list_
From: Elena Reshetova
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Cc: Manfred Spraul
Signed-off-by: Elena Reshetova
Hello Rui,
I know this is late, but please send these six fixes for next rc3.
The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/evalen
Prepare to mark sensitive kernel structures for randomization by making
sure they're using designated initializers. In this case, no initializers
are needed (they can be NULL initialized and callers adjusted to check
for NULL, which is more efficient than an indirect call).
Cc: Robin Holt
Cc: Chr
Casey Schaufler wrote:
> > But currently, LSM_HOOK_INIT() macro depends on the address of
> > security_hook_heads being known at compile time. If we use an enum
> > so that LSM_HOOK_INIT() macro does not need to know absolute address of
> > security_hook_heads, it will help us to use that allocator
Prepare to mark sensitive kernel structures for randomization by making
sure they're using designated initializers. In this case, no initializers
are needed (they can be NULL initialized and callers adjusted to check
for NULL, which is more efficient than an indirect call).
Cc: Robin Holt
Cc: Chr
On Thu, 27 Apr 2017 16:03:45 +0100
David Howells wrote:
> Jérémy Lefaure wrote:
>
> > When building object-list.o, gcc 6 raises a warning on the sprintf call
> > in fscache_objlist_show:
> >
> > CC fs/fscache/object-list.o
> > fs/fscache/object-list.c: In function ‘fscache_objlist_show’
On Fri, May 26, 2017 at 10:27:18AM +0530, Viresh Kumar wrote:
> On 26-04-17, 11:41, Lukasz Luba wrote:
> > Hi Viresh,
> >
> > I went through the v4 code and it looks good to me.
> > Feel free to add for the v4 series
> > Reviewed-by: Lukasz Luba
>
> @Eduardo: You missed adding this to the patche
On Tue, May 9, 2017 at 10:50 AM, Dong Aisheng wrote:
> On new LPUART versions, the oversampling ratio for the receiver can be
> changed from 4x (00011) to 32x (1) which could help us get a more
> accurate baud rate divider.
>
> The idea is to use the best OSR (over-sampling rate) possible.
> N
Add device tree binding documentation for the Qualcomm GLINK RPM, used
for communication with the Resource Power Management subsystem in
various Qualcomm SoCs.
Acked-by: Rob Herring
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- Change node in example to "mailbox"
- Add Rob's ack.
...
This introduces a basic driver for communicating over "native glink"
with the RPM found in Qualcomm platforms.
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- Call mbox_client_txdone() after mbox_send_message()
- Depend on MAILBOX, rather than the APCS_IPC driver
drivers/rpmsg/Kconfig
On May 26, 2017 12:09:04 PM PDT, Dmitry Vyukov wrote:
>Some 64-bit atomic operations use 'long long' as operand/return type
>(e.g. asm-generic/atomic64.h, arch/x86/include/asm/atomic64_32.h);
>while others use 'long' (e.g. arch/x86/include/asm/atomic64_64.h).
>This makes it impossible to write por
Introduce a binding for the Qualcomm APCS global block, exposing a
mailbox for invoking interrupts on remote processors in the system.
Acked-by: Rob Herring
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- None
.../bindings/mailbox/qcom,apcs-kpss-global.txt | 46
This implements a driver that exposes the IPC bits found in the APCS
Global block in various Qualcomm platforms. The bits are used to signal
inter-processor communication signals from the application CPU to other
masters.
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- Add COMPILE_TEST
-
Some mailbox hardware doesn't have to perform any additional operations
on startup of shutdown, so make these optional.
Signed-off-by: Bjorn Andersson
---
Changes since v6:
- None
drivers/mailbox/mailbox.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/dr
From: Vivien Didelot
Date: Fri, 26 May 2017 18:02:42 -0400
> mv88e6xxx_serdes_power returns an error, so no need to print an error
> message inside of it. Rather print it in its caller when the error is
> ignored, which is in the mv88e6xxx_port_disable void function.
>
> Catch and return its err
On Sat, May 27, 2017 at 6:46 PM, Kirill A. Shutemov
wrote:
> On Sat, May 27, 2017 at 11:09:54AM -0400, Brian Gerst wrote:
>> > static inline int pgd_none(pgd_t pgd)
>> > {
>> > + if (p4d_folded)
>> > + return 0;
>> > /*
>> > * There is no need to do a workaro
On Sat, May 27, 2017 at 11:09:54AM -0400, Brian Gerst wrote:
> > static inline int pgd_none(pgd_t pgd)
> > {
> > + if (p4d_folded)
> > + return 0;
> > /*
> > * There is no need to do a workaround for the KNL stray
> > * A/D bit erratum here. PGDs onl
From: Firo Yang
Date: Fri, 26 May 2017 22:37:38 +0800
> syszkaller fuzzer triggered a divide by zero, when set calibration
> through ioctl().
>
> To fix it, test 'bitrate' if it is negative or 0, just return -EINVAL.
>
> Reported-by: Andrey Konovalov
> Signed-off-by: Firo Yang
Applied, thank
On Tue, May 9, 2017 at 11:20 AM, wrote:
> On some Layerscape boards like LS2085ARDB/LS2080ARDB,
> input pull-up resistors on PCA954x Mux device are
> missing on board. So, if mux are disabled after powered-on,
> input lines will float leading to incorrect functionality.
>
> Hence, PCA954x Mux de
On 5/27/2017 4:17 AM, Tetsuo Handa wrote:
> Commit 3dfc9b02864b19f4 ("LSM: Initialize security_hook_heads upon
> registration.") treats "struct security_hook_heads" as an implicit array
> of "struct list_head" so that we can eliminate code for static
> initialization. Although we haven't encountere
On Tue, May 9, 2017 at 11:19 AM, Claudiu Beznea
wrote:
> Extends PWM framework to support PWM dead-times.
> The notions introduced are rising edge dead-time
> and falling edge dead-time. These are useful for
> PWM controllers with channels that have more than
> one outputs.
> The implementation ad
On Tue, May 9, 2017 at 3:15 PM, Claudiu Beznea
wrote:
> Extends PWM framework to support PWM modes. The currently
> implemented PWM modes were called PWM complementary mode
> and PWM push-pull mode. For devices that have more than one
> output per PWM channel:
> - PWM complementary mode is standar
Kees Cook wrote:
> On Sat, May 27, 2017 at 1:41 AM, Christoph Hellwig wrote:
> > On Fri, May 26, 2017 at 01:17:09PM -0700, Kees Cook wrote:
> >> The LSM initialization routines walk security_hook_heads as an array
> >> of struct list_head instead of via names to avoid a ton of needless
> >> source
ieee80211_tx_status() is only one of the possible ways a driver can
report a handled packet, some drivers call this for every packet while
others calls it rarely or never.
In order to invoke the TX LED in the non-status reporting cases this
patch pushes the call to ieee80211_led_tx() into
ieee8021
On Tue, May 9, 2017 at 7:52 PM, Niklas Cassel wrote:
> From: Niklas Cassel
Commit message?
> seq_printf(seq, "%d [0x%x]: 0x%x 0x%x 0x%x 0x%x\n",
> - i, (unsigned int)virt_to_phys(ep),
> + i, (unsigned int)
Hi Elena,
[auto build test ERROR on next-20170526]
[cannot apply to linus/master linux/master kees/for-next/pstore v4.9-rc8
v4.9-rc7 v4.9-rc6 v4.12-rc2]
[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/c
Dear Friend.
Greetings.
My Name is Mustapha Ali, I am a banker by profession. I am from
Ouagadougou, Burkina Faso, West Africa. My reason of contacting you is
to transfer an abandoned fund $5M US Dollars to your account if you
agree with me.
The owner of this fund died since 2003 with his Next O
On Sat, May 27, 2017 at 4:14 AM, Pali Rohár wrote:
> Hi! Note that in WMI is stored binary MOF (BMOF; .bmf file; compiled
> MOF), not ordinary MOF data which are plain text. So maybe it could make
> sense to include "B" into name of sysfs entry? Or not? (Just suggestion)
>
> On Saturday 27 May 201
On Sat 2017-05-27 22:30:35, Sakari Ailus wrote:
> On Sat, May 27, 2017 at 10:12:40AM +0200, Pavel Machek wrote:
> > V4L2_CID_EXPOSURE_BIAS does not exist, fix documentation.
> >
> > Signed-off-by: Pavel Machek
> >
> > diff --git a/Documentation/media/uapi/v4l/extended-controls.rst
> > b/Documen
On 05/27/2017 01:52 PM, Badhri Jagan Sridharan wrote:
User space applications in some cases have the need to enforce a
specific port type(DFP/UFP/DRP). This change allows userspace to
attempt setting the desired port type. Low level drivers can
however reject the request if the specific port type
User space applications in some cases have the need to enforce a
specific port type(DFP/UFP/DRP). This change allows userspace to
attempt setting the desired port type. Low level drivers can
however reject the request if the specific port type is not supported.
Signed-off-by: Badhri Jagan Sridhara
On Sat, May 27, 2017 at 11:48 PM, Pali Rohár wrote:
> On Saturday 27 May 2017 15:33:14 Andy Shevchenko wrote:
>> On Sat, May 27, 2017 at 4:17 PM, Pali Rohár
>> wrote:
>> Okay, got it. But on your opinion does it make sense to do
>>
>> pr_info("\tobject_id: %2pE\n", g->object_id);
>>
>> instead?
On Saturday 27 May 2017 15:33:14 Andy Shevchenko wrote:
> On Sat, May 27, 2017 at 4:17 PM, Pali Rohár
> wrote:
> > On Saturday 27 May 2017 15:07:09 Andy Shevchenko wrote:
> >> On Sat, May 27, 2017 at 2:51 PM, Pali Rohár
> >>
> >> wrote:
> >> > Remove
> >> > also reserved member as it does not ha
On Fri, May 26, 2017 at 7:09 PM, Mika Westerberg
wrote:
> +static inline u8 dual_link_from_link(u8 link)
> +{
> + return link ? ((link - 1) ^ 0x01) + 1 : 0;
> +}
I have got better one (IIUC):
return (link + 1) ^ 0x01) - 1;
--
With Best Regards,
Andy Shevchenko
Thanks Geunter for comments. Will fix them in my next patch.
On Fri, May 26, 2017 at 7:24 PM, Guenter Roeck wrote:
> On 05/26/2017 04:07 PM, Badhri Jagan Sridharan wrote:
>>
>> User space applications in some cases have the need to enforce a
>> specific port type(DFP/UFP/DRP). This change allows
On Fri, May 26, 2017 at 10:43 PM, Greg Kroah-Hartman
wrote:
> On Fri, May 26, 2017 at 01:42:57PM -0700, Badhri Jagan Sridharan wrote:
>> User space applications in some cases have the need to enforce a
>> specific port type(DFP/UFP/DRP). This change allows userspace to
>> attempt setting the desir
On Thu, May 11, 2017 at 3:52 PM, Arnd Bergmann wrote:
> gcc-7 warns about the result of a constant multiplication used as
> a boolean:
>
> drivers/ide/ide-timings.c: In function 'ide_timing_quantize':
> drivers/ide/ide-timings.c:112:24: error: '*' in boolean context, suggest '&&'
> instead [-Werr
Hi Elena,
[auto build test ERROR on next-20170526]
[cannot apply to linus/master linux/master kees/for-next/pstore v4.9-rc8
v4.9-rc7 v4.9-rc6 v4.12-rc2]
[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/c
2017-05-26 23:26 GMT+02:00 Liam Breck :
> Hi Enric,
>
> On Fri, May 26, 2017 at 4:04 AM, Enric Balletbo i Serra
> wrote:
>> The TS pin of the TPS56217 connects to the NTC resistor in the battery
>> pack. By default the device is setup to support a 10-kohm but can also
>> be configured to support a
Hi Liam,
2017-05-26 23:22 GMT+02:00 Liam Breck :
> Hi Enric,
>
> I'll also incorporate these changes into v14 of my patchset. (See my prev
> msg.)
>
Perfect, thanks
>
> On Fri, May 26, 2017 at 4:04 AM, Enric Balletbo i Serra
> wrote:
>> Add the parameters to define the battery charging voltag
Hi Liam,
2017-05-26 23:20 GMT+02:00 Liam Breck :
> Hi Enric,
>
> On Fri, May 26, 2017 at 4:04 AM, Enric Balletbo i Serra
> wrote:
>> Add charging voltage and current characteristics to the battery DT for
>> proper handling of the battery by fuel-gauge and charger chips.
>>
>> Signed-off-by: Enric
On Sat, May 27, 2017 at 1:47 AM, Christoph Hellwig wrote:
>> + { .isFunctionNeededInRuntimeTable = NULL,
>> + .tableFunction = tf_vega10_thermal_initialize },
>
> I'd say drop the NULL initializations as they are implicit anyway.
Oh, dur, yeah, I'll improve this.
-Kees
--
Kees Cook
P
GREETINGS,
I AM BORTE ,I WAS DIAGNOSE WITH OVARIAN CANCER,WHICH DOCTORS HAVE
CONFIRMED THAT I HAVE ONLY FEW WEEKS TO LIVE, SO I HAVE DECIDED TO
DONATE EVERYTHING I HAVE TO THE ORPHANAGE AND THE POOR WIDOWS THROUGH
YOU IN YOUR AREA.PLEASE KINDLY REPLY ME ONLY ON MY EMAIL ADDRES HERE
(borteog
On Sat, May 27, 2017 at 1:41 AM, Christoph Hellwig wrote:
> On Fri, May 26, 2017 at 01:17:09PM -0700, Kees Cook wrote:
>> The LSM initialization routines walk security_hook_heads as an array
>> of struct list_head instead of via names to avoid a ton of needless
>> source. Whitelist this to avoid t
On Sat, May 27, 2017 at 1:42 AM, Christoph Hellwig wrote:
> On Fri, May 26, 2017 at 01:17:15PM -0700, Kees Cook wrote:
>> Since the ACPICA source is maintained externally to the kernel, we can
>> neither switch it to designated initializers nor mark it
>> __no_randomize_layout. Until ACPICA-upstre
On Sat, May 27, 2017 at 10:49 PM, Rafael J. Wysocki wrote:
> On Friday, May 26, 2017 10:31:14 PM Darren Hart wrote:
>> From: "Darren Hart (VMware)"
>>
>> This series is based on the original work of
>> Andy Lutomirski [1]. I have made minor edits, and in
>> one instance, squashed two patches in
From: Elena Reshetova
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Cc: Manfred Spraul
Signed-off-by: Elena Reshetova
On Fri, Mar 3, 2017 at 4:23 PM, Andrew Morton wrote:
> On Mon, 20 Feb 2017 13:29:46 +0200 Elena Reshetova
> wrote:
>
>> Now when new refcount_t type and API are finally merged
>> (see include/linux/refcount.h), the following
>> patches convert various refcounters in the ipc susystem from atomic_
On Friday, May 26, 2017 10:31:14 PM Darren Hart wrote:
> From: "Darren Hart (VMware)"
>
> This series is based on the original work of
> Andy Lutomirski [1]. I have made minor edits, and in
> one instance, squashed two patches in which the latter undid the former.
>
> This series converts WMI [
On Mon, Feb 20, 2017 at 3:29 AM, Elena Reshetova
wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
> Signed
On Mon, Feb 20, 2017 at 3:29 AM, Elena Reshetova
wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
> Signed
On Mon, Feb 20, 2017 at 3:29 AM, Elena Reshetova
wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
> Signed
On Sun, May 14, 2017 at 10:37 PM, Alexey Dobriyan wrote:
> Standard "while (*s)" test is unnecessary because NUL won't pass
> valid-digit test anyway. Save one branch per parsed character.
> - while (*s) {
> + while (1) {
In such cases I prefer
do {} while ();
Since it makes easier
On Sat, May 27, 2017 at 10:12:40AM +0200, Pavel Machek wrote:
> V4L2_CID_EXPOSURE_BIAS does not exist, fix documentation.
>
> Signed-off-by: Pavel Machek
>
> diff --git a/Documentation/media/uapi/v4l/extended-controls.rst
> b/Documentation/media/uapi/v4l/extended-controls.rst
> index abb1057..7
On Friday, May 26, 2017 05:39:53 PM Peter Hutterer wrote:
> On May 25 2017, Benjamin Tissoires wrote:
> > On May 15 2017 or thereabouts, Rafael J. Wysocki wrote:
>
> > > >> >> Benjamin, my understanding is that this is the case, is it correct?
> > > >> >
> > > >> > That is correct. This patch I re
When plugging an USB webcam I see the following message:
[106385.615559] xhci_hcd :04:00.0: WARN Successful completion on short TX:
needs XHCI_TRUST_TX_LENGTH quirk?
[106390.583860] handle_tx_event: 913 callbacks suppressed
With this patch applied, I get no more printing of this message.
Sig
On Wed, May 17, 2017 at 9:37 AM, Nicolas Iooss
wrote:
> Hello,
>
> The patch I sent a few months ago still applies cleanly on top of
> 4.12-rc1. What should I do in order to get it merged in 4.13?
>
> In case you no longer have my initial email, the patch has been
> archived in https://patchwork.k
On Saturday, May 27, 2017 07:17:42 PM Sricharan R wrote:
> While deferring the probe of IOMMU masters, xlate and
> add_device callbacks called from iort_iommu_configure
> can pass back error values like -ENODEV, which means
> the IOMMU cannot be connected with that master for real
> reasons. Before
On Sat, 2017-05-27 at 17:45 +, Trond Myklebust wrote:
> On Mon, 2017-05-22 at 14:04 -0500, Eric W. Biederman wrote:
> > David Howells writes:
> >
> > > Here are a set of patches to define a container object for the
> > > kernel and
> > > to provide some methods to create and manipulate them.
On Mon, May 15, 2017 at 10:10 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Mon, 15 May 2017 21:03:21 +0200
>
> A few update suggestions were taken into account
> from static source code analysis.
You need to fold these 6 in to two:
PNP: Improve a size determination
PNP: Delete an
Correct the typo, the wrongly typed function does not exist.
Fixes: 6c9c6d6301287e ("dma-debug: New interfaces to debug dma mapping errors")
Signed-off-by: Wolfram Sang
---
Documentation/DMA-API.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/DMA-API.txt b/D
From: Colin Ian King
Trivial fix to spelling mistake in DRM_ERROR error message.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
b/drivers/gpu/drm/vmwgfx/vmwgf
On Wed, May 24, 2017 at 08:03:45PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 24 May 2017 19:29:25 +0200
>
> Omit an extra message for a memory allocation failure in this function.
That's no extra message, that's "won't continue past that point if it happens".
> This is
On Sat, May 27, 2017 at 9:17 AM, Dmitry Torokhov
wrote:
> On May 27, 2017 9:04:38 AM PDT, Andy Lutomirski wrote:
>>On Sat, May 27, 2017 at 3:50 AM, Pali Rohár
>>wrote:
>>> On Saturday 27 May 2017 07:31:30 Darren Hart wrote:
- dell_wmi_input_dev->name = "Dell WMI hotkeys";
- del
On Tue, May 23, 2017 at 10:38 PM, Greg Kroah-Hartman
wrote:
> On Tue, May 23, 2017 at 09:32:13PM +0200, Raphaël Beamonte wrote:
>> drivers/staging/lustre/lustre/llite/xattr.c:89:62: warning: Variable
>> length array is used.
>> drivers/staging/lustre/lustre/llite/xattr.c:366:62: warning: Variable
Hi,
On 27/05/17 12:08 PM, Geert Uytterhoeven wrote:
> Still, those code patch could be protected by #ifdef CONFIG_HAS_IOMEM,
> or better, if (IS_ENABLED(CONFIG_HAS_IOMEM)).
Well I think it would have to be the former seeing the latter would
still end up trying to compile the missing function. But
On Wed, May 24, 2017 at 3:04 PM, Vitaly Kuznetsov wrote:
> Hyper-V hosts may support more than 64 vCPUs, we need to use
> HVCALL_FLUSH_VIRTUAL_ADDRESS_SPACE_EX/LIST_EX hypercalls in this
> case.
> +{
> + /*
> +* We can't be sure that translated vcpu numbers will always be
> +
Hi Logan,
On Thu, May 25, 2017 at 5:53 PM, Logan Gunthorpe wrote:
> On 25/05/17 09:48 AM, Richard Weinberger wrote:
>> Which ones are failing?
>> I thought we killed the problem by making CONFIG_COMPILE_TEST depend on !UML.
>
> None, at the moment. My work is trying to add iomem support to scatte
On Wed, May 24, 2017 at 3:04 PM, Vitaly Kuznetsov wrote:
> We need to pass only 8 bytes of input for HvSignalEvent which makes it a
> perfect fit for fast hypercall. hv_input_signal_event_buffer is not needed
> any more and hv_input_signal_event is converted to union for convenience.
> +union hv_
Hi,
my qemu testis of mips images are failing in -next. Symptom is a hang during
boot; see http://kerneltests.org/builders/qemu-mips-next for some examples.
I bisected the problem in next-20170526. It points to commit 4d6501dce079c
("kthread: Fix use-after-free if kthread fork fails"). Reverting
Signed-off-by: Sylvain 'ythier' Hitier
---
include/linux/moduleparam.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
index 6be1949..1ee7b30 100644
--- a/include/linux/moduleparam.h
+++ b/include/linux/moduleparam.h
1 - 100 of 261 matches
Mail list logo
