The command 'perf annotate' parses the output of objdump and also
investigates the comments produced by objdump. For example the
output of objdump produces (on x86):
23eee: 4c 8b 3d 13 01 21 00 mov 0x210113(%rip),%r15
# 234008
and the function mov__parse() is cal
From: Joonsoo Kim
Hello,
This patchset introduces a new tool, valid access checker.
Vchecker is a dynamic memory error detector. It provides a new debug feature
that can find out an un-intended access to valid area. Valid area here means
the memory which is allocated and allowed to be accessed
From: Joonsoo Kim
To prepare per object memory for vchecker, we need to change the layout
of the object when kmem_cache initialization. Add such code on
vchecker_cache_create() which is called when kmem_cache initialization.
And, this memory should be initialized when object is populated. Do it
From: Joonsoo Kim
They will be used for the vchecker in the following patch.
Make it non-static and add declairation in header files.
Signed-off-by: Joonsoo Kim
---
include/linux/kasan.h | 1 +
mm/kasan/kasan.c | 2 +-
mm/kasan/kasan.h | 2 ++
mm/kasan/report.c | 2 +-
4 files ch
On Mon, Nov 27, 2017 at 09:37:38PM -0800, Eric Biggers wrote:
> On Mon, Nov 27, 2017 at 10:56:47AM -0800, syzbot wrote:
> > Hello,
> >
> > syzkaller hit the following crash on
> > 1ea8d039f9edcfefb20d8ddfe136930f6e551529
> > git://git.cmpxchg.org/linux-mmots.git/master
> > compiler: gcc (GCC) 7.1.
From: Joonsoo Kim
Vchecker is a dynamic memory error detector. It provides a new debug
feature that can find out an un-intended access to valid area. Valid
area here means the memory which is allocated and allowed to be
accessed by memory owner and un-intended access means the read/write
that is
From: Joonsoo Kim
There is a usecase that check if stack trace is new or not during specific
period. Since stackdepot library doesn't support removal of stack trace,
it's impossible to know above thing. Since removal of stack trace is not
easy in the design of stackdepot library, we need another
The driver has been in the tree for a while, but its binding document
is missing. Hence, here it is.
Signed-off-by: Masahiro Yamada
---
.../pinctrl/socionext,uniphier-pinctrl.txt | 27 ++
MAINTAINERS| 1 +
2 files changed, 28
From: Joonsoo Kim
Since there is a different callpath even in the vchecker, static skip
value doesn't always exclude vchecker's stacktrace. Fix it through
checking stacktrace dynamically.
v2: skip two depth of stack at default, it's safe!
Signed-off-by: Joonsoo Kim
---
mm/kasan/vchecker.c | 4
On 11/27/2017 09:22 PM, Andy Lutomirski wrote:
> On Mon, Nov 27, 2017 at 2:49 AM, Ingo Molnar wrote:
>> From: Dave Hansen
>>
>> Short summary: Use x86 PCID feature to avoid flushing the TLB at all
>> interrupts and syscalls. Speed them up. Makes context switches
>> and TLB flushing slower.
>
>
From: Namhyung Kim
Since we're finding a cause of broken data, it'd be desired not to miss
any suspects. It doesn't use GFP_ATOMIC since it includes __GFP_HIGH
which is for system making forward progress.
It also adds a WARN_ON whenever it fails to allocate pages even with
__GFP_ATOMIC.
Signed
From: Joonsoo Kim
Getting full callstack is heavy job so it's sometimes better to
reduce this overhead by limiting callstack depth. So, this patch
makes the callstack depth configurable by using debugfs interface.
Signed-off-by: Joonsoo Kim
---
mm/kasan/vchecker.c | 81
From: Joonsoo Kim
kmalloc() is used everywhere in the kernel and it doesn't distiniguish
the callers since it doesn't much help to efficiently manage the memory.
However, there is a difference in the view of the debugging. A bug usually
happens on the objects allocated by specific allocation cal
From: Joonsoo Kim
Vchecker requires kmalloc caller address to support validation on
*specific* kmalloc user. Therefore, this patch passes slab allocation
caller address to vchecker hook. This caller address will be used in the
following patch.
Signed-off-by: Joonsoo Kim
---
include/linux/slab.
From: Joonsoo Kim
It's not easy to understand what can be done by the vchecker.
This sample could explain it and help to understand the vchecker.
Signed-off-by: Joonsoo Kim
---
lib/Kconfig.kasan | 9
lib/Makefile| 1 +
lib/vchecker_test.c | 117 ++
From: Namhyung Kim
The is_new argument is to check whether the given stack trace was
already in the stack depot or newly added. It'll be used by vchecker
callstack in the next patch.
Also add WARN_ONCE if stack depot failed to allocate stack slab for some
reason. This is unusual as it allocate
From: Joonsoo Kim
There is no reason not to support inline KASAN build. Support it.
Note that vchecker_check() function is now placed on kasan report function
to support inline build because gcc generates the inline check code and
then directly jump to kasan report function when poisoned value i
From: Namhyung Kim
By default, callstack checker only collects callchains. When a user
writes 'on' to the callstack file in debugfs, it checks and reports new
callstacks. Writing 'off' to disable it again.
# cd /sys/kernel/debug/vchecker
# echo 0 8 > anon_vma/callstack
# echo 1 > anon_vm
From: Namhyung Kim
The callstack checker is to find invalid code paths accessing to a
certain field in an object. Currently it only saves all stack traces at
the given offset. Reporting will be added in the next patch.
The below example checks callstack of anon_vma:
# cd /sys/kernel/debug/v
From: Joonsoo Kim
This is a main document for vchecker user.
Signed-off-by: Joonsoo Kim
---
Documentation/dev-tools/vchecker.rst | 200 +++
1 file changed, 200 insertions(+)
create mode 100644 Documentation/dev-tools/vchecker.rst
diff --git a/Documentation/dev
From: Joonsoo Kim
The purpose of the value checker is finding invalid user writing
invalid value at the moment that the value is written. However, there is
not enough infrastructure so that we cannot easily detect this case
in time.
However, by following way, we can emulate similar effect.
1. S
From: Joonsoo Kim
Since stack depot library doesn't support removal operation,
after removing and adding again callstack cb, callstack checker cannot
correctly judge whether this callstack is new or not for current cb
if the same callstack happens for previous cb.
This problem can be fixed by pe
From: Joonsoo Kim
Mark/unmark the shadow of the objects that is allocated before the
vchecker is enabled/disabled. It is necessary to fully debug the system.
Since there is no synchronization way to prevent slab object free,
we cannot synchronously mark/unmark the shadow of the allocated object.
On Tue, 28 Nov 2017, SF Markus Elfring wrote:
> >> It seems that I got no responses so far for clarification requests
> >> according to the documentation in a direction I hoped for.
> >
> > That's because you are pretty unresponsive to direction.
>
> From which places did you get this impression
On Tue, Nov 28, 2017 at 5:05 AM, Zhouyi Zhou wrote:
> When there are huge amount of quarantined cache allocates in system,
> number of entries in global_quarantine[i] will be great. Meanwhile,
> there is no relax in while loop in function qlist_move_cache which
> hold quarantine_lock. As a result,
On Thu, 16 Nov 2017 20:30:24 +0100,
SF Markus Elfring wrote:
>
> >> There is a general source code transformation pattern involved.
> >> So I find that it is systematic.
> >>
> >> But I did not dare to develop a script variant for the semantic patch
> >> language (Coccinelle software) which can ha
From: Patrick Bruenn
Neither rtc-imxdi nor rtc-mxc are compatible with i.MX53.
Add a modernized version of mxc_v2 from here:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/rtc/rtc-mxc_v2.c?h=imx_2.6.35_11.09.01
Changes to that version:
- updated to v4.15-rc1
- removed i
Am Dienstag, 28. November 2017, 08:29:44 CET schrieb Eric Biggers:
Hi Eric,
>
> Sometimes you have to reboot to get the reproducer to work, because the bug
> has to do with referencing counting of the "null skcipher" which is a
> global resource. Here's a patch that fixes it, it seems:
>
> ---
Hi,
On 11/28/2017 03:29 PM, Greg Kroah-Hartman wrote:
> On Tue, Nov 28, 2017 at 12:52:24PM +0800, Lu Baolu wrote:
>> This corrects the endpiont type value set to the DbC bulk in endpoint.
>> The previous value doesn't cause any problems because that we now only
>> use the bulk out endpoint. Set th
>> It seems that I got no responses so far for clarification requests
>> according to the documentation in a direction I hoped for.
>
> That's because you are pretty unresponsive to direction.
>From which places did you get this impression?
> You've gotten _many_ replies to your patches
I got
Hi Alex,
>>>
> Hi Gang,
>
> On 2017/11/28 13:33, Gang He wrote:
>> Hello Alex,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 2017/11/27 17:46, Gang He wrote:
Add ocfs2_overwrite_io function, which is used to judge if
overwrite allocated blocks, otherwise, the write will bring extra
block
On 11/27/2017 09:16 PM, Andy Lutomirski wrote:
> We need to split up __flush_tlb_one() into __flush_tlb_one() and
> __flush_tlb_one_kernel(). We've gotten away with having a single
> function for both this long because we've never had PCID on and
> nonglobal kernel mappings around. So we're buste
On Thu, 16 Nov 2017 12:52:41 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Thu, 16 Nov 2017 11:22:26 +0100
>
> The function "release_firmware" is called in the current implementation of
> the function "_request_firmware" after a failure was detected.
> Link:
> https://elixir.
On 2017/11/28 13:44, Gang He wrote:
> Hi Changwei,
>
>
>> Hi,
>> Gang
>>
>> On 2017/11/27 17:48, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>
>> Can yo
Signed-off-by: Masahiro Yamada
---
Documentation/devicetree/bindings/arm/uniphier.txt | 40 ++
MAINTAINERS| 1 +
2 files changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/uniphier.txt
diff --git a/Doc
This series is based on v4.15-rc1 and composed of
scpsys control (PATCH 1-4) and device tree (PATCH 5-6)
changes since v6:
- Rebase to v4.15-rc1.
changes since v5:
- Refine bus protection with proper variable name
and better implementation for the if statement.
changes since v4:
- Refine scpsy
Add power dt-bindings for MT2712.
Acked-by: Rob Herring
Signed-off-by: Weiyi Lu
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 3 +++
include/dt-bindings/power/mt2712-power.h | 26 ++
2 files changed, 29 insertions(+)
create mode 100644 include/dt-bindi
On Tue, Nov 28, 2017 at 07:30:46AM +0100, Stephan Mueller wrote:
> Am Montag, 27. November 2017, 23:43:08 CET schrieb Eric Biggers:
>
> Hi Eric,
>
> > No, that doesn't help. I tested v4.15-rc1 with all the extra commits from
> > crypto-2.6.git/master applied:
> >
> > crypto: algif_aead - sk
MT2712 add "set/clear" bus control register to each control register set
instead of providing only one "enable" control register, we could avoid
the read-modify-write racing by declaring "bus_prot_reg_update" as "false"
in scp_soc_data or declaring as "true" to use the legacy update method.
By impr
Add clock controller nodes for MT2712, include topckgen, infracfg,
pericfg, mcucfg and apmixedsys. This patch also add six oscillators that
provide clocks for MT2712.
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 115 ++
1 file changed, 115 i
This series is based on v4.15-rc1 and composed of
scpsys control (PATCH 1-4) and device tree (PATCH 5-6)
changes since v6:
- Rebase to v4.15-rc1.
changes since v5:
- Refine bus protection with proper variable name
and better implementation for the if statement.
changes since v4:
- Refine scpsy
add scpsys driver for MT2712
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 106 +++---
1 file changed, 100 insertions(+), 6 deletions(-)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
index c0f3219..435ce5e 1
add power controller node for MT2712
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index 5703793..61dd763 100644
--
On Tue, Nov 28, 2017 at 12:52:24PM +0800, Lu Baolu wrote:
> This corrects the endpiont type value set to the DbC bulk in endpoint.
> The previous value doesn't cause any problems because that we now only
> use the bulk out endpoint. Set the hardware with the correct value any
> way.
>
> Signed-off
There are dependent clock jpgdec/audio in scpsys on MT2712,
and will exist three dependent clocks on MT2712 VDEC.
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/so
On Wed, 22 Nov 2017 17:47:14 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Wed, 22 Nov 2017 17:43:25 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfr
On Mon, Nov 27, 2017 at 09:12:39PM +, Chris Coffey wrote:
> This patch fixes build errors that occur when trying to build the
> MOST modules. For example, the cdev module build fails with:
>
> make[3]: *** No rule to make target 'drivers/staging/most/aim-cdev/cdev.o',
> needed by 'drivers/sta
Hello Joseph,
>>>
>
> On 17/11/28 11:35, Gang He wrote:
>> Hello Joseph,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 17/11/27 17:46, Gang He wrote:
Add ocfs2_overwrite_io function, which is used to judge if
overwrite allocated blocks, otherwise, the write will bring extra
block alloca
Commit-ID: 55d2d0ad2fb4325f615d1950486fbc5e6fba1769
Gitweb: https://git.kernel.org/tip/55d2d0ad2fb4325f615d1950486fbc5e6fba1769
Author: Chunyu Hu
AuthorDate: Mon, 27 Nov 2017 22:21:39 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 28 Nov 2017 08:15:40 +0100
x86/idt: Load idt early i
Hi Jiada
> register SSI_MODE is set when SSI works in TDM Extended,
> but it isn't reset when SSI starts to work in other modes,
> thus causes issues.
>
> This patch clearss SSI_MODE register when SSI works in modes
> other than TDM Extended.
>
> Fixes: 186fadc132f0 ("ASoC: rsnd: add TDM Extend
On Mon, Nov 27, 2017 at 07:05:22PM -0500, Mikulas Patocka wrote:
>
>
> On Sat, 25 Nov 2017, Greg KH wrote:
>
> > On Mon, Nov 13, 2017 at 02:00:45PM -0500, Mikulas Patocka wrote:
> > > A small patch for schedule(), so that the code goes straght in the common
> > > case.
> > >
> > > Signed-off-by
There are some resets that are not associated with gates. These are
represented by a reset controller.
Reviewed-by: Andrew Jeffery
Signed-off-by: Joel Stanley
---
v5:
- Add Andrew's Reviewed-by
v3:
- Add named initalisers for the reset defines
- Add define for ADC
---
drivers/clk/clk-aspe
The majority of the clocks in the system are gates paired with a reset
controller that holds the IP in reset.
This borrows from clk_hw_register_gate, but registers two 'gates', one
to control the clock enable register and the other to control the reset
IP. This allows us to enforce the ordering:
This registers a platform driver to set up all of the non-core clocks.
The clocks that have configurable rates are now registered.
Reviewed-by: Andrew Jeffery
Signed-off-by: Joel Stanley
--
v6:
- Add Andrew's reviewed-by
v5:
- Remove eclk configuration. We do not have enough information to
c
This driver supports the ast2500, ast2400 (and derivative) BMC SoCs from
Aspeed.
This is v6. See patches for detailed changelogs.
v6: Added reviewed-bys
v5: Address review from Andrew
v4: Address review from Andrew and Stephen.
v3: Address review from Andrew and has seen more testing on hardwar
This adds the stub of a driver for the ASPEED SoCs. The clocks are
defined and the static registration is set up.
Reviewed-by: Andrew Jeffery
Signed-off-by: Joel Stanley
---
v6:
- Add SPDX copyright notices
v5:
- Add Andrew's reviewed-by
- Make aspeed_gates not initconst to avoid section mism
This registers the core clocks; those which are required to calculate
the rate of the timer peripheral so the system can load a clocksource
driver.
Reviewed-by: Andrew Jeffery
Signed-off-by: Joel Stanley
---
v5:
- Add Andrew's Reviewed-by
v4:
- Add defines to document the BIT() macros
v3:
On 27/11/17 05:56, Vinod Koul wrote:
On Mon, Nov 20, 2017 at 06:47:52AM +, Srinivas Kandagatla wrote:
+ * -ENOTCONN: If the transmitted message was not ACKed by destination
+ * device.
I am preferring ENODATA in SDW for this case, as Slaves didnt respond or
ACK.
Isn't that a ti
On Mon, 27 Nov 2017, Andy Lutomirski wrote:
> On Mon, Nov 27, 2017 at 8:57 PM, Chunyu Hu wrote:
> >> > To make WARN()s can work earlier to ap, we load the idt_table early
> >> > in start_secondary, and keep the second time idt load in cpu_init,
> >> > as there is a load_ucode_ap() there.
> >>
> >>
Hi Stephen,
Thanks for the patch.
On 27/11/17 10:24, Stephen Boyd wrote:
Some GIC configurations don't have an accessible ITS, but they
want to support MSIs through the distributor's SETSPI registers
or through the IMPLEMENTATION DEFINED message-based interrupt
request register region. This mod
This is akpm domain.
On Mon, 27 Nov 2017, Giuseppe Scrivano wrote:
kern_mount_data is a relatively expensive operation when creating a
new IPC namespace, so delay the mount until its first usage when not
creating the the global namespace.
On my machine, the time for creating 1000 new IPC names
I have a little bit of a hard time to find the right addressee for
this patch because there is no maintainer entry for drivers/firmware.
Can you apply the following through your tree?
Add missing entry for firmware subdirectory in drivers/Kconfig.
Signed-off-by: Heiner Kallweit
---
drivers/Kcon
2017-11-27 21:51 GMT+01:00 Arnd Bergmann :
[...]
>> There already is an effort to come up with a new AF_PACKET V4 [1].
>> We should make sure that any new interface does not have the
>> Y2038/Y2106 issue. But, if a new version is being developed and
>> that subsumes all existing use cases, then the
register SSI_MODE is set when SSI works in TDM Extended,
but it isn't reset when SSI starts to work in other modes,
thus causes issues.
This patch clearss SSI_MODE register when SSI works in modes
other than TDM Extended.
Fixes: 186fadc132f0 ("ASoC: rsnd: add TDM Extend Mode support")
Signed-off
On Mon, 27 Nov 2017 19:44:12 +0100,
Pavel Machek wrote:
>
> On Mon 2017-11-27 19:35:32, Takashi Iwai wrote:
> > On Mon, 27 Nov 2017 19:31:51 +0100,
> > Pavel Machek wrote:
> > >
> > > On Mon 2017-11-27 17:33:28, Takashi Iwai wrote:
> > > > On Mon, 27 Nov 2017 17:30:11 +0100,
> > > > Pavel Machek
On Mon, Nov 27, 2017 at 05:51:56PM +, Hartley Sweeten wrote:
> On Monday, November 27, 2017 3:28 AM, Ian Abbott wrote:
> > On 26/11/17 01:50, Alex Frappier Lachapelle wrote:
> >> + const struct comedi_lrange *lrange;
> >
> > NAK. The following lines of source code allocate memory poin
2017-11-27 22:30 GMT+08:00 Arnd Bergmann :
> On Mon, Nov 27, 2017 at 1:28 PM, Greentime Hu wrote:
>> @@ -0,0 +1,55 @@
>> +/dts-v1/;
>> +/ {
>> + compatible = "nds32 ae3xx";
>
> The compatible string doesn't seem to match the binding, it should always have
> vendor prefix.
Sorry I forgot to
Sphinx complains that it can't find intel_guc_loader.c, and rightly so:
The file has been renamed.
Fixes: e8668bbcb0f9 ("drm/i915/guc: Rename intel_guc_loader.c to
intel_guc_fw.c")
Cc: Michal Wajdeczko
Signed-off-by: Jonathan Neuschäfer
---
Documentation/gpu/i915.rst | 4 ++--
1 file changed,
On 17/11/28 11:35, Gang He wrote:
> Hello Joseph,
>
>
>> Hi Gang,
>>
>> On 17/11/27 17:46, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>> Signed-off-b
On Sat, 11 Nov 2017 20:22:36 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Sat, 11 Nov 2017 20:02:07 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a b
On Sat, 11 Nov 2017 19:13:15 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Sat, 11 Nov 2017 18:34:04 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a b
From: Shaohui Xie
Gianfar does not support EEE, but it can connect to a PHY which supports
EEE and the PHY advertises EEE by default, and its link partner also
advertises EEE, so the PHY enters low power mode when traffic rate is low,
which causes packet loss if an application's traffic rate is l
On 27/11/17 21:34, Thomas Gleixner wrote:
> XEN_PV paravirtualizes read/write_c3. This does not work with KAISER as the
> CR3 switch from and to user space PGD would require to map the whole XEN_PV
> machinery into both. It's also not clear whether the register space is
> sufficient to do so. All o
This patch-set introduces three patches to fix the memory related
issues. one fixes DMA operation failure when smmu is enabled.
the other two patches fixes incorrect usage of dma API that may
cause coherency problems.
Wei Hu (Xavier) (3):
RDMA/hns: Fix the issue of IOVA not page continuous in hi
If the smmu is enabled, the length of sg obtained from
__iommu_map_sg_attrs is not 4kB. When the IOVA is set with the sg
dma address, the IOVA will not be page continuous. so, the current
code has MTPT configuration error that probably cause dma operation
failure. In order to fix this issue, the IO
In general dma_alloc_coherent() return a CPU virtual address and
a DMA address, and we have no guarantee that the underlying memory
even has an associated struct page at all.
This patch gets rid of the page operation after dma_alloc_coherent,
and records the VA returned form dma_alloc_coherent in
In general dma_alloc_coherent() return a CPU virtual address and
a DMA address, and we have no guarantee that the virtual address
is either in the linear map or vmalloc, and not some other special
place. we have no guarantee that the underlying memory even has
an associated struct page at all.
In
Hi, Zhi
The patch have already got merged in 4.15 rc1 as
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=424268c7494c2ae24c95565b9047bbf30309e88a
Sean
On Mon, 2017-11-13 at 20:39 +0800, Zhi Mao wrote:
> Hi Thierry,
>
> Just have a ping for this patch.
>
Currently, leaking_addresses.pl only supports scanning 64 bit
architectures. This is due to how the regular expressions are formed. We
can do better than this. 32 architectures can be supported if we take
into consideration the kernel virtual address split.
Add support for ix86 32 bit architecture
Am Montag, 27. November 2017, 23:43:08 CET schrieb Eric Biggers:
Hi Eric,
> No, that doesn't help. I tested v4.15-rc1 with all the extra commits from
> crypto-2.6.git/master applied:
>
> crypto: algif_aead - skip SGL entries with NULL page
> crypto: af_alg - remove locking in async
On 2017/11/28 2:36, Jason Gunthorpe wrote:
> On Mon, Nov 27, 2017 at 10:41:21AM +0800, Wei Hu (Xavier) wrote:
>> This patch-set introduces three patches to fix about the memory
>> related issues.
> If these patches are for-rc can you revise the commit message to more
> clearly explain what the bu
On Mon, Nov 27, 2017 at 08:42:16AM +0530, kaiwan.billimo...@gmail.com wrote:
> Currently, leaking_addresses.pl only supports scanning and displaying 'leaked'
> 64-bit kernel virtual addresses. We can scan for and display 'leaked' 32-bit
> kernel virtual addresses as well.
Hi Kaiwan,
This is start
On 11/28/2017 06:35 AM, Brian Norris wrote:
Bridge drivers/helpers shouldn't be clobbering the drvdata, since a
parent driver might need to own this. Instead, let's return our
'dw_mipi_dsi' object and have callers pass that back to us for removal.
Reviewed-by: Archit Taneja
Signed-off-by:
Linus Torvalds writes:
> On Mon, Nov 27, 2017 at 4:03 PM, Linus Torvalds
> wrote:
>>
>> So the big remaining ones for me are the /proc//stack (stack
>> pointers) and the /proc/net/* ones.
>>
>> I'm a bit disappointed that those haven't been fixed already and
>> aren't even in this series..
>
> O
Hi,
Thanks a lot for working on this. Some comments below.
On 11/28/2017 07:25 AM, Nickey Yang wrote:
Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
MIPI DSI host controller bridge.
Signed-off-by: Nickey Yang
---
drivers/gpu/drm/rockchip/Kconfig|
Hi,
On (11/27/17 17:48), Byungchul Park wrote:
[..]
> > + /* Owner will clear console_waiter on hand off
> > */
> > + while (READ_ONCE(console_waiter))
> > + cpu_relax();
> > +
> > + sp
Hi Guenter,
Thanks again for you review.
I am very glad that this patch has been accepted.
Best Regards,
Eric Long
On Mon, Nov 27, 2017 at 08:09:18PM -0800, Guenter Roeck wrote:
> On 11/27/2017 06:18 PM, Eric Long wrote:
> >This patch adds the documentation for Spreadtrum watchdog driver.
> >
>
Hi Gang,
On 2017/11/28 13:33, Gang He wrote:
> Hello Alex,
>
>
>> Hi Gang,
>>
>> On 2017/11/27 17:46, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>> Si
add Arnaldo Carvalho de Melo
On 11/28/2017 02:13 PM, Li Zhijian wrote:
since 6aa7de0, we failed to build perf with C++(clang)
to fix the following compile errors
--
lizhijian@haswell-OptiPlex-9020:~/lkp/linux/tools/perf$ make
LLVM_CONFIG=/usr/bin/llvm-config-3.9 LIBCLANGLLVM=1
...
On Mon, Nov 27, 2017 at 11:36:37AM -0700, Jason Gunthorpe wrote:
> On Mon, Nov 27, 2017 at 10:41:21AM +0800, Wei Hu (Xavier) wrote:
> > This patch-set introduces three patches to fix about the memory
> > related issues.
>
> If these patches are for-rc can you revise the commit message to more
> cle
since 6aa7de0, we failed to build perf with C++(clang)
to fix the following compile errors
--
lizhijian@haswell-OptiPlex-9020:~/lkp/linux/tools/perf$ make
LLVM_CONFIG=/usr/bin/llvm-config-3.9 LIBCLANGLLVM=1
...
CC util/probe-finder.o
In file included from /home/lizj/linux/tools
Hi Linus,
I sent this last week as a follow on to the one you pulled, the tag
hasn't changed but the pull request has as you pulled the old tag.
This has a TTM regression fix for some virt gpus (bochs vga), a few
i915 stable fixes,
one vc4 fix, one uapi fix.
Dave.
The following changes since co
Since numa statistics has been separated from zone statistics framework,
but the functionality of zone_statistics() updates numa counters. Thus, the
function name makes people confused. So, change the name to
numa_statistics() as well as its call sites accordingly.
Signed-off-by: Kemi Wang
---
m
The existed implementation of NUMA counters is per logical CPU along with
zone->vm_numa_stat[] separated by zone, plus a global numa counter array
vm_numa_stat[]. However, unlike the other vmstat counters, numa stats don't
effect system's decision and are only read from /proc and /sys, it is a
slow
Hello Alex,
>>>
> Hi Gang,
>
> On 2017/11/27 17:46, Gang He wrote:
>> Return EAGAIN if any of the following checks fail for direct I/O:
>> Can not get the related locks immediately,
>> Blocks are not allocated at the write location, it will trigger
>> block allocation and block IO operations.
>
Hi Hans,
2017-11-27 18:26 GMT+08:00 Hans Verkuil :
> On 11/24/2017 03:36 AM, Jacob Chen wrote:
>> From: Jeffy Chen
>>
>> Add the header for userspace
>
> I gather that this effectively documents the metadata?
>
> I recommend using kernel-doc formatting here.
>
> One thing I immediately noticed is
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323
commit: d59158162e032917a428704160a2063a02405ec6 tracing: Add support for
preempt and irq enable/disable events
date: 7 weeks ago
config: x86_64-randconfig-s0-11281
For each function, it's exactly only one place need to return the found
rq, all other cases are NULL. So there is no need to explicitly set the
local variable later_rq/lowest_rq to NULL.
Signed-off-by: Zhen Lei
---
kernel/sched/deadline.c | 12
kernel/sched/rt.c | 12 -
On Mon, 2017-11-27 at 13:15 +, Colin King wrote:
> drivers/atm/eni.c
Aren't all those ++ variables unused?
They seem to be emitted in an
#if 0
printk(...)
#endif
Maybe these should be removed or changed
to something like:
#if 0
#define DEBUG_INCR(var) do { (var)++ } while (0)
#else
Hi Changwei,
>>>
> Hi,
> Gang
>
> On 2017/11/27 17:48, Gang He wrote:
>> Add ocfs2_overwrite_io function, which is used to judge if
>> overwrite allocated blocks, otherwise, the write will bring extra
>> block allocation overhead.
>>
>
> Can you elaborate how this overhead is introduced?
> Fo
1 - 100 of 1344 matches
Mail list logo
