Given that READ_ONCE() now implies smp_read_barrier_depends(),
there is no need for the open-coded smp_read_barrier_depends() in
mn10300_serial_receive_interrupt() and mn10300_serial_poll_get_char().
This commit therefore removes them, but replaces them with comments
calling out that carrying depen
The comment in tracepoint_add_func() mentions smp_read_barrier_depends(),
whose use should be quite restricted. This commit updates the comment
to instead mention the smp_store_release() and rcu_dereference_sched()
that the current code actually uses.
Signed-off-by: Paul E. McKenney
Cc: Ingo Mol
Because READ_ONCE() now implies read_barrier_depends(), the
read_barrier_depends() in next_desc() is now redundant. This commit
therefore removes it and the related comments.
Signed-off-by: Paul E. McKenney
Cc: "Michael S. Tsirkin"
Cc: Jason Wang
Cc:
Cc:
Cc:
---
drivers/vhost/vhost.c | 7 +
READ_ONCE() now implies smp_read_barrier_depends(), which means that
the instances in arpt_do_table(), ipt_do_table(), and ip6t_do_table()
are now redundant. This commit removes them and adjusts the comments.
Signed-off-by: Paul E. McKenney
Cc: Pablo Neira Ayuso
Cc: Jozsef Kadlecsik
Cc: Floria
The smp_read_barrier_depends() does nothing at all except on DEC Alpha,
and no current DEC Alpha systems use Infiniband:
lkml.kernel.org/r/20171023085921.jwbntptn6ictbnvj@tower
This commit therefore makes Infiniband depend on !ALPHA and removes
the now-ineffective invocations of smp_read_
This is not required.
Looking with dmidecode, Glimmer reports:
...
BIOS Information
Vendor: coreboot
Version: Google_Glimmer.5216.198.19
...
Therefore, the first entry of cros_ec_lpc_dmi_table will match.
Gwendal.
On Fri, Dec 1, 2017 at 5:42 AM, Thierry Escande
wrote:
> This pat
Because READ_ONCE() now implies smp_read_barrier_depends(), the
smp_read_barrier_depends() in get_ksm_page() is now redundant.
This commit removes it and updates the comments.
Signed-off-by: Paul E. McKenney
Cc: Andrew Morton
Cc: Andrea Arcangeli
Cc: Minchan Kim
Cc: Michal Hocko
Cc: "Kirill A
Now that READ_ONCE() implies smp_read_barrier_depends(), the
get_xol_area() and get_trampoline_vaddr() no longer need their
smp_read_barrier_depends() calls, which this commit removes.
While we are here, convert the corresponding smp_wmb() to an
smp_store_release().
Signed-off-by: Paul E. McKenney
The code in __d_alloc() carefully orders filling in the NUL character
of the name (and the length, hash, and the name itself) with assigning
of the name itself. However, prepend_name() does not order the accesses
to the ->name and ->len fields, other than on TSO systems. This commit
therefore rep
Now that the associative-array library properly heads dependency chains,
the various smp_read_barrier_depends() calls in security/keys/keyring.c
are no longer needed. This commit therefore removes them.
Signed-off-by: Paul E. McKenney
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
C
This commit keeps only the historical and low-level discussion of
smp_read_barrier_depends().
Signed-off-by: Paul E. McKenney
---
Documentation/RCU/Design/Requirements/Requirements.html | 3 ++-
Documentation/RCU/rcu_dereference.txt | 6 +-
Documentation/RCU/whatisRCU.txt
Now that both smp_read_barrier_depends() and read_barrier_depends()
are being de-emphasized, warn if any are added.
Signed-off-by: Paul E. McKenney
Cc: Andy Whitcroft
Cc: Joe Perches
---
scripts/checkpatch.pl | 6 ++
1 file changed, 6 insertions(+)
diff --git a/scripts/checkpatch.pl b/scr
Now that smp_read_barrier_depends() has been de-emphasized, the less
said about it, the better.
Signed-off-by: Paul E. McKenney
Cc: Pablo Neira Ayuso
Cc: Jozsef Kadlecsik
Cc: Florian Westphal
Cc:
Cc:
---
include/linux/netfilter/nfnetlink.h | 3 +--
1 file changed, 1 insertion(+), 2 deletion
Now that smp_read_barrier_depends() is implied by READ_ONCE(), the several
smp_read_barrier_depends() calls may be removed from lib/assoc_array.c.
This commit makes this change and marks the READ_ONCE() calls that head
address dependencies.
Signed-off-by: Paul E. McKenney
Cc: Jonathan Corbet
Cc:
Now that smp_read_barrier_depends() has been de-emphasized, the less
said about it, the better.
Signed-off-by: Paul E. McKenney
Cc: Thomas Gleixner
Cc: Mark Rutland
Cc: Kate Stewart
Cc: Ingo Molnar
Cc: Philippe Ombredanne
Cc: Greg Kroah-Hartman
---
include/linux/genetlink.h | 3 +--
1 file
READ_ONCE() now implies smp_read_barrier_depends(), so this patch
removes the now-redundant smp_read_barrier_depends() from
raw_read_seqcount_latch().
Signed-off-by: Paul E. McKenney
Cc: Peter Zijlstra
Cc: Ingo Molnar
---
include/linux/seqlock.h | 3 +--
1 file changed, 1 insertion(+), 2 delet
> -Original Message-
> From: Geert Uytterhoeven [mailto:ge...@linux-m68k.org]
> Sent: Wednesday, November 29, 2017 2:48 AM
> To: Nikolova, Tatyana E ; Roland Dreier
> ; Jason Gunthorpe ; Doug
> Ledford
> Cc: Arnd Bergmann ; linux-r...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Geer
Checked against 3bf98755f9c670c5c10ca05cba22848d65117cb2 (CHROMIUM:
iio: accel: Add cros_ec_accel_legacy driver)
Fixup f2b141a242e59017dbc774dc916748670a41da0b (FIXUP: CHROMIUM: iio:
accel: Add cros_ec_accel_legacy driver) is required for devices with
secondary Embedded Controllers.
Gwendal.
On
On 12/01/2017 11:49 AM, Philippe Ombredanne wrote:
David, Greg,
On Fri, Dec 1, 2017 at 6:42 PM, David Daney wrote:
On 11/30/2017 11:53 PM, Philippe Ombredanne wrote:
[...]
--- /dev/null
+++ b/arch/mips/cavium-octeon/resource-mgr.c
@@ -0,0 +1,371 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+
On Fri, Dec 01, 2017 at 02:17:19PM -0500, Sean Paul wrote:
> On Fri, Dec 1, 2017 at 2:06 PM, Ville Syrjälä
> wrote:
> > On Fri, Dec 01, 2017 at 12:20:28PM -0500, Sean Paul wrote:
> >> Once the Aksv is available in the PCH, we need to get it on the wire to
> >> the receiver via DDC. The hardware do
Hello!
This series contains torture-test updates:
1. Suppress CPU stall warnings during shutdown ftrace dump.
2. Prepare scripting for shift from %p to %pK because NULL-pointers
printout changes.
3. Change printk() %p to %pK.
4. Reduce #ifdefs for preempt_schedule()
From: SeongJae Park
Both the 'kvm.sh' and 'kvm-test-1-run.sh' scripts log messages by printing
the message to 'stdout' and then also printing it into the log file.
Generation of the message thus occurs twice, once for 'stdout' and once
for the log file. Moreover, many of the messages contain 'da
The purpose of torture_runnable is to allow rcutorture and locktorture
to be started and stopped via sysfs when they are built into the kernel
(as in not compiled as loadable modules). However, the 0444 permissions
for both instances of torture_runnable prevent this use case from ever
being put in
From: SeongJae Park
The kvm-recheck-(lock|rcu|rcuperf).sh scripts check whether the
user-specified results directory exists. If not, it prints out error
message that says the specified directory is unreadable. To make the
message more precise, this commit adds a readability check.
Fixes: 2193e
From: SeongJae Park
The '--qemu-args' option's help text is wrongly copied from '--qemu-cmd'
option and its argument type description message format is inconsistent
with other arguments. This commit fixes the usage and type messages to
be consistent with others.
Fixes: e9ce640001c6 ("rcutorture
There is some confusion about where patches to kernel/torture.c
and kernel/locking/locktorture.c should be sent. This commit
therefore updates MAINTAINERS appropriately.
Reported-by: Peter Zijlstra
Signed-off-by: Paul E. McKenney
Acked-by: Peter Zijlstra (Intel)
---
MAINTAINERS | 22 +
Distros have been shipping with CONFIG_STRICT_DEVMEM=y for years now. It
is probably time to flip this default for x86 and arm64.
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 947d3e2
On Thu, Nov 30, 2017 at 6:14 PM, wrote:
> +&ecspi3 {
> + fsl,spi-num-chipselects = <1>;
Please remove this property. It is no longer used.
> + dvicape@39 {
> + compatible = "sil164_simple";
This compatible string does not exist.
> +&lcdif {
> + pinctrl-name
From: SeongJae Park
The 'configinit.sh' script checks the format of optional argument for the
build directory, printing an error message if the format is not valid.
However, the error message uses the wrong variable, indicating an empty
string even though the user entered a non-empty (but erroneo
This commit adds a torture_preempt_schedule() that is nothingness
in !PREEMPT builds and is preempt_schedule() otherwise. Then
torture_preempt_schedule() is used to eliminate several ugly #ifdefs,
both in rcutorture and in locktorture.
Signed-off-by: Paul E. McKenney
---
include/linux/torture.h
From: SeongJae Park
The variable `alldone` is defined but not used within an awk script.
This commit therefore removes it.
Fixes:53954671033d ("rcutorture: Do better bin packing")
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/kvm.sh |
On Thu, Nov 30, 2017 at 6:14 PM, wrote:
> From: Tyler Baker
>
> Build the imx7d-sbc-iot-imx7 device tree blob.
>
> Signed-off-by: Tyler Baker
> ---
> arch/arm/boot/dts/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> in
From: SeongJae Park
Inclusions of 'functions.sh' from 'kvm-test-1-run.sh' and
'kvm-recheck*.sh' use its absolute path. Because the directory containing
'functions.sh' is already in PATH, the full path is unnecessary. This
commit therefore simplifies the inclusions to use the short relative path
On Wed, Nov 29, 2017 at 11:56:05AM -0600, Julia Cartwright wrote:
> Hey Thomas, Peter-
>
> Gratian and I have been debugging into a nasty and difficult race w/
> futexes seemingly the culprit. The original symptom we were seeing
> was a seemingly spurious -EDEADLK from a futex(LOCK_PI) operation.
Signed-off-by: Paul E. McKenney
---
kernel/torture.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/torture.c b/kernel/torture.c
index 572576ad9f58..37b94012a3f8 100644
--- a/kernel/torture.c
+++ b/kernel/torture.c
@@ -576,7 +576,7 @@ void stutter_wait(const char *ti
The stutter_wait() function repeatedly fetched stutter_pause_test, and
should really just fetch it once on each pass. The races should be
harmless, but why have the races? Also, the whole point of the value
"2" for stutter_pause_test is to get everyone to start at very nearly
the same time, but t
From: Davidlohr Bueso
We should account for nreader threads, not writers in this
callback. Could even trigger a div by 0 if the user explicitly
disables writers.
Signed-off-by: Davidlohr Bueso
Signed-off-by: Paul E. McKenney
---
kernel/locking/locktorture.c | 2 +-
1 file changed, 1 insertion
On Fri, Dec 01, 2017 at 09:52:27PM +0200, Andy Shevchenko wrote:
> On Tue, Nov 28, 2017 at 9:41 PM, Michel Dänzer wrote:
> > On 2017-11-28 08:30 PM, Andy Shevchenko wrote:
> >> On Tue, Nov 28, 2017 at 8:06 PM, Michel Dänzer wrote:
> >>> On 2017-11-28 05:57 PM, Darren Hart wrote:
>
> Merged
On 12/01/2017 07:28 PM, Linus Torvalds wrote:
> [ Sorry for HTML email crud - traveling and on mobile right now ]
>
> On Nov 30, 2017 23:54, "Al Viro" wrote:
>
> Would cause problems for tracepoints in there, though. And that, BTW,
> is precisely why I don't want tracepoints in core VFS, TYVM -
On Thu, Nov 30, 2017 at 6:14 PM, wrote:
> From: Tyler Baker
>
> Add device tree nodes for the USB hub, and USB OTG. i2c2 on this
> platform supports low state retention power state so lets use it.
>
> Signed-off-by: Tyler Baker
> ---
> arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 36
> ++
On Fri, 2017-12-01 at 11:51 -0800, Paul E. McKenney wrote:
> Now that both smp_read_barrier_depends() and read_barrier_depends()
> are being de-emphasized, warn if any are added.
This would also warn on existing files when run
with ./scripts/checkpatch.pl -f
Do you want it to check new patches o
From: Davidlohr Bueso
Things can explode for locktorture if the user does combinations
of nwriters_stress=0 nreaders_stress=0. Fix this by not assuming
we always want to torture writer threads.
Reported-by: Jeremy Linton
Signed-off-by: Davidlohr Bueso
Signed-off-by: Paul E. McKenney
Reviewed-
The torture_shutdown() function directly invokes ftrace_dump(), which
can result in RCU CPU stall warnings when the ftrace buffer is large,
which it usually is. This commit therefore invoks rcu_ftrace_dump()
in place of ftrace_dump(), suppressing RCU CPU stall warnings during
this time.
Signed-of
This commit changes the %p printk() in rcutorture to %pK. This could
be considered irrelevant, given that any user able to start rcutorture
could inflict far heavier damage on the system, but it doesn't hurt to
change it and doing so avoids script-generated noise.
Reported-by: Tobin C. Harding
S
This commit attempts to make a very rare rcutorture failure happen
more often by increasing the fraction of RCU-preempt read-side critical
sections that are preempted.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/rcutorture.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
From: Tommi Rantala
Date: Wed, 29 Nov 2017 12:48:42 +0200
> Remove the second tipc_rcv() call in tipc_udp_recv(). We have just
> checked that the bearer is not up, and calling tipc_rcv() with a bearer
> that is not up leads to a TIPC div-by-zero crash in
> tipc_node_calculate_timer(). The crash i
From: SeongJae Park
The 'kvm.sh' rcutorture script requires that it be invoked from the top
of Linux-kernel source tree. It is just a subtle restriction, but users
using it for the first time could forget the restriction and be confused.
Moreover, it makes commands a little longer, which can be
Because %p prints "(null)" and %pK prints "" or (on
32-bit systems) "", this commit adjusts torture-test scripting
accordingly.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/parse-torture.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
Hi Geert,
On 11/30/2017 02:36 PM, Geert Uytterhoeven wrote:
> Fixes: 7df4f9a9f0667ee6 ("leds: ledtrig-activity: Add a system activity LED
> trigger")
> Signed-off-by: Geert Uytterhoeven
> ---
> drivers/leds/trigger/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
From: SeongJae Park
The 'config2frag.sh' script is not used, so this commit removes it.
Fixes: c87b9c601ac8 ("rcutorture: Add KVM-based test framework")
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
.../selftests/rcutorture/bin/config2frag.sh| 25 --
From: SeongJae Park
Check for build-directory existence and write permissions are provided in
both 'kvm-test-1-run.sh' an 'kvm-build.sh'. Because the 'kvm-build.sh'
is dependent on 'kvm-test-1-run.sh' ('kvm-build.sh' uses variables that
defined from its caller.), these checks are unnecessarily d
On Thu, Nov 30, 2017 at 6:14 PM, wrote:
> From: Tyler Baker
>
> Enable dma on all SPI and UART interfaces.
You only touched SPI ports, not the UART.
On Thu, Nov 30, 2017 at 6:14 PM, wrote:
> From: Tyler Baker
>
> In the i.MX7D the PCIe PHY can use either externel oscillator or
> internal PLL as a reference clock source.
> Add support for the PHY Reference Clock source including
> device tree property phy-ref-clk.
> External oscillator is use
Hi guys,
On Fri, Dec 01, 2017 at 09:14:43PM +0100, Jacek Anaszewski wrote:
> Hi Geert,
>
> On 11/30/2017 02:36 PM, Geert Uytterhoeven wrote:
> > Fixes: 7df4f9a9f0667ee6 ("leds: ledtrig-activity: Add a system activity LED
> > trigger")
> > Signed-off-by: Geert Uytterhoeven
> > ---
> > drivers/l
Commit 1d3e53e8624a ("x86/entry/64: Refactor IRQ stacks and make
them NMI-safe") added DEBUG_ENTRY_ASSERT_IRQS_OFF macro that acceses
eflags using 'pushfq' instruction when testing for IF bit. On PV Xen
guests looking at IF flag directly will always see it set, resulting
in 'ud2'.
Introduce SAVE_F
If fpga_mgr_register() fails, a clock is left undisabled.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/fpga/socfpga-a10.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/fpga/socfpga-a10.c b/drive
The Subject could be improved to something like: Convert from fbdev to
drm bindings
On Thu, Nov 30, 2017 at 11:02 AM, Marco Franchi wrote:
> It is preferred to use the panel compatible string rather than passing
> the LCD timming in the device tree.
Typo: timing
>
> So pass the "sii,43wvf1g" co
From: Scott Branden
Date: Thu, 30 Nov 2017 11:35:58 -0800
> Add support to reset appplication processors inside SmartNICs by
> defining new ETH_RESET_AP bit.
>
> And use new ETH_RESET_AP bit in bnxt ethernet driver.
Looks good, series applied, thanks!
On 11/29/2017 04:36 AM, Elena Reshetova wrote:
> Some functions from refcount_t API provide different
> memory ordering guarantees that their atomic counterparts.
> This adds a document outlining these differences.
>
> Signed-off-by: Elena Reshetova
> ---
> Documentation/core-api/index.rst
On 12/01/2017 08:56 AM, Lee Jones wrote:
> On Thu, 30 Nov 2017, Jacek Anaszewski wrote:
>
>> On 11/30/2017 09:31 AM, Lee Jones wrote:
>>> On Thu, 30 Nov 2017, Lee Jones wrote:
>>>
On Wed, 29 Nov 2017, Bjorn Andersson wrote:
> The pointer returned by of_device_get_match_data() doesn't
David,
On Fri, Dec 1, 2017 at 9:01 PM, David Daney wrote:
> On 12/01/2017 11:49 AM, Philippe Ombredanne wrote:
>>
>> David, Greg,
>>
>> On Fri, Dec 1, 2017 at 6:42 PM, David Daney
>> wrote:
>>>
>>> On 11/30/2017 11:53 PM, Philippe Ombredanne wrote:
>>
>> [...]
>>
>> --- /dev/null
>>
On 12/01/2017 12:10 PM, Kees Cook wrote:
Distros have been shipping with CONFIG_STRICT_DEVMEM=y for years now. It
is probably time to flip this default for x86 and arm64.
With my Fedora hat on,
Acked-by: Laura Abbott
Signed-off-by: Kees Cook
---
lib/Kconfig.debug | 2 +-
1 file changed,
On 12/01/2017 06:39 PM, Al Viro wrote:
[...]
> If that does not scream "wrong or missing primitive", I don't know what would.
> You want something along the lines of "create a filesystem object at given
> location, calling this function with this argument for actual object
> creation"?
> Fair enou
Hi Linus,
Here are some bug fixes for 4.15-rc2.
--D
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.15-fixes-4
for
renameat has been deprecated in favor of renameat2 for new ports. This
allows the audit tests to build on RISC-V.
Reviewed-by: Christoph Hellwig
CC: Olof Johansson
Signed-off-by: Palmer Dabbelt
---
include/asm-generic/audit_dir_write.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/inc
On 12/01/2017 12:41 PM, Philippe Ombredanne wrote:
David,
On Fri, Dec 1, 2017 at 9:01 PM, David Daney wrote:
On 12/01/2017 11:49 AM, Philippe Ombredanne wrote:
David, Greg,
On Fri, Dec 1, 2017 at 6:42 PM, David Daney
wrote:
On 11/30/2017 11:53 PM, Philippe Ombredanne wrote:
[...]
---
On 12/1/2017 12:34 AM, Johannes Thumshirn wrote:
James Smart writes:
On 11/30/2017 7:12 AM, Johannes Thumshirn wrote:
One major usability difference between NVMf RDMA and FC is resolving
the default host transport address in RDMA. This is perfectly doable
in FC as well, as we already have all
On Wednesday 29 November 2017 17:33:58 Masaki Ota wrote:
> From: Masaki Ota
> - The issue is that Thinkpad L570 TrackStick does not work. Because the main
> interface of Thinkpad L570 device is SMBus, so ALPS overlooked PS2 interface
> Firmware setting of TrackStick. The detail is that TrackStic
On Fri, Dec 01, 2017 at 12:47:24PM +0100, Jan Kara wrote:
> On Thu 30-11-17 20:05:48, Luis R. Rodriguez wrote:
> > On Thu, Nov 30, 2017 at 06:13:10PM +0100, Jan Kara wrote:
> > > ... I dislike the _by_user() suffix as there may be different places that
> > > call freeze_super() (e.g. device mapper
As done for /proc/kcore in
commit df04abfd181a ("fs/proc/kcore.c: Add bounce buffer for ktext data")
this adds a bounce buffer when reading memory via /dev/mem. This
is needed to allow kernel text memory to be read out when built with
CONFIG_HARDENED_USERCOPY (which refuses to read out kernel t
>>> [ 30.811750] CR2: fdeb2f98 CR3: 000423fae001 CR4:
>>> 001607e0
>>> [ 30.819712] Call Trace:
>>> [ 30.822442]
>>> [ 30.825170] trace_hardirqs_on_thunk+0x1c/0x1c
>> ...
>>> [ 31.000571] R13: 0050 R14: 0076 R15:
>>> 7f59f76f2d60
>>> [
On Wed, Nov 29, 2017 at 10:39:19AM -0800, vcap...@pengaru.com wrote:
> Hello,
>
> Recently I noticed substantial audio dropouts when listening to MP3s in
> `cmus` while doing big and churny `git checkout` commands in my linux git
> tree.
>
> It's not something I've done much of over the last coup
From: Sukadev Bhattiprolu
Date: Tue, 28 Nov 2017 13:39:43 -0600
Subject: [PATCH 1/1]: powerpc: block interrupts when updating TIDR
clear_thread_tidr() is called in interrupt context as a part of delayed
put of the task structure (i.e as a part of timer interrupt). To prevent
a deadlock, block int
On 12/01/2017 04:48 AM, Al Viro wrote:
> On Fri, Dec 01, 2017 at 01:33:04AM +, Al Viro wrote:
>
>> Use of file descriptors should be limited to "got a number from userland,
>> convert to struct file *" on the way in and "install struct file * into
>> descriptor table and return the descriptor
clang's AddressSanitizer implementation adds redzones on either side of
alloca()ed buffers. These redzones are 32-byte aligned and at least 32
bytes long.
__asan_alloca_poison() is passed the size and address of the allocated
buffer, *excluding* the redzones on either side. The left redzone will
[PATCH v3 1/5] kasan: add compiler support for clang
Moved to start of patchset
[PATCH v3 2/5] kasan/Makefile: Support LLVM style asan parameters.
Using Andrey's version.
Fixed up bug with testing CFLAGS_KASAN_SHADOW
Modifed to not output gcc style options on llvm
[PATCH v3 3/5] kasan: su
From: Grygorii Strashko
Date: Thu, 30 Nov 2017 18:21:09 -0600
> This is set of non critical clean ups and optimizations for TI
> CPSW and ALE drivers.
>
> Rebased on top on net-next.
Series applied, thank you.
For now we can hard-code ASAN ABI level 5, since historical clang builds
can't build the kernel anyway. We also need to emulate gcc's
__SANITIZE_ADDRESS__ flag, or memset() calls won't be instrumented.
Signed-off-by: Greg Hackmann
Signed-off-by: Paul Lawrence
---
include/linux/compiler-clang.h
Signed-off-by: Greg Hackmann
Signed-off-by: Paul Lawrence
---
lib/test_kasan.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/lib/test_kasan.c b/lib/test_kasan.c
index ef1a3ac1397e..2724f86c4cef 100644
--- a/lib/test_kasan.c
+++ b/lib/test_kasan.c
@@ -472,6 +472,26 @
From: Alexander Potapenko
As a code-size optimization, LLVM builds since r279383 may
bulk-manipulate the shadow region when (un)poisoning large memory
blocks. This requires new callbacks that simply do an uninstrumented
memset().
This fixes linking the Clang-built kernel when using KASAN.
Sign
LLVM doesn't understand GCC-style paramters ("--param asan-foo=bar"),
thus we currently we don't use inline/globals/stack instrumentation
when building the kernel with clang.
Add support for LLVM-style parameters ("-mllvm -asan-foo=bar") to
enable all KASAN features.
Signed-off-by: Andrey Ryabini
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git
tags/riscv-for-linus-4.15-rc2_cleanups
for you to fetch c
Hi,
On Wed, Nov 29, 2017 at 6:27 PM, Chris Zhong wrote:
> Hi Doug
>
> Thank you for mentioning this patch.
>
> I think the focus of the discussion is: can we put the grf control bit to
> dts.
>
> The RK3399 has 2 Type-C phy, but only one DP controller, this "uphy_dp_sel"
>
> can help to switch th
On Fri, Dec 01, 2017 at 12:14:17PM -0800, Joe Perches wrote:
> On Fri, 2017-12-01 at 11:51 -0800, Paul E. McKenney wrote:
> > Now that both smp_read_barrier_depends() and read_barrier_depends()
> > are being de-emphasized, warn if any are added.
>
> This would also warn on existing files when run
On Fri, Dec 01, 2017 at 12:11:15PM -0800, Darren Hart wrote:
> On Wed, Nov 29, 2017 at 11:56:05AM -0600, Julia Cartwright wrote:
> > Hey Thomas, Peter-
> >
> > Gratian and I have been debugging into a nasty and difficult race w/
> > futexes seemingly the culprit. The original symptom we were seei
On Fri, Dec 01, 2017 at 02:05:44PM -0500, Jeff Layton wrote:
> On Thu, 2017-11-30 at 17:41 +0100, Jiri Kosina wrote:
> > On Fri, 1 Dec 2017, Yu Chen wrote:
> >
> > > BTW, is nfs able to be included in this set? I also encountered a
> > > freeze() failure due to nfs access during that stage recent
Hi Linus,
The following changes since commit fcfa447062b2061e11f68b846d61cbfe60d0d604:
NFS: Revert "NFS: Move the flock open mode check into nfs_flock()"
(2017-11-17 16:43:52 -0500)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.1
Rework set_parent core function so it can be called when the prepare lock
is already held by the caller.
This rework is done to ease the integration of the "protected" clock
functionality.
Acked-by: Linus Walleij
Tested-by: Quentin Schulz
Tested-by: Maxime Ripard
Acked-by: Michael Turquette
S
The current implementation of clk_core_set_rate_nolock() bails out early
if the requested rate is exactly the same as the one set. It should bail
out if the request would not result in a rate a change. This is important
when the rate is not exactly what is requested, which is fairly common
with PLL
The patch adds clk_core_protect and clk_core_unprotect to the internal
CCF API. These functions allow to set a new constraint along the clock
tree to prevent any change, even indirect, which may result in rate
change or glitch.
Tested-by: Maxime Ripard
Acked-by: Michael Turquette
Signed-off-by:
Using clock rate protection, we can now enforce CLK_SET_RATE_GATE along the
clock tree
Acked-by: Linus Walleij
Tested-by: Quentin Schulz
Tested-by: Maxime Ripard
Acked-by: Michael Turquette
Signed-off-by: Jerome Brunet
---
drivers/clk/clk.c | 16 +---
1 file changed, 13 insertion
clk_summary debugfs entry was already well over the traditional 80
characters per line limit but it grew even larger with the addition of
clock protection.
clock enable_cnt prepare_cnt protect_cnt
rate accuracy phase
Calling clk_core_set_rate() with core->req_rate is basically a no-op
because of the early bail-out mechanism.
This may leave the clock in inconsistent state if the rate is out the
requested range. Calling clk_core_set_rate() with the closest rate
limit could solve the problem but:
- The underlying
Using clock rate protection, we can now provide a way for clock consumer
to claim exclusive control over the rate of a producer
So far, rate change operations have been a "last write wins" affair. This
changes allows drivers to explicitly protect against this behavior, if
required.
Of course, if
Create a core function for set_phase, as it is done for set_rate and
set_parent.
This rework is done to ease the integration of "protected" clock
functionality.
Acked-by: Linus Walleij
Tested-by: Quentin Schulz
Tested-by: Maxime Ripard
Acked-by: Michael Turquette
Signed-off-by: Jerome Brunet
This Patchset is related the RFC [0] and the discussion around
CLK_SET_RATE_GATE available here [1]
This patchset introduce clock protection to the CCF core. This can then
be used for:
* Provide a way for a consumer to claim exclusivity over the rate control
of a provider. Some clock consumers
Rework the way the callbacks round_rate() and determine_rate() are called.
The goal is to do this at a single point and make it easier to add
conditions before calling them.
Because of this factorization, rate returned by determine_rate() is also
checked against the min and max rate values
This r
ENOSYS is special and should only be used for incorrect syscall number.
It does not seem to be the case here.
Reported by checkpatch.pl while working on clock protection.
Acked-by: Linus Walleij
Tested-by: Quentin Schulz
Tested-by: Maxime Ripard
Acked-by: Michael Turquette
Signed-off-by: Jero
On 12/1/2017 9:54 AM, Tony Lindgren wrote:
* Dave Gerlach [171130 22:58]:
This is a resend of v5 of this series found here [1]. It introduces
relocatable PM handlers for the emif that are copied to sram and
run from there during low power mode entry.
The patches still have the previous ACKs bu
Am Freitag, 1. Dezember 2017, 13:42:46 CET schrieb Doug Anderson:
> Hi,
>
> On Wed, Nov 29, 2017 at 6:27 PM, Chris Zhong wrote:
> > Hi Doug
> >
> > Thank you for mentioning this patch.
> >
> > I think the focus of the discussion is: can we put the grf control bit to
> > dts.
> >
> > The RK3399 ha
601 - 700 of 834 matches
Mail list logo
