<<< No Message Collected >>>
<<< No Message Collected >>>
If the address belongs to an inlined function, the source information
back to the first non-inlined function will be printed.
For example:
perf report --inline
-0.69% 0.00% inline ld-2.23.so [.] dl_main
- dl_main
0.56% _dl_relocate_object
If the address belongs to an inlined function, the source information
back to the first non-inlined function will be printed.
For example:
perf report --inline
-0.69% 0.00% inline ld-2.23.so [.] dl_main
- dl_main
0.56% _dl_relocate_object
On 03/03/17 at 12:43pm, Borislav Petkov wrote:
> On Sun, Feb 26, 2017 at 12:09:08PM +0800, Baoquan He wrote:
> > Am I right on understanding it?
>
> That's exactly what I mean: KERNEL_IMAGE_SIZE is 512M by default but
> we're not hard-constrained to it - we're hard-constrained to a 1G limit
> as
On 03/03/17 at 12:43pm, Borislav Petkov wrote:
> On Sun, Feb 26, 2017 at 12:09:08PM +0800, Baoquan He wrote:
> > Am I right on understanding it?
>
> That's exactly what I mean: KERNEL_IMAGE_SIZE is 512M by default but
> we're not hard-constrained to it - we're hard-constrained to a 1G limit
> as
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
Hi Stephen
On Wed, Mar 01, 2017 at 11:17:05AM -0800, Stephen Boyd wrote:
> On 02/15, Maxime Ripard wrote:
> > On Tue, Feb 14, 2017 at 06:26:39PM +0800, Chen-Yu Tsai wrote:
> > > On Tue, Feb 14, 2017 at 5:58 PM, Maxime Ripard
> > > wrote:
> > > > On Tue, Feb 14,
Hi Stephen
On Wed, Mar 01, 2017 at 11:17:05AM -0800, Stephen Boyd wrote:
> On 02/15, Maxime Ripard wrote:
> > On Tue, Feb 14, 2017 at 06:26:39PM +0800, Chen-Yu Tsai wrote:
> > > On Tue, Feb 14, 2017 at 5:58 PM, Maxime Ripard
> > > wrote:
> > > > On Tue, Feb 14, 2017 at 11:35:25AM +0800, Chen-Yu
This reset is required in order to fully reset the internal state of the
MIPI controller.
Signed-off-by: John Keeping
---
On Thu, 2 Mar 2017 13:56:46 -0800, Brian Norris wrote:
> On Fri, Feb 24, 2017 at 12:55:06PM +, John Keeping wrote:
> > + /*
> > +* Note that the
This reset is required in order to fully reset the internal state of the
MIPI controller.
Signed-off-by: John Keeping
---
On Thu, 2 Mar 2017 13:56:46 -0800, Brian Norris wrote:
> On Fri, Feb 24, 2017 at 12:55:06PM +, John Keeping wrote:
> > + /*
> > +* Note that the reset was not
On Friday, 2017-03-03 14:04:26 +0300, Dan Carpenter wrote:
> On Thu, Mar 02, 2017 at 01:44:36PM -0800, Laura Abbott wrote:
> > static struct sg_table *ion_map_dma_buf(struct dma_buf_attachment
> > *attachment,
> > enum dma_data_direction direction)
> > {
> >
On Friday, 2017-03-03 14:04:26 +0300, Dan Carpenter wrote:
> On Thu, Mar 02, 2017 at 01:44:36PM -0800, Laura Abbott wrote:
> > static struct sg_table *ion_map_dma_buf(struct dma_buf_attachment
> > *attachment,
> > enum dma_data_direction direction)
> > {
> >
From: Sunil Goutham
When booted with ACPI, random mac addresses are being
assigned to node1 interfaces due to mismatch of bgx_id
in BGX driver and ACPI tables.
This patch fixes this issue by setting maximum BGX devices
per node based on platform/soc instead of a macro. This
From: Sunil Goutham
When booted with ACPI, random mac addresses are being
assigned to node1 interfaces due to mismatch of bgx_id
in BGX driver and ACPI tables.
This patch fixes this issue by setting maximum BGX devices
per node based on platform/soc instead of a macro. This
change will set the
Ugh... No. This is totally wrong.
Please review how endianness works.
regards,
dan carpenter
Ugh... No. This is totally wrong.
Please review how endianness works.
regards,
dan carpenter
On Thu, Mar 02, 2017 at 03:07:21PM -0800, Steve Longerbeam wrote:
>
>
> On 03/02/2017 07:53 AM, Sakari Ailus wrote:
> >Hi Steve,
> >
> >On Wed, Feb 15, 2017 at 06:19:15PM -0800, Steve Longerbeam wrote:
> >>Add a new FRAME_TIMEOUT event to signal that a video capture or
> >>output device has
On Thu, Mar 02, 2017 at 03:07:21PM -0800, Steve Longerbeam wrote:
>
>
> On 03/02/2017 07:53 AM, Sakari Ailus wrote:
> >Hi Steve,
> >
> >On Wed, Feb 15, 2017 at 06:19:15PM -0800, Steve Longerbeam wrote:
> >>Add a new FRAME_TIMEOUT event to signal that a video capture or
> >>output device has
On 3 March 2017 at 14:21, Rob Herring wrote:
> On Thu, Mar 02, 2017 at 02:22:09PM +0800, Chunyan Zhang wrote:
>> SC9860 use the same serial device, so added a new compatible string to
>> support SC9860 as well, also added an example of how to describe this
>> serial device in DT.
On 3 March 2017 at 14:21, Rob Herring wrote:
> On Thu, Mar 02, 2017 at 02:22:09PM +0800, Chunyan Zhang wrote:
>> SC9860 use the same serial device, so added a new compatible string to
>> support SC9860 as well, also added an example of how to describe this
>> serial device in DT.
>>
>>
On 02/03/17 19:50, Alban wrote:
Add the binding to expose MTD partitions as nvmem providers.
It would be nice to see more description of this patch, explaining the
real use case.
Signed-off-by: Alban
---
.../devicetree/bindings/nvmem/mtd-nvmem.txt| 29
Looks good. Thanks.
regards,
dan carpenter
Looks good. Thanks.
regards,
dan carpenter
On 02/03/17 19:50, Alban wrote:
Add the binding to expose MTD partitions as nvmem providers.
It would be nice to see more description of this patch, explaining the
real use case.
Signed-off-by: Alban
---
.../devicetree/bindings/nvmem/mtd-nvmem.txt| 29 ++
1
On Thu, Mar 02, 2017 at 01:44:44PM -0800, Laura Abbott wrote:
>
> Practiaclly speaking, most Ion heaps are either going to be available
> all the time (system heaps) or found based off of the reserved-memory
> node. Parse the CMA and reserved-memory nodes to assign the heaps.
>
> Signed-off-by:
On Thu, Mar 02, 2017 at 01:44:44PM -0800, Laura Abbott wrote:
>
> Practiaclly speaking, most Ion heaps are either going to be available
> all the time (system heaps) or found based off of the reserved-memory
> node. Parse the CMA and reserved-memory nodes to assign the heaps.
>
> Signed-off-by:
On 03/02/2017 12:09 PM, Minchan Kim wrote:
> try_to_munlock returns SWAP_MLOCK if the one of VMAs mapped
> the page has VM_LOCKED flag. In that time, VM set PG_mlocked to
> the page if the page is not pte-mapped THP which cannot be
> mlocked, either.
Right.
>
> With that,
On 03/02/2017 12:09 PM, Minchan Kim wrote:
> try_to_munlock returns SWAP_MLOCK if the one of VMAs mapped
> the page has VM_LOCKED flag. In that time, VM set PG_mlocked to
> the page if the page is not pte-mapped THP which cannot be
> mlocked, either.
Right.
>
> With that,
This patch fixes an issue that phy_create() never enables the pm_runtime.
And then, we can remove calling the pm_runtime_{en,dis}able from some
phy drivers.
Fixes: ff764963479a ("drivers: phy: add generic PHY framework")
Cc: sta...@vger.kernel.org # v3.13+
Signed-off-by: Yoshihiro Shimoda
This patch fixes an issue that phy_create() never enables the pm_runtime.
And then, we can remove calling the pm_runtime_{en,dis}able from some
phy drivers.
Fixes: ff764963479a ("drivers: phy: add generic PHY framework")
Cc: sta...@vger.kernel.org # v3.13+
Signed-off-by: Yoshihiro Shimoda
---
All low-level PM/SMP code using virt_to_phys() should actually use
__pa_symbol() against kernel symbols. Update the documentation to move
away from virt_to_phys().
Cfr. commit 6996cbb2372189f7 ("ARM: 8641/1: treewide: Replace uses of
virt_to_phys with __pa_symbol")
Signed-off-by: Geert
All low-level PM/SMP code using virt_to_phys() should actually use
__pa_symbol() against kernel symbols. Update the documentation to move
away from virt_to_phys().
Cfr. commit 6996cbb2372189f7 ("ARM: 8641/1: treewide: Replace uses of
virt_to_phys with __pa_symbol")
Signed-off-by: Geert
The following Coccinelle script was used to detect this:
@r@
expression x;
void* e;
type T;
identifier f;
@@
(
*((T *)e)
|
((T *)x)[...]
|
((T*)x)->f
|
- (T*)
e
)
Signed-off-by: simran singhal
---
drivers/staging/nvec/nvec_kbd.c | 2 +-
1 file changed, 1
From: Liang Li
Add a new feature bit, VIRTIO_BALLOON_F_CHUNK_TRANSFER. Please check
the implementation patch commit for details about this feature.
Signed-off-by: Liang Li
Signed-off-by: Wei Wang
Cc: Michael S. Tsirkin
From: Liang Li
Add a new feature bit, VIRTIO_BALLOON_F_CHUNK_TRANSFER. Please check
the implementation patch commit for details about this feature.
Signed-off-by: Liang Li
Signed-off-by: Wei Wang
Cc: Michael S. Tsirkin
Cc: Paolo Bonzini
Cc: Cornelia Huck
Cc: Amit Shah
Cc: Dave Hansen
Cc:
The following Coccinelle script was used to detect this:
@r@
expression x;
void* e;
type T;
identifier f;
@@
(
*((T *)e)
|
((T *)x)[...]
|
((T*)x)->f
|
- (T*)
e
)
Signed-off-by: simran singhal
---
drivers/staging/nvec/nvec_kbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi,
On Wed, Mar 01, 2017 at 05:37:08PM -0800, Tony Lindgren wrote:
> * Sebastian Reichel [170301 17:10]:
> > Hi,
> >
> > Tony, since your omap4-droid4 dts patches were not
> > yet in a public repository and they would merge conflict
> > with my patches I put them all together
Hi,
On Wed, Mar 01, 2017 at 05:37:08PM -0800, Tony Lindgren wrote:
> * Sebastian Reichel [170301 17:10]:
> > Hi,
> >
> > Tony, since your omap4-droid4 dts patches were not
> > yet in a public repository and they would merge conflict
> > with my patches I put them all together into a single
> >
From: Michael Grzeschik
This adds a readonly nvmem driver for the i.MX IC Identification Module
(IIM). The IIM is found on the older i.MX SoCs like the i.MX25, i.MX27,
i.MX31, i.MX35, i.MX51 and the i.MX53.
The IIM can control up to 8 fuse banks with 256 bit each.
From: Michael Grzeschik
This adds a readonly nvmem driver for the i.MX IC Identification Module
(IIM). The IIM is found on the older i.MX SoCs like the i.MX25, i.MX27,
i.MX31, i.MX35, i.MX51 and the i.MX53.
The IIM can control up to 8 fuse banks with 256 bit each. Not all of the
banks are
The check for duplicate processor ids happens at boot time based on the
ACPI table contents, but the final sanity checks for a processor happen
at hotplug time.
At hotplug time, where the physical information is available, which might
differ from the ACPI table information, a check for duplicate
On 03/02/2017 04:45 PM, Laurent Pinchart wrote:
> Hi Neil,
>
> Thank you for the patch.
>
> On Thursday 02 Mar 2017 16:29:31 Neil Armstrong wrote:
>> Some display pipelines can only provide non-RBG input pixels to the HDMI TX
>> Controller, this patch takes the pixel format from the plat_data if
The check for duplicate processor ids happens at boot time based on the
ACPI table contents, but the final sanity checks for a processor happen
at hotplug time.
At hotplug time, where the physical information is available, which might
differ from the ACPI table information, a check for duplicate
On 03/02/2017 04:45 PM, Laurent Pinchart wrote:
> Hi Neil,
>
> Thank you for the patch.
>
> On Thursday 02 Mar 2017 16:29:31 Neil Armstrong wrote:
>> Some display pipelines can only provide non-RBG input pixels to the HDMI TX
>> Controller, this patch takes the pixel format from the plat_data if
Hi Pavel,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.10 next-20170303]
[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/Pavel-Machek/omap3isp-Correctly-set
Hi Pavel,
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.10 next-20170303]
[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/Pavel-Machek/omap3isp-Correctly-set
On 03/03/17 09:50, Srinivas Kandagatla wrote:
On 13/02/17 15:31, Sascha Hauer wrote:
From: Michael Grzeschik
This adds a readonly nvmem driver for the i.MX IC Identification Module
(IIM). The IIM is found on the older i.MX SoCs like the i.MX25, i.MX27,
i.MX31,
On 03/03/17 09:50, Srinivas Kandagatla wrote:
On 13/02/17 15:31, Sascha Hauer wrote:
From: Michael Grzeschik
This adds a readonly nvmem driver for the i.MX IC Identification Module
(IIM). The IIM is found on the older i.MX SoCs like the i.MX25, i.MX27,
i.MX31, i.MX35, i.MX51 and the
On Fri, Mar 03, 2017 at 11:14:29AM +0900, Jaehoon Chung wrote:
> On 03/02/2017 10:18 AM, Sergio Prado wrote:
> > Allows configuring Samsung S3C24XX MMC/SD/SDIO controller using a device
> > tree.
> >
> > Signed-off-by: Sergio Prado
> > ---
> >
On Fri, Mar 03, 2017 at 11:14:29AM +0900, Jaehoon Chung wrote:
> On 03/02/2017 10:18 AM, Sergio Prado wrote:
> > Allows configuring Samsung S3C24XX MMC/SD/SDIO controller using a device
> > tree.
> >
> > Signed-off-by: Sergio Prado
> > ---
> > drivers/mmc/host/s3cmci.c | 298
> >
We were reading clock rate directly from device tree "clock-frequency"
property of corresponding clock node in show_cpuinfo function.
Such approach is correct only in case cpu is always clocked by
"fixed-clock". If we use clock driver that allows rate to be changed
this won't work as rate may
We were reading clock rate directly from device tree "clock-frequency"
property of corresponding clock node in show_cpuinfo function.
Such approach is correct only in case cpu is always clocked by
"fixed-clock". If we use clock driver that allows rate to be changed
this won't work as rate may
This patch series replaces reading device tree with getting CPU
clock frequency via clock driver in show_cpuinfo function.
In order to achieve this we also add cpu nodes to device tree which
describes SMP system and add "clocks" properties to all ARC cpu nodes.
Vlad Zakharov (3):
ARC: [dts]
This patch series replaces reading device tree with getting CPU
clock frequency via clock driver in show_cpuinfo function.
In order to achieve this we also add cpu nodes to device tree which
describes SMP system and add "clocks" properties to all ARC cpu nodes.
Vlad Zakharov (3):
ARC: [dts]
Trying to get clock for CPU cores on SMP systems I found that I was only
able to get clock for core[0]. That was because only one cpu@0 node was
represented in ARC HS device tree and it was impossible to get clock for
"non-existing" cores.
So as ARC HS may have up to 4 cores we update device tree
Trying to get clock for CPU cores on SMP systems I found that I was only
able to get clock for core[0]. That was because only one cpu@0 node was
represented in ARC HS device tree and it was impossible to get clock for
"non-existing" cores.
So as ARC HS may have up to 4 cores we update device tree
ARC CPU cores are driven by core_clk so we add corresponding "clocks"
property to ARC cpu nodes.
Signed-off-by: Vlad Zakharov
---
arch/arc/boot/dts/skeleton.dtsi| 1 +
arch/arc/boot/dts/skeleton_hs.dtsi | 1 +
arch/arc/boot/dts/skeleton_hs_idu.dtsi | 1 +
3
ARC CPU cores are driven by core_clk so we add corresponding "clocks"
property to ARC cpu nodes.
Signed-off-by: Vlad Zakharov
---
arch/arc/boot/dts/skeleton.dtsi| 1 +
arch/arc/boot/dts/skeleton_hs.dtsi | 1 +
arch/arc/boot/dts/skeleton_hs_idu.dtsi | 1 +
3 files changed, 3
On 02/03/17 19:50, Alban wrote:
Allow drivers that use the nvmem API to read data stored on MTD devices.
This add a simple mtd user that register itself as a read-only nvmem
device.
Good stuff!! and useful for MAC addresses.
Am not going to repeat the same comments as Boris, but I totally
On 02/03/17 19:50, Alban wrote:
Allow drivers that use the nvmem API to read data stored on MTD devices.
This add a simple mtd user that register itself as a read-only nvmem
device.
Good stuff!! and useful for MAC addresses.
Am not going to repeat the same comments as Boris, but I totally
On Thursday 02 March 2017 02:46 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Feb 21, 2017 at 07:33:13PM +0530, Hari Bathini escreveu:
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the device
number and inode
On Thursday 02 March 2017 02:46 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Feb 21, 2017 at 07:33:13PM +0530, Hari Bathini escreveu:
This patch introduces a cgroup identifier entry field in perf report to
identify or distinguish data of different cgroups. It uses the device
number and inode
Introduce two helpers, is_migrate_highatomic() and is_migrate_highatomic_page().
Simplify the code, no functional changes.
Signed-off-by: Xishi Qiu
---
include/linux/mmzone.h | 5 +
mm/page_alloc.c| 14 ++
2 files changed, 11 insertions(+), 8
Introduce two helpers, is_migrate_highatomic() and is_migrate_highatomic_page().
Simplify the code, no functional changes.
Signed-off-by: Xishi Qiu
---
include/linux/mmzone.h | 5 +
mm/page_alloc.c| 14 ++
2 files changed, 11 insertions(+), 8 deletions(-)
diff --git
On 03/03/2017 at 09:03:25 +0100, Thomas Petazzoni wrote:
> On Thu, 2 Mar 2017 18:31:13 +0100, Alexandre Belloni wrote:
>
> > + irq = irq_of_parse_and_map(pdev->dev.of_node, 0);
>
> Any reason to use irq_of_parse_and_map() over the more conventional
> platform_get_irq() ?
>
No particular
On 03/03/2017 at 09:03:25 +0100, Thomas Petazzoni wrote:
> On Thu, 2 Mar 2017 18:31:13 +0100, Alexandre Belloni wrote:
>
> > + irq = irq_of_parse_and_map(pdev->dev.of_node, 0);
>
> Any reason to use irq_of_parse_and_map() over the more conventional
> platform_get_irq() ?
>
No particular
On Fri, Mar 03, 2017 at 09:54:07AM +, Srinivas Kandagatla wrote:
>
>
> On 03/03/17 09:50, Srinivas Kandagatla wrote:
> >
> >
> > On 13/02/17 15:31, Sascha Hauer wrote:
> > > From: Michael Grzeschik
> > >
> > > This adds a readonly nvmem driver for the i.MX IC
On Fri, Mar 03, 2017 at 09:54:07AM +, Srinivas Kandagatla wrote:
>
>
> On 03/03/17 09:50, Srinivas Kandagatla wrote:
> >
> >
> > On 13/02/17 15:31, Sascha Hauer wrote:
> > > From: Michael Grzeschik
> > >
> > > This adds a readonly nvmem driver for the i.MX IC Identification Module
> > >
The IIM is part of the i.MX device trees for long already, add a binding
document for it.
Signed-off-by: Sascha Hauer
---
.../devicetree/bindings/nvmem/imx-iim.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
The IIM is part of the i.MX device trees for long already, add a binding
document for it.
Signed-off-by: Sascha Hauer
---
.../devicetree/bindings/nvmem/imx-iim.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
This adds a readonly nvmem driver for the i.MX IC Identification Module (IIM)
which is found on the older i.MX SoCs. The IIM is part of the i.MX dts files
for long now, but so far there is no binding document for it, so add one now.
Sascha
Changes since v1:
- Fix unterminated array as reported
Use is_migrate_isolate_page() to simplify the code, no functional changes.
Signed-off-by: Xishi Qiu
---
mm/page_isolation.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/page_isolation.c b/mm/page_isolation.c
index f4e17a5..7927bbb 100644
---
This adds a readonly nvmem driver for the i.MX IC Identification Module (IIM)
which is found on the older i.MX SoCs. The IIM is part of the i.MX dts files
for long now, but so far there is no binding document for it, so add one now.
Sascha
Changes since v1:
- Fix unterminated array as reported
Use is_migrate_isolate_page() to simplify the code, no functional changes.
Signed-off-by: Xishi Qiu
---
mm/page_isolation.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/page_isolation.c b/mm/page_isolation.c
index f4e17a5..7927bbb 100644
--- a/mm/page_isolation.c
From: Sunil Goutham
This patch set fixes multiples issues such as IOMMU
translation faults when kernel is booted with IOMMU enabled
on host, incorrect MAC ID reading from ACPI tables and IPv6
UDP packet drop due to failure of checksum validation.
Sunil Goutham (3):
net:
From: Sunil Goutham
This patch set fixes multiples issues such as IOMMU
translation faults when kernel is booted with IOMMU enabled
on host, incorrect MAC ID reading from ACPI tables and IPv6
UDP packet drop due to failure of checksum validation.
Sunil Goutham (3):
net: thunderx: Fix IOMMU
Hi, Richard
On 03/03/2017 04:56 PM, Richard Weinberger wrote:
> Hyunchul Lee,
>
> Am 03.03.2017 um 08:44 schrieb Hyunchul Lee:
>> From: Hyunchul Lee
>>
>> When write syscall is called, every time security label is searched to
>> determine that file's privileges should be
Hi, Richard
On 03/03/2017 04:56 PM, Richard Weinberger wrote:
> Hyunchul Lee,
>
> Am 03.03.2017 um 08:44 schrieb Hyunchul Lee:
>> From: Hyunchul Lee
>>
>> When write syscall is called, every time security label is searched to
>> determine that file's privileges should be changed.
>> If
Hello,
On Thu, 2 Mar 2017 18:31:13 +0100, Alexandre Belloni wrote:
> + irq = irq_of_parse_and_map(pdev->dev.of_node, 0);
Any reason to use irq_of_parse_and_map() over the more conventional
platform_get_irq() ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux
Hello,
On Thu, 2 Mar 2017 18:31:13 +0100, Alexandre Belloni wrote:
> + irq = irq_of_parse_and_map(pdev->dev.of_node, 0);
Any reason to use irq_of_parse_and_map() over the more conventional
platform_get_irq() ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux
On Thu, Mar 02, 2017 at 01:44:36PM -0800, Laura Abbott wrote:
> static struct sg_table *ion_map_dma_buf(struct dma_buf_attachment
> *attachment,
> enum dma_data_direction direction)
> {
> struct dma_buf *dmabuf = attachment->dmabuf;
> struct
On Thu, Mar 02, 2017 at 01:44:36PM -0800, Laura Abbott wrote:
> static struct sg_table *ion_map_dma_buf(struct dma_buf_attachment
> *attachment,
> enum dma_data_direction direction)
> {
> struct dma_buf *dmabuf = attachment->dmabuf;
> struct
On Fri, Mar 3, 2017 at 11:11 AM, Dmitry Vyukov wrote:
> On Fri, Mar 3, 2017 at 11:09 AM, Dmitry Vyukov wrote:
>> Hello,
>>
>> I am getting the following use-after-free reports while running
>> syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760.
On Fri, Mar 3, 2017 at 11:11 AM, Dmitry Vyukov wrote:
> On Fri, Mar 3, 2017 at 11:09 AM, Dmitry Vyukov wrote:
>> Hello,
>>
>> I am getting the following use-after-free reports while running
>> syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. Seems
>> that work items are not properly
Hi All,
I discovered a deadlock when IMA is used in conjunction with NFS. I
booted with "ima_tcb". The deadlock happens when IMA measures the first
file on a NFS. It seems the IMA measurement triggers further NFS reads
and the NFS code then tries to acquire a lock it's already holding.
Hi All,
I discovered a deadlock when IMA is used in conjunction with NFS. I
booted with "ima_tcb". The deadlock happens when IMA measures the first
file on a NFS. It seems the IMA measurement triggers further NFS reads
and the NFS code then tries to acquire a lock it's already holding.
From: Sunil Goutham
ACPI support has been added to ARM IOMMU driver in 4.10
kernel and that has resulted in VNIC interfaces throwing
translation faults when kernel is booted with ACPI as
driver was not using DMA API.
On T88 HW takes care of data coherency when performing
From: Sunil Goutham
ACPI support has been added to ARM IOMMU driver in 4.10
kernel and that has resulted in VNIC interfaces throwing
translation faults when kernel is booted with ACPI as
driver was not using DMA API.
On T88 HW takes care of data coherency when performing
DMA operations hence in
From: Sunil Goutham
When BGX/LMACs are in QSGMII mode, for some LMACs, mode info is
not being printed. This patch will fix that. With changes already
done to not do any sort of serdes 2 lane mapping config calculation
in kernel driver, we can get rid of this logic.
From: Sunil Goutham
When BGX/LMACs are in QSGMII mode, for some LMACs, mode info is
not being printed. This patch will fix that. With changes already
done to not do any sort of serdes 2 lane mapping config calculation
in kernel driver, we can get rid of this logic.
Signed-off-by: Sunil Goutham
> On Thu, 2 Mar 2017, Thomas Gleixner wrote:
> > On Wed, 1 Mar 2017, Thomas Gleixner wrote:
> > > On Thu, 2 Mar 2017, Meelis Roos wrote:
> > >
> > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine,
> > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514
> On Thu, 2 Mar 2017, Thomas Gleixner wrote:
> > On Wed, 1 Mar 2017, Thomas Gleixner wrote:
> > > On Thu, 2 Mar 2017, Meelis Roos wrote:
> > >
> > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine,
> > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514
On 01/03/17 06:40, Peng Fan wrote:
Add compatible string for i.MX7D/S
Signed-off-by: Peng Fan
Cc: Shawn Guo
Cc: Srinivas Kandagatla
Cc: Maxime Ripard
Cc: Rob Herring
On 01/03/17 06:40, Peng Fan wrote:
Add compatible string for i.MX7D/S
Signed-off-by: Peng Fan
Cc: Shawn Guo
Cc: Srinivas Kandagatla
Cc: Maxime Ripard
Cc: Rob Herring
Cc: Mark Rutland
---
Documentation/devicetree/bindings/nvmem/imx-ocotp.txt | 1 +
1 file changed, 1 insertion(+)
Thanks
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This contains a bugfix and cleanups.
Thanks,
Miklos
---
Miklos Szeredi (3):
fuse: add missing FR_FORCE
fuse: cleanup fuse_file refcounting
fuse: release: private_data
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This contains a bugfix and cleanups.
Thanks,
Miklos
---
Miklos Szeredi (3):
fuse: add missing FR_FORCE
fuse: cleanup fuse_file refcounting
fuse: release: private_data
I do have ECB selected as well:
DM_CRYPT=y
CRYPTO_ECB=y
CRYPTO_XTS=y
name : ecb(aes)
driver : ecb-aes-s5p
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : ablkcipher
async: yes
blocksize: 16
min keysize :
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus
Because copy up can take a long time, serialized copy ups could be a big
performance bottleneck. This update allows concurrent copy up of regular files
eliminating this potential
1101 - 1200 of 1450 matches
Mail list logo