On 02/28/2017 12:31 PM, Florian Fainelli wrote:
> On 02/22/2017 01:22 PM, Steve Lin wrote:
>> Adds crypto hardware (SPU) to Northstar Plus device tree file.
>>
>> Signed-off-by: Steve Lin
>
> Applied, thanks!
And dropped, since there is a dependency on "ARM: dts: NSP:
On 02/28/2017 12:31 PM, Florian Fainelli wrote:
> On 02/22/2017 01:22 PM, Steve Lin wrote:
>> Adds crypto hardware (SPU) to Northstar Plus device tree file.
>>
>> Signed-off-by: Steve Lin
>
> Applied, thanks!
And dropped, since there is a dependency on "ARM: dts: NSP: Add mailbox
(PDC) to NSP"
mem_cgroup_free() indirectly calls wb_domain_exit() which is not
prepared to deal with a struct wb_domain object that hasn't executed
wb_domain_init(). For instance, the following warning message is
printed by lockdep if alloc_percpu() fails in mem_cgroup_alloc():
INFO: trying to register
mem_cgroup_free() indirectly calls wb_domain_exit() which is not
prepared to deal with a struct wb_domain object that hasn't executed
wb_domain_init(). For instance, the following warning message is
printed by lockdep if alloc_percpu() fails in mem_cgroup_alloc():
INFO: trying to register
On 03/06/2017 07:52 AM, Daniel Vetter wrote:
> On Mon, Mar 06, 2017 at 03:43:53PM +0200, Laurent Pinchart wrote:
>> Hi Daniel,
>>
>> On Monday 06 Mar 2017 11:32:04 Daniel Vetter wrote:
>>> On Fri, Mar 03, 2017 at 10:50:20AM -0800, Laura Abbott wrote:
On 03/03/2017 08:41 AM, Laurent Pinchart
The kernel security team is regularly asked to provide CVE identifiers,
which we don't normally do. This updates the documentation to mention
this and adds some more details about coordination and patch handling
that come up regularly. Based on an earlier draft by Willy Tarreau.
Signed-off-by:
On 03/06/2017 07:52 AM, Daniel Vetter wrote:
> On Mon, Mar 06, 2017 at 03:43:53PM +0200, Laurent Pinchart wrote:
>> Hi Daniel,
>>
>> On Monday 06 Mar 2017 11:32:04 Daniel Vetter wrote:
>>> On Fri, Mar 03, 2017 at 10:50:20AM -0800, Laura Abbott wrote:
On 03/03/2017 08:41 AM, Laurent Pinchart
The kernel security team is regularly asked to provide CVE identifiers,
which we don't normally do. This updates the documentation to mention
this and adds some more details about coordination and patch handling
that come up regularly. Based on an earlier draft by Willy Tarreau.
Signed-off-by:
On Mon, Mar 6, 2017 at 8:50 PM, James Simmons wrote:
>
>> Doubly linked lists which are iterated using list_empty
>> and list_entry macros have been replaced with list_for_each_entry_safe
>> macro.
>> This makes the iteration simpler and more readable.
>>
>> This patch
On Mon, Mar 6, 2017 at 8:50 PM, James Simmons wrote:
>
>> Doubly linked lists which are iterated using list_empty
>> and list_entry macros have been replaced with list_for_each_entry_safe
>> macro.
>> This makes the iteration simpler and more readable.
>>
>> This patch replaces the while loop
On 03/06/2017 02:11 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.71 release.
> There are 113 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
On 03/06/2017 02:11 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.71 release.
> There are 113 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
Hi Javier,
On Monday, 6 March 2017 10:09:09 PST Javier Martinez Canillas wrote:
> On 02/24/2017 06:56 PM, Paul Burton wrote:
> > On Monday, 20 February 2017 21:39:11 PST Dmitry Torokhov wrote:
> >> The OF device table must be terminated, otherwise we'll be walking past
> >> it and into areas
Hi Javier,
On Monday, 6 March 2017 10:09:09 PST Javier Martinez Canillas wrote:
> On 02/24/2017 06:56 PM, Paul Burton wrote:
> > On Monday, 20 February 2017 21:39:11 PST Dmitry Torokhov wrote:
> >> The OF device table must be terminated, otherwise we'll be walking past
> >> it and into areas
On 03/06/2017 09:00 AM, Emil Velikov wrote:
> On 6 March 2017 at 10:29, Daniel Vetter wrote:
>> On Fri, Mar 03, 2017 at 10:46:03AM -0800, Laura Abbott wrote:
>>> On 03/03/2017 08:39 AM, Laurent Pinchart wrote:
Hi Daniel,
On Friday 03 Mar 2017 10:56:54 Daniel Vetter
On 03/06/2017 09:00 AM, Emil Velikov wrote:
> On 6 March 2017 at 10:29, Daniel Vetter wrote:
>> On Fri, Mar 03, 2017 at 10:46:03AM -0800, Laura Abbott wrote:
>>> On 03/03/2017 08:39 AM, Laurent Pinchart wrote:
Hi Daniel,
On Friday 03 Mar 2017 10:56:54 Daniel Vetter wrote:
> On
Hi Geert,
> > This tool allows to construct and concat multiple I2C messages into one
> > single transfer. Its aim is to test I2C master controllers, and so there
> > is no SMBus fallback.
>
> Thanks for the tool!
Very welcome :)
>
> > I've been missing such a tool a number of times now, so I
Hi Geert,
> > This tool allows to construct and concat multiple I2C messages into one
> > single transfer. Its aim is to test I2C master controllers, and so there
> > is no SMBus fallback.
>
> Thanks for the tool!
Very welcome :)
>
> > I've been missing such a tool a number of times now, so I
Hi,
On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote:
> > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out.
> Top ten first word of commit summary:
...
> 61 btrfs
I can comment on the btrfs part. We have lots of cleanups for 4.11 and
good part of all
Hi,
On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote:
> > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out.
> Top ten first word of commit summary:
...
> 61 btrfs
I can comment on the btrfs part. We have lots of cleanups for 4.11 and
good part of all
This expands on the Kconfig help text for CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 97d62c2da6c2..4a73d46711fb
This expands on the Kconfig help text for CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 97d62c2da6c2..4a73d46711fb 100644
---
This continues in applying the CHECK_DATA_CORRUPTION tests where
appropriate, and pulling similar CONFIGs under the same check. Most
notably, this adds the checks to refcount_t so that system builders can
Oops their kernels when encountering a potential refcounter attack. (And
so now the LKDTM
This continues in applying the CHECK_DATA_CORRUPTION tests where
appropriate, and pulling similar CONFIGs under the same check. Most
notably, this adds the checks to refcount_t so that system builders can
Oops their kernels when encountering a potential refcounter attack. (And
so now the LKDTM
This converts from WARN() to CHECK_DATA_CORRUPTION() (so that system
builders can choose between WARN and BUG). Additionally moves refcount_t
sanity-check conditionals into regular function flow.
Now when built with CONFIG_BUG_ON_DATA_CORRUPTION, the LKDTM REFCOUNT_*
tests correctly kill
This converts from WARN() to CHECK_DATA_CORRUPTION() (so that system
builders can choose between WARN and BUG). Additionally moves refcount_t
sanity-check conditionals into regular function flow.
Now when built with CONFIG_BUG_ON_DATA_CORRUPTION, the LKDTM REFCOUNT_*
tests correctly kill
This improves the compiler branch-hinting used in CHECK_DATA_CORRUPTION(),
similar to how it is done in WARN_ON() and friends.
Signed-off-by: Kees Cook
---
include/linux/bug.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/bug.h
Similar to CONFIG_DEBUG_CREDENTIALS, CONFIG_DEBUG_SG already handles
calling BUG, and performs inexpensive checks. This enables it under
CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
This improves the compiler branch-hinting used in CHECK_DATA_CORRUPTION(),
similar to how it is done in WARN_ON() and friends.
Signed-off-by: Kees Cook
---
include/linux/bug.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/bug.h b/include/linux/bug.h
Similar to CONFIG_DEBUG_CREDENTIALS, CONFIG_DEBUG_SG already handles
calling BUG, and performs inexpensive checks. This enables it under
CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
When performing notifier function pointer sanity checking, allow
CONFIG_BUG_ON_DATA_CORRUPTION to upgrade from a WARN to a BUG.
Additionally enables CONFIG_DEBUG_NOTIFIERS when selecting
CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
kernel/notifier.c | 5
When performing notifier function pointer sanity checking, allow
CONFIG_BUG_ON_DATA_CORRUPTION to upgrade from a WARN to a BUG.
Additionally enables CONFIG_DEBUG_NOTIFIERS when selecting
CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
kernel/notifier.c | 5 +++--
lib/Kconfig.debug |
Since CONFIG_DEBUG_CREDENTIALS already handles reporting and issuing a
BUG when it encounters corruption, add this to the list of corruption
test CONFIGs that are enabled under CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 3 ++-
1 file
Since CONFIG_DEBUG_CREDENTIALS already handles reporting and issuing a
BUG when it encounters corruption, add this to the list of corruption
test CONFIGs that are enabled under CONFIG_BUG_ON_DATA_CORRUPTION.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 3 ++-
1 file changed, 2
On Fri, 2017-02-17 at 15:19 +1100, Dave Chinner wrote:
> On Wed, Feb 15, 2017 at 10:41:40PM +, Ben Hutchings wrote:
> > 3.16.40-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Dave Chinner
> >
> > commit
On Fri, 2017-02-17 at 15:19 +1100, Dave Chinner wrote:
> On Wed, Feb 15, 2017 at 10:41:40PM +, Ben Hutchings wrote:
> > 3.16.40-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Dave Chinner
> >
> > commit
On Mon, Mar 06, 2017 at 11:03:56AM -0800, Linus Torvalds wrote:
> On Mon, Mar 6, 2017 at 10:42 AM, Thomas Gleixner wrote:
> >
> > We probably need to split it apart:
> >
> >- Apply the mm core only parts to a branch which can be pulled into
> > Andrews mm-tree
> >
> >
On Mon, Mar 06, 2017 at 11:03:56AM -0800, Linus Torvalds wrote:
> On Mon, Mar 6, 2017 at 10:42 AM, Thomas Gleixner wrote:
> >
> > We probably need to split it apart:
> >
> >- Apply the mm core only parts to a branch which can be pulled into
> > Andrews mm-tree
> >
> >- Base the x86
Hello,
On Fri, Feb 17, 2017 at 12:37:11PM +0100, Krzysztof Opasiak wrote:
> > We need to limit and monitor the number of file descriptors processes
> > keep open. If a process exceeds certain limit we'd like to terminate it
> > and restart it or reboot the whole system. Currently the RLIMIT API
>
On Sun, 5 Mar 2017 12:37:31 +0530
Sunil Kovvuri wrote:
> On Tue, Feb 14, 2017 at 10:14 AM, Alex Williamson
> wrote:
> > On Sat, 30 Jan 2016 01:33:58 +0530
> > Manish Jaggi wrote:
> >
> >> Cavium devices matching
Hello,
On Fri, Feb 17, 2017 at 12:37:11PM +0100, Krzysztof Opasiak wrote:
> > We need to limit and monitor the number of file descriptors processes
> > keep open. If a process exceeds certain limit we'd like to terminate it
> > and restart it or reboot the whole system. Currently the RLIMIT API
>
On Sun, 5 Mar 2017 12:37:31 +0530
Sunil Kovvuri wrote:
> On Tue, Feb 14, 2017 at 10:14 AM, Alex Williamson
> wrote:
> > On Sat, 30 Jan 2016 01:33:58 +0530
> > Manish Jaggi wrote:
> >
> >> Cavium devices matching this quirk do not perform
> >> peer-to-peer with other functions, allowing
Hello Paul,
On 03/06/2017 03:54 PM, Paul Burton wrote:
> Hi Javier,
>
> On Monday, 6 March 2017 10:09:09 PST Javier Martinez Canillas wrote:
>> On 02/24/2017 06:56 PM, Paul Burton wrote:
>>> On Monday, 20 February 2017 21:39:11 PST Dmitry Torokhov wrote:
The OF device table must be
Hello Paul,
On 03/06/2017 03:54 PM, Paul Burton wrote:
> Hi Javier,
>
> On Monday, 6 March 2017 10:09:09 PST Javier Martinez Canillas wrote:
>> On 02/24/2017 06:56 PM, Paul Burton wrote:
>>> On Monday, 20 February 2017 21:39:11 PST Dmitry Torokhov wrote:
The OF device table must be
The rwsem_down_read_failed() function was relocted from above the
optimistic spinning section to below that section. This enables
it to use functions in that section in future patches. There is no
code change.
Signed-off-by: Waiman Long
---
kernel/locking/rwsem-xadd.c | 96
On 2017/03/06 06:38PM, Russell King - ARM Linux wrote:
> On Mon, Mar 06, 2017 at 11:37:20PM +0530, Naveen N. Rao wrote:
> > On 2017/02/08 01:24AM, Naveen N Rao wrote:
> > > ... as the weak variant will do.
> > >
> > > Signed-off-by: Naveen N. Rao
> > > ---
> > >
The rwsem_down_read_failed() function was relocted from above the
optimistic spinning section to below that section. This enables
it to use functions in that section in future patches. There is no
code change.
Signed-off-by: Waiman Long
---
kernel/locking/rwsem-xadd.c | 96
On 2017/03/06 06:38PM, Russell King - ARM Linux wrote:
> On Mon, Mar 06, 2017 at 11:37:20PM +0530, Naveen N. Rao wrote:
> > On 2017/02/08 01:24AM, Naveen N Rao wrote:
> > > ... as the weak variant will do.
> > >
> > > Signed-off-by: Naveen N. Rao
> > > ---
> > > arch/arm/probes/kprobes/core.c
In rwsem_wake(), we can safely check the wait_list to see if waiters
are present without lock when there are spinners to fall back on in
case we miss a waiter. The advantage is that we can save a pair of
spin_lock/unlock calls when the wait_list is empty. This translates
to a reduction in latency
In rwsem_wake(), we can safely check the wait_list to see if waiters
are present without lock when there are spinners to fall back on in
case we miss a waiter. The advantage is that we can save a pair of
spin_lock/unlock calls when the wait_list is empty. This translates
to a reduction in latency
Commit fc62d0207ae0 ("kprobes: Introduce weak variant of
kprobe_exceptions_notify()") introduces a generic empty version of the
function for architectures that don't need special handling, like arm.
As such, remove the arch/arm/ specific handler.
Signed-off-by: Naveen N. Rao
v1->v2:
- Replace trylock with a more light-weight raw_spin_is_locked()
call to reduce overhead.
- Run fio test in addition to rwsem microbenchmark.
This patch set introduces minor changes to the rwsem code path to
provide minor performance improvement especially with short critical
Commit fc62d0207ae0 ("kprobes: Introduce weak variant of
kprobe_exceptions_notify()") introduces a generic empty version of the
function for architectures that don't need special handling, like arm.
As such, remove the arch/arm/ specific handler.
Signed-off-by: Naveen N. Rao
---
v1->v2:
- Replace trylock with a more light-weight raw_spin_is_locked()
call to reduce overhead.
- Run fio test in addition to rwsem microbenchmark.
This patch set introduces minor changes to the rwsem code path to
provide minor performance improvement especially with short critical
Currently, when down_read() fails, the active read locking isn't undone
until the rwsem_down_read_failed() function grabs the wait_lock. If the
wait_lock is contended, it may takes a while to get the lock. During
that period, writer lock stealing will be disabled because of the
active read lock.
Currently, when down_read() fails, the active read locking isn't undone
until the rwsem_down_read_failed() function grabs the wait_lock. If the
wait_lock is contended, it may takes a while to get the lock. During
that period, writer lock stealing will be disabled because of the
active read lock.
On 2017/03/04 01:34PM, Masami Hiramatsu wrote:
> On Sat, 4 Mar 2017 11:35:51 +0900
> Masami Hiramatsu wrote:
>
> > On Sat, 4 Mar 2017 09:49:11 +0900
> > Masami Hiramatsu wrote:
> >
> > > On Thu, 2 Mar 2017 23:25:06 +0530
> > > "Naveen N. Rao"
On 2017/03/04 01:34PM, Masami Hiramatsu wrote:
> On Sat, 4 Mar 2017 11:35:51 +0900
> Masami Hiramatsu wrote:
>
> > On Sat, 4 Mar 2017 09:49:11 +0900
> > Masami Hiramatsu wrote:
> >
> > > On Thu, 2 Mar 2017 23:25:06 +0530
> > > "Naveen N. Rao" wrote:
> > >
> > > > We indicate support for
On Mon, Mar 6, 2017 at 10:42 AM, Thomas Gleixner wrote:
>
> We probably need to split it apart:
>
>- Apply the mm core only parts to a branch which can be pulled into
> Andrews mm-tree
>
>- Base the x86 changes on top of it
I'll happily take some of the
On Mon, Mar 6, 2017 at 10:42 AM, Thomas Gleixner wrote:
>
> We probably need to split it apart:
>
>- Apply the mm core only parts to a branch which can be pulled into
> Andrews mm-tree
>
>- Base the x86 changes on top of it
I'll happily take some of the preparatory patches for 4.11
Hi Stephen,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201
commit: e2427b09ba929c2b9d02556b74a85161a7364792 phy: Add support for
Qualcomm's USB HS phy
date: 5 weeks ago
Hi Stephen,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201
commit: e2427b09ba929c2b9d02556b74a85161a7364792 phy: Add support for
Qualcomm's USB HS phy
date: 5 weeks ago
Am 06.03.2017 um 18:21 schrieb Alban:
> On Fri, 3 Mar 2017 23:21:29 +0100
> Richard Weinberger wrote:
>
>> Am 03.03.2017 um 15:11 schrieb Boris Brezillon:
And add a list of successfully added notifiers, along with their
data pointer, to the MTD device. That's simple and
Am 06.03.2017 um 18:21 schrieb Alban:
> On Fri, 3 Mar 2017 23:21:29 +0100
> Richard Weinberger wrote:
>
>> Am 03.03.2017 um 15:11 schrieb Boris Brezillon:
And add a list of successfully added notifiers, along with their
data pointer, to the MTD device. That's simple and would also
On Thu, 2017-02-16 at 09:42 +0800, Hangbin Liu wrote:
> > 2017-02-16 6:41 GMT+08:00 Ben Hutchings :
> > 3.2.85-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Hangbin Liu
> >
> > commit
On Thu, 2017-02-16 at 09:42 +0800, Hangbin Liu wrote:
> > 2017-02-16 6:41 GMT+08:00 Ben Hutchings :
> > 3.2.85-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Hangbin Liu
> >
> > commit 24803f38a5c0b6c57ed800b47e695f9ce474bc3a
On March 6, 2017 9:12:41 AM PST, Logan Gunthorpe wrote:
>
>
>On 06/03/17 12:28 AM, H. Peter Anvin wrote:
>> On 03/05/17 23:01, Logan Gunthorpe wrote:
>>>
>>> On 05/03/17 12:54 PM, Borislav Petkov wrote:
Logan, wanna give that a try, see if it takes care of your issue?
On March 6, 2017 9:12:41 AM PST, Logan Gunthorpe wrote:
>
>
>On 06/03/17 12:28 AM, H. Peter Anvin wrote:
>> On 03/05/17 23:01, Logan Gunthorpe wrote:
>>>
>>> On 05/03/17 12:54 PM, Borislav Petkov wrote:
Logan, wanna give that a try, see if it takes care of your issue?
>>>
>>> Well honestly
plied.
Second verification was by make tools/objtool and comparing the generated
binaries
in tools/objtool/arch/x86/decode.o with diff.
Patch is against 4.11-rc1 (localversion-next is next-20170306)
arch/x86/tools/gen-insn-attr-x86.awk | 12 ++--
tools/objtool/arch/x86/insn/gen-
cation was by make tools/objtool and comparing the generated
binaries
in tools/objtool/arch/x86/decode.o with diff.
Patch is against 4.11-rc1 (localversion-next is next-20170306)
arch/x86/tools/gen-insn-attr-x86.awk | 12 ++--
tools/objtool/arch/x86/insn/gen-insn-attr-x86.awk | 12 +
This patchset adds the support for the dio2125 from Dioo microcircuits.
The dio2125 is audio driver with adjustable gain. The EN pad allows to
enable or disable the outputs of the driver.
The link to the datasheet is not provided as part of the commit. It is not
provided the manufacturer and it
This patchset adds the support for the dio2125 from Dioo microcircuits.
The dio2125 is audio driver with adjustable gain. The EN pad allows to
enable or disable the outputs of the driver.
The link to the datasheet is not provided as part of the commit. It is not
provided the manufacturer and it
Dioo (http://http://www.dioo.com) design and produce power analog and
mixed signal IC.
Signed-off-by: Jerome Brunet
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
Dioo (http://http://www.dioo.com) design and produce power analog and
mixed signal IC.
Signed-off-by: Jerome Brunet
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
On Mon, Mar 6, 2017 at 6:31 PM, David Ahern wrote:
> On 3/4/17 1:15 PM, Eric Dumazet wrote:
>> On Sat, 2017-03-04 at 19:57 +0100, Dmitry Vyukov wrote:
>>> On Fri, Mar 3, 2017 at 8:12 PM, David Ahern
>>> wrote:
On 3/3/17 6:39 AM, Dmitry
On Mon, Mar 6, 2017 at 6:31 PM, David Ahern wrote:
> On 3/4/17 1:15 PM, Eric Dumazet wrote:
>> On Sat, 2017-03-04 at 19:57 +0100, Dmitry Vyukov wrote:
>>> On Fri, Mar 3, 2017 at 8:12 PM, David Ahern
>>> wrote:
On 3/3/17 6:39 AM, Dmitry Vyukov wrote:
> I am getting heap out-of-bounds
Sie benötigen eine Finanzierung?
Wir vergeben Darlehen. Bewerben Sie sich jetzt. Senden Sie
uns u.a. Details zurück und Sie erhalten in Kürze Antwort
Vorname:
Familienname:
Geschlecht:
Land:
Telefonnummer:
benötigter Darlehensbetrag:
Gewünschte Laufzeit:
Mit
he
> >two files differ.
> >
> > Patch was checked by manual review of the diff between the initial file and
> > the
> > regenerated file after the below patch was applied.
> > Second verification was by make tools/objtool and comparing the generated
> >
Sie benötigen eine Finanzierung?
Wir vergeben Darlehen. Bewerben Sie sich jetzt. Senden Sie
uns u.a. Details zurück und Sie erhalten in Kürze Antwort
Vorname:
Familienname:
Geschlecht:
Land:
Telefonnummer:
benötigter Darlehensbetrag:
Gewünschte Laufzeit:
Mit
files differ.
> >
> > Patch was checked by manual review of the diff between the initial file and
> > the
> > regenerated file after the below patch was applied.
> > Second verification was by make tools/objtool and comparing the generated
> > binar
> > Hi Michael
> >
> > Some quick feedback.
> >
> > On Mon, Mar 06, 2017 at 03:31:04PM +1030, Jonathan Woithe wrote:
> > > > > I can add that immediately after loading the driver the value
> > > > > returned by a
> > > > > read of bl_power is 0. As noted above, setting to 1 makes no
> > > > >
On Mon, Mar 06, 2017 at 10:18:45AM -0600, Nathan Royce wrote:
> I tried the patch you submitted, however it also fails for the most part.
>
> "For the most part" because "xts" is now found.
> $ grep xts /proc/crypto
> name : xts(aes)
> driver : xts(ecb-aes-s5p)
Ah, so probably I
> > Hi Michael
> >
> > Some quick feedback.
> >
> > On Mon, Mar 06, 2017 at 03:31:04PM +1030, Jonathan Woithe wrote:
> > > > > I can add that immediately after loading the driver the value
> > > > > returned by a
> > > > > read of bl_power is 0. As noted above, setting to 1 makes no
> > > > >
On Mon, Mar 06, 2017 at 10:18:45AM -0600, Nathan Royce wrote:
> I tried the patch you submitted, however it also fails for the most part.
>
> "For the most part" because "xts" is now found.
> $ grep xts /proc/crypto
> name : xts(aes)
> driver : xts(ecb-aes-s5p)
Ah, so probably I
KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
uninitialized memory in selinux_socket_bind():
==
BUG: KMSAN: use of unitialized memory
inter: 0
CPU: 3 PID: 1074 Comm: packet2 Tainted: GB
On Tue, Mar 07, 2017 at 01:58:23AM +0800, Ayaka wrote:
>
>
> 從我的 iPad 傳送
>
> > Ville Syrjälä 於 2017年3月6日 下午9:06 寫道:
> >
> >> On Sun, Mar 05, 2017 at 06:00:31PM +0800, Randy Li wrote:
> >> P010 is a planar 4:2:0 YUV with interleaved UV plane, 10 bits
> >> per
On Tue, Mar 07, 2017 at 01:58:23AM +0800, Ayaka wrote:
>
>
> 從我的 iPad 傳送
>
> > Ville Syrjälä 於 2017年3月6日 下午9:06 寫道:
> >
> >> On Sun, Mar 05, 2017 at 06:00:31PM +0800, Randy Li wrote:
> >> P010 is a planar 4:2:0 YUV with interleaved UV plane, 10 bits
> >> per channel video format.
> >>
> >>
KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
uninitialized memory in selinux_socket_bind():
==
BUG: KMSAN: use of unitialized memory
inter: 0
CPU: 3 PID: 1074 Comm: packet2 Tainted: GB
On 03/06/2017 09:21 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-off-by:
On 03/06/2017 09:21 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-off-by:
On Mon, 6 Mar 2017, Linus Torvalds wrote:
> On Mon, Mar 6, 2017 at 5:53 AM, Kirill A. Shutemov
> wrote:
> > Here is v4 of 5-level paging patchset. Please review and consider applying.
>
> I think we should just aim for this being in 4.12. I don't see any
> real
* Keerthy [170301 02:31]:
> Currently the slope and offset values for calculating the
> hot spot temperature of a particular thermal zone is part
> of driver data. Pass them here instead and obtain the values
> while of node parsing.
>
> Tested for the slope and constant values
On Mon, 6 Mar 2017, Linus Torvalds wrote:
> On Mon, Mar 6, 2017 at 5:53 AM, Kirill A. Shutemov
> wrote:
> > Here is v4 of 5-level paging patchset. Please review and consider applying.
>
> I think we should just aim for this being in 4.12. I don't see any
> real reason to delay merging it, the
* Keerthy [170301 02:31]:
> Currently the slope and offset values for calculating the
> hot spot temperature of a particular thermal zone is part
> of driver data. Pass them here instead and obtain the values
> while of node parsing.
>
> Tested for the slope and constant values on DRA7-EVM.
>
>
The sole remaining caller of kmem_zalloc_greedy is bulkstat, which uses
it to grab 1-4 pages for staging of inobt records. The infinite loop in
the greedy allocation function is causing hangs[1] in generic/269, so
just get rid of the greedy allocator in favor of kmem_zalloc_large.
This makes
The sole remaining caller of kmem_zalloc_greedy is bulkstat, which uses
it to grab 1-4 pages for staging of inobt records. The infinite loop in
the greedy allocation function is causing hangs[1] in generic/269, so
just get rid of the greedy allocator in favor of kmem_zalloc_large.
This makes
On Mon, Mar 6, 2017 at 2:54 AM, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following crash while running syzkaller fuzzer on
> net-next/8d70eeb84ab277377c017af6a21d0a337025dede:
>
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection
On Mon, Mar 6, 2017 at 2:54 AM, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following crash while running syzkaller fuzzer on
> net-next/8d70eeb84ab277377c017af6a21d0a337025dede:
>
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] SMP
On Mon, 6 Mar 2017, Charles Keepax wrote:
> When an IRQ is nested the nested handler is called directly from within the
> threaded handler of the parent IRQ, however, the code in handle_nested_irq
> only calls a single handler. This means when a shared IRQ is nested only
> the first of the shared
On Mon, 6 Mar 2017, Charles Keepax wrote:
> When an IRQ is nested the nested handler is called directly from within the
> threaded handler of the parent IRQ, however, the code in handle_nested_irq
> only calls a single handler. This means when a shared IRQ is nested only
> the first of the shared
701 - 800 of 2074 matches
Mail list logo