On Mon, Feb 11, 2019 at 09:22:58AM -0800, Dan Williams wrote:
> I honestly don't like the idea that random subsystems can pin down
> file blocks as a side effect of gup on the result of mmap. Recall that
> it's not just RDMA that wants this guarantee. It seems safer to have
> the file be in an
> On Feb 10, 2019, at 9:18 PM, Andy Lutomirski wrote:
>
>
>
> On Feb 10, 2019, at 4:39 PM, Nadav Amit wrote:
>
>>> On Jan 28, 2019, at 4:34 PM, Rick Edgecombe
>>> wrote:
>>>
>>> From: Nadav Amit
>>>
>>> To prevent improper use of the PTEs that are used for text patching, we
>>> want to
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
drivers/firewire/core-device.c: In function ‘set_broadcast_channel’:
drivers/firewire/core-device.c:969:7: warning: this statement may fall
On Sat, Feb 9, 2019 at 3:09 PM Stefan Agner wrote:
>
> Remove the -mno-warn-deprecated assembler flag to make sure the GNU
> assembler warns in case non-unified syntax is used.
>
> Signed-off-by: Stefan Agner
> ---
> Changes in v2:
> - Remove AFLAGS_NOWARN from CFLAGS_ISA
Thanks for making this
On Mon, 11 Feb 2019 02:01:18 -0500
Kimberly Brown wrote:
> On Fri, Feb 08, 2019 at 02:32:09PM -0800, Stephen Hemminger wrote:
> > On Fri, 8 Feb 2019 05:01:12 -0500
> > Kimberly Brown wrote:
> >
> > You are right, the current behavior is broken.
> > It would be good to add a description of
Provide Kconfig entries to enable/disable user stack pointer checking
and also for architectures to expose the system call controls via
prctl() once they have augmented their system call entry path to perform
the necessary checks.
Cc: Kees Cook
Cc: Jann Horn
Cc: Andrew Morton
Cc: Matthew
Hook up a prctl() option to control the level of user stack pointer
checking for the current task. By default, no checking is performed, but
checks can be independently controlled for system calls and page faults.
The option is inherited across fork() and preserved across exec().
Cc: Kees Cook
We now have a comment explaining the first sched_domain based NOHZ kick,
so might as well comment them all.
While at it, unwrap a line that fits under 80 characters.
Co-authored-by: Peter Zijlstra
Signed-off-by: Valentin Schneider
---
kernel/sched/fair.c | 13 +++--
1 file changed, 11
By marking stack VMAs with VM_USERSTACK, we can perform optional checks
on entry to the kernel from system calls and user faults to ensure that
the user stack pointer does indeed point to a stack VMA. If the stack
pointer is found to point elsewhere, a SIGSEGV can be delivered to the
current
Hi all,
I attended an interesting talk at LCA last month that described some of the
security features deployed in OpenBSD [1]. One hardening feature that piqued
my interest was, on syscall entry and page faults from userspace, checking
that the user stack pointer for a task points at pages that
The LLC nohz condition will become true as soon as >=2 CPUs in a
single LLC domain are busy. On big.LITTLE systems, this translates to
two or more CPUs of a "cluster" (big or LITTLE) being busy.
Issuing a nohz kick in these conditions isn't desired for asymmetric
systems, as if the busy CPUs can
In
commit 5fbdfae5221a ("sched/fair: Kick nohz balance if rq->misfit_task_load")
was added a trigger for nohz kicks, which is required to offload misfit tasks
from LITTLE to big CPUs. However, those kicks could be issued a lot more
frequently than what is strictly needed.
This patch-set tunes
Allow the user stack pointer value to be checked on system call entry
and deliver a SIGSEGV if the check does not pass.
Cc: Kees Cook
Cc: Jann Horn
Cc: Andrew Morton
Cc: Matthew Wilcox
Cc: Michal Hocko
Cc: Peter Zijlstra
Signed-off-by: Will Deacon
---
arch/arm64/Kconfig | 1 +
In
commmit 3b1baa6496e6 ("sched/fair: Add 'group_misfit_task' load-balance type")
we set rq->misfit_task_load whenever the current running task has a
utilization greater than 80% of rq->cpu_capacity. A non-zero value in
this field enables misfit load balancing.
However, if the task being
On Mon, Feb 11, 2019 at 09:48:11AM -0800, Dave Hansen wrote:
> On 2/9/19 4:49 PM, Michael S. Tsirkin wrote:
> > On Mon, Feb 04, 2019 at 10:15:52AM -0800, Alexander Duyck wrote:
> >> From: Alexander Duyck
> >>
> >> Add guest support for providing free memory hints to the KVM hypervisor for
> >>
On Mon, Feb 11, 2019 at 06:48:46PM +0100, Jan Kara wrote:
> On Mon 11-02-19 13:59:24, Linux Upstream wrote:
> > >
> > >> Signed-off-by: Chintan Pandya
> > >
> > > NAK.
> > >
> > > This is bound to regress some stuff. Now agreed that using non-atomic
> > > ops is tricky, but many are in places
On 2/11/19 8:48 AM, Jarkko Sakkinen wrote:
> You are missing a cover letter from this patch set. Please have it in
> v2. Also use tag "selftests/tpm2" instead of having two tags in the
> short summaries. Now they look a bit weird.
Since when is the cover letter mandatory?
I understand that is
On Mon, Feb 11, 2019 at 06:07:51PM +0100, Sedat Dilek wrote:
> From: Sedat Dilek
>
> commit 1917d42d14b7 ("fcoe: use enum for fip_mode") introduces a separate
> enum for the fip_mode that shall be used during initialisation handling
> until it is passed to fcoe_ctrl_link_up to set the initial
ARCH_MEMORY_PROBE is a useful thing for testing and debugging hotplug,
but being able to exercise the (arguably trickier) hot-remove path would
be even more useful. Extend the feature to allow removal of offline
sections to be triggered manually to aid development.
Since process dictates the new
On Mon 11-02-19 13:59:24, Linux Upstream wrote:
> >
> >> Signed-off-by: Chintan Pandya
> >
> > NAK.
> >
> > This is bound to regress some stuff. Now agreed that using non-atomic
> > ops is tricky, but many are in places where we 'know' there can't be
> > concurrency.
> >
> > If you can show
On Mon, Feb 11, 2019 at 09:41:19AM -0800, Dave Hansen wrote:
> On 2/9/19 4:44 PM, Michael S. Tsirkin wrote:
> > So the policy should not leak into host/guest interface.
> > Instead it is better to just keep the pages pinned and
> > ignore the hint for now.
>
> It does seems a bit silly to have
On 2/9/19 4:49 PM, Michael S. Tsirkin wrote:
> On Mon, Feb 04, 2019 at 10:15:52AM -0800, Alexander Duyck wrote:
>> From: Alexander Duyck
>>
>> Add guest support for providing free memory hints to the KVM hypervisor for
>> freed pages huge TLB size or larger. I am restricting the size to
>> huge
The inX() I/O accessors must enforce ordering against subsequent calls
to the delay() routines, so that a read-back from a device can be used
to postpone a subsequent write to the same device.
On some architectures, including arm64, this ordering can only be
achieved by creating a dependency on
Hi all,
Ordering port read accesses against non-memory-mapped clocksource reads can
require funky dependency code in conjunction with memory barriers. This isn't
possible to implement with the asm-generic definition of io.h, since the value
read from the device is not passed through to the
Ensure that inX() provides the same ordering guarantees as readX()
by hooking up __io_par() so that it maps directly to __iormb().
Reported-by: Andrew Murray
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/io.h | 1 +
1 file changed, 1 insertion(+)
diff --git
On 2/9/19 4:44 PM, Michael S. Tsirkin wrote:
> So the policy should not leak into host/guest interface.
> Instead it is better to just keep the pages pinned and
> ignore the hint for now.
It does seems a bit silly to have guests forever hinting about freed
memory when the host never has a hope of
On Mon, Feb 11, 2019 at 11:24:02AM -0500, Nitesh Narayan Lal wrote:
>
> On 2/11/19 9:17 AM, Michael S. Tsirkin wrote:
> > On Mon, Feb 11, 2019 at 08:30:03AM -0500, Nitesh Narayan Lal wrote:
> >> On 2/9/19 7:57 PM, Michael S. Tsirkin wrote:
> >>> On Mon, Feb 04, 2019 at 10:15:58AM -0800, Alexander
On Sat, Feb 02, 2019 at 10:54:25PM -0800, Sandeep Patil wrote:
> The 'pss_locked' field of smaps_rollup was being calculated incorrectly.
> It accumulated the current pss everytime a locked VMA was found. Fix
> that by adding to 'pss_locked' the same time as that of 'pss' if the vma
> being
On Fri, Feb 8, 2019 at 6:25 AM Sugaya Taichi
wrote:
>
> This adds a compatible string "socionext,milbeaut-m10v-smp"
> for Milbeaut M10V to the 32 bit ARM CPU device tree binding.
>
> Signed-off-by: Sugaya Taichi
> ---
> Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
> 1 file changed, 1
On Mon, Jan 14, 2019 at 04:45:06PM +0530, Kishon Vijay Abraham I wrote:
> pci_epf_alloc_space() sets the MEM TYPE flags to indicate a 32-bit
> Base Address Register irrespective of the size. Fix it here to indicate
> 64-bit BAR if the size is > 2GB.
>
> Signed-off-by: Kishon Vijay Abraham I
>
On Thu, 7 Feb 2019 at 20:10, Eric Anholt wrote:
>
> Signed-off-by: Eric Anholt
Reviewed-by: Thomas Spurden
> ---
> drivers/gpu/drm/v3d/v3d_drv.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/v3d/v3d_drv.c b/drivers/gpu/drm/v3d/v3d_drv.c
>
On Mon, Feb 11, 2019 at 09:34:25AM -0800, Alexander Duyck wrote:
> On Sat, 2019-02-09 at 19:44 -0500, Michael S. Tsirkin wrote:
> > On Mon, Feb 04, 2019 at 10:15:46AM -0800, Alexander Duyck wrote:
> > > From: Alexander Duyck
> > >
> > > Add the host side of the KVM memory hinting support. With
The lcd display of the gta04 has a backlight but the backlight
was not referenced in the lcd node, so screen blanking did
not turn off the backlight. Fix that.
Signed-off-by: Andreas Kemnade
---
the backlight property for the driver was accepted here:
On Fri, Feb 8, 2019 at 8:05 AM Johan Hovold wrote:
>
> Fixed regulators do not have associated bus addresses and are typically
> placed directly under the root node where their names must still be
> unique despite not having a unit address.
>
> Fix the malformed example node which had a unit
On Mon, Feb 11, 2019 at 08:31:34AM -0800, Alexander Duyck wrote:
> On Sat, 2019-02-09 at 19:49 -0500, Michael S. Tsirkin wrote:
> > On Mon, Feb 04, 2019 at 10:15:52AM -0800, Alexander Duyck wrote:
> > > From: Alexander Duyck
> > >
> > > Add guest support for providing free memory hints to the
On Sat, 2019-02-09 at 19:44 -0500, Michael S. Tsirkin wrote:
> On Mon, Feb 04, 2019 at 10:15:46AM -0800, Alexander Duyck wrote:
> > From: Alexander Duyck
> >
> > Add the host side of the KVM memory hinting support. With this we expose a
> > feature bit indicating that the host will pass the
Hi Arnd,
On Mon, Feb 11, 2019 at 06:11:48PM +0100, Arnd Bergmann wrote:
> On Mon, Feb 11, 2019 at 4:30 PM Will Deacon wrote:
>
> > Given the lack of Intel response here, I went away to do some digging.
> > As evidenced by the commit message, there is certainly an understanding
> > amongst some
On 2/10/19 3:39 PM, Florian Fainelli wrote:
> Hi all,
>
> This patch series finishes by the removal of switchdev_ops. To get there
> we need to do a few things:
>
> - get rid of the one and only call to switchdev_port_attr_get() which is
> used to fetch the device's bridge port flags
On Mon 11-02-19 08:24:38, Steve Magnani wrote:
> Refuse to mount a volume read-write without a coherent Logical Volume
> Integrity Descriptor, because we can't generate truly unique IDs without
> one.
>
> This fixes a bug where all inodes created on a UDF filesystem following
> mount without a
On Mon, Feb 11, 2019 at 05:27:37PM +, Marc Zyngier wrote:
> On 11/02/2019 17:14, Alexander Syring wrote:
> > According to U-Boot dts file enabling the SPI-NOR flash for use in
> > Linux
> >
> > Signed-off-by: Alexander Syring
> > ---
> > .../boot/dts/marvell/armada-8040-mcbin.dtsi | 23
On 2/11/19 7:27 AM, Jonathan Corbet wrote:
> On Sun, 10 Feb 2019 22:34:11 -0800
> Randy Dunlap wrote:
>
>> From: Randy Dunlap
>>
>> Fix markup warning by quoting the '*' character with a backslash.
>>
>> Documentation/vm/slub.rst:71: WARNING: Inline emphasis start-string without
>> end-string.
The "KERNEL I/O BARRIER EFFECTS" section of memory-barriers.txt is vague,
x86-centric, out-of-date, incomplete and demonstrably incorrect in places.
This is largely because I/O ordering is a horrible can of worms, but also
because the document has stagnated as our understanding has evolved.
On 19/12/2018 12:52, Dave Martin wrote:
On Tue, Dec 18, 2018 at 05:59:38PM +, Catalin Marinas wrote:
On Tue, Dec 18, 2018 at 04:03:38PM +0100, Andrey Konovalov wrote:
On Wed, Dec 12, 2018 at 4:02 PM Catalin Marinas wrote:
The summary of our internal discussions (mostly between kernel
On 11/02/2019 17:14, Alexander Syring wrote:
> According to U-Boot dts file enabling the SPI-NOR flash for use in
> Linux
>
> Signed-off-by: Alexander Syring
> ---
> .../boot/dts/marvell/armada-8040-mcbin.dtsi | 23 +++
> 1 file changed, 18 insertions(+), 5 deletions(-)
>
>
On Mon, Feb 11, 2019 at 06:09:43PM +0100, Peter Zijlstra wrote:
>
> Clarify the whole signed vs unsigned issue for atomic_t.
>
> There has been enough confusion on this topic to warrant a few explicit
> words I feel.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> Documentation/atomic_t.txt
On 2019-02-10 2:28 a.m., Peng Fan wrote:
> arm64_memory_present is doing same thing as memblocks_present, so
> let's use common code memblocks_present instead of platform
> specific arm64_memory_present.
I've already sent patches for this[1]. The arm64 one was already queued
up by Catalin.
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 852b6d57dc7f kvm: add device control API.
The bot has tested the following trees: v4.20.7, v4.19.20, v4.14.98, v4.9.155,
v4.4.173, v3.18.134.
v4.20.7: Build OK!
v4.19.20: Build
<20181011184646.154065-1-psh...@google.com>
References: <1549562945-5503-3-git-send-email-pbonz...@redhat.com>
<20181011184646.154065-1-psh...@google.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's
According to U-Boot dts file enabling the SPI-NOR flash for use in
Linux
Signed-off-by: Alexander Syring
---
.../boot/dts/marvell/armada-8040-mcbin.dtsi | 23 +++
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtsi
On Mon, Feb 11, 2019 at 02:32:15PM +0100, Marc Gonzalez wrote:
> Unfortunately, this optimization breaks UFS on systems where vccq
> powers not only the Flash chip, but the host controller as well,
> such as APQ8098 MEDIABOX or MTP8998:
...
> In my opinion, the rationale for the original patch
On Mon, Feb 11, 2019 at 2:24 AM Jan Kara wrote:
>
> On Fri 08-02-19 12:50:37, Dan Williams wrote:
> > On Fri, Feb 8, 2019 at 3:11 AM Jan Kara wrote:
> > >
> > > On Fri 08-02-19 15:43:02, Dave Chinner wrote:
> > > > On Thu, Feb 07, 2019 at 04:55:37PM +, Christopher Lameter wrote:
> > > > >
+Alistair Strachan
On Mon, Feb 11, 2019 at 9:11 AM Greg KH wrote:
>
> On Mon, Feb 11, 2019 at 10:15:18PM +0530, Souptick Joarder wrote:
> > On Mon, Feb 11, 2019 at 9:27 PM Greg KH wrote:
> > >
> > > On Mon, Feb 11, 2019 at 09:21:19PM +0530, Souptick Joarder wrote:
> > > > On Mon, Feb 11, 2019
Hi David,
On Sun, 2019-02-10 at 18:46 +0100, David Kozub wrote:
> On Fri, 8 Feb 2019, Derrick, Jonathan wrote:
>
> > On Mon, 2019-02-04 at 23:44 +0100, David Kozub wrote:
> > > On Mon, 4 Feb 2019, Christoph Hellwig wrote:
> > >
> > > > > + /* first do a discovery0 */
> > > > > + error =
On Mon, Feb 11, 2019 at 06:14:01PM +0100, Alexander Syring wrote:
> According to U-Boot dts file enabling the SPI-NOR flash for use in
> Linux
Some of us already use u-boot on Macchiatobin, and have u-boot in SPI
NOR flash. The u-boot environment is stored at 0x3f currently.
Merging this
Le lundi 11 février 2019 à 16:16 +0100, Hans Verkuil a écrit :
> Hi Maxime,
>
> A quick review below. Note that I am no expert on the codec details, so
> I leave that to others. I'm mainly concentrating on the structs, flags, etc.
>
> On 2/11/19 3:39 PM, Maxime Ripard wrote:
> > From: Pawel
> > >> ---
> > >> net/xdp/xdp_umem.c | 6 ++
> > >> 1 file changed, 2 insertions(+), 4 deletions(-)
> > >>
> > >> diff --git a/net/xdp/xdp_umem.c b/net/xdp/xdp_umem.c index
> > >> 5ab236c5c9a5..25e1e76654a8 100644
> > >> --- a/net/xdp/xdp_umem.c
> > >> +++ b/net/xdp/xdp_umem.c
> > >> @@
Hi all,
Here's the typed component topic branch.
drm-intel maintainers: Please pull, I need this for the mei hdcp work from Ram.
drm-misc maintainers: Please pull, there's a drm doc patch follow-up
that I want to stuff into drm-misc-next.
Greg: The drm side missed our feature cutoff, so will
From: Sedat Dilek
commit 1917d42d14b7 ("fcoe: use enum for fip_mode") introduces a separate
enum for the fip_mode that shall be used during initialisation handling
until it is passed to fcoe_ctrl_link_up to set the initial fip_state.
That change was incomplete and gcc quietly converted in
sorry, I couldn't look at this patch before.
On 02/04, Ivan Delalande wrote:
>
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1660,7 +1660,12 @@ int search_binary_handler(struct linux_binprm *bprm)
> if (retval < 0 && !bprm->mm) {
> /* we got to flush_old_exec() and
On Mon, Feb 11, 2019 at 04:58:39PM +, Mark Brown wrote:
> On Mon, Feb 11, 2019 at 05:50:08PM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Feb 11, 2019 at 02:39:24PM +, Mark Brown wrote:
>
> > > This is more a new feature than a bug fix, it doesn't look like obvious
> > > stable material.
On Mon, 2019-02-11 at 15:39 +0100, Maxime Ripard wrote:
>
> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> index d6eed479c3a6..6fc955926bdb 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
> @@ -645,6 +645,7 @@ struct
On Mon, Feb 11, 2019 at 4:30 PM Will Deacon wrote:
> Given the lack of Intel response here, I went away to do some digging.
> As evidenced by the commit message, there is certainly an understanding
> amongst some developers that inX/outX() are strongly ordered on x86 and
> this was re-enforced
On Mon, Feb 11, 2019 at 10:15:18PM +0530, Souptick Joarder wrote:
> On Mon, Feb 11, 2019 at 9:27 PM Greg KH wrote:
> >
> > On Mon, Feb 11, 2019 at 09:21:19PM +0530, Souptick Joarder wrote:
> > > On Mon, Feb 11, 2019 at 9:10 PM Greg KH
> > > wrote:
> > > >
> > > > On Mon, Feb 11, 2019 at
On Mon, Feb 11, 2019 at 08:44:02AM +0100, Greg KH wrote:
> On Mon, Feb 11, 2019 at 07:40:52AM +1100, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > In commit
> >
> > 344c0152d878 ("selftests: firmware: fix verify_reqs() return value")
> >
> > Fixes tag
> >
> > Fixes: a6a9be9270c87
On Mon, Feb 11, 2019 at 01:47:16PM +0100, Ingo Molnar wrote:
> * Alexey Dobriyan wrote:
> > QUESTION: is it possible to tell gcc "this function is semantically
> > equivalent to memset(3) so make high level optimizations but call it
> > when it is necessary"? I suspect the answer is "no" :-\
>
On Mon, Feb 11, 2019 at 7:39 AM Jonathan Corbet wrote:
>
> Linus, perhaps you'd like to take this one directly?
Done.
Linus
Clarify the whole signed vs unsigned issue for atomic_t.
There has been enough confusion on this topic to warrant a few explicit
words I feel.
Signed-off-by: Peter Zijlstra (Intel)
---
Documentation/atomic_t.txt | 17 +
1 file changed, 17 insertions(+)
diff --git
On Mon, Feb 11, 2019 at 04:17:58PM +0100, David Sterba wrote:
> On Mon, Feb 11, 2019 at 03:17:13PM +0100, Greg Kroah-Hartman wrote:
> > 4.19-stable review patch. If anyone has any objections, please let me know.
>
> This does not IMO belong to stable. It was a preparatory patch for a
> locking
On Mon, Feb 11, 2019 at 8:57 AM Christoph Hellwig wrote:
>
> On Fri, Feb 08, 2019 at 10:35:13AM -0800, Todd Kjos wrote:
> > Binder buffers have always been mapped into kernel space
> > via map_kernel_range_noflush() to allow the binder driver
> > to modify the buffer before posting to userspace
On 2/10/19 11:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190208:
>
on i386:
ERROR: "__umoddi3" [net/wireless/cfg80211.ko] undefined!
ERROR: "__umoddi3" [net/mac80211/mac80211.ko] undefined!
--
~Randy
Hello,
syzbot found the following crash on:
HEAD commit:df3865f8f568 Merge branch 'i2c/for-current' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11274624c0
kernel config: https://syzkaller.appspot.com/x/.config?x=8f00801d7b7c4fe6
On Mon, Feb 11, 2019 at 10:04:32AM -0500, Neil Horman wrote:
> On Sun, Feb 10, 2019 at 10:46:16AM -0200, Marcelo Ricardo Leitner wrote:
> > On Sat, Feb 09, 2019 at 03:12:17PM -0800, David Miller wrote:
> > > From: Marcelo Ricardo Leitner
> > > Date: Wed, 6 Feb 2019 18:37:54 -0200
> > >
> > > >
On Mon, Feb 11, 2019 at 11:35:24AM -0500, Waiman Long wrote:
> On 02/11/2019 06:58 AM, Peter Zijlstra wrote:
> > Which is clearly worse. Now we can write that as:
> >
> > int __down_read_trylock2(unsigned long *l)
> > {
> > long tmp = READ_ONCE(*l);
> >
> > while (tmp >= 0) {
> >
On Mon, Feb 11, 2019 at 5:40 PM Miklos Szeredi wrote:
>
> On Mon, Feb 11, 2019 at 4:07 PM Amir Goldstein wrote:
> >
> > On Mon, Feb 11, 2019 at 4:33 PM Miklos Szeredi wrote:
> > >
> > > On Mon, Feb 11, 2019 at 2:08 PM Amir Goldstein wrote:
> > > >
> > > > On Mon, Feb 11, 2019 at 2:37 PM Miklos
On Mon, Feb 11, 2019 at 05:17:48PM +0200, Oded Gabbay wrote:
> From: Omer Shpigelman
>
> This patch adds the Virtual Memory and MMU modules.
>
> Goya has an internal MMU which provides process isolation on the internal
> DDR. The internal MMU also performs translations for transactions that go
Hello,
syzbot found the following crash on:
HEAD commit:d13937116f1e Linux 5.0-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=143d98a740
kernel config: https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
dashboard link:
On Mon, Feb 11, 2019 at 04:48:30PM +0100, Koen Vandeputte wrote:
>
> On 11.02.19 15:14, Greg Kroah-Hartman wrote:
> > 4.20-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > [ Upstream commit 3831a2a0010c72e3956020cbf1057a1701a2e469 ]
> >
On Mon, Feb 11, 2019 at 11:35:12AM +, Catalin Marinas wrote:
> Hi Dave,
>
> On Wed, Dec 12, 2018 at 05:01:12PM +, Dave P Martin wrote:
> > On Mon, Dec 10, 2018 at 01:50:57PM +0100, Andrey Konovalov wrote:
> > > arm64 has a feature called Top Byte Ignore, which allows to embed pointer
> >
On Fri, Feb 8, 2019 at 10:52 AM Souptick Joarder wrote:
>
> On Thu, Feb 7, 2019 at 10:17 PM Matthew Wilcox wrote:
> >
> > On Thu, Feb 07, 2019 at 09:19:47PM +0530, Souptick Joarder wrote:
> > > Just thought to take opinion for documentation before placing it in v3.
> > > Does it looks fine ?
> >
On Mon, Feb 11, 2019 at 05:50:08PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Feb 11, 2019 at 02:39:24PM +, Mark Brown wrote:
> > This is more a new feature than a bug fix, it doesn't look like obvious
> > stable material.
> Normally we take "new quirks and device ids", and given that this
Am Dienstag, den 04.12.2018, 14:27 +0100 schrieb Stefan Agner:
> Add a fault handler which handles immediate reads in Thumb-2
> mode. Install the appropriate handler depending on which mode
> the kernel has been built. This avoids an "Unhandled fault:
> external abort on non-linefetch (0x1008) at
On Fri, Feb 08, 2019 at 10:35:13AM -0800, Todd Kjos wrote:
> Binder buffers have always been mapped into kernel space
> via map_kernel_range_noflush() to allow the binder driver
> to modify the buffer before posting to userspace for
> processing.
>
> In recent Android releases, the number of
Am Dienstag, den 04.12.2018, 14:27 +0100 schrieb Stefan Agner:
> The custom fault handler is currently only meant to handle kernel
> mode bus faults. Exit in case the abort happened in user mode.
>
> Signed-off-by: Stefan Agner
Reviewed-by: Lucas Stach
> ---
>
On Mon, Feb 11, 2019 at 09:49:07AM -0500, Steven Rostedt wrote:
> On Mon, 11 Feb 2019 15:16:05 +0100
> Greg Kroah-Hartman wrote:
>
> > 4.20-stable review patch. If anyone has any objections, please let me know.
> >
>
> This is not a bug fix and was not meant for stable. Please do not apply.
On Mon, Feb 11, 2019 at 05:49:12PM +0100, Federico Vaga wrote:
> It adds the SPDX tag and it removes the old text about the GPLv2.
>
> Signed-off-by: Federico Vaga
I can convert the platform_data header to SPDX again. No need to resend
because of that.
signature.asc
Description: PGP
On Mon, Feb 11, 2019 at 03:34:20PM +0100, Christian Borntraeger wrote:
>
> On 11.02.2019 15:17, Greg Kroah-Hartman wrote:
> > 4.20-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > [ Upstream commit
The i.MX8MQ uses the same OCOTP block as the i.MX7D, but with
fourfold increase in fuse banks.
Signed-off-by: Lucas Stach
---
drivers/nvmem/imx-ocotp.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/nvmem/imx-ocotp.c b/drivers/nvmem/imx-ocotp.c
index
Add compatible for i.MX8MQ and add both i.MX7D/S and i.M8MQ
to the description.
Signed-off-by: Lucas Stach
---
Documentation/devicetree/bindings/nvmem/imx-ocotp.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/nvmem/imx-ocotp.txt
The i.MX OCOTP controller is used in numerous Freescale/NXP
SoCs from the MXC family, so the strict dependency on the
i.MX6 SoC is too narrow. Broaden it to cover all the MXC
familiy members.
Signed-off-by: Lucas Stach
---
drivers/nvmem/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2
On Mon, Feb 11, 2019 at 02:39:24PM +, Mark Brown wrote:
> On Mon, Feb 11, 2019 at 03:14:53PM +0100, Greg Kroah-Hartman wrote:
>
> > On the Allwinner A64 SoCs, the audio codec has a built-in headphone
> > amplifier. This amplifier has a power supply separate from the rest of
> > the analog
If the Interrupt Flag (IF) is not set, we should not handle the IRQ:
- the line can be shared with other devices
- it can be a spurious interrupt
To avoid reading twice the status register, the ocores_process() function
expects it to be read by the caller.
Signed-off-by: Federico Vaga
Acked-by:
Miscellaneous style fixes from checkpatch
Signed-off-by: Federico Vaga
---
drivers/i2c/busses/i2c-ocores.c | 29 ++---
1 file changed, 18 insertions(+), 11 deletions(-)
diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
index 78085a8..b32d67c
Detecting a timeout is ok, but we also need to assert a STOP command on
the bus in order to prevent it from generating interrupts when there are
no on going transfers.
Example: very long transmission.
1. ocores_xfer: START a transfer
2. ocores_isr : handle byte by byte the transfer
3.
This driver assumes that an interrupt line is always available for
the I2C master. This is not always the case and this patch adds support
for a polling version.
Report from Andrew Lunn:
I did some timing tests for this. On my box, we request a udelay of
80uS. The kernel actually delays for
It adds the SPDX tag and it removes the old text about the GPLv2.
Signed-off-by: Federico Vaga
---
drivers/i2c/busses/i2c-ocores.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
index 5dea7b9..78085a8
This patch set provides improvements to the i2c-ocore driver.
[V5 -> V6]
- remove redundant code introduced in V5 (double read control register)
[V4 -> V5]
- deterministic status of IEN bit in register "CONTROL" at the end of
ocores_init()
- more style fixes
[V3 -> V4]
- add
Folks. I suspect that this isn't actually a ZFS bug but a general
memory manager problem. I would appreciate input from mm folks. I
parked the detailed bug report here for now:
https://github.com/zfsonlinux/zfs/issues/8396
Short story:
When running a ZFS on a Linux 4.19/4.20 NFS server the
On 02/08, Eric W. Biederman wrote:
>
> signal: Always notice exiting tasks
Sorry, I could not look at these patches before...
So I think this one should be reverted, it makes PTRACE_EVENT_EXIT even more
broken.
Once again, why we can't do something like
--- x/kernel/signal.c
You are missing a cover letter from this patch set. Please have it in
v2. Also use tag "selftests/tpm2" instead of having two tags in the
short summaries. Now they look a bit weird.
On Tue, Feb 05, 2019 at 12:28:39PM -0800, Tadeusz Struk wrote:
> Three new tests added:
> 1. Send get random cmd,
On 04/02/2019 15:37, Marc Gonzalez wrote:
> Cc: sta...@vger.kernel.org # 3.15+
> Fixes: 3f0c820664483 ("drivers: of: add initialization code for dynamic
> reserved memory")
> Acked-by: Marek Szyprowski
> Acked-by: Prateek Patel
> Tested-by: Marc Gonzalez
> Signed-off-by: Mike Rapoport
> ---
601 - 700 of 2376 matches
Mail list logo
