Hi Zhaoyang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.16-rc7 next-20180329]
[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
Hi Zhaoyang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.16-rc7 next-20180329]
[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
On 29 March 2018 at 19:40, Heiner Kallweit wrote:
> Am 29.03.2018 um 09:41 schrieb Vincent Guittot:
>>
>> I'm finally not so sure that i have the right set up to reproduce the
>> problem as I haven't been able to reproduce it since.
>>
>> Heiner,
>>
>> How fast the problem happens on your board ?
On Thu, Mar 29, 2018 at 09:58:54PM -0400, Jerome Glisse wrote:
> dma_map_resource() is the right API (thought its current implementation
> is fill with x86 assumptions). So i would argue that arch can decide to
> implement it or simply return dma error address which trigger fallback
> path into the
From: Fengguang Wu
NULL check before kfree is not needed.
Generated by: scripts/coccinelle/free/ifnullfree.cocci
Fixes: ad85ae608fe0 ("gpio: Remove VLA from gpiolib")
CC: Laura Abbott
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
url:
https://github.com/0day-ci/linux/commits/
On Thu, Mar 29, 2018 at 04:05:43PM -0300, Thiago Jung Bauermann wrote:
> kexec_file_load() on powerpc doesn't support kdump kernels yet, so it
> returns -ENOTSUPP in that case.
>
> I've recently learned that this errno is internal to the kernel and isn't
> supposed to be exposed to userspace. Ther
On Fri, 30 Mar 2018, Nicolai Stange wrote:
> Julia Lawall writes:
>
> > On Thu, 29 Mar 2018, Fabio Estevam wrote:
> >
> >> Hi Julia,
> >>
> >> On Thu, Mar 29, 2018 at 4:12 PM, Julia Lawall wrote:
> >> > Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE
> >> > for debugfs files
On 29 March 2018 at 23:30, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.9.92 release.
> There are 28 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
Julia Lawall writes:
> On Thu, 29 Mar 2018, Fabio Estevam wrote:
>
>> Hi Julia,
>>
>> On Thu, Mar 29, 2018 at 4:12 PM, Julia Lawall wrote:
>> > Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE
>> > for debugfs files.
>> >
>> > Semantic patch information:
>> > Rationale: DEFINE
On Thu, 2018-03-29 at 23:03 -0700, Quytelda Kahja wrote:
> If we just want to have the address field full of zeros during the
> driver probe, is there a reason we should zero it explicitly here?
> When the 'struct net_device' is first allocated using
> alloc_etherdev(), the dev_addr field is explic
If we just want to have the address field full of zeros during the
driver probe, is there a reason we should zero it explicitly here?
When the 'struct net_device' is first allocated using
alloc_etherdev(), the dev_addr field is explicitly set to zeros (in
the subfunction dev_addr_init() in net/core
There was no code for handling memory leaks of device_init_rings() and
request_irq(). It needs to free allocated memory in the device_init_rings()
, when request_irq() is failed. Add freeing sequences of irq and device
init rings.
Signed-off-by: Ji-Hun Kim
---
It's additional memory leak handling
This fixes xfstests/generic/392.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 15 +++
fs/f2fs/inode.c | 4
2 files changed, 19 insertions(+)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 000f93f6767e..675c39d85111 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -6
There are no null pointer checking on rd_info and td_info values which
are allocated by kzalloc. It has potential null pointer dereferencing
issues. Implement error handling code on device_init_rd*, device_init_td*
and vnt_start for the allocation failures.
Signed-off-by: Ji-Hun Kim
---
Changes v
On 03/29/2018 02:12 AM, Zephaniah E. Loss-Cutler-Hull wrote:
> On 03/28/2018 10:13 PM, Paolo Valente wrote:
>> In addition, the outcome of your attempt without
>> CONFIG_DEBUG_BLK_CGROUP would give us useful bisection information:
>> - if no failure occurs, then the issue is likely to be confined i
On (03/29/18 15:56), Maninder Singh wrote:
> Hello Nick/Sergey,
>
> Any suggestion or comments, so that we can change code and resend the patch?
Well... there were no replies to
https://marc.info/?l=linux-kernel&m=152161450026771&w=2
and
https://marc.info/?l=linux-kernel&m=152161860627974&w=2
2018-03-29 11:19 GMT+09:00 Ulf Magnusson :.
>> %%
>> +static void expand_string(const char *in)
>> +{
>> + char *p, *q;
>> +
>> + p = expand_string_value(in);
>> +
>> + q = p + strlen(p);
>> + while (q > p)
>> + unput(*--q);
>> +
>> + free(p);
>> +}
>>
On Thu, Mar 29, 2018 at 4:23 AM, Takashi Iwai wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> tags/sound-4.16
No such tag. Forgot to push?
There's the "for-linus" branch that matches the commit id you stated,
but no tags that point to it..
Hmm?
Linus
On 2018-03-29 07:03, Jonathan Corbet wrote:
> On Thu, 29 Mar 2018 05:01:32 -0400
> Richard Guy Briggs wrote:
>
> > > A little detail, but still...
> >
> > I am understanding that you would prefer more context (as opposed to
> > operational detail) in the description, laying out the use case fo
we cannot limit a process RSS although there is ulimit -m,
not sure why and when ulimit -m is not working, make it work
similar requirement:
https://stackoverflow.com/questions/3360348/why-ulimit-cant-limit-resident-memory-successfully-and-how
Signed-off-by: Li RongQing
---
mm/memory.c | 14 +++
Append 'p' sign to 'S' tag designating the type of context switch out event so
'Sp' means preemption context switch. Documentation is extended to cover
new presentation changes.
perf script --show-switch-events -F +misc -I -i perf.data:
hdparm 4073 [004] U 762.198265: 3801
Print additional 'preempt' tag for PERF_RECORD_SWITCH[_CPU_WIDE] OUT records
when
event header misc field contains PERF_RECORD_MISC_SWITCH_OUT_PREEMPT bit set
designating preemption context switch out event:
tools/perf/perf report -D -i perf.data | grep _SWITCH
0 768361415226 0x27f076 [0x28]:
Zhou reported a bug on Hisilicon arm64 D06 platform with 64KB page size:
[2.470908] kernel BUG at lib/ioremap.c:72!
[2.475079] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[2.480551] Modules linked in:
[2.483594] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
4.16.0-rc7-00062-g0b
Store preempting context switch out event into Perf trace as a part of
PERF_RECORD_SWITCH[_CPU_WIDE] record.
Percentage of preempting and non-preempting context switches help
understanding the nature of workloads (CPU or IO bound) that are running
on a machine;
The event is treated as preempt
2018-03-29 4:47 GMT+09:00 Keith Busch :
> On Wed, Mar 28, 2018 at 10:06:46AM +0200, Christoph Hellwig wrote:
>> For PCIe devices the right policy is not a round robin but to use
>> the pcie device closer to the node. I did a prototype for that
>> long ago and the concept can work. Can you look in
Implement preempting context switch out event as a part of
PERF_RECORD_SWITCH[_CPU_WIDE] record. The event is treated as preemption
one when task->state value of the thread being switched out is TASK_RUNNING;
Percentage of preempting and non-preempting context switches help
understanding the n
syzbot discovered that ucma_join_ip_multicast() mishandles AF_IB request
addresses. If an RDMA_USER_CM_CMD_JOIN_IP_MCAST request has
cmd.addr.sa_family=AF_IB then ucma_join_ip_multicast() reads beyond the
end of its cmd.addr.
Reject non IP RDMA_USER_CM_CMD_JOIN_IP_MCAST requests.
RDMA_USER_CM_CMD
The __FILE__ macro is used everywhere in the kernel to locate the file
printing the log message, such as WARN_ON(), etc. If the kernel is
built out of tree, this can be a long absolute path, like this:
WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:...
This is becau
On 3/29/2018 5:54 PM, Gary R Hook wrote:
> Implement a skeleton framework for debugfs support in the
> AMD IOMMU.
>
>
> Signed-off-by: Gary R Hook
> ---
> drivers/iommu/Kconfig |6 ++---
> drivers/iommu/Makefile|2 +-
> drivers/iommu/amd_iommu_debugfs.c | 47
>
On Thu, 29 Mar 2018 21:32:21 -0400, "Theodore Y. Ts'o" said:
> Yes, the breakage is my fault; my apologies. The new version of the
> patch is already posted in bugzilla (and on linux-ext4). I'll be
> pushing out a refreshed ext4.git branch shortly.
Confirming that reverting de57a63ea4389e39b1cd
On 3/29/2018 5:54 PM, Gary R Hook wrote:
> Provide base enablement for using debugfs to expose internal data of
> an IOMMU driver. When enabled, create the /sys/kernel/debug/iommu
So this can't actually create anything yet since nothing invokes the
function. Maybe describe how it should be used b
Add support for UniPhier PXs3 SoC. It is equivalent to LD20.
Signed-off-by: Kunihiko Hayashi
---
drivers/thermal/uniphier_thermal.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/thermal/uniphier_thermal.c
b/drivers/thermal/uniphier_thermal.c
index 9570473..55477d7 100644
--- a
Add a compatible string for thermal monitor implemented on
UniPhier PXs3 SoC.
Signed-off-by: Kunihiko Hayashi
---
Documentation/devicetree/bindings/thermal/uniphier-thermal.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/thermal/uniphier-thermal.txt
b/D
Add support for thermal monitor implemented on UniPhier PXs3 SoC.
Kunihiko Hayashi (2):
dt-bindings: thermal: uniphier: add a compatible string for PXs3
thermal: uniphier: add UniPhier PXs3 support
Documentation/devicetree/bindings/thermal/uniphier-thermal.txt | 1 +
drivers/thermal/uniphier
On 2018/3/30 11:39, Ji-Hun Kim wrote:
On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote:
On 2018/3/30 10:44, Ji-Hun Kim wrote:
@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw)
}
dev_dbg(&priv->pcid->dev, "call device init rd0 ring\n");
- de
On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote:
>
>
> On 2018/3/30 10:44, Ji-Hun Kim wrote:
> >@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw)
> > }
> > dev_dbg(&priv->pcid->dev, "call device init rd0 ring\n");
> >-device_init_rd0_ring(priv);
> >-
On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote:
>
>
> On 2018/3/30 10:44, Ji-Hun Kim wrote:
> >@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw)
> > }
> > dev_dbg(&priv->pcid->dev, "call device init rd0 ring\n");
> >-device_init_rd0_ring(priv);
> >-
On Fri, Mar 30, 2018 at 12:05 AM, Steven Rostedt wrote:
> On Thu, 29 Mar 2018 18:41:44 +0800
> Zhaoyang Huang wrote:
>
>> It is reported that some user app would like to echo a huge
>> number to "/sys/kernel/debug/tracing/buffer_size_kb" regardless
>> of the available memory, which will cause th
Hi Cyrille,
Commits
3efa50903ff3 ("mtd: fsl-quadspi: Distinguish the mtd device names")
85da6da22843 ("dt-bindings: fsl-quadspi: Add the example of two SPI NOR")
are missing a Signed-off-by from their committer.
P.S. should I be changing the contact I have for the spi-nor trees?
--
Cheers
Hi Alison,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on v4.16-rc7]
[also build test WARNING on next-20180329]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Hi,
On Thu, 29 Mar 2018 15:08:04 +0200 Andrew Lunn wrote:
> On Thu, Mar 29, 2018 at 04:42:40PM +0800, Jisheng Zhang wrote:
> >
> > Change the entry name and move it to its alphabetical location.
> > We move to ARM/Synaptics instead of ARM/Marvell.
>
> Hi Jisheng
>
> Please could you add some
Add detailed documentation for Coresight panic kdump, which contains
the idea for why need Coresight panic kdump and introduce the
implementation of Coresight panic kdump framework; the last section is
to explain what's usage.
Credits to Mathieu Poirier for many suggestions since the first version
Hi Thomas,
On Fri, Mar 09, 2018 at 04:08:19PM +0100, Thomas Gleixner wrote:
> On Fri, 9 Mar 2018, Ming Lei wrote:
> > On Fri, Mar 09, 2018 at 11:08:54AM +0100, Thomas Gleixner wrote:
> > > > > So my understanding is that these irq patches are enhancements and
> > > > > not bug
> > > > > fixes. I'
After kernel panic happens, Coresight tracing data has much useful info
which can be used for analysis. For example, the trace info from ETB
RAM can be used to check the CPU execution flows before the crash. So
we can save the tracing data from sink devices, and rely on kdump to
save DDR content
For easy management and friendly adding more Coresight documentation,
this commit creates a new directory: Documentation/trace/coresight.
This commit also moves Coresight related docs into the new directory
and updates MAINTAINERS file to reflect docs movement.
Signed-off-by: Leo Yan
---
Docume
If Coresight path is enabled for specific CPU, the sink device handler
need to be set to kdump node; on the other hand we also need to clear
sink device handler when path is disabled.
This patch sets sink devices handler for kdump node for two separate
Coresight enabling modes: CS_MODE_SYSFS and C
ETMv4 hardware information and configuration needs to be saved as
metadata; the metadata format should be compatible with 'perf' tool and
finally is used by tracing data decoder. ETMv4 works as tracer per CPU,
we cannot wait for gathering ETM info after CPU panic has happened in
case there have CP
Since Coresight panic kdump functionality has been ready, this patch is
to hook panic callback function for ETB/ETF driver. The driver data
structure has allocated a buffer when the session started, so simply
save tracing data into this buffer when panic happens and update buffer
related info for
This patch set is to explore Coresight tracing data for postmortem
debugging. When kernel panic happens, the Coresight panic kdump can
help to save on-chip tracing data and tracer metadata into DRAM, later
relies on kdump and crash/perf tools to recovery tracing data for
"offline" analysis.
The d
On 2018/3/30 10:44, Ji-Hun Kim wrote:
@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw)
}
dev_dbg(&priv->pcid->dev, "call device init rd0 ring\n");
- device_init_rd0_ring(priv);
- device_init_rd1_ring(priv);
- device_init_td0_ring(priv);
-
Synaptics has acquired the Multimedia Solutions Business of Marvell[1].
So change the berlin entry name and move it to its alphabetical
location. We move to ARM/Synaptics instead of ARM/Marvell.
This patch also updates my email address from marvell to synaptics.
[1] https://www.synaptics.com/comp
On Thu, Mar 29, 2018 at 10:05:35AM +1100, Dave Chinner wrote:
>On Wed, Mar 28, 2018 at 07:30:06PM +, Sasha Levin wrote:
>> This is actually something I want maintainers to dictate. What sort of
>> testing would make the XFS folks happy here? Right now I'm doing
>> "./check 'xfs/*'" with xfstest
On 2018年03月30日 10:05, Tiwei Bie wrote:
On Mon, Mar 26, 2018 at 11:38:53AM +0800, Jason Wang wrote:
This patch introduces basic support for event suppression aka driver
and device area. Compile tested only.
Signed-off-by: Jason Wang
---
[...]
+
+static bool vhost_notify_packed(struct vhost_
There are no null pointer checking on rd_info and td_info values which
are allocated by kzalloc. It has potential null pointer dereferencing
issues. Implement error handling code on device_init_rd*, device_init_td*
and vnt_start for the allocation failures.
Signed-off-by: Ji-Hun Kim
---
Changes v
On Fri, Mar 30, 2018 at 09:39:03AM +0800, Ganesh Mahendran wrote:
> 2018-03-30 9:29 GMT+08:00 Minchan Kim :
> > Hi Ganesh,
> >
> > On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote:
> >> 2018-03-29 14:54 GMT+08:00 Minchan Kim :
> >> > binder_update_page_range needs down_write of mmap
On Thu, Mar 29, 2018 at 02:37:10PM -0700, Casey Schaufler wrote:
> On 3/29/2018 2:14 PM, Sargun Dhillon wrote:
> > This patch introduces a mechanism to add mutable hooks and immutable
> > hooks to the callback chain. It adds an intermediary item to the
> > chain which separates mutable and immutabl
On 2018年03月29日 22:44, Michael S. Tsirkin wrote:
On Thu, Mar 29, 2018 at 04:00:04PM +0800, Jason Wang wrote:
Vq log_base is the userspace address of bitmap which has nothing to do
with IOTLB. So it needs to be validated unconditionally otherwise we
may try use 0 as log_base which may lead to pi
Fixes the following sparse warning:
drivers/gpu/drm/amd/amdkfd/kfd_chardev.c:1150:6: warning:
symbol 'kfd_dev_is_large_bar' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Passing NULL pointer to PTR_ERR will result in return value of 0
indicating success which is clearly not what it is intended here.
This patch returns -EINVAL instead.
Fixes: 5ec7e02854b3 ("drm/amdkfd: Add ioctls for GPUVM memory management")
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/amd/amd
Linus. :-)
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.16-rc7 next-20180329]
[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/Minchan-Kim/ANDROID-binder-change-down_wri
On 3/30/2018 9:43 AM, Wei Yang Wrote:
On Thu, Mar 29, 2018 at 04:06:38PM +0800, Jia He wrote:
On 3/28/2018 5:26 PM, Wei Yang Wrote:
On Sun, Mar 25, 2018 at 08:02:16PM -0700, Jia He wrote:
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the
On Mon, Mar 26, 2018 at 11:38:53AM +0800, Jason Wang wrote:
> This patch introduces basic support for event suppression aka driver
> and device area. Compile tested only.
>
> Signed-off-by: Jason Wang
> ---
[...]
> +
> +static bool vhost_notify_packed(struct vhost_dev *dev,
> +
For new Centaur CPUs the ucode will take care of the preservation of
cache coherence between CPU cores in C-states and the other CPU cores
regardless of how deep the C-states are, so it is not necessary to
flush the caches in software before entering C3.
Signed-off-by: David Wang
Changes from v1
On Thu, Mar 29, 2018 at 10:25:52AM -0600, Logan Gunthorpe wrote:
>
>
> On 29/03/18 10:10 AM, Christian König wrote:
> > Why not? I mean the dma_map_resource() function is for P2P while other
> > dma_map_* functions are only for system memory.
>
> Oh, hmm, I wasn't aware dma_map_resource was exc
From: David Howells
Date: Thu, 29 Mar 2018 23:25:46 +0100
> David Miller wrote:
>
>> David, this GIT URL has tons of unrelated changes. It seems to bring in
>> the parts of Linus's tree that haven't proagated to 'net' yet.
>
> Sorry about that, I rebased on the wrong branch by accident.
>
>
From: Jaegeuk Kim
When remounting ext4 from ro to rw, currently it allows its transition,
even if ext4_commit_super() returns EIO. Even worse thing is, after that,
fs/buffer complains buffer dirty bits like:
Call trace:
[] mark_buffer_dirty+0x184/0x1a4
[] __ext4_handle_dirty_super+0x4c/0xfc
On Thu, Mar 29, 2018 at 04:06:38PM +0800, Jia He wrote:
>
>
>On 3/28/2018 5:26 PM, Wei Yang Wrote:
>> On Sun, Mar 25, 2018 at 08:02:16PM -0700, Jia He wrote:
>> > Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>> > where possible") optimized the loop in memmap_init_zone().
On Thu, Mar 29, 2018 at 03:19:46PM -0400, Daniel Jordan wrote:
> On 03/20/2018 04:54 AM, Aaron Lu wrote:
> > This series is meant to improve zone->lock scalability for order 0 pages.
> > With will-it-scale/page_fault1 workload, on a 2 sockets Intel Skylake
> > server with 112 CPUs, CPU spend 80% of
2018-03-30 9:29 GMT+08:00 Minchan Kim :
> Hi Ganesh,
>
> On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote:
>> 2018-03-29 14:54 GMT+08:00 Minchan Kim :
>> > binder_update_page_range needs down_write of mmap_sem because
>> > vm_insert_page need to change vma->vm_flags to VM_MIXEDMAP u
In Makefile.config, to make all libraries flags have _SUPPORT suffix,
rename HAVE_DWARF_GETLOCATIONS to HAVE_DWARF_GETLOCATIONS_SUPPORT
Signed-off-by: Jin Yao
---
tools/perf/Makefile.config | 2 +-
tools/perf/util/dwarf-aux.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
We keep having bug reports that when users build perf on their own,
but they don't install some needed libraries such as libelf,
libbfd/libibery.
The perf can build, but it is missing important functionality.
This patch provides a new option '-vv' for perf which will
print the compiled-in status
From: Jiri Olsa
Adding IS_BUILTIN macro and its dependencies into
tools world.
It's taken from kernel's include/linux/kconfig.h,
which can't be taken completely due to its kconfig
dependencies.
Signed-off-by: Jiri Olsa
---
tools/include/tools/config.h | 34 ++
Since a new option '--build-options' is created for 'perf version',
so we need to document it.
Signed-off-by: Jin Yao
---
tools/perf/Documentation/perf-version.txt | 24
1 file changed, 24 insertions(+)
create mode 100644 tools/perf/Documentation/perf-version.txt
diff
This patch checks the values passed by CFLAGS (-DHAVE_XXX) and then
print the status of libraries.
For example, if HAVE_DWARF_SUPPORT is defined, that means the
library "dwarf" is compiled-in. The patch will print the status
"on" for this library otherwise it print the status "OFF".
A new option
We keep having bug reports that when users build perf on their own,
but they don't install some needed libraries such as libelf,
libbfd/libibery.
The perf can build, but it is missing important functionality. And
users may complain that perf has issue or bug.
This patch-set support to print the s
On Thu, Mar 29, 2018 at 02:35:44PM -0400, Stephen Smalley wrote:
> >
> > broke a longstanding assumption by SELinux that it could call getxattr with
> > a NULL buffer and 0 size to probe whether the filesystem supports the
> > security xattrs at mount time.
> >
> > Options for fixing:
> > - Rev
Hi Ganesh,
On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote:
> 2018-03-29 14:54 GMT+08:00 Minchan Kim :
> > binder_update_page_range needs down_write of mmap_sem because
> > vm_insert_page need to change vma->vm_flags to VM_MIXEDMAP unless
> > it is set. However, when I profile bin
On Thu, Mar 29, 2018 at 2:32 PM, Nick Desaulniers
wrote:
> On Tue, Mar 27, 2018 at 1:39 PM Kees Cook wrote:
>>[...]
>> + if (numdevs > (INT_MAX - sizeof(*ios)) /
>> + sizeof(struct ore_per_dev_state))
>> + return -ENOMEM;
>> + size_ios = sizeof(*ios)
2018-03-29 14:54 GMT+08:00 Minchan Kim :
> binder_update_page_range needs down_write of mmap_sem because
> vm_insert_page need to change vma->vm_flags to VM_MIXEDMAP unless
> it is set. However, when I profile binder working, it seems
> every binder buffers should be mapped in advance by binder_mma
Hi Kyle,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on v4.16-rc7]
[cannot apply to sound/for-next next-20180329]
[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
Hi Miklos,
Commit
cbf293becfa4 ("ovl: cleanup setting OVL_INDEX")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpGOkpUoJzao.pgp
Description: OpenPGP digital signature
On Wed, Mar 28, 2018 at 08:14:03AM -0700, Tim Harvey wrote:
> Signed-off-by: Tim Harvey
> ---
> drivers/watchdog/Kconfig | 10
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/gsc_wdt.c | 146
> +
> 3 files changed, 157 insertions(+)
>
New centaur CPUs(Familiy == 7) also support this cpu temperature sensor.
Change from v2 to v3:
*replace "goto" with "if...else.." according to suggestion from Guenter
Change from v1 to v2:
*fixed the wrong if condition in patch v1.
Signed-off-by: David Wang
---
drivers/hwmon/via-cpute
On Fri, Mar 30, 2018 at 07:42:37AM +0800, kbuild test robot wrote:
> Hi Minchan,
>
> I love your patch! Yet something to improve:
Glad to hear.
It's first time someone loves my patch. ;-)
>
> [auto build test ERROR on staging/staging-testing]
> [also build test ERROR on
Hi Stanimir,
+/* Get the slice entry by index */
+static struct llcc_slice_desc *llcc_slice_get_entry(struct device *dev, int n)
drop this *slice* word from function names
Please note that we are activating/de-activating a "slice" of the LLCC
and not a whole LLCC. "slice" makes perfect sens
On Tue, Mar 27, 2018 at 4:57 PM, Ganesh Goudar wrote:
> Hi,
>
> Kindly pull the new firmware from the following URL.
> git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
>
> Thanks
> Ganesh
>
> The following changes since commit eb6ad87c6f38cde9ec1556f3de4171a5164deda8:
>
> cxgb4: upd
Thanks, that patch has solved issue.
On Thu, Mar 29, 2018 at 7:51 PM, Steffen Klassert
wrote:
> Please always make sure to Cc net...@vger.kernel.org
> on networking problems.
>
> On Wed, Mar 28, 2018 at 10:21:32PM +, Derek Robson wrote:
>> The ipsec VPN is broken in 4.16-rc7 and seem to have
Hi Kyle,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on v4.16-rc7]
[cannot apply to sound/for-next next-20180329]
[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
On Wed, 2018-03-28 at 16:43 +0800, Wen Yang wrote:
> There would be so many same lines printed by frequent prink if one
> disk went wrong, like,
> [ 546.185242] sd 0:1:0:0: rejecting I/O to offline device
> [ 546.185258] sd 0:1:0:0: rejecting I/O to offline device
> [ 546.185280] sd 0:1:0:0: re
There is no need to handle 3/4 empty/full interrupts
as the maximum supported transfer length in PIO mode
is 64 bytes for sun4i-family SoCs. As long as a
problem was reported previously with filling FIFO
on A10s then we stick with 63 bytes depth.
Signed-off-by: Sergey Suloev
---
drivers/spi/spi
Hi Minchan,
I love your patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.16-rc7 next-20180329]
[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
Hi,
On 03/29/2018 04:52 PM, Joerg Roedel wrote:
> On Mon, Mar 26, 2018 at 08:38:21AM +0800, Lu Baolu wrote:
>> Hi Joerg,
>>
>> A gentle ping. :-)
>>
>> Any comments on this patch set?
> Yes, it doesn't apply on-top of my x86/vt-d branch. Please rebase it
> after the merge-window to rc1 and re-send
On 3/29/18 4:04 PM, Matias Bjørling wrote:
> Hi Jens,
>
> Here is a bunch of patches for 4.17. They include:
>
> - Open-Channel 2.0 support by Javier and I.
> - Lots of refactoring patches to enable 2.0 support.
> - Fixes to pblk from Hans, Markus, and Dan.
> - Introduction of write amplicati
On 03/29/2018 12:00 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.126 release.
> There are 20 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 s
On 03/29/2018 12:00 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.92 release.
> There are 28 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 sh
On 03/29/2018 11:59 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.32 release.
> There are 43 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 s
On 03/29/2018 11:59 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.15.15 release.
> There are 47 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 s
Minor changes to fulfill the coding style and
improve the readability.
Signed-off-by: Sergey Suloev
---
drivers/spi/spi-sun4i.c | 32 +---
1 file changed, 17 insertions(+), 15 deletions(-)
diff --git a/drivers/spi/spi-sun4i.c b/drivers/spi/spi-sun4i.c
index 2a49c22.
On Thu, Mar 29, 2018 at 9:02 AM, Jan Kara wrote:
> On Wed 21-03-18 15:57:48, Dan Williams wrote:
[..]
> I find it quite tricky that in case we pass zero page / empty entry into
> dax_[dis]associate_entry(), it will not do anything because
> dax_entry_size() will return 0. Can we add an explicit ch
Hello,
syzbot hit the following crash on upstream commit
0b412605ef5f5c64b31f19e2910b1d5eba9929c3 (Thu Mar 29 01:07:23 2018 +)
Merge tag 'drm-fixes-for-v4.16-rc8' of
git://people.freedesktop.org/~airlied/linux
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=5a170e19c963a2e0
1 - 100 of 1077 matches
Mail list logo
