On 5/13/18 2:10 PM, Eric Biggers wrote:
On Wed, Mar 21, 2018 at 09:00:01AM -0700, syzbot wrote:
[...]
Still reproducible on Linus' tree (commit 66e1c94db3cd4) and linux-next
(next-20180511). Here's a simplified reproducer:
Thanks for the test case !!
Regards,
Santosh
Hello,
syzbot found the following crash on:
HEAD commit:3eb2ce825ea1 Linux 4.16-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16bd9d9380
kernel config: https://syzkaller.appspot.com/x/.config?x=8addcf4530d93e53
dashboard link: https://syzkaller.a
Hi Shuah,
Today's linux-next merge of the kselftest tree got a conflict in:
tools/testing/selftests/kvm/vmx_tsc_adjust_test.c
between commit:
bcb2b94ae010 ("KVM: selftests: exit with 0 status code when tests cannot be
run")
from the kvm-fixes tree and commit:
13911360966d ("selftests:
Hi,
On 05/12/2018 04:54 AM, Jacob Pan wrote:
> DMA faults can be detected by IOMMU at device level. Adding a pointer
> to struct device allows IOMMU subsystem to report relevant faults
> back to the device driver for further handling.
> For direct assigned device (or user space drivers), guest OS
On Sun, May 13, 2018 at 11:40:07AM +0300, Alexander Popov wrote:
> It seems that previously I was very "lucky" to accidentally have those
> MIN_STACK_LEFT,
> call trace depth and oops=panic together to experience a hang on stack
> overflow
> during BUG().
>
>
> When I run my test in a loop _wit
On Mon, May 14, 2018 at 5:02 AM, Eric Biggers wrote:
> Sorry, messed up address for KVM mailing list. See message below.
>
> On Sun, May 13, 2018 at 08:00:07PM -0700, Eric Biggers wrote:
>> With CONFIG_KCOV=y and an AMD processor, running the following program
>> crashes
>> the kernel with no ou
On 14.05.2018 06:33, Oleksij Rempel wrote:
>
>
> On 12.05.2018 13:13, Rafael J. Wysocki wrote:
>> On Friday, May 4, 2018 8:50:52 PM CEST Oleksij Rempel wrote:
>>> Hallo Andrew,
>>> I need your ACK or NACK for this patch.
>>>
>>> This function is used to configure external PMIC to interpret
>>>
On Sun, May 13, 2018 at 08:47:24PM -0700, Randy Dunlap wrote:
> On 05/13/2018 08:15 PM, Joel Fernandes (Google) wrote:
> > rcu_seq_snap may be tricky for someone looking at it for the first time.
> > Lets document how it works with an example to make it easier.
> >
> > Signed-off-by: Joel Fernande
On Sun, May 13, 2018 at 07:22:06PM -0700, Paul E. McKenney wrote:
[..]
> > > > > > If you don't mind going through the if conditions in the funnel
> > > > > > locking loop
> > > > > > with me, it would be quite helpful so that I don't mess the code up
> > > > > > and would
> > > > > > also help m
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
WARNING:
drivers/staging/vc04_services/bcm2835-camera/bcm2835-v4l2.o(.data+0x0): Section
mismatch in reference from the variable bcm2835_camera_driver to the function
.init.text:bcm28
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/staging/most/video/video.c: In function 'vidioc_enum_fmt_vid_cap':
drivers/staging/most/video/video.c:265:25: warning: unused variable 'mdev'
[-Wunused-variable]
struct most_v
On 12.05.2018 13:13, Rafael J. Wysocki wrote:
> On Friday, May 4, 2018 8:50:52 PM CEST Oleksij Rempel wrote:
>> Hallo Andrew,
>> I need your ACK or NACK for this patch.
>>
>> This function is used to configure external PMIC to interpret
>> signal which will be triggered by pm_power_off as power o
On Mon, May 14, 2018 at 05:04:15AM +0100, Al Viro wrote:
> diff --git a/fs/sysfs/mount.c b/fs/sysfs/mount.c
> index b428d317ae92..92682fcc41f6 100644
> --- a/fs/sysfs/mount.c
> +++ b/fs/sysfs/mount.c
> @@ -25,7 +25,7 @@ static struct dentry *sysfs_mount(struct file_system_type
> *fs_type,
> {
>
From: Holger Hans Peter Freyther
perf probe --funcs will demangle C++ symbols by default but these
functions can not be used for listing sourcecode. Modify the scanner
to start searching for a line number only after a single ':'.
./perf probe -x ./cxx-example -L \
"std::vector >::at:1"
From: Holger Hans Peter Freyther
Using --funcs --no-demangle on a C++ binary does not list any of the C++
functions. Change the default filter to not exclude the Common C++ ABI
symbols.
$ ./perf probe -x ./cxx-example --funcs --no-demangle
...
_ZN9__gnu_cxx13new_allocatorIiEC1Ev
...
Signed-
From: Holger Hans Peter Freyther
If die_match_name does not match, attempt to demangle the linkage name.
To use the generic demangling API we require to have a struct dso. Store
it inside the debuginfo and pass it to the relevant callbacks.
./perf probe -x ./foo -L \
"std::vector >::at:2
From: Holger Hans Peter Freyther
Currently perf probe -x app --funcs will list and demangle C++ functions
but the other probe actions can't work with them. When asking probe to not
demangle it will not list any of the application symbols creating the
impression that there are no symbols at all.
From: Holger Hans Peter Freyther
If the linkage name looks like a common C++ ABI name use it instead of
the original function name. This makes adding a uprobe for a C++ symbol
possible.
./perf probe -x ./cxx-example "std::vector >::at"
Added new event:
probe_foo:_ZNSt6vectorIiSaIiEE2atEm (on
From: Holger Hans Peter Freyther
Update call sites with die_match_name to call matches_demangled as well.
This requires to pass the struct debuginfo/struct dso to the callbacks
and modifies the closure/void *data parameter. For most functions this
will change the parameter from struct probe_finde
From: Holger Hans Peter Freyther
The demangled C++ function name contains spaces and using the generic
argc_split would split the function in the middle. Create a separate
version that counts the number of opening and closing '<', '>' for
templated functions.
$ ./perf probe -x ./foo -V "std::vec
On Fri, Feb 09, 2018 at 12:00:01PM -0800, syzbot wrote:
> syzbot has found reproducer for the following crash on net-next commit
> 617aebe6a97efa539cc4b8a52adccd89596e6be0 (Sun Feb 4 00:25:42 2018 +)
> Merge tag 'usercopy-v4.16-rc1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
Al,
Are you ok with this approach to changing vfs timestamps?
Kees mentioned that he wants to merge a patch to pstore that changes
it to use timespec64 internally for 4.17:
https://lkml.org/lkml/2018/5/13/3
I'm not sure how we usually merge such flag day patches. Should this
be targeted for 4.17
On Mon, May 14, 2018 at 12:20:16PM +0900, Tetsuo Handa wrote:
> But there remains a refcount bug because deactivate_locked_super() from
> kernfs_mount_ns() triggers kobj_ns_drop() from sysfs_kill_sb() via
> sb->kill_sb() when kobj_ns_drop() is always called by sysfs_mount()
> if kernfs_mount_ns()
On 05/13/2018 08:15 PM, Joel Fernandes (Google) wrote:
> rcu_seq_snap may be tricky for someone looking at it for the first time.
> Lets document how it works with an example to make it easier.
>
> Signed-off-by: Joel Fernandes (Google)
> ---
> kernel/rcu/rcu.h | 24 +++-
> 1
Hi all,
Today's linux-next merge of the rcu tree got a conflict in:
drivers/nvme/host/core.c
between commit:
12d9f07022dc ("nvme: fix use-after-free in nvme_free_ns_head")
from Linus' tree and commit:
d9cf21bae6cf ("nvme: Avoid flush dependency in delete controller flow")
from the rcu
On Mon, Apr 23, 2018 at 08:46:26AM -0600, Jaegeuk Kim wrote:
> 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+
On 2018/5/10 21:20, Sahitya Tummala wrote:
> f2fs_ioc_shutdown() ioctl gets stuck in the below path
> when going down with full sync (F2FS_GOING_DOWN_FULLSYNC)
> option.
>
> __switch_to+0x90/0xc4
> percpu_down_write+0x8c/0xc0
> freeze_super+0xec/0x1e4
> freeze_bdev+0xc4/0xcc
> f2fs_ioctl+0xc0c/0x1
Hi,
On 05/12/2018 04:54 AM, Jacob Pan wrote:
> When Shared Virtual Address (SVA) is enabled for a guest OS via
> vIOMMU, we need to provide invalidation support at IOMMU API and driver
> level. This patch adds Intel VT-d specific function to implement
> iommu passdown invalidate API for shared vir
This reverts commit bc2bebe8de8ed4ba6482c9cc370b0dd72ffe8cd2.
The WoL feature is a must to pass Energy Star 6.1 and above,
the power consumption will be measured during S3 with WoL is enabled.
Reverting "alx: remove WoL support", and will try to fix the unintentional
wake up issue when WoL is ena
From: Finley Xiao
This driver is modified to support PX30 SoC.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
drivers/soc/rockchip/pm_domains.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/soc/rockchip/pm_domains.c
b/drivers/soc/rock
From: Finley Xiao
According to a description from TRM, add all the power domains.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
include/dt-bindings/power/px30-power.h | 32
1 file changed, 32 insertions(+)
create mode 100644 include/dt-bindings/p
From: Finley Xiao
Add binding documentation for the power domains
found on Rockchip PX30 SoCs.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
Documentation/devicetree/bindings/soc/rockchip/power_domain.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/device
This driver is modified to support RK3228 SoC.
Signed-off-by: Elaine Zhang
---
drivers/soc/rockchip/pm_domains.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/soc/rockchip/pm_domains.c
b/drivers/soc/rockchip/pm_domains.c
index 99a2dd8a7801..90dcd5e21a
Add binding documentation for the power domains
found on Rockchip RK3228 SoCs.
Signed-off-by: Elaine Zhang
---
Documentation/devicetree/bindings/soc/rockchip/power_domain.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
b
According to a description from TRM, add all the power domains.
Signed-off-by: Elaine Zhang
---
include/dt-bindings/power/rk3228-power.h | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 include/dt-bindings/power/rk3228-power.h
diff --git a/include/dt-binding
This driver is modified to support RK3128 SoC.
Signed-off-by: Elaine Zhang
---
drivers/soc/rockchip/pm_domains.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/soc/rockchip/pm_domains.c
b/drivers/soc/rockchip/pm_domains.c
index 01d4ba26a054..99a2dd8a7801 1
According to a description from TRM, add all the power domains.
Signed-off-by: Elaine Zhang
---
include/dt-bindings/power/rk3128-power.h | 28
1 file changed, 28 insertions(+)
create mode 100644 include/dt-bindings/power/rk3128-power.h
diff --git a/include/dt-bindi
Add binding documentation for the power domains
found on Rockchip RK3128 SoCs.
Signed-off-by: Elaine Zhang
---
Documentation/devicetree/bindings/soc/rockchip/power_domain.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
b
From: Finley Xiao
Solve the pd could only ever turn off but never turn them on again,
If the pd registers have the writemask bits.
Fix up the code error for commit:
commit 79bb17ce8edb3141339b5882e372d0ec7346217c
Author: Elaine Zhang
Date: Fri Dec 23 11:47:52 2016 +080
From: Caesar Wang
This driver is modified to support RK3036 SoC.
Signed-off-by: Caesar Wang
Signed-off-by: Elaine Zhang
---
drivers/soc/rockchip/pm_domains.c | 32
1 file changed, 32 insertions(+)
diff --git a/drivers/soc/rockchip/pm_domains.c
b/drivers/soc/
From: Caesar Wang
Add binding documentation for the power domains
found on Rockchip RK3036 SoCs.
Signed-off-by: Caesar Wang
Signed-off-by: Elaine Zhang
---
Documentation/devicetree/bindings/soc/rockchip/power_domain.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devi
From: Caesar Wang
According to a description from TRM, add all the power domains.
Signed-off-by: Caesar Wang
Signed-off-by: Elaine Zhang
---
include/dt-bindings/power/rk3036-power.h | 27 +++
1 file changed, 27 insertions(+)
create mode 100644 include/dt-bindings/powe
add power domain support for RK3036/RK3128/RK3228/PX30 Soc.
fix up the wrong value when set power domain up.
Change in V2:
Fix up the commit message description and Assign author.
Caesar Wang (3):
dt-bindings: power: add RK3036 SoCs header for power-domain
dt-bindings: add binding for rk3036
On Fri, 2018-05-11 at 16:47 +0530, Gautham R. Shenoy wrote:
> From: "Gautham R. Shenoy"
>
> Each of the SMT4 cores forming a fused-core are more or less
> independent units. Thus when multiple tasks are scheduled to run on
> the fused core, we get the best performance when the tasks are spread
>
Thanks for posting this... A couple of comments below.
On Fri, 2018-05-11 at 16:47 +0530, Gautham R. Shenoy wrote:
> From: "Gautham R. Shenoy"
>
> A pair of IBM POWER9 SMT4 cores can be fused together to form a
> big-core with 8 SMT threads. This can be discovered via the
> "ibm,thread-groups" C
Commit be4b8beed87d ("rcu: Move RCU's grace-period-change code to ->gp_seq")
removed the cpuend grace period trace point. This patch adds it back.
Signed-off-by: Joel Fernandes (Google)
---
kernel/rcu/tree.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/rcu/tre
The 'c' variable was used previously to store the grace period
that is being requested. However it is not very meaningful for
a code reader, this patch replaces it with gp_seq_start indicating that
this is the grace period that was requested. Also updating tracing with
the new name.
Just a clean u
rcu_seq_snap may be tricky for someone looking at it for the first time.
Lets document how it works with an example to make it easier.
Signed-off-by: Joel Fernandes (Google)
---
kernel/rcu/rcu.h | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/kernel/r
Recently we had a discussion about cond_resched unconditionally
recording a voluntary context switch [1].
Lets add a comment clarifying that how this API is to be used.
[1]
https://lkml.kernel.org/r/1526027434-21237-1-git-send-email-byungchul.p...@lge.com
Signed-off-by: Joel Fernandes (Google)
The funnel locking loop in rcu_start_this_gp uses rcu_root as a
temporary variable while walking the combining tree. This causes a
tiresome exercise of a code reader reminding themselves that rcu_root
may not be root. Lets just call it rcu_node, and then finally when
rcu_node is the rcu_root, lets
Currently the tree RCU clean up code records a CleanupMore trace event
even if the GP was already in progress. This makes CleanupMore show up
twice for no reason. Avoid it.
Signed-off-by: Joel Fernandes (Google)
---
kernel/rcu/tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
cpustart shows a stale gp_seq. This is because rdp->gp_seq is updated
only at the end of the __note_gp_changes function. For this reason, use
rnp->gp_seq instead. I believe we can't update rdp->gp_seq too early so
lets just use the gp_seq from rnp instead.
Signed-off-by: Joel Fernandes (Google)
-
In recent discussion [1], the check for whether a leaf believes RCU is
not idle, is being added back to funnel locking code, to avoid more
locking. In this we are marking the leaf node for a future grace-period
and bailing out since a GP is currently in progress. However the
tracepoint is missing.
Hi,
Here are some fixes, clean ups and some code comments changes mostly
for the new funnel locking, gp_seq changes and some tracing. Its based
on latest rcu/dev branch.
thanks,
- Joel
Joel Fernandes (Google) (8):
rcu: Add comment documenting how rcu_seq_snap works
rcu: Clarify usage of cond
On Mon, May 14, 2018 at 11:03:50AM +0800, Ian Kent wrote:
> The autofs module has long since been removed so there's no need to have
> two separate include files for autofs.
Umm... Why does fs/compat_ioctl.c need either include, actually?
> --- a/fs/compat_ioctl.c
> +++ b/fs/compat_ioctl.c
> @@
Copy source files from the autofs4 directory to the autofs directory.
Signed-off-by: Ian Kent
---
fs/autofs/autofs_i.h | 273 ++
fs/autofs/dev-ioctl.c | 761
fs/autofs/expire.c| 632 +
fs/autofs/init.c
Update naming within autofs source to be consistent by changing occurrences
of autofs4 to autofs.
Signed-off-by: Ian Kent
---
fs/autofs4/autofs_i.h | 88
fs/autofs4/dev-ioctl.c | 18 ++-
fs/autofs4/expire.c| 132 ---
fs/autofs4/init.c | 12 +-
Update Kconfig and add a depricated warning.
Signed-off-by: Ian Kent
---
fs/autofs4/Kconfig | 32 ++--
1 file changed, 22 insertions(+), 10 deletions(-)
diff --git a/fs/autofs4/Kconfig b/fs/autofs4/Kconfig
index 44727bf18297..53bc592a250d 100644
--- a/fs/autofs4/Kc
Finally remove autofs4 references in the filesystems documentation.
Signed-off-by: Ian Kent
---
Documentation/filesystems/00-INDEX |4 ++--
Documentation/filesystems/autofs-mount-control.txt |8
Documentation/filesystems/autofs.txt | 10 +-
Create Makefile and Kconfig for autofs module.
Signed-off-by: Ian Kent
---
fs/Kconfig |1 +
fs/Makefile|1 +
fs/autofs/Kconfig | 20
fs/autofs/Makefile |7 +++
4 files changed, 29 insertions(+)
create mode 100644 fs/autofs/Kconfig
create
There are two files in Documentation/filsystems that should now
use autofs rather than autofs4 in their names.
Signed-off-by: Ian Kent
---
Documentation/filesystems/autofs-mount-control.txt | 407 +++
Documentation/filesystems/autofs.txt | 529
..
Delete the now unused autofs4 module files.
Signed-off-by: Ian Kent
---
fs/autofs4/autofs_i.h | 273 --
fs/autofs4/dev-ioctl.c | 761 ---
fs/autofs4/expire.c| 632
fs/autofs4/init.c | 48 --
fs/autofs
Update the autofs entry in MAINTAINERS to reflect the rename of
autofs4 to autofs.
Signed-off-by: Ian Kent
---
MAINTAINERS |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 58b9861ccf99..6189ff91fda7 100644
--- a/MAINTAINERS
+++ b/MAINTAIN
The autofs module has long since been removed so there's no need to have
two separate include files for autofs.
Signed-off-by: Ian Kent
---
fs/autofs4/autofs_i.h |2
fs/compat_ioctl.c |1
include/uapi/linux/auto_fs.h | 169 ++---
On Fri, May 11, 2018 at 03:49:33PM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Allow writing to the trace_markers file initiate triggers defined in
> tracefs/ftrace/print/trigger file. This will allow of user space to trigger
> the same type of triggers (including histogram
Update Makefile to build from source in fs/autofs instead of
fs/autofs4.
Signed-off-by: Ian Kent
---
fs/autofs4/Makefile |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/autofs4/Makefile b/fs/autofs4/Makefile
index a811c1f7d9ab..417dd726d9ef 100644
--- a/fs/autofs4/Ma
On 2018-05-13 오전 2:26, Steven Rostedt wrote:
On Sat, 12 May 2018 07:41:19 -0700
"Paul E. McKenney" wrote:
Don't get me wrong, this discussion was quite useful to me. We probably
need to at least change the comments, and perhaps the code as well. But
I agree that we need input from Peter an
On 05/10/2018 01:06 AM, Jiri Slaby wrote:
> ---
> Documentation/asm-annotations.rst | 218
> arch/x86/include/asm/linkage.h| 10 +-
> include/linux/linkage.h | 257
> --
> 3 files changed, 475 insertions(+), 10 d
Sorry, messed up address for KVM mailing list. See message below.
On Sun, May 13, 2018 at 08:00:07PM -0700, Eric Biggers wrote:
> With CONFIG_KCOV=y and an AMD processor, running the following program crashes
> the kernel with no output (I'm testing in a VM, so it's using nested
> virtualization)
On 2018-05-12 오전 7:41, Joel Fernandes wrote:
On Fri, May 11, 2018 at 09:17:46AM -0700, Paul E. McKenney wrote:
On Fri, May 11, 2018 at 09:57:54PM +0900, Byungchul Park wrote:
Hello folks,
I think I wrote the title in a misleading way.
Please change the title to something else such as,
"rcu:
With CONFIG_KCOV=y and an AMD processor, running the following program crashes
the kernel with no output (I'm testing in a VM, so it's using nested
virtualization):
#include
#include
#include
int main()
{
int dev, vm, cpu;
Hi all,
After merging the block tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/memstick/core/mspro_block.c: In function 'mspro_block_init_disk':
drivers/memstick/core/mspro_block.c:1173:24: warning: unused variable 'host'
[-Wunused-variable]
struct memstick
On Wed, 2018-05-09 at 13:33 -0700, João Paulo Rechi Vita wrote:
> On Tue, May 8, 2018 at 1:37 AM, Pkshih wrote:
> > On Mon, 2018-05-07 at 14:49 -0700, João Paulo Rechi Vita wrote:
> >> On Tue, May 1, 2018 at 10:58 PM, Pkshih wrote:
> >> > On Wed, 2018-05-02 at 05:44 +, Pkshih wrote:
> >> >>
>
Hello,
On Sunday, 13 May 2018 15:57:55 EEST Niklas Söderlund wrote:
> On 2018-05-11 12:00:02 +0200, Jacopo Mondi wrote:
> > Describe HDMI input connected to VIN4 interface for R-Car D3 Draak
> > development board.
> >
> > Signed-off-by: Jacopo Mondi
> > ---
> >
> > arch/arm64/boot/dts/renesas/
On Sun, May 13, 2018 at 11:19:46AM +0900, Tetsuo Handa wrote:
> This is what I reported at
> https://groups.google.com/d/msg/syzkaller-bugs/ISOJlV2I2QM/qHslGMi3AwAJ .
>
> We are currently waiting for comments from Al Viro.
1) the damn thing is unusable without javashit. Which gets about
the sam
Hello,
On Friday, 11 May 2018 16:45:16 EEST Simon Horman wrote:
> On Fri, May 11, 2018 at 01:25:23PM +0200, Niklas Söderlund wrote:
> > Hi Jacopo,
> >
> > Thanks for your work.
> >
> > On 2018-05-11 12:00:01 +0200, Jacopo Mondi wrote:
> > > Describe VIN4 interface for R-Car D3 R8A77995 SoC.
> >
Hi Jacopo,
Thank you for the patch.
On Friday, 11 May 2018 13:00:00 EEST Jacopo Mondi wrote:
> Add compatible string for R-Car D3 R8A7795 to list of SoCs supported by
> rcar-vin driver.
>
> Signed-off-by: Jacopo Mondi
Reviewed-by: Laurent Pinchart
> ---
> Documentation/devicetree/bindings/m
On 5/11/2018 9:39 PM, Suzuki K Poulose Wrote:
Marc
Thanks for looping me in. Comments below.
On 03/05/18 03:02, Jia He wrote:
Hi Marc
Thanks for the review
On 5/2/2018 10:26 PM, Marc Zyngier Wrote:
[+ Suzuki]
On 02/05/18 08:08, Jia He wrote:
From: Jia He
In our armv8a server (QDF240
From: Hoeun Ryu
On some SoCs like i.MX6DL/QL have only one muxed SPI for multi-core system.
On the systems, a CPU can be interrupted by overflow irq but it is possible that
the overflow actually occurs on another CPU.
This patch broadcasts the irq using smp_call_function_single_async() so that
Thank you for the review.
I understand your NACK.
But I'd like to just fix the part of smp_call_function() in the next version.
You can simply ignore it.
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: Friday, May 11, 2018 7:39 PM
> To: ��ȣ��
> Cc: 'Hoeun
Hi,
On Sat, May 12, 2018 at 08:32:18PM +0200, Yann Ylavic wrote:
> On Fri, May 11, 2018 at 9:49 PM, Steven Rostedt wrote:
> []
> >
> > static int regex_match_front(char *str, struct regex *r, int len)
> > {
> > - if (len < r->len)
> > + if (len && len < r->len)
> > r
On Sun, May 13, 2018 at 12:51:20PM -0700, Joel Fernandes wrote:
> On Sun, May 13, 2018 at 12:09:06PM -0700, Paul E. McKenney wrote:
> > On Sun, May 13, 2018 at 09:49:53AM -0700, Joel Fernandes wrote:
> > > On Sun, May 13, 2018 at 08:38:42AM -0700, Paul E. McKenney wrote:
> > > > On Sat, May 12, 201
Hi,
On 05/12/2018 04:54 AM, Jacob Pan wrote:
> When Shared Virtual Memory is exposed to a guest via vIOMMU, extended
> IOTLB invalidation may be passed down from outside IOMMU subsystems.
> This patch adds invalidation functions that can be used for additional
> translation cache types.
>
> Signed
On Sun, 2018-05-13 at 23:48 +0300, Adrian Bunk wrote:
> On Wed, May 09, 2018 at 11:46:00PM +0100, Ben Hutchings wrote:
[...]
> > # Options for a new fix
> >
> > It is unlikely that any further fix will be forthcoming on the kernel
> > side, so I believe that we need to do one of:
> >
> > 1. Add e
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/lib/bpf/libbpf.c
between commit:
3597683c9da6 ("tools: bpf: handle NULL return in bpf_prog_load_xattr()")
from the bpf tree and commit:
17387dd5ac2c ("tools: bpf: don't complain about no kernel version for
n
Okay, I'll submit a new patch with some more description of why we
need this feature.
Thanks.
2018-05-10 20:34 GMT+08:00 Andrew Lunn :
> On Thu, May 10, 2018 at 01:58:24PM +0800, AceLan Kao wrote:
>> Hi Andrew,
>>
>> We have some machines using Qualcomm Atheros Killer E2400 Gigabit
>> Ethernet Con
On 2018年05月12日 01:39, Cong Wang wrote:
On Thu, May 10, 2018 at 7:49 PM, Jason Wang wrote:
static void __tun_detach(struct tun_file *tfile, bool clean)
{
struct tun_file *ntfile;
@@ -736,7 +727,8 @@ static void __tun_detach(struct tun_file *tfile, bool clean)
Hi,
On 05/12/2018 04:53 AM, Jacob Pan wrote:
> PFSID should be used in the invalidation descriptor for flushing
> device IOTLBs on SRIOV VFs.
This patch could be submitted separately.
>
> Signed-off-by: Jacob Pan
> ---
> drivers/iommu/dmar.c| 6 +++---
> drivers/iommu/intel-iommu.c |
On 05/13/2018 07:40 PM, Adam Ford wrote:
On Wed, May 9, 2018 at 12:25 PM, David Lechner wrote:
This series converts mach-davinci to use the common clock framework.
The series works like this, the first 3 patches fix some issues with the clock
drivers that have already been accepted into the ma
Hi,
On 05/12/2018 04:53 AM, Jacob Pan wrote:
> When SRIOV VF device IOTLB is invalidated, we need to provide
> the PF source ID such that IOMMU hardware can gauge the depth
> of invalidation queue which is shared among VFs. This is needed
> when device invalidation throttle (DIT) capability is sup
Prevent destruction of a uio_device while user space apps hold open
file descriptors to that device. Further, access to the 'info' member
of the struct uio_device is protected by spinlock. This is to ensure
stale pointers to data not under control of the UIO subsystem are not
dereferenced.
Signed-
Drive all return paths for uio_write() through a single block at the
end of the function.
Signed-off-by: Hamish Martin
Reviewed-by: Chris Packham
---
v2: no changes
drivers/uio/uio.c | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --git a/drivers/uio/uio
If a UIO device is removed while a user space app has an open file
descriptor to that device's /dev/uio* file, a kernel oops can occur when
the file descriptor is ultimately closed. The oops is triggered by
dereferencing either the uio_listener struct's 'dev' pointer, or at the
next level, when de
On 2018-05-11 8:24 PM, Rob Herring wrote:
On Thu, May 10, 2018 at 10:45 PM, Levin Du wrote:
On 2018-05-10 8:50 PM, Robin Murphy wrote:
On 10/05/18 10:16, d...@t-chip.com.cn wrote:
From: Levin Du
Adding a new gpio controller named "gpio-syscon10" to rk3328, providing
access to the pins defin
On 2018-05-11 8:22 PM, Rob Herring wrote:
On Thu, May 10, 2018 at 4:16 AM, wrote:
From: Levin Du
Adding a new gpio controller named "gpio-syscon10" to rk3328, providing
access to the pins defined in the syscon GRF_SOC_CON10.
Boards using these special pins to control regulators or LEDs, c
Hi, Andy Shevchenko
Yao is on maternity leave, and I'll take over the job after discussing with her.
> -邮件原件-
> 发件人: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> 发送时间: 2018年5月14日 7:16
> 收件人: chenyao (F)
> 抄送: songxiaowei ; Wangbinghui
> ; Lorenzo Pieralisi ;
> Bjorn Helgaas ; xuw
--
Hello
Greetings to you please i have a business proposal for you contact me
for more detailes asap thanks.
Best Regards,
Miss.Zeliha ömer faruk
Esentepe Mahallesi Büyükdere
Caddesi Kristal Kule Binasi
No:215
Sisli - Istanbul, Turkey
Theodore Y. Ts'o dixit:
>that problems helps most of our users, and we shouldn't let the
>perfect be the enemy of the good.
Agreed. Start small, then enhance one bootloader at a time.
Or boot protocol, I assume.
>Also note that the bootloader has depend on userspace to refresh the
>seed entropy,
Hi Stephen,
On Mon, May 14, 2018 at 09:21:58AM +1000, Stephen Rothwell wrote:
> Hi Shawn,
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> arch/arm/boot/dts/imx6dl-aristainetos_7.dtb: Warning (reg_format):
> /soc/ipu@240/port
Hi all,
After merging the vfs tree, today's linux-next build (arm
multi_v7_defconfig and others) produced this warning:
:1332:2: warning: #warning syscall io_pgetevents not implemented [-Wcpp]
Introduced by commit
7a074e96dee6 ("aio: implement io_pgetevents")
Just a heads up to all the other
101 - 200 of 438 matches
Mail list logo
