On 1.03.2017 12:31, Michal Hocko wrote:
> On Wed 01-03-17 11:22:51, Vlastimil Babka wrote:
>> On 03/01/2017 08:48 AM, Nikolay Borisov wrote:
>>> Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
>>> during memory allocation") added the memalloc_noio_(save|restore)
Le 01/03/2017 à 05:54, Vignesh R a écrit :
>
>
> On Wednesday 01 March 2017 03:11 AM, Richard Weinberger wrote:
>> Vignesh,
>>
>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
>>> Many SPI controller drivers use DMA to read/write from m25p80 compatible
>>> flashes. Therefore enable bounce buffers
> I also checked all the other .ko files and they were properly aligned. So I
> think this should hopefully work, and I like that its not a per-arch fix.
>
> Sachin, sorry to bother you again, but I'm hoping you can try David's latest
> patch to scripts/module-common.lds, just to test in your
On Mon, 20 Feb 2017, Dou Liyang wrote:
> Currently, We make the mapping of "cpuid <-> nodeid" fixed at the booting
> time.
> It keeps consistent with the WorkQueue and avoids some bugs which may be
> caused
> by the dynamic assignment.
>
> But, The ACPI table is unreliable and it is very risky
> I also checked all the other .ko files and they were properly aligned. So I
> think this should hopefully work, and I like that its not a per-arch fix.
>
> Sachin, sorry to bother you again, but I'm hoping you can try David's latest
> patch to scripts/module-common.lds, just to test in your
On Mon, 20 Feb 2017, Dou Liyang wrote:
> Currently, We make the mapping of "cpuid <-> nodeid" fixed at the booting
> time.
> It keeps consistent with the WorkQueue and avoids some bugs which may be
> caused
> by the dynamic assignment.
>
> But, The ACPI table is unreliable and it is very risky
* Thomas Gleixner wrote:
> On Wed, 1 Mar 2017, Ingo Molnar wrote:
> >
> > * Jiri Slaby wrote:
> >
> > > This is a start of series to unify use of ENTRY, ENDPROC, GLOBAL, END,
> > > and other macros across x86. When we have all this sorted out, this will
>
* Thomas Gleixner wrote:
> On Wed, 1 Mar 2017, Ingo Molnar wrote:
> >
> > * Jiri Slaby wrote:
> >
> > > This is a start of series to unify use of ENTRY, ENDPROC, GLOBAL, END,
> > > and other macros across x86. When we have all this sorted out, this will
> > > help to inject DWARF unwinding
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.
Keerthy (7):
ARM: DRA7: Thermal: Add
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.
Keerthy (7):
ARM: DRA7: Thermal: Add
Thank you Brendan for reviewing,
On Wednesday 01 March 2017 10:34 AM, Brendan Gregg wrote:
> On Tue, Feb 28, 2017 at 2:31 PM, Brendan Gregg
> wrote:
>> G'Day Ravi,
>>
> [...]
>> Now retrying perf:
>>
>> # ./perf record -e sdt_node:http__server__request -a
>> ^C[ perf
On Wed, Mar 1, 2017 at 8:55 PM, Mel Gorman wrote:
> On Wed, Mar 01, 2017 at 01:42:40PM +1100, Balbir Singh wrote:
>> >>>The idea of this patchset was to introduce
>> >>>the concept of memory that is not necessarily system memory, but is
>> >>>coherent
>> >>>in terms of
Add Chen, Catalin
On Thu, 16 Feb 2017 09:11:29 +0800 zhouxianrong wrote:
>
>
> On 2017/2/15 15:10, Ard Biesheuvel wrote:
> > On 15 February 2017 at 01:44, zhouxianrong wrote:
> >>
> >>
> >> On 2017/2/14 17:03, Ard Biesheuvel wrote:
> >>>
> >>> On 14 February 2017 at 06:53,
Thank you Brendan for reviewing,
On Wednesday 01 March 2017 10:34 AM, Brendan Gregg wrote:
> On Tue, Feb 28, 2017 at 2:31 PM, Brendan Gregg
> wrote:
>> G'Day Ravi,
>>
> [...]
>> Now retrying perf:
>>
>> # ./perf record -e sdt_node:http__server__request -a
>> ^C[ perf record: Woken up 1 times to
On Wed, Mar 1, 2017 at 8:55 PM, Mel Gorman wrote:
> On Wed, Mar 01, 2017 at 01:42:40PM +1100, Balbir Singh wrote:
>> >>>The idea of this patchset was to introduce
>> >>>the concept of memory that is not necessarily system memory, but is
>> >>>coherent
>> >>>in terms of visibility/access with
Add Chen, Catalin
On Thu, 16 Feb 2017 09:11:29 +0800 zhouxianrong wrote:
>
>
> On 2017/2/15 15:10, Ard Biesheuvel wrote:
> > On 15 February 2017 at 01:44, zhouxianrong wrote:
> >>
> >>
> >> On 2017/2/14 17:03, Ard Biesheuvel wrote:
> >>>
> >>> On 14 February 2017 at 06:53, wrote:
>
Unnecessary parentheses are removed as reported by checkpatch.pl
to make coder nicer and to improve readability.
Also coding style is improved as it's often nicer to read if
&(foo[0]) is converted to foo like:
memcpy(&(ap->bssid[0]), &(ap_info->bssid[0]), ETH_ALEN);
memcpy(ap->bssid,
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.
Signed-off-by: Keerthy
---
arch/arm/boot/dts/dra7.dtsi | 17 +
Unnecessary parentheses are removed as reported by checkpatch.pl
to make coder nicer and to improve readability.
Also coding style is improved as it's often nicer to read if
&(foo[0]) is converted to foo like:
memcpy(&(ap->bssid[0]), &(ap_info->bssid[0]), ETH_ALEN);
memcpy(ap->bssid,
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.
Signed-off-by: Keerthy
---
arch/arm/boot/dts/dra7.dtsi | 17 +
1 file changed,
Now that slope and offset data are being passed from
device tree no need to populate in driver data.
Signed-off-by: Keerthy
---
drivers/thermal/ti-soc-thermal/dra752-thermal-data.c | 10 --
drivers/thermal/ti-soc-thermal/omap4-thermal-data.c | 4
Now that slope and offset data are being passed from
device tree no need to populate in driver data.
Signed-off-by: Keerthy
---
drivers/thermal/ti-soc-thermal/dra752-thermal-data.c | 10 --
drivers/thermal/ti-soc-thermal/omap4-thermal-data.c | 4
On Mon, 20 Feb 2017, Dou Liyang wrote:
> After we never do the last mapping of "cpuid <-> nodeid" at booting time. we
> also no need to enable MADT APIs to return disabled apicid.
>
> So, The patch work for reverting the commit 8ad893faf2:
> "x86/acpi: Enable MADT APIs to return disabled
On Mon, 20 Feb 2017, Dou Liyang wrote:
> After we never do the last mapping of "cpuid <-> nodeid" at booting time. we
> also no need to enable MADT APIs to return disabled apicid.
>
> So, The patch work for reverting the commit 8ad893faf2:
> "x86/acpi: Enable MADT APIs to return disabled
For now we will increase the data area size to 1G, and the cmd area
size to 128M. The tcmu-runner should mmap() about (128M + 1G) when
running and the TCMU will dynamically grows the data area from 0 to
max 1G size.
Cool. This is a good approach for an initial patch but this raises
concerns
On 03/01/2017 08:48 AM, Nikolay Borisov wrote:
> Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
> during memory allocation") added the memalloc_noio_(save|restore) functions
> to enable people to modify the MM behavior by disbaling I/O during memory
> allocation. This
For now we will increase the data area size to 1G, and the cmd area
size to 128M. The tcmu-runner should mmap() about (128M + 1G) when
running and the TCMU will dynamically grows the data area from 0 to
max 1G size.
Cool. This is a good approach for an initial patch but this raises
concerns
On 03/01/2017 08:48 AM, Nikolay Borisov wrote:
> Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
> during memory allocation") added the memalloc_noio_(save|restore) functions
> to enable people to modify the MM behavior by disbaling I/O during memory
> allocation. This
The Mali is clocked by two identical clock paths behind a glitch free mux
to safely change frequency while running.
The two "mali_0" and "mali_1" clocks are composed of a mux, divider and gate.
Expose these two clocks trees using generic clocks.
Finally the glitch free mux is added as "mali"
The Mali is clocked by two identical clock paths behind a glitch free mux
to safely change frequency while running.
The two "mali_0" and "mali_1" clocks are composed of a mux, divider and gate.
Expose these two clocks trees using generic clocks.
Finally the glitch free mux is added as "mali"
On Thu, 27 Oct 2016, Josh Poimboeuf wrote:
> TODO:
> - support .klp.arch.objname..altinstructions/parainstructions
> - split up the patches better
> - patch creation documentation
> - more tooling support for detecting missing relocations? or
> automatically converting them if a sympos isn't
On Thu, 27 Oct 2016, Josh Poimboeuf wrote:
> TODO:
> - support .klp.arch.objname..altinstructions/parainstructions
> - split up the patches better
> - patch creation documentation
> - more tooling support for detecting missing relocations? or
> automatically converting them if a sympos isn't
Hello,
I've got the following deadlock report while running syzkaller fuzzer
on linux-next/51788aebe7cae79cb334ad50641347465fc188fd:
==
[ INFO: possible circular locking dependency detected ]
4.10.0-next-20170301+ #1 Not tainted
Hello,
I've got the following deadlock report while running syzkaller fuzzer
on linux-next/51788aebe7cae79cb334ad50641347465fc188fd:
==
[ INFO: possible circular locking dependency detected ]
4.10.0-next-20170301+ #1 Not tainted
Add missing MALI clock IDs and expose the muxes and gates in the dt-bindings.
Signed-off-by: Neil Armstrong
---
drivers/clk/meson/gxbb.h | 9 -
include/dt-bindings/clock/gxbb-clkc.h | 5 +
2 files changed, 13 insertions(+), 1 deletion(-)
diff
> -Original Message-
> From: Rob Herring [mailto:robh...@kernel.org]
> Sent: Wednesday, March 01, 2017 1:20 AM
>
> On Mon, Jan 30, 2017 at 8:43 AM, Madalin Bucur
> wrote:
> > Signed-off-by: Madalin Bucur
> > ---
>
> [...]
>
> > diff --git
Add missing MALI clock IDs and expose the muxes and gates in the dt-bindings.
Signed-off-by: Neil Armstrong
---
drivers/clk/meson/gxbb.h | 9 -
include/dt-bindings/clock/gxbb-clkc.h | 5 +
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git
> -Original Message-
> From: Rob Herring [mailto:robh...@kernel.org]
> Sent: Wednesday, March 01, 2017 1:20 AM
>
> On Mon, Jan 30, 2017 at 8:43 AM, Madalin Bucur
> wrote:
> > Signed-off-by: Madalin Bucur
> > ---
>
> [...]
>
> > diff --git
On 02/28/2017 12:41 PM, Greg Kurz wrote:
>>> +++ b/include/linux/syscalls.h
>>> @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char
>>> __user *filename,
>>> asmlinkage long sys_faccessat(int dfd, const char __user *filename, int
>>> mode);
>>> asmlinkage long
On Wed, Mar 01, 2017 at 12:15:40PM +0800, Icenowy Zheng wrote:
> SoCs after A31 has a clock controller module in the PRCM part.
>
> Support the clock controller module on H5 and A64 now.
>
> Signed-off-by: Icenowy Zheng
> ---
> drivers/clk/sunxi-ng/Kconfig| 6 +
On 02/28/2017 12:41 PM, Greg Kurz wrote:
>>> +++ b/include/linux/syscalls.h
>>> @@ -775,6 +775,8 @@ asmlinkage long sys_futimesat(int dfd, const char
>>> __user *filename,
>>> asmlinkage long sys_faccessat(int dfd, const char __user *filename, int
>>> mode);
>>> asmlinkage long
On Wed, Mar 01, 2017 at 12:15:40PM +0800, Icenowy Zheng wrote:
> SoCs after A31 has a clock controller module in the PRCM part.
>
> Support the clock controller module on H5 and A64 now.
>
> Signed-off-by: Icenowy Zheng
> ---
> drivers/clk/sunxi-ng/Kconfig| 6 +
>
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.
Signed-off-by: Keerthy
---
arch/arm/boot/dts/omap443x.dtsi | 4
1 file
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.
Signed-off-by: Keerthy
---
arch/arm/boot/dts/omap443x.dtsi | 4
1 file changed, 4
Currently slope and offset values for calculating the hot spot
temperature of a thermal zone is being taken directly from driver
data. So try fetching it from device tree if not present only then
take it from driver data.
Signed-off-by: Keerthy
---
Currently slope and offset values for calculating the hot spot
temperature of a thermal zone is being taken directly from driver
data. So try fetching it from device tree if not present only then
take it from driver data.
Signed-off-by: Keerthy
---
On Wed, 1 Mar 2017 11:09:57 +0100
Cyrille Pitchen wrote:
> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
> > Vignesh,
> >
> > Am 27.02.2017 um 13:08 schrieb Vignesh R:
> >> Filesystems like UBIFS may pass vmalloc'd buffers to SPI NOR layer which
> >> will end
On Wed, 1 Mar 2017 11:09:57 +0100
Cyrille Pitchen wrote:
> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
> > Vignesh,
> >
> > Am 27.02.2017 um 13:08 schrieb Vignesh R:
> >> Filesystems like UBIFS may pass vmalloc'd buffers to SPI NOR layer which
> >> will end up in SPI layer. SPI core
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: Elena Reshetova
Signed-off-by:
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: Elena Reshetova
Signed-off-by: Hans Liljestrand
On Rab, 2017-03-01 at 10:01 +0100, Arnd Bergmann wrote:
> On Wed, Mar 1, 2017 at 8:23 AM, Loh, Tien Hock om> wrote:
> >
> > Arnd, Greg,
> Please don't top-post.
OK.
>
> >
> > I checked the attributes returned by the soc attribute subsystem,
> > but
> > it seems that it
On Rab, 2017-03-01 at 10:01 +0100, Arnd Bergmann wrote:
> On Wed, Mar 1, 2017 at 8:23 AM, Loh, Tien Hock om> wrote:
> >
> > Arnd, Greg,
> Please don't top-post.
OK.
>
> >
> > I checked the attributes returned by the soc attribute subsystem,
> > but
> > it seems that it is lacking something
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: Elena Reshetova
Signed-off-by:
Commit-ID: e86a2d2d34e20289ae7d46692e16d43c3a785db9
Gitweb: http://git.kernel.org/tip/e86a2d2d34e20289ae7d46692e16d43c3a785db9
Author: Masanari Iida
AuthorDate: Mon, 27 Feb 2017 22:07:03 +0900
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar
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: Elena Reshetova
Signed-off-by:
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: Elena Reshetova
Signed-off-by: Hans Liljestrand
Commit-ID: e86a2d2d34e20289ae7d46692e16d43c3a785db9
Gitweb: http://git.kernel.org/tip/e86a2d2d34e20289ae7d46692e16d43c3a785db9
Author: Masanari Iida
AuthorDate: Mon, 27 Feb 2017 22:07:03 +0900
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:51:41 +0100
x86/intel_rdt: Remove
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: Elena Reshetova
Signed-off-by: Hans Liljestrand
Commit-ID: e98fe5127b9cc8ab33d1094b81c19deb1f9082bf
Gitweb: http://git.kernel.org/tip/e98fe5127b9cc8ab33d1094b81c19deb1f9082bf
Author: Tobin C. Harding
AuthorDate: Mon, 20 Feb 2017 10:12:36 +1100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017
Commit-ID: 58ab9a088ddac4efe823471275859d64f735577e
Gitweb: http://git.kernel.org/tip/58ab9a088ddac4efe823471275859d64f735577e
Author: Dave Hansen
AuthorDate: Thu, 23 Feb 2017 14:26:03 -0800
Committer: Thomas Gleixner
CommitDate: Wed, 1
Commit-ID: e98fe5127b9cc8ab33d1094b81c19deb1f9082bf
Gitweb: http://git.kernel.org/tip/e98fe5127b9cc8ab33d1094b81c19deb1f9082bf
Author: Tobin C. Harding
AuthorDate: Mon, 20 Feb 2017 10:12:36 +1100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 11:27:26 +0100
x86/purgatory: Fix
Commit-ID: 58ab9a088ddac4efe823471275859d64f735577e
Gitweb: http://git.kernel.org/tip/58ab9a088ddac4efe823471275859d64f735577e
Author: Dave Hansen
AuthorDate: Thu, 23 Feb 2017 14:26:03 -0800
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:51:50 +0100
x86/pkeys: Check against
Commit-ID: aa5ec3f715d576353c7d8f4f8085634bd845b73f
Gitweb: http://git.kernel.org/tip/aa5ec3f715d576353c7d8f4f8085634bd845b73f
Author: Masanari Iida
AuthorDate: Mon, 27 Feb 2017 21:29:22 +0900
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar
Commit-ID: aa5ec3f715d576353c7d8f4f8085634bd845b73f
Gitweb: http://git.kernel.org/tip/aa5ec3f715d576353c7d8f4f8085634bd845b73f
Author: Masanari Iida
AuthorDate: Mon, 27 Feb 2017 21:29:22 +0900
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:51:40 +0100
x86/vmware: Remove
Commit-ID: 153654dbe595a68845ba14d5b0bfe299fa6a7e99
Gitweb: http://git.kernel.org/tip/153654dbe595a68845ba14d5b0bfe299fa6a7e99
Author: Rui Wang
AuthorDate: Tue, 28 Feb 2017 21:34:28 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017
Commit-ID: 1b17c6df852851b40c3c27c66b8fa2fd99cf25d8
Gitweb: http://git.kernel.org/tip/1b17c6df852851b40c3c27c66b8fa2fd99cf25d8
Author: Andrew Banman
AuthorDate: Fri, 17 Feb 2017 11:07:49 -0600
Committer: Ingo Molnar
CommitDate: Wed, 1 Mar 2017
Commit-ID: f2ae5da726172fcf82f7be801489dd585f6a38eb
Gitweb: http://git.kernel.org/tip/f2ae5da726172fcf82f7be801489dd585f6a38eb
Author: Rui Wang
AuthorDate: Tue, 28 Feb 2017 21:34:29 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017
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: Elena Reshetova
Signed-off-by:
Commit-ID: 153654dbe595a68845ba14d5b0bfe299fa6a7e99
Gitweb: http://git.kernel.org/tip/153654dbe595a68845ba14d5b0bfe299fa6a7e99
Author: Rui Wang
AuthorDate: Tue, 28 Feb 2017 21:34:28 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:51:41 +0100
x86/PCI: Implement
Commit-ID: 1b17c6df852851b40c3c27c66b8fa2fd99cf25d8
Gitweb: http://git.kernel.org/tip/1b17c6df852851b40c3c27c66b8fa2fd99cf25d8
Author: Andrew Banman
AuthorDate: Fri, 17 Feb 2017 11:07:49 -0600
Committer: Ingo Molnar
CommitDate: Wed, 1 Mar 2017 10:28:20 +0100
x86/platform/uv/BAU: Fix
Commit-ID: f2ae5da726172fcf82f7be801489dd585f6a38eb
Gitweb: http://git.kernel.org/tip/f2ae5da726172fcf82f7be801489dd585f6a38eb
Author: Rui Wang
AuthorDate: Tue, 28 Feb 2017 21:34:29 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:51:41 +0100
x86/ioapic: Split IOAPIC
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: Elena Reshetova
Signed-off-by: Hans Liljestrand
On Wed, Mar 01, 2017 at 04:21:28PM +0900, Byungchul Park wrote:
> On Tue, Feb 28, 2017 at 07:15:47PM +0100, Peter Zijlstra wrote:
> > On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote:
> > > + /*
> > > + * Each work of workqueue might run in a different context,
> > > + * thanks to
Commit-ID: 8392f16d38bb5222c03073a3906b7fd272386faf
Gitweb: http://git.kernel.org/tip/8392f16d38bb5222c03073a3906b7fd272386faf
Author: Borislav Petkov
AuthorDate: Tue, 21 Feb 2017 19:36:39 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017
On Wed, Mar 01, 2017 at 04:21:28PM +0900, Byungchul Park wrote:
> On Tue, Feb 28, 2017 at 07:15:47PM +0100, Peter Zijlstra wrote:
> > On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote:
> > > + /*
> > > + * Each work of workqueue might run in a different context,
> > > + * thanks to
Commit-ID: 8392f16d38bb5222c03073a3906b7fd272386faf
Gitweb: http://git.kernel.org/tip/8392f16d38bb5222c03073a3906b7fd272386faf
Author: Borislav Petkov
AuthorDate: Tue, 21 Feb 2017 19:36:39 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 11:27:26 +0100
x86/boot: Correct
Now when new refcount_t type and API are finally merged
(see include/linux/refcount.h), the following
patches convert various refcounters in the generic fs code from atomic_t
to refcount_t. By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free
Now when new refcount_t type and API are finally merged
(see include/linux/refcount.h), the following
patches convert various refcounters in the generic fs code from atomic_t
to refcount_t. By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free
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: Elena Reshetova
Signed-off-by:
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: Elena Reshetova
Signed-off-by: Hans Liljestrand
Commit-ID: 73667e31a153a66da97feb1584726222504924f8
Gitweb: http://git.kernel.org/tip/73667e31a153a66da97feb1584726222504924f8
Author: Arnd Bergmann
AuthorDate: Tue, 14 Feb 2017 22:17:17 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017
Commit-ID: b28ace12661fbcfd90959c1e84ff5a85113a82a1
Gitweb: http://git.kernel.org/tip/b28ace12661fbcfd90959c1e84ff5a85113a82a1
Author: Franck Demathieu
AuthorDate: Thu, 23 Feb 2017 10:48:55 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 1
Commit-ID: 73667e31a153a66da97feb1584726222504924f8
Gitweb: http://git.kernel.org/tip/73667e31a153a66da97feb1584726222504924f8
Author: Arnd Bergmann
AuthorDate: Tue, 14 Feb 2017 22:17:17 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:51:40 +0100
x86/hyperv: Hide
Commit-ID: b28ace12661fbcfd90959c1e84ff5a85113a82a1
Gitweb: http://git.kernel.org/tip/b28ace12661fbcfd90959c1e84ff5a85113a82a1
Author: Franck Demathieu
AuthorDate: Thu, 23 Feb 2017 10:48:55 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 10:08:20 +0100
irqchip/crossbar:
drivers/staging/media/atomisp/i2c/imx/../ov8858.c:2199:3-8: No need to set
.owner here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
Signed-off-by:
drivers/staging/media/atomisp/i2c/imx/../ov8858.c:2199:3-8: No need to set
.owner here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
Signed-off-by: Fengguang Wu
---
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_compat_css20.c:551:3-4:
Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Alan Cox
Signed-off-by: Fengguang Wu
---
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_compat_css20.c:551:3-4:
Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Alan Cox
Signed-off-by: Fengguang Wu
---
atomisp_compat_css20.c |2 +-
1 file changed, 1 insertion(+),
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_v4l2.c:465:2-3: Unneeded
semicolon
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_v4l2.c:511:2-3: Unneeded
semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Alan Cox
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_v4l2.c:465:2-3: Unneeded
semicolon
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_v4l2.c:511:2-3: Unneeded
semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Alan Cox
Signed-off-by:
> On Tue, Feb 28, 2017 at 10:45:25AM +0100, Michał Kępień wrote:
> > Some platform drivers use devm_input_allocate_device() together with
> > sparse_keymap_setup() in their .probe callbacks. While using the former
> > simplifies error handling, using the latter necessitates calling
> >
drivers/staging/media/atomisp/platform/clock/vlv2_plat_clock.c:248:3-8: No need
to set .owner here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
> On Tue, Feb 28, 2017 at 10:45:25AM +0100, Michał Kępień wrote:
> > Some platform drivers use devm_input_allocate_device() together with
> > sparse_keymap_setup() in their .probe callbacks. While using the former
> > simplifies error handling, using the latter necessitates calling
> >
drivers/staging/media/atomisp/platform/clock/vlv2_plat_clock.c:248:3-8: No need
to set .owner here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
Signed-off-by: Fengguang Wu
* tip-bot for Josh Poimboeuf wrote:
> Commit-ID: 90a7e63a31b8f7d630d12ef0d8d37d3ab87f76e5
> Gitweb: http://git.kernel.org/tip/90a7e63a31b8f7d630d12ef0d8d37d3ab87f76e5
> Author: Josh Poimboeuf
> AuthorDate: Wed, 1 Mar 2017 00:05:04 -0600
>
* tip-bot for Josh Poimboeuf wrote:
> Commit-ID: 90a7e63a31b8f7d630d12ef0d8d37d3ab87f76e5
> Gitweb: http://git.kernel.org/tip/90a7e63a31b8f7d630d12ef0d8d37d3ab87f76e5
> Author: Josh Poimboeuf
> AuthorDate: Wed, 1 Mar 2017 00:05:04 -0600
> Committer: Ingo Molnar
> CommitDate: Wed, 1
ti_thermal_expose_sensor always takes the
devm_thermal_zone_of_sensor_register call for registration
with the device tree nodes present for all the bandgap sensors
for omap3/4/5 and dra7 family. There are large chunks of unused
code. Removing all of them.
Signed-off-by: Keerthy
drivers/staging/media/atomisp/i2c/ov2680.c:1535:3-8: No need to set .owner
here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
Signed-off-by: Fengguang
ti_thermal_expose_sensor always takes the
devm_thermal_zone_of_sensor_register call for registration
with the device tree nodes present for all the bandgap sensors
for omap3/4/5 and dra7 family. There are large chunks of unused
code. Removing all of them.
Signed-off-by: Keerthy
---
drivers/staging/media/atomisp/i2c/ov2680.c:1535:3-8: No need to set .owner
here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
Signed-off-by: Fengguang Wu
---
ov2680.c |
1401 - 1500 of 1758 matches
Mail list logo