On Fri, 6 Jul 2018 15:54:37 -0600 Ross Zwisler
wrote:
> On Fri, Jul 06, 2018 at 11:23:27PM +0200, Oscar Salvador wrote:
> > On Fri, Jul 06, 2018 at 01:06:58PM -0600, Ross Zwisler wrote:
> > > The following commit in -next:
> > >
> > > commit 054620849110 ("mm/sparse.c: make sparse_init_one_sect
Move some code that will be needed for the lazy -> !lazy state
transition when a lazy TLB CPU has gotten out of date.
No functional changes, since the if (real_prev == next) branch
always returns.
Signed-off-by: Rik van Riel
Acked-by: Dave Hansen
Suggested-by: Andy Lutomirski
---
arch/x86/mm/
CPUs in !is_lazy have either received TLB flush IPIs earlier on during
the munmap (when the user memory was unmapped), or have context switched
and reloaded during that stage of the munmap.
Page table free TLB flushes only need to be sent to CPUs in lazy TLB
mode, which TLB contents might not yet
Song noticed switch_mm_irqs_off taking a lot of CPU time in recent
kernels, using 1.9% of a 48 CPU system during a netperf run. Digging
into the profile, the atomic operations in cpumask_clear_cpu and
cpumask_set_cpu are responsible for about half of that CPU use.
However, the CPUs running netperf
The mm_struct always contains a cpumask bitmap, regardless of
CONFIG_CPUMASK_OFFSTACK. That means the first step can be to
simplify things, and simply have one bitmask at the end of the
mm_struct for the mm_cpumask.
This does necessitate moving everything else in mm_struct into
an anonymous sub-st
Andy discovered that speculative memory accesses while in lazy
TLB mode can crash a system, when a CPU tries to dereference a
speculative access using memory contents that used to be valid
page table memory, but have since been reused for something else
and point into la-la land.
The latter proble
Lazy TLB mode can result in an idle CPU being woken up by a TLB flush,
when all it really needs to do is reload %CR3 at the next context switch,
assuming no page table pages got freed.
Memory ordering is used to prevent race conditions between switch_mm_irqs_off,
which checks whether .tlb_gen chan
Don't access the provided buffer out of bounds - this can cause a kernel
out-of-bounds read when invoked through sys_splice() or other things that
use kernel_write()/__kernel_write().
Fixes: 7f8ec5a4f01a ("x86/mtrr: Convert to use strncpy_from_user() helper")
Signed-off-by: Jann Horn
---
arch/x8
On Fri, 6 Jul 2018 16:36:41 +0100 Mark Rutland wrote:
> > >
> > > Acked-by: Matthew Wilcox
> >
> > Cheers!
> >
> > I assume that Andrew will pick this up, if he's also happy with it.
>
> I've just started fuzzing, and found this also applies with
> node_tag_set(). I'll spin a v2 with that fi
From: Tobias Lindskog
When ashmem_shrink is called from direct reclaim on a user thread, a
call to do_fallocate will check for permissions against the security
policy of that user thread. It can thus fail by chance if called on a
thread that isn't permitted to modify the relevant ashmem areas.
On Fri, 6 Jul 2018 17:24:28 -0400
Steven Rostedt wrote:
> I'll investigate further.
Note, I enabled function tracing to trace the scheduler function:
# trace-cmd start -p function -l schedule
And then ran cyclictest. That does not cause any noticeable increase
in latency (try it). So there is
This is two minor bug fixes (aacraid, target) and a fix for a potential
exploit in the way sg handles teardown.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
The short changelog is:
David Disseldorp (1):
scsi: target: Fix truncated PR-
On Fri, 6 Jul 2018 21:27:20 +0200
Boris Brezillon wrote:
> On Mon, 25 Jun 2018 10:44:42 +1200
> Chris Packham wrote:
>
> > Hi,
> >
> > I'm looking at adding support for the Micron MT29F1G08ABAFAWP-ITE:F chip
>
> Hm, it's even worse than I thought. The model name does not include the
> -ITE
On Fri, 2018-07-06 at 15:39 -0400, Prarit Bhargava wrote:
>
> On 07/06/2018 02:44 PM, Don Zickus wrote:
> > On Fri, Jul 06, 2018 at 11:31:13AM -0700, Joe Perches wrote:
> > > On Fri, 2018-07-06 at 13:54 -0400, Don Zickus wrote:
> > > > On Tue, Jun 26, 2018 at 01:16:11PM -0700, Joe Perches wrote:
>
This should speed up accessing new system calls introduced with the
kernel rather than waiting for libaudit updates to include them.
It also enables users to specify wildcards, for example, perf trace -e
'open*', just like was already possible on x86, s390, and powerpc, which
means arm64 can now p
Will be used for generating the syscall id/string translation table.
Arm64's unistd.h simply #includes the asm-generic/unistd.h, so,
since we will want to know whether either change, we grab both:
arch/arm64/include/uapi/asm/unistd.h
and
include/uapi/asm-generic/unistd.h
Cc: Ravi Bangoria
This should speed up accessing new system calls introduced with the
kernel rather than waiting for libaudit updates to include them.
Using the existing other arch scripts resulted in this error:
tools/perf/arch/arm64/entry/syscalls//mksyscalltbl: 25: printf:
__NR3264_ftruncate: expected numeric
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
tags/keystone_config_for_4.19
for you to fetch changes u
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
tags/soc_drivers_for_4.19
for you to fetch changes up to
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
tags/keystone_dts_for_4.19
for you to fetch changes up t
On Fri, 6 Jul 2018 08:22:01 +0200
Claudio wrote:
> Hello all,
>
> I have been experimenting with the idea of leaving ftrace enabled, with sched
> events,
> on production systems.
>
> The main concern that I am having at the moment is about the impact on the
> system.
> Enabling the sched even
On Fri, Jul 06, 2018 at 11:48:58PM +0300, Andy Shevchenko wrote:
> On Fri, Jul 6, 2018 at 9:39 PM, Tycho Andersen wrote:
> > On Fri, Jul 06, 2018 at 07:49:09PM +0300, Andy Shevchenko wrote:
> >> On Fri, Jul 6, 2018 at 7:24 PM, Tycho Andersen wrote:
>
> > but without the initialization I get,
>
Ignore this.. Will send again with subjects fixed
On 7/6/2018 2:16 PM, Santosh Shilimkar wrote:
Subject: [GIT PULL 3/3] SOC: Driver updates for v4.19
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the
Subject: [GIT PULL 1/3] ARM: Keystone DTS update for v4.19
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.gi
Subject: [GIT PULL 2/3] ARM: Keystone config update for v4.19
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone
Subject: [GIT PULL 3/3] SOC: Driver updates for v4.19
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
ta
On Thu, Jun 28, 2018 at 1:22 AM
wrote:
>
> Levin writes:
>
> > Rob Herring writes:
> >
> >> On Sat, Jun 02, 2018 at 04:40:09PM +0800, Levin Du wrote:
> >>>
> >>> Rob Herring writes:
> >>>
> >>> > On Thu, May 31, 2018 at 9:05 PM, Levin wrote:
> >>> > > Hi Rob,
> >>> > >
> >>> > >
> >>> > > On 2
On Fri, Jul 06, 2018 at 06:14:44PM +0100, David Woodhouse wrote:
> On Fri, 2018-07-06 at 10:11 -0700, Paul E. McKenney wrote:
> > > The preempt state is alread a bit complicated and shadowed in the
> > > preempt_count (on some architectures) adding additional bits to it like
> > > this is just aski
On Fri, Jul 06, 2018 at 04:37:21PM -0400, Alan Stern wrote:
> On Thu, 5 Jul 2018, Andrea Parri wrote:
>
> > > At any rate, it looks like instead of strengthening the relation, I
> > > should write a patch that removes it entirely. I also will add new,
> > > stronger relations for use with locking
The strncpy causes a warning [-Wstringop-truncation] here,
which indicates that it never appends a NUL byte to the path.
The NUL byte is only there because the buffer is allocated
with kzalloc(PAGE_SIZE, GFP_KERNEL), but since the range-check
is also off-by-one, and PAGE_SIZE==PATH_MAX the returned
This fixes to support unaligned dio as buffered writes.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index e66379961804..6e8e78bb64a7 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -2425,7 +
Quoting Anson Huang (2018-06-21 23:32:33)
> According to Reference Manual Rev.0, 06/2017,
> there are GPIO LPCGs defined in CCM CCGRs,
> add them into clock tree.
>
> Signed-off-by: Anson Huang
> ---
Applied to clk-next
Quoting Lei YU (2018-06-25 18:55:25)
> The SDCLK was named SDCLKCLK, and no one has used this yet.
> Fix it.
>
> Signed-off-by: Lei YU
> ---
Applied to clk-next
Quoting Robert Jarzmik (2018-06-27 12:41:23)
> This clock is especially used by the RTC driver, so export it so that
> devicetree users can use it.
>
> Signed-off-by: Robert Jarzmik
> ---
Applied to clk-next
Quoting Robert Jarzmik (2018-07-04 22:34:10)
> Robert Jarzmik writes:
>
> > This clock is especially used by the RTC driver, so export it so that
> > devicetree users can use it.
> >
> > Signed-off-by: Robert Jarzmik
> > ---
> > Since v2: fix missing parenthesis in clk-pxa25x.c and clk-pxa3xx.c
On Fri, Jul 06, 2018 at 07:11:24AM +0800, Stanley Chu wrote:
> This patch adds bindings of new "System Timer" on Mediatek SoCs.
>
> Remove RTC clock in the same time because it is not used by
> both "General Purpose Timer" and "System Timer" now.
>
> Signed-off-by: Stanley Chu
> ---
> .../bindi
mdev_access() calls mbochs_get_page() with mdev_state->ops_lock held,
while mbochs_get_page() locks the mutex by itself.
It leads to unavoidable deadlock.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
samples/vfio-mdev/mbochs.c | 4 +++-
1
On 07/06/2018 10:50 AM, Greg Kroah-Hartman wrote:
On Fri, Jul 06, 2018 at 08:41:34AM -0700, Joe Perches wrote:
On Fri, 2018-07-06 at 17:30 +0200, Greg Kroah-Hartman wrote:
On Wed, May 09, 2018 at 08:15:46AM -0700, Joe Perches wrote:
Add a prefixing macro to dev_ uses similar to the pr_fmt
pref
On Fri, Jul 6, 2018 at 9:39 PM, Tycho Andersen wrote:
> On Fri, Jul 06, 2018 at 07:49:09PM +0300, Andy Shevchenko wrote:
>> On Fri, Jul 6, 2018 at 7:24 PM, Tycho Andersen wrote:
> but without the initialization I get,
>
> CC drivers/tty/serial/serial_core.o
> In file included from ./incl
Quoting Joel Stanley (2018-06-07 00:09:59)
> This is used by the host to talk to the BMC's PCIe slave device. The BMC
> is not involved, but the clock needs to be enabled so the host can use
> the device.
>
> Fixes: 15ed8ce5f84e ("clk: aspeed: Register gated clocks")
> Cc: sta...@vger.kernel.org #
In general, accessing userspace memory beyond the length of the supplied
buffer in VFS read/write handlers can lead to both kernel memory corruption
(via kernel_read()/kernel_write(), which can e.g. be triggered via
sys_splice()) and privilege escalation inside userspace.
In this case, the affecte
Quoting Faiz Abbas (2018-07-05 07:23:15)
> Add clkctrl data for the m_can clocks and register it within the
> clkctrl driver
>
> Acked-by: Rob Herring
> CC: Tero Kristo
> Signed-off-by: Faiz Abbas
> ---
Acked-by: Stephen Boyd
but Tero should ack it too.
iput() ends up calling ->evict() on new inode, which is not yet initialized
by owning fs. So use destroy_inode() instead.
Add to sb->s_inodes list only if inode is not in I_CREATING state (meaning
that it wasn't allocated with new_inode(), which already does the
insertion).
Reported-by: Al Viro
On Thu, 5 Jul 2018, Andrea Parri wrote:
> > At any rate, it looks like instead of strengthening the relation, I
> > should write a patch that removes it entirely. I also will add new,
> > stronger relations for use with locking, essentially making spin_lock
> > and spin_unlock be RCsc.
>
> Thank
Quoting Paul Cercueil (2018-06-27 05:14:59)
> The UDC clock of the JZ4740 SoC can be gated, but the data structure
> representing it was missing the CGU_CLK_GATE flag to make it work.
>
> Signed-off-by: Paul Cercueil
> ---
Applied to clk-next
Quoting Paul Cercueil (2018-06-27 05:14:58)
> The register field for configuring the divider for the i2s clock
> occupies the bits [8-0], which means 9 bits and not 8.
>
> Signed-off-by: Paul Cercueil
> ---
Applied to clk-next
On Fri, Jun 29, 2018 at 05:38:02PM +0200, Parthiban Nallathambi wrote:
> Adding device tree binding for vcnl4035 and vendor
> prefix for Vishay Intertechnology
>
> Signed-off-by: Parthiban Nallathambi
> ---
> .../devicetree/bindings/iio/light/vcnl4035.txt| 19
> +++
> Do
On Fri, Jun 29, 2018 at 02:50:53PM +0530, Rohit kumar wrote:
> This adds APSS based ADSP PIL driver for QCOM SoCs.
> Added initial support for SDM845 with ADSP bootup and
> shutdown operation handled from Application Processor
> SubSystem(APSS).
>
> Signed-off-by: Rohit kumar
> ---
> Changes sinc
On Fri, Jul 6, 2018 at 12:38 PM Mathieu Desnoyers
wrote:
>
> Should I change all 4 bytes __get_user()/__put_user() in kernel/rseq.c
> for get_user()/put_user() to ensure consistency ?
Probably.
*If* this actually turns out to be somethinig that shows up on
profiles, it's almost certainly going t
On Fri, Jul 6, 2018 at 12:31 PM, Linus Torvalds
wrote:
> On Fri, Jul 6, 2018 at 12:23 PM Mathieu Desnoyers
> wrote:
>>
>> For -rc, I would favor the following simpler approach. Or I could even
>> just use get_user() instead. Thoughts ?
>
> Please just use "get_user()".
>
> In fact, we should be t
On Fri, Jul 06, 2018 at 11:31:13AM -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 13:54 -0400, Don Zickus wrote:
> > On Tue, Jun 26, 2018 at 01:16:11PM -0700, Joe Perches wrote:
> > > On Tue, 2018-06-26 at 14:25 -0400, Prarit Bhargava wrote:
> > > > OSes have additional maintainers that should b
On Thu, Jul 05, 2018 at 10:25:12PM +0530, Balakrishna Godavarthi wrote:
> In function qca_setup, we set initial and operating speeds for Qualcomm
> Bluetooth SoC's. This block of code is common across different
> Qualcomm Bluetooth SoC's. Instead of duplicating the code, created
> a wrapper functio
On 07/06/2018 02:44 PM, Don Zickus wrote:
> On Fri, Jul 06, 2018 at 11:31:13AM -0700, Joe Perches wrote:
>> On Fri, 2018-07-06 at 13:54 -0400, Don Zickus wrote:
>>> On Tue, Jun 26, 2018 at 01:16:11PM -0700, Joe Perches wrote:
On Tue, 2018-06-26 at 14:25 -0400, Prarit Bhargava wrote:
> O
Hi Benjamin,
On Fri, Jul 6, 2018 at 3:03 PM Benjamin Gaignard
wrote:
> The format specifier "%p" can leak kernel addresses.
> Use "%pK" instead.
Still? Isn't the value randomized these days?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyon
Hi Codrin,
On 18/06/2018 17:12:38+0300, Codrin Ciubotariu wrote:
> From: Cyrille Pitchen
>
> This patch adds DT nodes for I2S0 and I2S1. It also adds an alias for
> each I2S node.
>
> Signed-off-by: Cyrille Pitchen
> [codrin.ciubota...@microchip.com: added phandle to new mux clock]
> Signed-of
- On Jul 6, 2018, at 3:35 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Jul 6, 2018, at 3:31 PM, Linus Torvalds torva...@linux-foundation.org
> wrote:
>
>> On Fri, Jul 6, 2018 at 12:23 PM Mathieu Desnoyers
>> wrote:
>>>
>>> For -rc, I would favor the following simpl
On Fri, Jul 6, 2018 at 1:29 AM, Aneesh Kumar K.V
wrote:
> This patch steal system RAM and use that to emulate pmem device using the
> e820 platform driver.
>
> This adds a new kernel command line 'pmemmap' which takes the format
>
> to allocate memory early in the boot. This memory is later regi
- On Jul 6, 2018, at 3:31 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Fri, Jul 6, 2018 at 12:23 PM Mathieu Desnoyers
> wrote:
>>
>> For -rc, I would favor the following simpler approach. Or I could even
>> just use get_user() instead. Thoughts ?
>
> Please just use "get_use
v5->v6:
- Drop the neg_dentry_pc boot command line option, but add a
"neg-dentry-pc" sysctl parameter instead.
- Change the "enforce-neg-dentry-limit" sysctl parameter to
"neg-dentry-enforce".
- Add a patch to add negative dentry to the head of the LRU initially
so that they will
From: Omar Sandoval
Now we only need kclist_lock from user context and at fs init time, and
the following changes need to sleep while holding the kclist_lock.
Signed-off-by: Omar Sandoval
---
fs/proc/kcore.c | 32 +++-
1 file changed, 15 insertions(+), 17 deletions(
From: Omar Sandoval
kclist_add() is only called at init time, so there's no point in
grabbing any locks. We're also going to replace the rwlock with a rwsem,
which we don't want to try grabbing during early boot.
Signed-off-by: Omar Sandoval
---
fs/proc/kcore.c | 3 +--
1 file changed, 1 inser
From: Omar Sandoval
Hi,
This series makes a few improvements to /proc/kcore. Patches 1 and 2 are
prep patches. Patch 3 is a fix/cleanup. Patch 4 is another prep patch.
Patches 5 and 6 are optimizations to ->read(). Patch 7 adds vmcoreinfo
to /proc/kcore. This series is based on v4.18-rc3. Please
- On Jul 6, 2018, at 1:09 PM, Marc Zyngier marc.zyng...@arm.com wrote:
> On 06/07/18 18:04, Will Deacon wrote:
>> Hi Mathieu,
>>
>> On Fri, Jul 06, 2018 at 12:59:22PM -0400, Mathieu Desnoyers wrote:
>>> The 4.18-rc3 arm32 kernel defconfig fails to boot on my Cubietruck.
>>> This issue appeare
On Fri, Jul 06, 2018 at 11:11:10AM -0700, Andi Kleen wrote:
> There are valid use cases to override the flags. I use it sometimes too,
> and know some other people do to.
>
> But you need to know what you're doing.
>
> Perhaps a warning during build would be reasonable. So if you ask
> for a bui
From: Omar Sandoval
There's a theoretical race condition that will cause /proc/kcore to miss
a memory hotplug event:
CPU0 CPU1
// hotplug event 1
kcore_need_update = 1
open_kcore() open_kcore()
kcore_update_ram()kcore_update_
For negative dentries that are accessed once and never reused again,
there is not much value in putting the dentries at the tail of the LRU
list and keep it for a long time. So a new DCACHE_LRU_HEAD flag is added
to a negative dentry when it is initially created. When such a dentry
is added to the
From: Omar Sandoval
The vmcoreinfo information is useful for runtime debugging tools, not
just for crash dumps. A lot of this information can be determined by
other means, but this is much more convenient.
Signed-off-by: Omar Sandoval
---
fs/proc/Kconfig| 1 +
fs/proc/kcore.c
From: Omar Sandoval
Now that we're using an rwsem, we can hold it during the entirety of
read_kcore() and have a common return path. This is preparation for the
next change.
Signed-off-by: Omar Sandoval
---
fs/proc/kcore.c | 70 -
1 file changed,
From: Omar Sandoval
The current code does a full search of the segment list every time for
every page. This is wasteful, since it's almost certain that the next
page will be in the same segment. Instead, check if the previous segment
covers the current page before doing the list search.
Signed-o
If a rogue application that generates a large number of negative
dentries is running, the automatic negative dentries pruning process
may not be fast enough to clear up the negative dentries in time. In
this case, it is possible that negative dentries will use up most
of the available memory in the
From: Omar Sandoval
Currently, the ELF file header, program headers, and note segment are
allocated all at once, in some icky code dating back to 2.3. Programs
tend to read the file header, then the program headers, then the note
segment, all separately, so this is a waste of effort. It's cleaner
On Fri, Jul 6, 2018 at 12:23 PM Mathieu Desnoyers
wrote:
>
> For -rc, I would favor the following simpler approach. Or I could even
> just use get_user() instead. Thoughts ?
Please just use "get_user()".
In fact, we should be thinking seriosly about just removing
__get_user() entirely. It's wron
On Mon, 25 Jun 2018 10:44:42 +1200
Chris Packham wrote:
> Hi,
>
> I'm looking at adding support for the Micron MT29F1G08ABAFAWP-ITE:F chip
Hm, it's even worse than I thought. The model name does not include the
-ITE suffix (E means ECC can't be disabled), which means we have no way
to detect th
On Fri, Jul 6, 2018 at 12:13 AM, Oscar Salvador
wrote:
> On Thu, Jul 05, 2018 at 08:44:18AM -0700, Kees Cook wrote:
>> On Thu, Jul 5, 2018 at 7:55 AM, wrote:
>> > From: Oscar Salvador
>> >
>> > The current code does not make sure to page align bss before calling
>> > vm_brk(), and this can lead
On Fri, 6 Jul 2018, Paolo Bonzini wrote:
> On 06/07/2018 18:13, Thomas Gleixner wrote:
> > @@ -241,6 +269,9 @@ void __init kvmclock_init(void)
> > return;
> > }
> >
> > + if (!hypervisor_is_type(X86_HYPER_KVM))
> > + kvmclock_vsyscall = 0;
> > +
>
> No need for this;
- On Jul 6, 2018, at 12:02 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Jul 5, 2018, at 2:05 PM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
[...]
> The 0-day bot noticed that __get_user() is unimplemented for 64-bit
> values on arm32 (although get_u
On Fri, Jul 06, 2018 at 01:22:57PM -0500, David Lechner wrote:
>On 07/06/2018 12:21 PM, Jonathan Cameron wrote:
>> On Mon, 2 Jul 2018 22:48:35 -0400
>> William Breathitt Gray wrote:
>>> Is frequency useful for other
>>> applications on its own (perhaps velocity of an automobile device
>>> equipped
I have a first gen HP Proliant DL585 ("G1" but the name was not used
back then) that boots up fine from poweron but usually fails bootup from
warm reboot, somewhere in PCI detection (will try to photographs the
screen some time).
I just stumbled upon an old OpenSolaris thead about the same DL58
This is on a AMD Athlon64 X2 compiling kernel with make -2:
[91550.438790]
[91550.438832] UBSAN: Undefined behaviour in lib/percpu_counter.c:92:14
[91550.438862] signed integer overflow:
[91550.43] 91550438785688
On Fri, Jul 06, 2018 at 12:58:57PM +0200, Sebastian Andrzej Siewior wrote:
> On SMP + !RT migrate_disable() is still around. It is not part of spin_lock()
> anymore so it has almost no users. However the futex code has a workaround for
> the !in_atomic() part of migrate disable which fails because
On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
> void uio_event_notify(struct uio_info *info)
> {
> - struct uio_device *idev = info->uio_dev;
> + struct uio_device *idev;
> +
> + if (!info)
> + return;
> +
> + idev = info->uio_dev;
>
For this one too, I am not su
> >> On Wed, 04 Jul 2018, Janusz Krzysztofik wrote:
> >>> On Tuesday, July 3, 2018 7:31:41 PM CEST Boris Brezillon wrote:
> On Tue, 3 Jul 2018 19:26:35 +0200 Janusz Krzysztofik wrote:
> > chip = find_chip_by_name(p->chip_label);
> > if (!chip) {
> >
> -Original Message-
> From: Roy Pledge
> Sent: Friday, July 6, 2018 9:52 PM
> To: Horia Geanta ; de...@driverdev.osuosl.org;
> linux-arm-ker...@lists.infradead.org; gre...@linuxfoundation.org; Leo Li
> ; Ioana Ciocoi Radulescu
>
> Cc: Laurentiu Tudor ; linux-
> ker...@vger.kernel.org; a..
On 7/6/2018 8:25 AM, Horia Geanta wrote:
> On 7/5/2018 10:41 PM, Roy Pledge wrote:
>> Move the NXP DPIO (Datapath I/O driver) from the staging/fsl-mc/bus/dpio
>> directory to the drivers/soc/fsl directory.
>>
>> The DPIO driver enables access to the Queue and Buffer Managemer (QBMAN)
>> hardware of
Quoting Saravanan Sekar (2018-07-03 02:25:22)
> Add REGMAP as dependency to avoid undefined reference to regmap symbol
>
> Signed-off-by: Saravanan Sekar
Fixes tag? This should come earlier in the series, or even at the
beginning.
On 07/06/18 01:29, Aneesh Kumar K.V wrote:
> This patch steal system RAM and use that to emulate pmem device using the
> e820 platform driver.
>
> This adds a new kernel command line 'pmemmap' which takes the format
>
> to allocate memory early in the boot. This memory is later registered as
> p
On Fri, Jul 06, 2018 at 11:31:13AM -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 13:54 -0400, Don Zickus wrote:
> > On Tue, Jun 26, 2018 at 01:16:11PM -0700, Joe Perches wrote:
> > > On Tue, 2018-06-26 at 14:25 -0400, Prarit Bhargava wrote:
> > > > OSes have additional maintainers that should b
On Fri, Jul 06, 2018 at 07:49:09PM +0300, Andy Shevchenko wrote:
> On Fri, Jul 6, 2018 at 7:24 PM, Tycho Andersen wrote:
>
> > Looking in uart_port_startup(), it seems that circ->buf (state->xmit.buf)
> > protected by the "per-port mutex", which based on uart_port_check() is
> > state->port.mutex
On 07/06/18 11:00, Chris Wilson wrote:
> Quoting Randy Dunlap (2018-07-06 18:55:57)
>> On 07/06/18 10:51, Chris Wilson wrote:
>>> Quoting Randy Dunlap (2018-07-06 18:48:55)
On 07/06/18 02:44, Chris Wilson wrote:
> net_dim.h has a rather useful extension to BITS_PER_BYTE to compute the
This DTS file have initial support Samsung Aries based phones.
Initial version have support for:
- sdcard
- internal memory (present only on non 4g variant)
- max8998 pmic and rtc
- max17040 fuel gauge
- gpio keys
- fimd (no panel driver yet)
- usb (peripherial mode)
- wifi
Signed-off-by: Paweł Ch
Adds missing interrupt-controller property to gph2 block,
to silence following warnings during build
/soc/pinctrl@e020/gph2: Missing interrupt-controller or interrupt-map
property
It's reguired by Samsung aries boards, an S5PV210 based
Samsung Galaxy S (i9000) and Galaxy S 4G phones, which
From: Jonathan Bakker
Document the binding for Samsung Galaxy S Fascinate 4G (SGH-T959P).
Signed-off-by: Jonathan Bakker
Signed-off-by: Paweł Chmiel
Acked-by: Rob Herring
--
Changes from v2:
- Added Acked-by
Changes from v1:
- Added missing commit msg.
--
---
Documentation/devicetree/bi
Document the binding for Samsung Galaxy S (i9000) phone
and whole Samsung Aries devices family (based on S5PV210).
Also because this is first not Exynos-based devices, document this information
at beginning of file.
Signed-off-by: Paweł Chmiel
Reviewed-by: Rob Herring
--
Changes from v2:
- Sq
This commit enables few options which are required to boot
typical Linux distro. It was tested by booting ArchLinux ARM
from sdcard.
Signed-off-by: Paweł Chmiel
---
arch/arm/configs/s5pv210_defconfig | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/configs/s5pv210_de
This patch series adds support for Samsung Galaxy S and Galaxy S 4G.
Both are commercial phone based on Aries family.
Changes from v2:
- Restored pinctrl nodes order
- Correct order of nodes in aries dtsi file
- Added Reviewed-by to one of patches
- Added Acked-by to one of patches
- Squ
Enable config options required for Samsung Aries based phones.
ARM_APPENDED_DTB is also needed, because stock bootloader
does not support loading dtb files.
Signed-off-by: Paweł Chmiel
---
arch/arm/configs/s5pv210_defconfig | 33 +++--
1 file changed, 31 insertions(+)
This is result of running savedefconfig.
It's preparation for adding support for Samsung Aries devices.
Signed-off-by: Paweł Chmiel
---
arch/arm/configs/s5pv210_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/s5pv210_defconfig
b/arch/arm/configs/s5pv210_defconfig
i
From: Jonathan Bakker
This DTS file have initial support Samsung SGH-T959P phone,
also known as Samsung Galaxy S 4G or fascinate4g.
It belongs to Samsung Aries devices family.
Initial version have support for:
- sdcard
- max8998 pmic and rtc
- max17040 fuel gauge
- gpio keys
- fimd (no panel driv
This DTS file have initial support Samsung Galaxy S phone,
also known as i9000.
It belongs to Samsung Aries devices family.
Initial version have support for:
- sdcard
- internal memory
- max8998 pmic and rtc
- max17040 fuel gauge
- gpio keys
- fimd (no panel driver yet)
- usb (peripherial mode)
- w
On Fri, 2018-07-06 at 13:54 -0400, Don Zickus wrote:
> On Tue, Jun 26, 2018 at 01:16:11PM -0700, Joe Perches wrote:
> > On Tue, 2018-06-26 at 14:25 -0400, Prarit Bhargava wrote:
> > > OSes have additional maintainers that should be cc'd on patches or may
> > > want to circulate internal patches.
>
101 - 200 of 584 matches
Mail list logo
