From: Thomas Gleixner
The tasklet is used to defer the execution of snd_pcm_period_elapsed() to
the softirq context. Using the HRTIMER_MODE_SOFT mode invokes the timer
callback in softirq context as well which renders the tasklet useless.
[o-takashi: avoid stall due to a
hrtimer callback functions are always executed in hard interrupt
context. Users of hrtimer which need their timer function to be executed
in soft interrupt context, make use of tasklets to get the proper context.
Add additional hrtimer clock bases for timers which must expire in softirq
context,
Jan,
Please see below for my comments.
On 11/9/2017 2:49 AM, Jan Beulich wrote:
On 09.11.17 at 00:06, wrote:
--- a/drivers/xen/xen-pciback/pci_stub.c
+++ b/drivers/xen/xen-pciback/pci_stub.c
@@ -244,6 +244,91 @@ struct pci_dev *pcistub_get_pci_dev(struct
On Wed, Nov 29, 2017 at 10:02:40AM +0100, Corentin Labbe wrote:
> On Tue, Nov 28, 2017 at 06:38:26PM +0100, Andrew Lunn wrote:
> > On Tue, Nov 28, 2017 at 05:48:22PM +0100, Corentin Labbe wrote:
> > > The driver expect "allwinner,leds-active-low" to be in PHY node, but
> > > the binding doc expect
Ideally we'd create the key through a macro at the real callers and
pass it all the way down. This would give us better coverage for cases
where a bunch of kthreads are created for the same thing.
But this gets the job done meanwhile and unblocks our CI. Refining
later on is always possible.
v2:
Hi all,
-rc1 set our CI on fire with a pile of issues that cross-release
highlights. The two patches in this series get things back into working
order on our side, so we pulled them into our local branches to unblock CI
and drm/i915.
But they're ofc far from polished, so pls look at this more as
The hrtimer_cpu_base struct has the CONFIG_HIGH_RES_TIMERS conditional
struct member hres_active. All related functions to this member are
conditional as well.
There is no functional change, when the hres_active member is
unconditional with all related functions and is set to zero during
From: Thomas Gleixner
The members migrate_enable and nohz_active in the timer/hrtimer per CPU
bases have been introduced to avoid accessing global variables for these
decisions.
Still that results in a (cache hot) load and conditional branch, which can
be avoided by using
From: Thomas Gleixner
The protection of a hrtimer which runs its callback against migration to a
different CPU has nothing to do with hard interrupt context.
The protection against migration of a hrtimer running the expiry callback
is the pointer in the cpu_base which holds
There are quite some places in the kernel which use a combination of
hrtimers and tasklets to make use of the precise expiry of hrtimers, which
schedule a tasklet to bring the actual function into softirq context.
This was introduced when the previous hrtimer softirq code was
removed. That code
>>> On 29.11.17 at 16:37, wrote:
> On 11/9/2017 2:49 AM, Jan Beulich wrote:
> On 09.11.17 at 00:06, wrote:
>>> +static int pcistub_reset_dev(struct pci_dev *dev)
>>> +{
>>> + struct xen_pcibk_dev_data *dev_data;
>>> + bool slot = false,
On Wed, Nov 29, 2017 at 11:46 PM, Andrew Lunn wrote:
> Hi ChenYu
>
>> It worked at one point. During some previous iteration, they lit up as
>> they were supposed to.
>
> For a released version of the kernel? Or during development work? If
> they did work, but broken, it would be
On Wed, Nov 29, 2017 at 4:00 PM, Souptick Joarder wrote:
> On Wed, Nov 29, 2017 at 6:25 AM, David Daney wrote:
>> From: Carlos Munoz
>>
>> The Cavium OCTEON cn78xx and cn73xx SoCs have network packet I/O
>> hardware that is
On 11/29/2017 06:00 PM, Joshua Abraham wrote:
Signed-off-by: Joshua Abraham
This patch fixes the issue:
CHECK: usleep_range is preferred over udelay; see
Documentation/timers/timers-howto.txt
---
drivers/staging/nvec/nvec.c | 2 +-
1 file changed, 1 insertion(+),
Op 28-11-17 om 16:13 schreef Thomas Voegtle:
> On Tue, 28 Nov 2017, Daniel Vetter wrote:
>
>> On Tue, Nov 28, 2017 at 12:16:03PM +0100, Maarten Lankhorst wrote:
>>> Some drivers like i915 start with crtc's enabled, but with deferred
>>> fbcon setup they were no longer disabled as part of fbdev
On Mon, Nov 27, 2017 at 11:22:28PM +0100, Maciej S. Szmigiero wrote:
> UDOO board has a possibility to disable most of imx6 SoC power supplies via
> "EN_5V" signal, which is connected to "NANDF_D4" pad.
>
> This reduces current consumption after shutdown from ~350 mA to ~40 mA and
> prevents a
On Tue, Nov 28, 2017 at 03:49:24PM -0200, Otavio Salvador wrote:
> This adds the partitions definition for the SPI NOR to provide
> backward compatibility with the documented[1] layout used with
> Boundary Devices BSP.
>
> 1. https://boundarydevices.com/boot-flash-access-linux/
>
> It exports to
On 29/11/17 14:47, Juergen Gross wrote:
> On 29/11/17 15:44, Paolo Bonzini wrote:
>> On 29/11/2017 15:25, Boris Ostrovsky wrote:
>> zeropage is x86/Linux-specific so we'd need some sort of firmware (like
>> grub) between a hypervisor and Linux to convert hvm_start_info to
>>
From: Benjamin Gaignard
Date: Wed, 29 Nov 2017 15:20:00 +0100
> Uniformize STMicroelectronics copyrights header
>
> Signed-off-by: Benjamin Gaignard
Applied.
On 11/29/2017 03:27 PM, Benjamin Gaignard wrote:
Uniformize STMicroelectronics copyrights header
Signed-off-by: Benjamin Gaignard
CC: Yannick Fertre
---
drivers/watchdog/stm32_iwdg.c | 4 ++--
1 file changed, 2 insertions(+), 2
Hi, Marc:
2017-11-28 17:37 GMT+08:00 Marc Zyngier :
> On 27/11/17 12:28, Greentime Hu wrote:
>> +static void ativic32_ack_irq(struct irq_data *data)
>> +{
>> + __nds32__mtsr_dsb(1 << data->hwirq, NDS32_SR_INT_PEND2);
>
> Consider writing (1 << data->hwirq) as
Fix a commit d614fd58a283 ("mips/ptrace: Preserve previous registers for
short regset write") bug and allow the last register requested with a
ptrace(2) PTRACE_SETREGSET call to be partially written if supplied this
way by the caller, like with other register sets.
Cc: sta...@vger.kernel.org #
> From: Linus Torvalds
> Sent: Wed Nov 29 01:17:05 CET 2017
> To: Geo Kozey
> Subject: Re: [kernel-hardening] Re: [PATCH v5 next 5/5] net: modules: use
> request_module_cap() to load 'netdev-%s' modules
>
>
> On Tue, Nov 28, 2017 at 3:51
As of today we assumed that "machine_desc->init_per_cpu" calls
are only usable on SMP systems when we want to run some piece of
code on early boot for each and every core, I guess assumption was
we have "machine_desc->init_early" for single-core cases where
the one and only master core can do all
Repeat terminal ACKs and now terminal ACKs are now generated from the
connection event processor rather from call handling as this allows us to
discard client call structures as soon as possible and free up the channel
for a follow on call.
However, in ACKs so generated, the additional
From: Thomas Gleixner
The tx_done_tasklet tasklet is used in invoke the hrtimer
(mvpp2_hr_timer_cb) in softirq context. This can be also achieved without
the tasklet but with HRTIMER_MODE_SOFT as hrtimer mode.
Signed-off-by: Thomas Gleixner
/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-fixes
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-fixes-20171129
David
---
David Howells (2):
rxrpc: Clean up whitespace
rxrpc: Fix ACK generation from the connection event processor
Clean up some whitespace from rxrpc.
Signed-off-by: David Howells
---
net/rxrpc/call_event.c |2 +-
net/rxrpc/conn_object.c |2 +-
net/rxrpc/input.c |4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/rxrpc/call_event.c
hrtimer_force_reprogram() needs to be available unconditionally for softirq
based hrtimers. Move the function and all required struct members out of
the CONFIG_HIGH_RES_TIMERS #ifdef.
There is no functional change because hrtimer_force_reprogram() is only
invoked when hrtimer_cpu_base.hres_active
On Wed, Nov 29, 2017 at 12:21:41AM +0200, Jarkko Sakkinen wrote:
> On Tue, Nov 28, 2017 at 02:00:03PM -0800, Sean Christopherson wrote:
> > What about SGX_LC_ENABLE? The title in the MSR section of the SDM is
> > "SGX Launch Control Enable", and it's more consistent with the other
> > bits
__run_hrtimer() is called with the hrtimer_cpu_base.lock held and
interrupts disabled. Before invoking the timer callback the base lock is
dropped, but interrupts stay disabled.
The upcoming support for softirq based hrtimers requires that interrupts
are enabled before the timer callback is
Preparatory patch for softirq based hrtimers to avoid code duplication. No
functional change.
Signed-off-by: Anna-Maria Gleixner
---
kernel/time/hrtimer.c | 20
1 file changed, 16 insertions(+), 4 deletions(-)
diff --git a/kernel/time/hrtimer.c
Preparatory patch for softirq based hrtimers to avoid code duplication. No
functional change.
Signed-off-by: Anna-Maria Gleixner
---
kernel/time/hrtimer.c | 44
1 file changed, 24 insertions(+), 20 deletions(-)
diff --git
The hrtimer_start[_range_ns]() starts a timer reliable on this CPU only
when HRTIMER_MODE_PINNED is set. Furthermore the HRTIMER_MODE_PINNED mode
is not considered, when a hrtimer is initialized.
Signed-off-by: Anna-Maria Gleixner
---
include/linux/hrtimer.h | 6 +++---
The sequence '/**' marks the start of a struct description. Add the
missing second asterisk. While at it adapt the ordering of the struct
members to the struct definition and document the purpose of
expires_next more precisely.
Signed-off-by: Anna-Maria Gleixner
---
So far only CLOCK_MONOTONIC and CLOCK_REALTIME were taken into account as
well as HRTIMER_MODE_ABS/REL in hrtimer_init tracepoint. The query for
detecting timer mode ABS or REL is not valid, since the introduction of
HRTIMER_MODE_PINNED.
HRTIMER_MODE_PINNED is not evaluated in hrtimer_init()
POSIX specification defines, that relative CLOCK_REALTIME timers are not
affected by clock modifications. Those timers have to use CLOCK_MONOTONIC
to ensure POSIX compliance.
The introduction of the additional mode HRTIMER_MODE_PINNED broke this
requirement for pinned timers. There is no user
schedule_hrtimeout_range_clock() uses an integer for the clock id
instead of the predefined type "clockid_t". The ID of the clock is
indicated in hrtimer code as clock_id. Therefore change the name of
the variable as well to make it consistent.
While at it, clean up the description for the
On Wed, Nov 29, 2017 at 04:37:12PM +0100, Andrew Lunn wrote:
> On Wed, Nov 29, 2017 at 10:02:40AM +0100, Corentin Labbe wrote:
> > On Tue, Nov 28, 2017 at 06:38:26PM +0100, Andrew Lunn wrote:
> > > On Tue, Nov 28, 2017 at 05:48:22PM +0100, Corentin Labbe wrote:
> > > > The driver expect
On Thu, Nov 23, 2017 at 12:08 AM, Hans Verkuil wrote:
> On 11/23/2017 05:27 AM, Tim Harvey wrote:
>> On Mon, Nov 20, 2017 at 7:39 AM, Hans Verkuil wrote:
>>> Hi Tim,
>>>
>>> Some more review comments:
>>>
>>> On 11/09/2017 07:45 PM, Tim Harvey wrote:
Hi Adrian,
On 29 November 2017 at 14:40, Adrian Hunter wrote:
> Hi
>
> Here is V15 of the hardware command queue patches without the software
> command queue patches, now using blk-mq and now with blk-mq support for
> non-CQE I/O.
I have applied patches 1->19 for next.
On Wed 29-11-17 14:42:51, Michal Hocko wrote:
> On Wed 29-11-17 22:34:50, Tetsuo Handa wrote:
> > register_shrinker() might return -ENOMEM error since Linux 3.12.
> > Call panic() as with other failure checks in this function if
> > register_shrinker() failed.
> >
> > Signed-off-by: Tetsuo Handa
On Wed, Nov 29, 2017 at 11:56:57AM +0100, Rasmus Villemoes wrote:
> On 2017-11-28 23:14, Guenter Roeck wrote:
> > On Tue, Nov 28, 2017 at 11:35:49AM +0100, Rasmus Villemoes wrote:
> >>
> >> The unit is milliseconds rather than seconds because that covers more
> >> use cases. For example, one can
On Thu, Nov 23, 2017 at 12:25 AM, Sakari Ailus wrote:
> On Wed, Nov 22, 2017 at 08:37:04PM -0800, Tim Harvey wrote:
>> On Tue, Nov 21, 2017 at 11:36 PM, Sakari Ailus wrote:
>> > Hi Tim,
>> >
>> > On Thu, Nov 09, 2017 at 10:45:33AM -0800, Tim Harvey
On Tue, Nov 28, 2017 at 10:56:31PM +0100, Jernej Škrabec wrote:
> Hi!
>
> Dne torek, 28. november 2017 ob 09:58:26 CET je Maxime Ripard napisal(a):
> > On Mon, Nov 27, 2017 at 05:07:04PM +0100, Jernej Škrabec wrote:
> > > Hi Maxime,
> > >
> > > Dne ponedeljek, 27. november 2017 ob 16:41:29 CET
On Wed, Nov 29, 2017 at 09:50:14AM -0500, David Miller wrote:
> From: Alan Cox
> Date: Wed, 29 Nov 2017 13:46:12 +
>
> > I really don't care what the module loading rules end up with and
> > whether we add CAP_SYS_YET_ANOTHER_MEANINGLESS_FLAG but what is
> >
On Wed, Nov 29, 2017 at 03:27:53PM +0100, Benjamin Gaignard wrote:
> Uniformize STMicroelectronics copyrights header
>
> Signed-off-by: Benjamin Gaignard
> CC: Yannick Fertre
> ---
> drivers/watchdog/stm32_iwdg.c | 4 ++--
> 1 file changed, 2
From: Theodore Ts'o
Date: Wed, 29 Nov 2017 10:54:06 -0500
> On Wed, Nov 29, 2017 at 09:50:14AM -0500, David Miller wrote:
>> From: Alan Cox
>> Date: Wed, 29 Nov 2017 13:46:12 +
>>
>> > I really don't care what the module loading rules end up with
On Wed, 29 Nov 2017, Thomas Gleixner wrote:
> On Wed, 29 Nov 2017, Peter Zijlstra wrote:
>
> > Here's more patches, includes the TLB invalidate rework.
> >
> > Has not actually been tested on a INVPCID machine yet, but does seem to
> > work fine on my IVB-EP (which is PCID only).
>
> I've
On Wed, Nov 29, 2017 at 12:12 PM, Mark Brown wrote:
> A frequent source of build problems is poor handling of optional PM
> support, almost all development is done with the PM options enabled
> but they can be turned off. Currently few if any of the build test
> services do
From: Michal Hocko
MAP_FIXED is used quite often to enforce mapping at the particular
range. The main problem of this flag is, however, that it is inherently
dangerous because it unmaps existing mappings covered by the requested
range. This can cause silent memory corruptions.
Hi,
I am resending with RFC dropped and ask for inclusion. There haven't
been any fundamental objections for the RFC [1]. I have also prepared
a man page patch which is 0/3 of this series.
This has started as a follow up discussion [2][3] resulting in the
runtime failure caused by hardening patch
From: Geert Uytterhoeven
Date: Wed, 29 Nov 2017 11:01:09 +0100
> On 64-bit (e.g. powerpc64/allmodconfig):
>
> drivers/net/ethernet/xilinx/ll_temac_main.c: In function
> 'temac_start_xmit_done':
> drivers/net/ethernet/xilinx/ll_temac_main.c:633:22: warning: cast
On Tue, 2017-11-28 at 13:36 +0100, Peter Zijlstra wrote:
> On Tue, Nov 28, 2017 at 06:59:01PM +0800, Zhang Rui wrote:
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > My Surface Pro 4 is unable to boot after 4.12. The symptom
> > > > > > is
> >
> > yes. Tried 4.4 distro and 4.12 vanilla
On 29/11/2017 15:25, Boris Ostrovsky wrote:
zeropage is x86/Linux-specific so we'd need some sort of firmware (like
grub) between a hypervisor and Linux to convert hvm_start_info to
bootparams.
>>> qemu?
>
> I think KVM folks didn't want to do this. I can't find the thread but I
>
Uniformize STMicroelectronics copyrights header
Add SPDX identifier
Signed-off-by: Benjamin Gaignard
---
arch/arm/mach-stm32/board-dt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-stm32/board-dt.c b/arch/arm/mach-stm32/board-dt.c
index
Acked-by: Gabriel Somlo
On Tue, Nov 28, 2017 at 10:40:27PM +0100, Vasyl Gomonovych wrote:
> Fix ptr_ret.cocci warnings:
> drivers/firmware/efi/efi.c:610:8-14: WARNING: PTR_ERR_OR_ZERO can be used
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Generated by:
Quoting Thomas Gleixner :
So I have to ask WHY this information was not in the changelog of the patch
in question:
1) How it works
2) Why comments have been chosen over macros
I will add this info and send the patch again.
In preparation to enabling
On Wed, Nov 29, 2017 at 08:05:47PM +0800, Jin Yao wrote:
> v3:
> ---
> Update according to Jiri's comments. The major modifications are:
>
> 1. Fix the crash issue when performing the git bisect.
>Move the removing of runtime_saved_values to the switching point
>(perf util: Remove a set
Fix a commit 72b22bbad1e7 ("MIPS: Don't assume 64-bit FP registers for
FP regset") public API regression, then activated by commit 1db1af84d6df
("MIPS: Basic MSA context switching support"), that caused the FCSR
register not to be read or written for CONFIG_CPU_HAS_MSA kernel
configurations
Complement commit d614fd58a283 ("mips/ptrace: Preserve previous
registers for short regset write") and like with the PTRACE_GETREGSET
ptrace(2) request also apply a BUILD_BUG_ON check for the size of the
`elf_fpreg_t' type in the PTRACE_SETREGSET request handler.
Cc: sta...@vger.kernel.org #
"/**" identifies a kerneldoc comment, so avoid using it for comments that
don't conform to kerneldoc syntax. Without this patch, kerneldoc throws
errors when building the kernel with W=1.
Cc: David Airlie
Cc: Thomas Hellstrom
Signed-off-by: Will Deacon
On 2017-11-29 15:42, Michal Hocko wrote:
>
> The first patch introduced MAP_FIXED_SAFE which enforces the given
> address but unlike MAP_FIXED it fails with ENOMEM if the given range
> conflicts with an existing one.
[s/ENOMEM/EEXIST/, as it seems you also did in the actual patch and
changelog]
"/**" identifies a kerneldoc comment, so avoid using it for comments that
don't conform to kerneldoc syntax. Without this patch, kerneldoc throws
errors when building the kernel with W=1.
Cc: Arend van Spriel
Cc: Franky Lin
Signed-off-by:
My bisect scripts starting running into build failures when trying to
compile 4.15-rc1 with the builds failing with things like:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c:2078: error: Cannot
parse struct or union!
The line in question is actually just a #define, but after some
Are you planning on sending a v9 with the discussed changes? afaict:
- Drop last two patches
- Fix tearing (WRITE/READ_ONCE())
- Reduce barrier usage for dlock_lists_empty() -- which I'll be sending
you shortly.
Thanks,
Davidlohr
On Tue, 31 Oct 2017, Waiman Long wrote:
v7->v8:
- Integrate
From: Thomas Gleixner
There are no more tasklet_hrtimer users of this interface.
Remove it.
Signed-off-by: Thomas Gleixner
Signed-off-by: Anna-Maria Gleixner
---
include/linux/interrupt.h | 25 ---
From: Srividya Desireddy
Date: Wed, 29 Nov 2017 20:23:15 +0530
Subject: [PATCH] zswap: Update with same-value filled page feature
Updated zswap document with details on same-value filled
pages identification feature.
The usage of zswap.same_filled_pages_enabled module
From: Gustavo A. R. Silva
Values assigned to both variable resend_at and ack_at are overwritten
before they can be used.
The correct fix here is to add 'now' to the previously computed value in
resend_at and ack_at.
Addresses-Coverity-ID: 1462262
Addresses-Coverity-ID:
Hi Maxime,
>
> So there's a couple of issues with those patches (the pull request
> itself is fine though :))
>
> I'll try to break them down as much as possible.
>
> A) If you want to have proper commit logs, you will usually do two
>things: first create a commit title, which is what
The softirq based hrtimer can utilize most of the existing hrtimers
functions, but need to operate on a different data set.
Add an active_mask argument to various functions so the hard and soft bases
can be selected. Fixup the existing callers and hand in the ACTIVE_HARD
mask.
Signed-off-by:
On Tue, 31 Oct 2017, Waiman Long wrote:
Linked list is used everywhere in the Linux kernel. However, if many
threads are trying to add or delete entries into the same linked list,
it can create a performance bottleneck.
This patch introduces a new list APIs that provide a set of distributed
All prerequisites to handle hrtimers for expiry in either hard or soft
interrupt context are in place.
Add the missing bit in hrtimer_init() which associates the timer to the
hard or the soft irq clock base.
Signed-off-by: Anna-Maria Gleixner
---
kernel/time/hrtimer.c
hrtimer_cpu_base.expires_next is used to cache the next event armed in the
timer hardware. The value is used to check whether an hrtimer can be
enqueued remotely. If the new hrtimer is expiring before expires_next, then
remote enqueue is not possible as the remote hrtimer hardware cannot be
The pointer to the currently running timer is stored in hrtimer_cpu_base
before the base lock is dropped and the callback is invoked.
This results in two levels of indirections and the upcoming support for
softirq based hrtimer requires splitting the "running" storage into soft
and hard irq
hrtimer_reprogram() is conditionally invoked from hrtimer_start_range_ns()
when hrtimer_cpu_base.hres_active is true.
In the !hres_active case there is a special condition for the nohz_active
case:
If the newly enqueued timer expires before the first expiring timer on a
remote CPU then the
There is a small overlapping conflict to net/rxrpc/call_object.c, it should
be easy to resolve. In your tree there was a setup_timer() --> timer_setup()
conversion, and in my tree there are new lines adding a lockdep_set_class()
call right beforehand.
1) The forcedeth conversion from pci_*()
hrtimer_cpu_base.next_timer stores the pointer to the next expiring timer
in a cpu base.
This pointer cannot be dereferenced and is solely used to check whether a
hrtimer which is removed is the hrtimer which is the first to expire in the
CPU base. If this is the case, then the timer hardware
hrtimer_reprogram() needs to be available unconditionally for softirq based
hrtimers. Move the function and all required struct members out of the
CONFIG_HIGH_RES_TIMERS #ifdef.
There is no functional change because hrtimer_reprogram() is only invoked
when hrtimer_cpu_base.hres_active is true.
__hrtimer_hres_active() is now available unconditionally. Replace the
direct access to hrtimer_cpu_base.hres_active.
No functional change.
Signed-off-by: Anna-Maria Gleixner
---
kernel/time/hrtimer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Hi ChenYu
> It worked at one point. During some previous iteration, they lit up as
> they were supposed to.
For a released version of the kernel? Or during development work? If
they did work, but broken, it would be good to know which commit broke
it. We can then add a fixes: tag to the patch
This commit adds a driver for the Virtual Box Guest PCI device used in
Virtual Box virtual machines. Enabling this driver will add support for
Virtual Box Guest integration features such as copy-and-paste, seamless
mode and OpenGL pass-through.
This driver also offers vboxguest IPC functionality
This commits adds a header describing the hardware interface for the
Virtual Box Guest PCI device used in Virtual Box virtual machines and
utility functions for talking to the Virtual Box hypervisor over this
interface.
These utility functions will used both by the vboxguest driver for the
PCI
On Wed, Nov 29, 2017 at 09:19:29AM +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 28 Nov 2017 14:41:14 -0600, Bjorn Helgaas wrote:
>
> > > + * struct cdns_pcie_rc_data - hardware specific data
> >
> > "cdns" is a weird abbreviation for "Cadence", since "Cadence" doesn't
> > contain an
This commit adds the headers describing the ioctl API for the
/dev/vboxguest device used by the Virtual Box Guest Additions
in Virtual Box virtual machines.
The driver providing the /dev/vboxguest device will allow Virtual Box
Guest Additions features such as copy-and-paste, seamless mode and
On Mon 27-11-17 12:33:41, Michal Hocko wrote:
> On Mon 27-11-17 19:09:24, JianKang Chen wrote:
> > From: Jiankang Chen
> >
> > __get_free_pages will return an virtual address,
> > but it is not just 32-bit address, for example a 64-bit system.
> > And this comment
On 11/28/2017 11:24 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.3 release.
> There are 193 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
> On Nov 29, 2017, at 4:47 AM, Peter Zijlstra wrote:
>
>> On Wed, Nov 29, 2017 at 08:09:51AM +0100, Ingo Molnar wrote:
>> diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S
>> index f81d50d7ceac..c0b52df8ee4f 100644
>> --- a/arch/x86/entry/entry_64.S
>>
> From: Theodore Ts'o
> Sent: Wed Nov 29 00:49:20 CET 2017
> Subject: Re: [kernel-hardening] Re: [PATCH v5 next 5/5] net: modules: use
> request_module_cap() to load 'netdev-%s' modules
>
> OK, but if the goal is to protect users who are running distro
> kernels, then a kernel
On 29/11/2017 15:47, Juergen Gross wrote:
> On 29/11/17 15:44, Paolo Bonzini wrote:
>> In either case, you would have a new option ROM. It could either be
>> very simple and similar to multiboot.S, or it could be larger and do the
>> same task as xen-pvh.S and enlighten_pvh.c (then get the
On Thu, Nov 30, 2017 at 01:43:05AM +1100, Stephen Rothwell wrote:
> Hi Lee,
>
> Commits
>
> 5f6bf7b9f96e ("mfd: twl4030-audio: Fix sibling-node lookup")
> 38c021ee7af3 ("mfd: twl6040: Fix child-node lookup")
>
> are missing a Signed-off-by from their author.
Ouch, sorry about that.
Lee,
On 11/29/2017 03:55 PM, Benjamin Gaignard wrote:
Uniformize STMicroelectronics copyrights header
Add SPDX identifier
Signed-off-by: Benjamin Gaignard
---
arch/arm/mach-stm32/board-dt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 11/29/2017 03:25 PM, Benjamin Gaignard wrote:
Uniformize STMicroelectronics copyrights header
Signed-off-by: Benjamin Gaignard
---
drivers/pinctrl/stm32/pinctrl-stm32.c | 1 +
drivers/pinctrl/stm32/pinctrl-stm32.h | 1 +
On 11/29/2017 03:22 PM, Benjamin Gaignard wrote:
Uniformize STMicroelectronics copyrights header
Signed-off-by: Benjamin Gaignard
---
drivers/irqchip/irq-stm32-exti.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/irqchip/irq-stm32-exti.c
On 11/29/2017 03:26 PM, Benjamin Gaignard wrote:
Uniformize STMicroelectronics copyrights header
Signed-off-by: Benjamin Gaignard
CC: Amelie Delaunay
---
drivers/rtc/rtc-stm32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
For the Micron SPI NOR, when the erase/program operation fails, especially,
for the failure results from intending to modify protected space, spi-nor
upper layers still get the return which shows the operation succeeds.
This because spi_nor_fsr_ready() only uses bit.7 to device whether ready.
For
On 2017-11-28 10:34 PM, Cheng, Tony wrote:
> That code is to handle NAN (not a number) in float. Unfortunately our HW
> architect decided NAN is one of the way to determine if something isn't
> supported. We have feed this back to our HW team and they will look into
> improving this for next
Complement commit c23b3d1a5311 ("MIPS: ptrace: Change GP regset to use
correct core dump register layout") and also reject outsized
PTRACE_SETREGSET requests to the NT_PRFPREG regset, like with the
NT_PRSTATUS regset.
Cc: sta...@vger.kernel.org # v3.17+
Fixes: c23b3d1a5311 ("MIPS: ptrace:
On Tue, Nov 28, 2017 at 10:43:39PM +0100, Jernej Škrabec wrote:
> Hi!
>
> Dne torek, 28. november 2017 ob 21:55:50 CET je Maxime Ripard napisal(a):
> > On Mon, Nov 27, 2017 at 09:57:46PM +0100, Jernej Skrabec wrote:
> > > DE2 have many CSC units - channel input CSC, channel output CSC and
> > >
On 11/29/2017 10:26 AM, Davidlohr Bueso wrote:
> Are you planning on sending a v9 with the discussed changes? afaict:
>
> - Drop last two patches
> - Fix tearing (WRITE/READ_ONCE())
> - Reduce barrier usage for dlock_lists_empty() -- which I'll be sending
> you shortly.
>
> Thanks,
> Davidlohr
401 - 500 of 2692 matches
Mail list logo