From: Jiri Kosina
As explained in
0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
we always, no matter what, have to bring up x86 HT siblings during boot at
least once in order to avoid first MCE bringing the system to its knees.
That means that whenever 'nosmt' is supplie
From: Jisheng Zhang
Date: Tue, 28 May 2019 07:02:07 +
> Before the netdev is registered, calling netdev_info() will emit
> something as "(unnamed net device) (uninitialized)", looks confusing.
>
> Before this patch:
> [3.155028] stmmaceth f7b6.ethernet (unnamed net_device)
> (uninit
> I think it makes more sense to sanitize size in size_index_elem(),
> don't you?
> - return (bytes - 1) / 8;
> + return array_index_nospec((bytes - 1) / 8, ARRAY_SIZE(size_index));
I think it should be fixed in poll.
Literally every small variable kmalloc call is going through this funct
On 5/29/19 2:25 PM, Qian Cai wrote:
> The commit 0619317ff8ba ("block: add polled wakeup task helper")
> replaced wake_up_process() with blk_wake_io_task() in
> end_swap_bio_read() which triggers a crash when running heavy swapping
> workloads.
>
> [T114538] kernel BUG at kernel/sched/core.c:3462!
On Wed, 29 May 2019 at 07:49, Richard Cochran wrote:
>
> On Wed, May 29, 2019 at 02:56:25AM +0300, Vladimir Oltean wrote:
> > The newly introduced function is called on both the RX and TX paths.
>
> NAK on this patch.
>
> > The boolean returned by port_txtstamp should only return false if the
> >
Hello,
YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> arch/mips/kernel/uprobes.c: In function 'arch_uprobe_pre_xol':
> arch/mips/kernel/uprobes.c:115:17: warning: variable 'epc' set but not used
> [-Wunused-but-set-variable]
>
> It's never used since introduction in
> co
Hello,
Masahiro Yamada wrote:
> Commit 8bd9cb51daac ("locking/atomics, asm-generic: Move some macros
> from to a new file") moved BIT_ULL()
> into . It only includes , so there is
> no longer "include file recursion hell".
>
> Signed-off-by: Masahiro Yamada
Applied to mips-next.
Thanks,
From: Peter Zijlstra
In preparation of further separating pick_next_task() and
set_curr_task() we have to pass the actual task into it, while there,
rename the thing to better pair with put_prev_task().
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 12 ++--
kerne
From: Peter Zijlstra
Avoid the RETRY_TASK case in the pick_next_task() slow path.
By doing the put_prev_task() early, we get the rt/deadline pull done,
and by testing rq->nr_running we know if we need newidle_balance().
This then gives a stable state to pick a task from.
Since the fast-path is
Third iteration of the Core-Scheduling feature.
This version fixes mostly correctness related issues in v2 and
addresses performance issues. Also, addressed some crashes related
to cgroups and cpu hotplugging.
We have tested and verified that incompatible processes are not
selected during schedul
From: Peter Zijlstra
Marks all tasks in a cgroup as matching for core-scheduling.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Julien Desfossez
Signed-off-by: Vineeth Remanan Pillai
---
Changes in v3
-
- Fixes the refcount management when deleting a tagged cgroup.
- Jul
From: Peter Zijlstra
Introduce the basic infrastructure to have a core wide rq->lock.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Julien Desfossez
Signed-off-by: Vineeth Remanan Pillai
---
Changes in v3
-
- Fixes a crash during cpu offline/offline with coresched enabled
From: Peter Zijlstra
Instead of only selecting a local task, select a task for all SMT
siblings for every reschedule on the core (irrespective which logical
CPU does the reschedule).
NOTE: there is still potential for siblings rivalry.
NOTE: this is far too complicated; but thus far I've failed
From: Peter Zijlstra
When a sibling is forced-idle to match the core-cookie; search for
matching tasks to fill the core.
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/sched.h | 1 +
kernel/sched/core.c | 131 +-
kernel/sched/idle.c | 1
From: Peter Zijlstra
In preparation of playing games with rq->lock, abstract the thing
using an accessor.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Vineeth Remanan Pillai
Signed-off-by: Julien Desfossez
---
Changes in v2
-
- Fixes a deadlock due in double_rq_lock and d
From: Peter Zijlstra
Not-Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 44 ++--
1 file changed, 42 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 5b8223c9a723..90655c9ad937 100644
--- a/kernel
From: Peter Zijlstra
Because sched_class::pick_next_task() also implies
sched_class::set_next_task() (and possibly put_prev_task() and
newidle_balance) it is not state invariant. This makes it unsuitable
for remote task selection.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Vineeth Rem
From: Peter Zijlstra
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/fair.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index d8a107aea69b..26d29126d6a5 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fai
From: Peter Zijlstra
Introduce task_struct::core_cookie as an opaque identifier for core
scheduling. When enabled; core scheduling will only allow matching
task to be on the core; where idle matches everything.
When task_struct::core_cookie is set (and core scheduling is enabled)
these tasks are
From: Peter Zijlstra
Currently the pick_next_task() loop is convoluted and ugly because of
how it can drop the rq->lock and needs to restart the picking.
For the RT/Deadline classes, it is put_prev_task() where we do
balancing, and we could do this before the picking loop. Make this
possible.
S
From: Peter Zijlstra
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 4778c48a7fda..416ea613eda8 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6287,7
From: Peter Zijlstra
Make sure the entire for loop has stop_cpus_in_progress set.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/stop_machine.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/stop_machine.c b/kernel/stop_machine.c
index 067cb83f37ea..583119e0c51c 100644
--- a/ke
From: Peter Zijlstra
Because pick_next_task() implies set_curr_task() and some of the
details haven't matter too much, some of what _should_ be in
set_curr_task() ended up in pick_next_task, correct this.
This prepares the way for a pick_next_task() variant that does not
affect the current state
From: Peter Zijlstra
For pick_next_task_fair() it is the newidle balance that requires
dropping the rq->lock; provided we do put_prev_task() early, we can
also detect the condition for doing newidle early.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/fair.c | 18 --
On 5/29/19 7:52 AM, Richard Cochran wrote:
On Wed, May 29, 2019 at 02:56:22AM +0300, Vladimir Oltean wrote:
Not all is rosy, though.
You can sure say that again!
PTP timestamping will only work when the ports are bridged. Otherwise,
the metadata follow-up frames holding RX timestamps won't
I've just noticed gmail redirected this message to the Spam folder.
I will have to improve my filters to secure myself against that.
Sorry for late reply and maybe unnecessary escalation of the issue.
On 5/24/19 1:56 PM, Mark Brown wrote:
On Thu, May 23, 2019 at 10:07:35PM +0200, Jacek Anaszews
On 5/22/19 9:02 PM, Mark Brown wrote:
On Wed, May 22, 2019 at 08:27:32PM +0200, Jacek Anaszewski wrote:
On 5/21/19 11:15 PM, Mark Brown wrote:
On Tue, May 21, 2019 at 10:30:38PM +0200, Jacek Anaszewski wrote:
regulator: lm363x: Make the gpio register enable flexible
regulator
Mark
On 5/29/19 10:10 AM, Mark Brown wrote:
On Wed, May 29, 2019 at 06:51:32AM -0500, Dan Murphy wrote:
Although I don't disagree with you I don't see how the interface is fragile
with only these 3 regulators defined.
Would it not be prudent to amend this driver if/when a new regulator is
need
29.05.2019 23:11, Sowjanya Komatineni пишет:
>
> On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
>> 29.05.2019 21:14, Sowjanya Komatineni пишет:
>>> On 5/29/19 8:29 AM, Dmitry Osipenko wrote:
29.05.2019 2:08, Sowjanya Komatineni пишет:
> This patch adds suspend and resume support for Tegra pi
On 5/29/19 3:58 PM, Lee Jones wrote:
On Fri, 24 May 2019, Jacek Anaszewski wrote:
Hi,
On 5/23/19 9:09 PM, Dan Murphy wrote:
Pavel
Thanks for the review
On 5/23/19 7:50 AM, Pavel Machek wrote:
Hi!
+++ b/drivers/leds/leds-lm36274.c
+static int lm36274_parse_dt(struct lm36274 *lm36274_da
locked_vm accounting is done roughly the same way in five places, so
unify them in a helper.
Include the helper's caller in the debug print to distinguish between
callsites.
Error codes stay the same, so user-visible behavior does too. The one
exception is that the -EPERM case in tce_account_loc
On Tue, May 21, 2019 at 3:57 AM Colin King wrote:
>
> From: Colin Ian King
>
> There is a spelling mistake in a pr_err message. Fix it.
>
> Signed-off-by: Colin Ian King
Applied. Thanks!
Regards,
Leo
> ---
> drivers/soc/fsl/dpaa2-console.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion
This reverts commit b0d659022e5c96ee5c4bd62d22d3da2d66de306b.
The reverted commit does nothing but adding two unnecessary lines
of code. It sets a local variable to NULL in two functions, but
that variable is not used anywhere in the rest of those functions.
This is just confusing, so let's remov
On 5/29/19 1:47 PM, Dmitry Osipenko wrote:
29.05.2019 23:11, Sowjanya Komatineni пишет:
On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
29.05.2019 21:14, Sowjanya Komatineni пишет:
On 5/29/19 8:29 AM, Dmitry Osipenko wrote:
29.05.2019 2:08, Sowjanya Komatineni пишет:
This patch adds suspend an
Hi,
On Wed, May 29, 2019 at 1:54 PM Guenter Roeck wrote:
>
> This reverts commit b0d659022e5c96ee5c4bd62d22d3da2d66de306b.
>
> The reverted commit does nothing but adding two unnecessary lines
> of code. It sets a local variable to NULL in two functions, but
> that variable is not used anywhere
Hi,
yes, I agree on this personally. I meant to correct this myself or at
least try to, but I didn't have time, as I was the one that found out
how they did their partition layout previously, this used to be good so
I asked Uwe Kleine-König if he could get this patch upstreamed, but as
it is I
On Wed, May 29, 2019 at 1:37 PM Vineeth Remanan Pillai
wrote:
>
> From: Peter Zijlstra
>
> Not-Signed-off-by: Peter Zijlstra (Intel)
No commit message, not-signed-off-by...
> ---
> kernel/sched/core.c | 44 ++--
> 1 file changed, 42 insertions(+), 2 del
On Wed, May 29, 2019 at 6:21 PM Oleg Nesterov wrote:
> On 05/29, Jann Horn wrote:
> > --- a/kernel/ptrace.c
> > +++ b/kernel/ptrace.c
> > @@ -324,6 +324,16 @@ static int __ptrace_may_access(struct task_struct
> > *task, unsigned int mode)
[...]
> > mm = task->mm;
>
> while at it, could you
Hi Stephen, Mauro,
On 2019-05-29 08:04:54 +1000, Stephen Rothwell wrote:
> Hi Mauro,
>
> In commit
>
> 0c310868826e ("media: rcar-csi2: Fix coccinelle warning for
> PTR_ERR_OR_ZERO()")
>
> Fixes tag
>
> Fixes: 3ae854cafd76 ("rcar-csi2: Use standby mode instead of resetting")
>
> has thes
On 5/29/19 1:56 PM, Sowjanya Komatineni wrote:
On 5/29/19 1:47 PM, Dmitry Osipenko wrote:
29.05.2019 23:11, Sowjanya Komatineni пишет:
On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
29.05.2019 21:14, Sowjanya Komatineni пишет:
On 5/29/19 8:29 AM, Dmitry Osipenko wrote:
29.05.2019 2:08, Sowja
On Wed, 29 May 2019, Yang Shi wrote:
> > Right, we've also encountered this. I talked to Kirill about it a week or
> > so ago where the suggestion was to split all compound pages on the
> > deferred split queues under the presence of even memory pressure.
> >
> > That breaks cgroup isolation and
Em Wed, 29 May 2019 23:05:11 +0200
"Niklas Söderlund" escreveu:
> Hi Stephen, Mauro,
>
> On 2019-05-29 08:04:54 +1000, Stephen Rothwell wrote:
> > Hi Mauro,
> >
> > In commit
> >
> > 0c310868826e ("media: rcar-csi2: Fix coccinelle warning for
> > PTR_ERR_OR_ZERO()")
> >
> > Fixes tag
> >
On Tue, 28 May 2019, Christoph Hellwig wrote:
> > wd719x_chip_init is getting called in interrupt disabled
> > mode(spin_lock_irqsave) , so we need to GFP_ATOMIC instead
> > of GFP_KERNEL.
> >
> > Issue identified by coccicheck
>
> I don't think request_firmware is any more happy being called un
On Wed, 29 May 2019, Hariprasad Kelam wrote:
> dont acquire lock before calling wd719x_chip_init.
>
> Issue identified by coccicheck
>
> Signed-off-by: Hariprasad Kelam
> -
> changes in v1: Replace GFP_KERNEL with GFP_ATOMIC.
> changes in v2: Call wd719x_chip_init without lock as suggested
The cpu-map DT entry in ARM can describe the CPU topology in much better
way compared to other existing approaches. RISC-V can easily adopt this
binding to represent its own CPU topology. Thus, both cpu-map DT
binding and topology parsing code can be moved to a common location so
that RISC-V or any
cpu-map binding can be used to described cpu topology for both
RISC-V & ARM. It makes more sense to move the binding to document
to a common place.
The relevant discussion can be found here.
https://lkml.org/lkml/2018/11/6/19
Signed-off-by: Atish Patra
Reviewed-by: Sudeep Holla
Reviewed-by: Rob
From: Sudeep Holla
The current ARM DT topology description provides the operating system
with a topological view of the system that is based on leaf nodes
representing either cores or threads (in an SMT system) and a
hierarchical set of cluster nodes that creates a hierarchical topology
view of h
Both RISC-V & ARM64 are using cpu-map device tree to describe
their cpu topology. It's better to move the relevant code to
a common place instead of duplicate code.
To: Will Deacon
To: Catalin Marinas
Signed-off-by: Atish Patra
[Tested on QDF2400]
Tested-by: Jeffrey Hugo
[Tested on Juno and ot
Currently, ARM32 and ARM64 uses different data structures to represent
their cpu topologies. Since, we are moving the ARM64 topology to common
code to be used by other architectures, we can reuse that for ARM32 as
well.
Take this opprtunity to remove the redundant functions from ARM32 and
reuse th
Currently, there are no topology defined for RISC-V.
Parse the cpu-map node from device tree and setup the
cpu topology.
CPU topology after applying the patch.
$cat /sys/devices/system/cpu/cpu2/topology/core_siblings_list
0-3
$cat /sys/devices/system/cpu/cpu3/topology/core_siblings_list
0-3
$cat /
From: Sudeep Holla
arm and arm64 shared lot of CPU topology related code. This was
consolidated under driver/base/arch_topology.c by Juri. Now RISC-V
is also started sharing the same code pulling more code from arm64
into arch_topology.c
Since I was involved in the review from the beginning, I w
From: Sudeep Holla
Commit 5d777b185f6d ("arch_topology: Make cpu_capacity sysfs node as read-only")
made cpu_capacity sysfs node read-only. Update the GENERIC_ARCH_TOPOLOGY
Kconfig help section to reflect the same.
Cc: Greg Kroah-Hartman
Signed-off-by: Sudeep Holla
---
drivers/base/Kconfig |
From: YueHaibing
Date: Tue, 28 May 2019 17:10:40 +0800
> Fix gcc build error while CONFIG_INET is not set
>
> drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.o: In function
> `__stmmac_test_loopback':
> stmmac_selftests.c:(.text+0x8ec): undefined reference to `ip_send_check'
> stmmac_selft
On Wed, 29 May 2019 22:11:06 +0200
"Thomas Meyer" wrote:
> Use vma_pages function on vma object instead of explicit computation.
>
> Signed-off-by: Thomas Meyer
> ---
>
> diff -u -p a/drivers/vfio/pci/vfio_pci_nvlink2.c
> b/drivers/vfio/pci/vfio_pci_nvlink2.c
> --- a/drivers/vfio/pci/vfio_pci
On Thu, 23 May 2019, Andrew Morton wrote:
> > We are going in circles, *yes* there is a problem for potential swap
> > storms today because of the poor interaction between memory compaction and
> > directed reclaim but this is a result of a poor API that does not allow
> > userspace to specify
On Wed 2019-05-29 22:26:48, Jiri Kosina wrote:
> From: Jiri Kosina
>
> As explained in
>
> 0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
>
> we always, no matter what, have to bring up x86 HT siblings during boot at
> least once in order to avoid first MCE bringing the syst
29.05.2019 23:56, Sowjanya Komatineni пишет:
>
> On 5/29/19 1:47 PM, Dmitry Osipenko wrote:
>> 29.05.2019 23:11, Sowjanya Komatineni пишет:
>>> On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
29.05.2019 21:14, Sowjanya Komatineni пишет:
> On 5/29/19 8:29 AM, Dmitry Osipenko wrote:
>> 29.0
Dear RT folks!
I'm pleased to announce the v5.0.19-rt11 patch set.
Changes since v5.0.19-rt10:
- Ignore a warning from lockdep when lockdep is disabled for different
lock types.
- Make the cpuidle an imx6 raw_spinlock_t.
- Add a proper depends in Kconfig for Atmel's tclib based cloc
On Wed, 29 May 2019, Pavel Machek wrote:
> > As explained in
> >
> > 0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
> >
> > we always, no matter what, have to bring up x86 HT siblings during boot at
> > least once in order to avoid first MCE bringing the system to its
> > knees
On 5/29/19 2:25 PM, Dmitry Osipenko wrote:
29.05.2019 23:56, Sowjanya Komatineni пишет:
On 5/29/19 1:47 PM, Dmitry Osipenko wrote:
29.05.2019 23:11, Sowjanya Komatineni пишет:
On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
29.05.2019 21:14, Sowjanya Komatineni пишет:
On 5/29/19 8:29 AM, Dmitr
Quoting Sebastian Andrzej Siewior (2019-05-29 08:25:40)
> From: Hugh Dickins
>
> Since commit
>
>d9c9ce34ed5c8 ("x86/fpu: Fault-in user stack if copy_fpstate_to_sigframe()
> fails")
>
> we use get_user_pages_unlocked() to pre-faulting user's memory if a
> write generates a pagefault while
30.05.2019 0:27, Sowjanya Komatineni пишет:
>
> On 5/29/19 2:25 PM, Dmitry Osipenko wrote:
>> 29.05.2019 23:56, Sowjanya Komatineni пишет:
>>> On 5/29/19 1:47 PM, Dmitry Osipenko wrote:
29.05.2019 23:11, Sowjanya Komatineni пишет:
> On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
>> 29.05
James Morris wrote:
> > +
> > + if (flags & ~KEYCTL_MOVE_EXCL)
> > + return -EINVAL;
> > +
> > + key_ref = lookup_user_key(id, KEY_LOOKUP_CREATE, KEY_NEED_LINK);
> > + if (IS_ERR(key_ref)) {
> > + ret = PTR_ERR(key_ref);
> > + goto error;
> > + }
>
> This co
AT_RANDOM content is always misaligned on x86_64:
$ LD_SHOW_AUXV=1 /bin/true | grep AT_RANDOM
AT_RANDOM: 0x7fff02101019
glibc copies first few bytes for stack protector stuff, aligned
access should be slightly faster.
Signed-off-by: Alexey Dobriyan
---
fs/binfmt_elf.c |
Apparently driver was never tested with DMA_PREP_INTERRUPT flag being
unset since it completely disables interrupt handling instead of skipping
the callbacks invocations, hence putting channel into unusable state.
The flag is always set by all of kernel drivers that use APB DMA, so let's
error out
The pull request you sent on Wed, 29 May 2019 09:04:42 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-5.2-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2b28601d62b01429d12e999fe3712aaf57ca2e26
Thank you!
--
The pull request you sent on Wed, 29 May 2019 09:54:08 -0600:
> git://git.lwn.net/linux.git tags/docs-5.2-fixes2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bec7550cca106c3ccc061e3e625516af63054fe4
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel
The pull request you sent on Tue, 28 May 2019 22:58:34 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.2-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9e82b4a91d46a690de3cbbe6960667caa508b27a
Thank you!
--
Deet-doot-do
After adding ethtool ring param sanity check patch:
commit 37e2d99b59c4765112533a1d38174fea58d28a51 ("ethtool: Ensure new
ring parameters are within bounds during SRINGPARAM")
cpsw has no ability to change rx descriptor numbers.
But the reason - initially "tx_max_pending" was not correctly set
wh
On Wed 2019-05-29 23:27:34, Jiri Kosina wrote:
> On Wed, 29 May 2019, Pavel Machek wrote:
>
> > > As explained in
> > >
> > > 0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
> > >
> > > we always, no matter what, have to bring up x86 HT siblings during boot at
> > > least once in
On Wed, May 29, 2019 at 3:33 AM Chuanhua Han wrote:
>
> The GPIO Input Buffer Enable register is used to control the input
> enable of each individual GPIO port. When an individual GPIO port's
> direction is set to input (GPIO_GPDIR[DRn=0]), the associated
> input enable must be set (GPIOxGPIE[IEn
On Wed, 29 May 2019 10:55:53 +0200 John Ogness
wrote:
> Commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in
> /proc/PID/stat") stopped reporting eip/esp and commit fd7d56270b52
> ("fs/proc: Report eip/esp in /prod/PID/stat for coredumping")
> reintroduced the feature to fix a regression
x 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
tags/keys-misc-20190529
for you to fetch changes up to 39de363a48ae151d766512c8e73a5564a3096c82:
keys: Grant Link permission to possesse
On Wed, 29 May 2019 14:46:24 +0530 Anshuman Khandual
wrote:
> This series enables memory hot remove on arm64 after fixing a memblock
> removal ordering problem in generic __remove_memory() and one possible
> arm64 platform specific kernel page table race condition. This series
> is based on late
From: Jiri Kosina
As explained in
0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
we always, no matter what, have to bring up x86 HT siblings during boot at
least once in order to avoid first MCE bringing the system to its knees.
That means that whenever 'nosmt' is supplie
Sorry, I hadn't registered that was uapi. You are right, as a
configuration setting it's an odd thing to expose there.
That define won't really be any use to user space except for type
range validation, and as such it would actually be unhelpful for it to
be other than 63.
I will add if defined(__
On Wed, May 29, 2019 at 11:01:35PM +0100, David Howells wrote:
>
> (2) Implement a keyctl to allow a key to be moved from one keyring to
> another, with the option of prohibiting key replacement in the
> destination keyring.
>
What is the use case, and where are the tests and document
The LS1021A-TSN is a development board built by VVDN/Argonboards in
partnership with NXP.
It features the LS1021A SoC and the first-generation SJA1105T Ethernet
switch for prototyping implementations of a subset of IEEE 802.1 TSN
standards.
It has two regular Ethernet ports and four switched, TSN
On Wed, May 29, 2019 at 3:33 AM Chuanhua Han wrote:
>
> GPIO3 and GPIO4 controllers share one irq number on Layerscape
> platform. In the current implementation, only one GPIO controller
> can register successfully.
>
> This patch is to allow two controllers to share a single interrupt
> number.
On Wed, 29 May 2019 12:26:20 +0200, Horatiu Vultur wrote:
> +static int ocelot_flower_replace(struct tc_cls_flower_offload *f,
> + struct ocelot_port_block *port_block)
> +{
> + struct ocelot_ace_rule *rule;
> + int ret;
> +
> + if (port_block->port->tc.bloc
On Thu, 30 May 2019 00:37:08 +0300 Alexey Dobriyan wrote:
> AT_RANDOM content is always misaligned on x86_64:
>
> $ LD_SHOW_AUXV=1 /bin/true | grep AT_RANDOM
> AT_RANDOM: 0x7fff02101019
>
> glibc copies first few bytes for stack protector stuff, aligned
> access should be slig
Hello,
On Wed, 29 May 2019, Jacky Hu wrote:
> gueh = (struct guehdr *)skb->data;
>
> gueh->control = 0;
> gueh->version = 0;
> - gueh->hlen = 0;
> + gueh->hlen = optlen >> 2;
> gueh->flags = 0;
> gueh->proto_ctype = *next_protocol;
>
> + dat
On Wed, May 29, 2019 at 05:22:36PM +0200, Christian Brauner wrote:
> This adds the clone3 system call.
>
> As mentioned several times already (cf. [7], [8]) here's the promised
> patchset for clone3().
>
> We recently merged the CLONE_PIDFD patchset (cf. [1]). It took the last
> free flag from cl
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-fixes-for-linus
for you to fetch changes up to 1cc54078d104f
On Wed, May 29, 2019 at 6:12 PM Oleg Nesterov wrote:
>
> Al, Linus, Eric, please help.
>
> The previous discussion was very confusing, we simply can not understand each
> other.
>
> To me everything looks very simple and clear, but perhaps I missed something
> obvious? Please correct me.
Thanks f
On Wed, 29 May 2019 22:11:10 +0300 Alexey Dobriyan wrote:
> Don't repeat function signatures twice.
>
> This is a kind-of-precursor for "struct proc_ops".
>
> Note:
>
> typeof(pde->proc_fops->...) ...;
>
> can't be used because ->proc_fops is "const struct file_operations *".
> "const"
On Mon, May 27, 2019 at 2:09 AM Gustavo Pimentel
wrote:
>
> On Fri, May 24, 2019 at 20:42:43, Alan Mikhak
> wrote:
>
> Hi Alan,
>
> > On Fri, May 24, 2019 at 1:59 AM Gustavo Pimentel
> > wrote:
> > >
> > > Hi Alan,
> > >
> > > This patch implementation is very HW implementation dependent and
> >
On Wed, 29 May 2019 15:06:53 -0400 Qian Cai wrote:
> The commit 0619317ff8ba ("block: add polled wakeup task helper")
> replaced wake_up_process() with blk_wake_io_task() in
> end_swap_bio_read() which triggers a crash when running heavy swapping
> workloads.
>
> [T114538] kernel BUG at kernel/s
--
Hello Good day,
Am Hamza Kabore, a senior staff in the EcoBank International Burkina
Faso, working as Bill & Exchange Manager. I discovered an abandoned
sum of 12.8 million usd in my department and i want the the fund to be
transferred to your account.
We shall share it 50% - 50%. No ri
As for FOLL_LONGTERM, it is checked in the slow path
__gup_longterm_unlocked(). But it is not checked in the fast path, which
means a possible leak of CMA page to longterm pinned requirement through
this crack.
Place a check in the fast path.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew
On Mon, May 06, 2019 at 10:20:03AM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> When IOMMU tries to enable PRI for VF device in
> iommu_enable_dev_iotlb(), it always fails because PRI support for PCIe
> VF device is currently broken in PCIE driv
On 5/29/19 4:44 PM, Andrew Morton wrote:
> On Wed, 29 May 2019 15:06:53 -0400 Qian Cai wrote:
>
>> The commit 0619317ff8ba ("block: add polled wakeup task helper")
>> replaced wake_up_process() with blk_wake_io_task() in
>> end_swap_bio_read() which triggers a crash when running heavy swapping
>>
On Tue, May 28, 2019 at 01:21:00PM +, Daniel Baluta wrote:
> From: Shengjiu Wang
>
> Audio MCLK source option is selected with a 4:1 MUX
> controller using MCLK Select bits in SAI xCR2 register.
>
> On imx6/7 mclk0 and mclk1 always point to the same clock
> source. Anyhow, this is no longer
On Wed, May 29, 2019 at 03:20:20PM -0700, Andrew Morton wrote:
> On Thu, 30 May 2019 00:37:08 +0300 Alexey Dobriyan
> wrote:
>
> > AT_RANDOM content is always misaligned on x86_64:
> >
> > $ LD_SHOW_AUXV=1 /bin/true | grep AT_RANDOM
> > AT_RANDOM: 0x7fff02101019
> >
> > glibc cop
On Mon, May 06, 2019 at 10:20:04AM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> When IOMMU tries to enable PASID for VF device in
> iommu_enable_dev_iotlb(), it always fails because PASID support for PCIe
> VF device is currently broken in PCIE
On Wed, May 29, 2019 at 05:57:14PM -0500, Bjorn Helgaas wrote:
> On Mon, May 06, 2019 at 10:20:03AM -0700,
> sathyanarayanan.kuppusw...@linux.intel.com wrote:
> > From: Kuppuswamy Sathyanarayanan
> >
> >
> > When IOMMU tries to enable PRI for VF device in
> > iommu_enable_dev_iotlb(), it always
On Tue, May 28, 2019 at 01:20:46PM +, Daniel Baluta wrote:
> 1) SAI clock source select MUX is really part of the hardware
> 2) flexibility! We let DT tell us which is the option for MUX
> option 0.
I think the "MUX" is plausible comparing to your previous version.
As long as DT maintainers a
On Wed, May 29, 2019 at 05:39:44PM +, Voon, Weifeng wrote:
> > > +static void stmmac_mdio_c45_setup(struct stmmac_priv *priv, int phyreg,
> > > + u32 *val, u32 *data)
> > > +{
> > > + unsigned int reg_shift = priv->hw->mii.reg_shift;
> > > + unsigned int reg_mask = pri
Hello,
On Sat, May 25, 2019 at 01:10:46PM +0800, Wang, Haiyue wrote:
>
> 在 2019-05-25 01:33, Eduardo Valentin 写道:
> >Hey,
> >
> >On Fri, May 24, 2019 at 10:43:16AM +0800, Wang, Haiyue wrote:
> >>Thanks for interest, the design idea is from:
> >>
> >>https://git.kernel.org/pub/scm/linux/kernel/git
At DT, files are being renamed to jason. Teach the script how to
handle such renames when used in fix mode.
Signed-off-by: Mauro Carvalho Chehab
---
scripts/documentation-file-ref-check | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/scripts/documentation
701 - 800 of 2316 matches
Mail list logo
