On Tue, 17 Oct 2017, Boris Ostrovsky wrote:
> On 10/06/2017 08:30 PM, Stefano Stabellini wrote:
> > Introduce a waitqueue to allow only one outstanding accept command at
> > any given time and to implement polling on the passive socket. Introduce
> > a flags field to keep track of in-flight accept
Provided you've tested this and the static_key guard stuff actually
works as intended, for the crypto/rng/siphash aspects:
Reviewed-by: Jason A. Donenfeld
The basic cpu stat is currently shown with "cpu." prefix in
cgroup.stat, and the same information is duplicated in cpu.stat when
cpu controller is enabled. This is ugly and not very scalable as we
want to expand the coverage of stat information which is always
available.
This patch makes cgroup
This is a test utility to verify ION buffer sharing in user space
between 2 independent processes.
It uses unix domain socket (with SCM_RIGHTS) as IPC to transfer an FD to
another process to share the same buffer.
This utility demonstrates how ION buffer sharing can be implemented between
two user
:
lkdtm, kprobes: Convert from jprobes to kprobes (2017-10-23 13:52:45 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-4.15-20171023
for you to fetch changes up to 65db92e0965ab56e8031d5c804f26d5be0e47047
From: Andi Kleen
Fix an incorrect description in the 'perf list' manpage. When a group
does not fit into the hardware it is partially scheduled, but does not
error out.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Link:
From: Arnaldo Carvalho de Melo
Out of print_binary() but receiving a fp pointer and expecting that the
printer be a fprintf like function, i.e. receive a FILE pointer and
return the number of characters printed.
Cc: Adrian Hunter
Cc: David Ahern
From: Jiri Olsa
There's no need for extra cpuid_parse arch callback, it can be handled
directly in init callback.
Adding the init function to x86 to cover the cpuid initialization.
Signed-off-by: Jiri Olsa
Cc: Andi Kleen
Cc: David
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/pmu-events/arch/x86/jaketown/jkt-metrics.json | 12
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
.../perf/pmu-events/arch/x86/ivytown/ivt-metrics.json | 18
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
.../pmu-events/arch/x86/skylakex/skx-metrics.json | 42
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/pmu-events/arch/x86/sandybridge/snb-metrics.json | 12
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
.../pmu-events/arch/x86/broadwell/bdw-metrics.json | 18
From: Christophe JAILLET
If the string passed in '--time' is invalid, or if failed to set
libtraceevent function resolver, we must do some cleanup before leaving.
As in the other error handling paths of this function.
Signed-off-by: Christophe JAILLET
From: Arnaldo Carvalho de Melo
To better organize the sources, and we may end up even using it
directly, without evlists and evsels.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/pmu-events/arch/x86/haswell/hsw-metrics.json | 16
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/pmu-events/arch/x86/haswellx/hsx-metrics.json | 16
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
.../pmu-events/arch/x86/broadwellx/bdx-metrics.json| 18
On Tue, Oct 17, 2017 at 06:49:58AM -0400, Rob Clark wrote:
> Now that drm/msm is converted over to use msm_get_clk() everywhere (that
> matters), which handles falling back to looking for a clock with the
> "_clk" suffix, we can remove "_clk" from the documentation so that new
> dts files added do
From: Lipeng
Date: Mon, 23 Oct 2017 19:51:00 +0800
> This patchset introduces various HNS3 bug fixes, optimizations and code
> improvements.
Series applied.
This corrects:
commit cce78da76601 ("watchdog: hpwdt: Add check for UEFI bits")
The test on HPE SMBIOS extension type 219 record "Misc Features"
bits for UEFI support is incorrect. The definition of the Misc Features
bits in the HPE SMBIOS OEM Extensions specification (and related
firmware) was
Do not claim the NMI (i.e. return NMI_DONE) if the source of
the NMI isn't the iLO watchdog or debug.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/watchdog/hpwdt.c
Changes v2
--
1. Re-order patches
2. Provide additional details for SMBIOS check patch.
Three short patches to the hpwdt driver.
1. An hpwdt SMBIOS check is incorrect due to a change in
the specification and firmware.
2. Do not claim NMI unless generated from iLO.
3. Add
Add support for WDIOC_GETPRETIMEOUT ioctl so that user applications
can determine when the NMI should arrive.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/watchdog/hpwdt.c
+ PM folks
Hi Jeffy,
It's probably good if you send the whole thing to linux-pm@ in the
future, if you're really trying to implement generic PCI/PM for device
tree systems.
On Thu, Oct 19, 2017 at 07:10:05PM +0800, Jeffy Chen wrote:
> Add support for PCIE_WAKE pin.
This is kind of an important
On 10/20/2017 05:54 PM, Gregory Fong wrote:
> On Thu, Oct 19, 2017 at 11:39 AM, Doug Berger wrote:
+static int brcmstb_gpio_resume(struct device *dev)
+{
+struct brcmstb_gpio_priv *priv = dev_get_drvdata(dev);
+struct brcmstb_gpio_bank *bank;
+
On Tue, 17 Oct 2017, Boris Ostrovsky wrote:
> > +static unsigned int pvcalls_front_poll_passive(struct file *file,
> > + struct pvcalls_bedata *bedata,
> > + struct sock_mapping *map,
> > +
On Mon, Oct 23, 2017 at 8:54 PM, Timur Tabi wrote:
> On 10/22/2017 11:56 PM, Amit Kucheria wrote:
>>
>>
>> "Most development boards and devices have one or more LEDs. It is
>> useful during debugging if they can be wired to show different
>> behaviours such as disk or cpu
We've been missing a goto to the unwind path...
Signed-off-by: Dmitry Torokhov
---
drivers/input/serio/ps2-gpio.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/serio/ps2-gpio.c b/drivers/input/serio/ps2-gpio.c
index b50e3817f3c4..c62cceb97bb1
From: Kan Liang
Add a Intel event file for perf.
Signed-off-by: Kan Liang
Acked-by: Andi Kleen
Cc: Jiri Olsa
Cc: Kan Liang
Cc: Sukadev Bhattiprolu
Link:
From: Arnaldo Carvalho de Melo
We've been mixing print() with fprintf() style printing for a while, but
now we need to use fprintf() like syntax uniformly as a preparatory
patch for supporting printing to different files, one per event.
Cc: Adrian Hunter
From: Christophe JAILLET
If the string passed in '--time' is invalid, we must do some cleanup
before leaving. As in the other error handling paths of this function.
Signed-off-by: Christophe JAILLET
Cc: Alexander Shishkin
From: Andi Kleen
Some of the metrics use an incorrect syntax for specifying the cmask for
an event. Convert to perf syntax so that they can be resolved.
Fixes metrics on Broadwell, SandyBridge.
Signed-off-by: Andi Kleen
Link:
From: Arnaldo Carvalho de Melo
When we use one of:
[acme@jouet linux]$ make help | grep perf
perf-tar-src-pkg- Build perf-4.14.0-rc3.tar source tarball
perf-targz-src-pkg - Build perf-4.14.0-rc3.tar.gz source tarball
perf-tarbz2-src-pkg - Build
From: Arnaldo Carvalho de Melo
We don't need perf.h, that is a kitchen sink, all we need is
perf_events.h for perf_ns_link_info, sys/types.h for pid_t and
linux/types.h for u64, list_head.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri
From: Arnaldo Carvalho de Melo
It becomes a perf_mmap method, "push", that build reads from a mmap and
"pushes" it to a consumer, that in the initial case, for 'perf record',
just writes it to the perf.data file descriptor, but may be used by
'top', etc.
Cc: Adrian Hunter
From: Arnaldo Carvalho de Melo
The previous prep patch was just to show exactly what changed in that
function, now its time to move that method and things only it uses to
the right place, mmap.[ch]
Cc: Adrian Hunter
Cc: David Ahern
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
.../pmu-events/arch/x86/skylake/skl-metrics.json | 20
From: Jiri Olsa
Otherwise we fail on virtual machines with no support for specific HW
events.
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link:
From: Andi Kleen
Signed-off-by: Andi Kleen
Link: http://lkml.kernel.org/r/20170914200748.ga13...@tassilo.jf.intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
.../pmu-events/arch/x86/ivybridge/ivb-metrics.json | 18
On Mon, Oct 23, 2017 at 3:04 PM, Guenter Roeck wrote:
> On Mon, Oct 23, 2017 at 10:01:42AM -0700, Andrey Smirnov wrote:
>> On Sat, Oct 21, 2017 at 9:47 AM, Guenter Roeck wrote:
>> > On Wed, Oct 18, 2017 at 10:01:35AM -0700, Andrey Smirnov wrote:
>> >> This
Currently we are leaking addresses from the kernel to user space. This
script as an attempt to find those leakages. Script parses `dmesg`
output and /proc and /sys files for suspicious entries.
Signed-off-by: Tobin C. Harding
---
My usual disclaimer; I am a long way from being a
On Tue, Oct 24, 2017 at 01:00:03AM +0200, Jason A. Donenfeld wrote:
> Provided you've tested this and the static_key guard stuff actually
> works as intended,
I tested by inserting a simple module that calls printf() with a bunch of
different specifiers. So it's tested but not stress tested. Some
Just something I noticed during my first 4.14 `make oldconfig`.
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 78cb2461012e..86dac3a573de 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1582,7 +1582,7 @@ config
On Mon, Oct 23, 2017 at 11:20:02AM -0700, Mike Kravetz wrote:
> On 10/23/2017 12:32 AM, Naoya Horiguchi wrote:
> > On Fri, Oct 20, 2017 at 10:49:46AM -0700, Mike Kravetz wrote:
> >> On 10/19/2017 07:30 PM, Naoya Horiguchi wrote:
> >>> On Thu, Oct 19, 2017 at 04:00:07PM -0700, Mike Kravetz wrote:
>
Currently, the existing qspinlock implementation will fallback to
test-and-set if the hypervisor has not set the PV_UNHALT flag.
This patch gives the opportunity to guest kernels to select
between test-and-set and the regular queueu fair lock implementation
based on the PV_DEDICATED KVM feature
on 2017/10/23 22:03, Tejun Heo wrote:
>>
>> And I think the following patch can solve the bug, right?
>>
>> diff --git a/kernel/workqueue_internal.h b/kernel/workqueue_internal.h
>> index 8635417..650680c 100644
>> --- a/kernel/workqueue_internal.h
>> +++ b/kernel/workqueue_internal.h
>> @@
Hi,
On 2017년 10월 18일 18:56, Marek Szyprowski wrote:
> Hi!
>
> This patchset enables proper detection and support for the following
> micro USB accessories: standard OTG cable (passive) and so called
> SmartDock (a Dock with OTG and MHL features).
>
> Tested on Exynos5433 TM2 board.
>
> Best
Hi Oliver
> -Original Message-
> From: Oliver Neukum [mailto:oneu...@suse.com]
> Sent: Monday, October 23, 2017 6:56 PM
> To: Ran Wang
> Cc: David S . Miller ; hayeswang
> ; linux-kernel@vger.kernel.org; linux-
>
On 2017年10月24日 00:19, Jens Axboe wrote:
> On 10/23/2017 10:27 AM, Kemi Wang wrote:
>> It's expensive to set buffer flags that are already set, because that
>> causes a costly cache line transition.
>>
>> A common case is setting the "verified" flag during ext4 writes.
>> This patch checks for
On 10/23/2017 02:26 PM, Vivien Didelot wrote:
> Hi Andrew,
>
> Andrew Lunn writes:
>
>> On Mon, Oct 23, 2017 at 02:17:29PM -0400, Vivien Didelot wrote:
>>> DSA has several bitmaps to store the type of ports: cpu_port_mask,
>>> dsa_port_mask and enabled_port_mask. But the code is
FYI, we noticed the following commit (built with gcc-4.9):
commit: 7d827b898c4556a2266e69ba9c6606e7b7342c71 ("printk: hash addresses
printed with %p")
url:
https://github.com/0day-ci/linux/commits/Tobin-C-Harding/printk-hash-addresses-printed-with-p/20171023-083947
in testcas
guard_bio_eod() needs to look at the partition capacity, not just the
capacity of the whole device, when determining if truncation is
necessary.
[ 60.268688] attempt to access beyond end of device
[ 60.268690] unknown-block(9,1): rw=0, want=67103509, limit=67103506
[ 60.268693]
It's expensive to set buffer flags that are already set, because that
causes a costly cache line transition.
A common case is setting the "verified" flag during ext4 writes.
This patch checks for the flag being set first.
With the AIM7/creat-clo benchmark testing on a 48G ramdisk based-on ext4
kemi writes:
>
> I'll see if I can find some
>> time to implement the above in a nice way.
>
> Agree. Maybe something like test_and_set_bit() would be more suitable.
test_and_set_bit is a very different operation for the CPU because
it is atomic for both. But we want the
+ linux-pm
On Thu, Oct 19, 2017 at 07:10:07PM +0800, Jeffy Chen wrote:
> Currently we are handling pcie wake irq in mrvl wifi driver.
> Move it to rockchip pcie driver for Gru boards.
It might be worth documenting one of the reasons for this patch, which
I'll comment on below:
> Signed-off-by:
Just gentle ping.
On Wed, 2017-09-27 at 18:44 +0800, Chen Zhong wrote:
> This patch add support to handle MediaTek PMIC MT6397/MT6323 key
> interrupts including pwrkey and homekey, also add setting for
> long press key shutdown behavior.
>
> Signed-off-by: Chen Zhong
>
On 2017年10月24日 09:21, Andi Kleen wrote:
> kemi writes:
>>
>> I'll see if I can find some
>>> time to implement the above in a nice way.
>>
>> Agree. Maybe something like test_and_set_bit() would be more suitable.
>
> test_and_set_bit is a very different operation for the
When queue_work() is used in irq handler, there is a potential
case that trigger NULL pointer dereference.
worker_thread()
|-spin_lock_irq()
|-process_one_work()
|-worker->current_pwq = pwq
|-spin_unlock_irq()
Hi,
On 24 October 2017 at 06:41, Rob Herring wrote:
> On Mon, Oct 16, 2017 at 08:03:14PM +0800, Baolin Wang wrote:
>> This patch adds the binding documentation for Spreadtrum SC27xx series
>> PMIC device.
>>
>> Signed-off-by: Baolin Wang
>> ---
>>
On Tue, Oct 10, 2017 at 08:49:13AM -0400, Boris Ostrovsky wrote:
>On 10/07/2017 06:36 PM, Levin, Alexander (Sasha Levin) wrote:
>> From: Jan Beulich
>>
>> [ Upstream commit 4fed1b125eb6252bde478665fc05d4819f774fa8 ]
>>
>> A negative return value indicates an error; in fact the
On 10/24/2017 02:59 AM, Doug Anderson wrote:
> Hi,
>
> On Tue, Oct 17, 2017 at 9:40 AM, Doug Anderson wrote:
>> ...
>> ...
>>> Yes, it looks hard to get concurrency right. I have a comment for your
>>> DRTO case(patch 5). Let's do some brainstorm there.
>>
>> Since your
Hi Al,
On Fri, 2017-10-20 at 21:11 +0100, Al Viro wrote:
> On Tue, Sep 26, 2017 at 04:10:14PM +0300, Tuomas Tynkkynen wrote:
> > Hi Al,
> >
> > On Wed, 2017-09-06 at 17:59 +0300, Tuomas Tynkkynen wrote:
> > > These two patches fix two hard-to-hit (but really annoying) bugs
> > > in
> > > 9p.
> >
On 10/22/2017 07:50 PM, Tetsuo Handa wrote:
Wei Wang wrote:
@@ -162,20 +160,20 @@ static unsigned fill_balloon(struct virtio_balloon *vb,
size_t num)
msleep(200);
break;
}
- set_page_pfns(vb, vb->pfns + vb->num_pfns,
Fix build problem:
>> WARNING: vmlinux.o(.text+0x4223a): Section mismatch in
reference from the function uv_tsc_check_sync() to the function
.init.text:uv_early_read_mmr() The function uv_tsc_check_sync()
references the function __init uv_early_read_mmr(). This is often
because
On 10/20/2017 05:03 AM, Thomas Gleixner wrote:
> On Thu, 19 Oct 2017, Prarit Bhargava wrote:
>> static void remove_siblinginfo(int cpu)
>> {
>> -int sibling;
>> +int phys_pkg_id, sibling;
>> struct cpuinfo_x86 *c = _data(cpu);
>>
>> for_each_cpu(sibling,
On 10/23/2017 09:10 AM, Borislav Petkov wrote:
On Mon, Oct 23, 2017 at 08:32:57AM -0500, Brijesh Singh wrote:
If both the command fails then we return status from the last command.
IIRC, in my previous patches I was returning status from sev_do_cmd()
instead of sev_platform_shutdown() but
On Mon, Oct 23, 2017 at 2:19 AM, Minas Harutyunyan
wrote:
> Could you please verify on your setup follow patches:
> 1. Vardan's patch.
> 2. Patch for TOUTCAL programming (new version see below).
> 4. Your patch 2/3 to avoid "Mode Mismatch" interrupts.
> 5. Your
Milian Wolff writes:
> bi = sample__resolve_bstack(sample, al);
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index 94d8f1ccedd9..e54741308e6c 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1824,6
Hello, Ingo,
[ Resend, this time remembering to CC LKML. ]
This pull request contains the following changes:
1. Documentation updates.
lkml.kernel.org/r/20171004212051.ga8...@linux.vnet.ibm.com
(But note that a number of these commits were redirected to
v4.14 on
Hello, Ingo,
This series is a first step towards making the core kernel no longer
need to consider DEC Alpha as a special case. This is accomplished
by two sets of patches, followed by a Coccinelle script:
1. Patches 1/19 through 15/19 in the following patches, which
change
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
Quoting "Gustavo A. R. Silva" :
In preparation to enabling -Wimplicit-fallthrough, this patchset aims
to mark switch cases where we are expecting to fall through.
In Kees Cook words:
"This is an unfortunate omission in the C language, and thankfully both
gcc and clang
On 16 October 2017 at 03:30, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
> instruct the PM core that it is desirable to leave the device in
> runtime suspend after
Mon, Oct 23, 2017 at 06:42:50PM +, Levin, Alexander (Sasha Levin) wrote:
> On Mon, Oct 23, 2017 at 11:39:22AM -0400, Tim Hansen wrote:
> >Mark hlist nodes in sk rcu iterator as protected by the rcu.
> >hlist_next_rcu accomplishes this and silences the warnings
> >sparse throws for
From: Markus Elfring
Date: Mon, 23 Oct 2017 21:27:30 +0200
Add a jump target so that a call of the function "mutex_unlock" is stored
only once at the end of this function implementation.
Replace three calls by goto statements.
This issue was detected by using the
On 10/23/2017 02:34 AM, Borislav Petkov wrote:
...
Just minor cleanups:
Thanks Boris, I have applied your cleanups.
-Brijesh
---
diff --git a/drivers/crypto/ccp/psp-dev.c b/drivers/crypto/ccp/psp-dev.c
index e9966d5fc6c4..f9a9a6e6ab99 100644
--- a/drivers/crypto/ccp/psp-dev.c
+++
On Mon, Oct 23, 2017 at 09:24:24PM +0200, Hans Verkuil wrote:
> Sounds good. That's the elevators on level LL by the way.
I'll be there, too!
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi
In the past we've avoided BUG_ON(X) where X might have side effects, on
the theory that it should actually be OK just to compile out BUG_ON()s.
Has that changed?
In any case, I don't find that this improves readability; dropping.
--b.
On Mon, Oct 23, 2017 at 01:16:35PM -0500, Gustavo A. R.
On 10/23, Chao Yu wrote:
> On 2017/10/19 10:15, Jaegeuk Kim wrote:
> > If some abnormal users try lots of atomic write operations, f2fs is able to
> > produce pinned pages in the main memory which affects system performance.
> > This patch limits that as 20% over total memory size, and if f2fs
From: Will Deacon
lockless_dereference is a nice idea, but its gained little traction in
kernel code since it's introduction three years ago. This is partly
because it's a pain to type, but also because using READ_ONCE instead
will work correctly on all architectures apart
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently harmful.
However, for some features it is
Hi,
On 10/20/2017 02:53 PM, Christ, Austin wrote:
Hey Jeremy,
Quick comment below.
On 10/12/2017 1:48 PM, Jeremy Linton wrote:
+static int topology_setup_acpi_cpu(struct acpi_table_header *table,
+ unsigned int cpu, int level)
+{
+ struct acpi_pptt_processor *cpu_node;
On Mon 2017-10-23 14:16:40, Linus Walleij wrote:
> On Mon, Oct 23, 2017 at 11:31 AM, Pavel Machek wrote:
>
> >> > Thinkpad X220... how do I tell if I was using them? I believe so,
> >> > because I uncovered bug in them before.
> >>
> >> You are certainly using bounce buffers. What
Mark hlist node in sk rcu iterator as protected by the rcu.
hlist_next_rcu accomplishes this and silences the warnings
sparse throws.
Found with make C=1 net/ipv4/udp.o on linux-next tag
next-20171009.
Signed-off-by: Tim Hansen
---
include/net/sock.h | 4 ++--
1 file
On Tue, Oct 17, 2017 at 11:06:22AM +0200, Maxime Ripard wrote:
> The TCON supports the LVDS interface to output to a panel or a bridge.
> Let's add support for it.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/sun4i/Makefile | 1 +-
>
Hi Mark,
[auto build test WARNING on tip/locking/core]
[also build test WARNING on v4.14-rc6 next-20171018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
- On Oct 23, 2017, at 7:30 PM, Ben Maurer bmau...@fb.com wrote:
>> if (!((long)ip - (long)start_ip <= (long)post_commit_offset))
>> return 1;
>
>> This introduces an issue here: if "ip" is lower than "start_ip", we
>> can incorrectly think we are in a critical section, when we are in
>>
Mr. Rostedt,
Just wanted to make sure there was nothing else you thought I should
modify for this patch. If there is, please let me know. I am eager to
fix anything that you think could make it better!
I hope that you had a great weekend!
Will
On Fri, Oct 13, 2017 at 2:40 PM, Will Hawkins
From: Will Deacon
linux/compiler.h is included indirectly by linux/types.h via
uapi/linux/types.h -> uapi/linux/posix_types.h -> linux/stddef.h
-> uapi/linux/stddef.h and is needed to provide a proper definition of
offsetof.
Unfortunately, compiler.h requires a definition
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently harmful.
However, for some features it is
From: Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently
On Mon, 2017-10-23 at 09:41 -0600, dann frazier wrote:
> (gdb) list *(sg_io+0x120)
> 0x084e71a8 is in sg_io (./include/linux/uaccess.h:113).
> 108 static inline unsigned long
> 109 _copy_from_user(void *to, const void __user *from, unsigned long n)
> 110 {
> 111 unsigned
From: Mark Rutland
workqueue: kill off ACCESS_ONCE()
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
1 - 100 of 1330 matches
Mail list logo