mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
synced 2026-11-13 07:31:07 +00:00
712,088 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Quentin Swain
|
f2aee92d18 |
staging: pi433: replace logical not with bitwise
sparse reports the following warning "warning: dubious: x & !y". Replaced te logical not with bitwise to resolve the warning Signed-off-by: Quentin Swain <dudebrobro179@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
Peter Rosin
|
25ff38ca79 |
staging: vboxvideo: remove dead gamma lut code
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are no longer used. Remove the dead code that was not doing anything sensible anyway. Signed-off-by: Peter Rosin <peda@axentia.se> Acked-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
Hans de Goede
|
01d79e9b6a |
staging: vboxvideo: Call fb_deferred_io_cleanup() on cleanup
On driver cleanup we need to call fb_deferred_io_cleanup() if build with CONFIG_FB_DEFERRED_IO set. Suggested-by: Michael Thayer <michael.thayer@oracle.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
|
Hans de Goede
|
70ed0929fc |
staging: vboxvideo: Add dri-devel to lists of email-addresses to send patches to
Patches for the vboxvideo driver should also be Cc-ed to dri-devel, update the TODO file accordingly. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
Cihangir Akturk
|
4a66af0d23 |
staging: vboxvideo: switch to drm_*{get,put} helpers
drm_*_reference() and drm_*_unreference() functions are just compatibility alias for drm_*_get() and drm_*_put() adn should not be used by new code. So convert all users of compatibility functions to use the new APIs. Signed-off-by: Cihangir Akturk <cakturk@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
|
Cihangir Akturk
|
227fe242e0 |
staging: vboxvideo: select DRM_TTM
vboxvideo code uses various ttm_* functions, so it needs "drivers/gpu/drm/ttm/*" to be built. In order to build these objects select DRM_TTM. This commit fixes "ttm_*" undefined build errors. Signed-off-by: Cihangir Akturk <cakturk@gmail.com> Acked-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
Eric Dumazet
|
ff244c6b29 |
tun: handle register_netdevice() failures properly
syzkaller reported a double free [1], caused by the fact
that tun driver was not updated properly when priv_destructor
was added.
When/if register_netdevice() fails, priv_destructor() must have been
called already.
[1]
BUG: KASAN: double-free or invalid-free in selinux_tun_dev_free_security+0x15/0x20 security/selinux/hooks.c:5023
CPU: 0 PID: 2919 Comm: syzkaller227220 Not tainted 4.13.0-rc4+ #23
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
print_address_description+0x7f/0x260 mm/kasan/report.c:252
kasan_report_double_free+0x55/0x80 mm/kasan/report.c:333
kasan_slab_free+0xa0/0xc0 mm/kasan/kasan.c:514
__cache_free mm/slab.c:3503 [inline]
kfree+0xd3/0x260 mm/slab.c:3820
selinux_tun_dev_free_security+0x15/0x20 security/selinux/hooks.c:5023
security_tun_dev_free_security+0x48/0x80 security/security.c:1512
tun_set_iff drivers/net/tun.c:1884 [inline]
__tun_chr_ioctl+0x2ce6/0x3d50 drivers/net/tun.c:2064
tun_chr_ioctl+0x2a/0x40 drivers/net/tun.c:2309
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x443ff9
RSP: 002b:00007ffc34271f68 EFLAGS: 00000217 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000004002e0 RCX: 0000000000443ff9
RDX: 0000000020533000 RSI: 00000000400454ca RDI: 0000000000000003
RBP: 0000000000000086 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000217 R12: 0000000000401ce0
R13: 0000000000401d70 R14: 0000000000000000 R15: 0000000000000000
Allocated by task 2919:
save_stack_trace+0x16/0x20 arch/x86/kernel/stacktrace.c:59
save_stack+0x43/0xd0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xaa/0xd0 mm/kasan/kasan.c:551
kmem_cache_alloc_trace+0x101/0x6f0 mm/slab.c:3627
kmalloc include/linux/slab.h:493 [inline]
kzalloc include/linux/slab.h:666 [inline]
selinux_tun_dev_alloc_security+0x49/0x170 security/selinux/hooks.c:5012
security_tun_dev_alloc_security+0x6d/0xa0 security/security.c:1506
tun_set_iff drivers/net/tun.c:1839 [inline]
__tun_chr_ioctl+0x1730/0x3d50 drivers/net/tun.c:2064
tun_chr_ioctl+0x2a/0x40 drivers/net/tun.c:2309
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
Freed by task 2919:
save_stack_trace+0x16/0x20 arch/x86/kernel/stacktrace.c:59
save_stack+0x43/0xd0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0x6e/0xc0 mm/kasan/kasan.c:524
__cache_free mm/slab.c:3503 [inline]
kfree+0xd3/0x260 mm/slab.c:3820
selinux_tun_dev_free_security+0x15/0x20 security/selinux/hooks.c:5023
security_tun_dev_free_security+0x48/0x80 security/security.c:1512
tun_free_netdev+0x13b/0x1b0 drivers/net/tun.c:1563
register_netdevice+0x8d0/0xee0 net/core/dev.c:7605
tun_set_iff drivers/net/tun.c:1859 [inline]
__tun_chr_ioctl+0x1caf/0x3d50 drivers/net/tun.c:2064
tun_chr_ioctl+0x2a/0x40 drivers/net/tun.c:2309
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
The buggy address belongs to the object at ffff8801d2843b40
which belongs to the cache kmalloc-32 of size 32
The buggy address is located 0 bytes inside of
32-byte region [ffff8801d2843b40, ffff8801d2843b60)
The buggy address belongs to the page:
page:ffffea000660cea8 count:1 mapcount:0 mapping:ffff8801d2843000 index:0xffff8801d2843fc1
flags: 0x200000000000100(slab)
raw: 0200000000000100 ffff8801d2843000 ffff8801d2843fc1 000000010000003f
raw: ffffea0006626a40 ffffea00066141a0 ffff8801dbc00100
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8801d2843a00: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
ffff8801d2843a80: 00 00 00 fc fc fc fc fc fb fb fb fb fc fc fc fc
>ffff8801d2843b00: 00 00 00 00 fc fc fc fc fb fb fb fb fc fc fc fc
^
ffff8801d2843b80: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
ffff8801d2843c00: fb fb fb fb fc fc fc fc fb fb fb fb fc fc fc fc
==================================================================
Fixes:
|
||
Andy Yan
|
b67377430e |
ARM: dts: rockchip: add pwm backlight for rv1108 evb
RV1108 EVB uses pwm0 modulate the backlight, add dt node to enable it. Signed-off-by: Andy Yan <andy.yan@rock-chips.com> Signed-off-by: Heiko Stuebner <heiko@sntech.de> |
||
|
Andy Yan
|
0c2d34aae2 |
ARM: dts: rockchip: add pwm dt nodes for rv1108
Add pwm device tree node for rv1108 soc Signed-off-by: Andy Yan <andy.yan@rock-chips.com> Signed-off-by: Heiko Stuebner <heiko@sntech.de> |
||
Joerg Roedel
|
af6ee6c1c4 | Merge branch 'for-joerg/arm-smmu/updates' of git://git.kernel.org/pub/scm/linux/kernel/git/will/linux into arm/smmu | ||
Kees Cook
|
c715b72c1b |
mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes
Moving the x86_64 and arm64 PIE base from 0x555555554000 to 0x000100000000 broke AddressSanitizer. This is a partial revert of: |
||
Laura Abbott
|
704b862f9e |
mm/vmalloc.c: don't unconditonally use __GFP_HIGHMEM
Commit |
||
zhong jiang
|
73223e4e2e |
mm/mempolicy: fix use after free when calling get_mempolicy
I hit a use after free issue when executing trinity and repoduced it
with KASAN enabled. The related call trace is as follows.
BUG: KASan: use after free in SyS_get_mempolicy+0x3c8/0x960 at addr ffff8801f582d766
Read of size 2 by task syz-executor1/798
INFO: Allocated in mpol_new.part.2+0x74/0x160 age=3 cpu=1 pid=799
__slab_alloc+0x768/0x970
kmem_cache_alloc+0x2e7/0x450
mpol_new.part.2+0x74/0x160
mpol_new+0x66/0x80
SyS_mbind+0x267/0x9f0
system_call_fastpath+0x16/0x1b
INFO: Freed in __mpol_put+0x2b/0x40 age=4 cpu=1 pid=799
__slab_free+0x495/0x8e0
kmem_cache_free+0x2f3/0x4c0
__mpol_put+0x2b/0x40
SyS_mbind+0x383/0x9f0
system_call_fastpath+0x16/0x1b
INFO: Slab 0xffffea0009cb8dc0 objects=23 used=8 fp=0xffff8801f582de40 flags=0x200000000004080
INFO: Object 0xffff8801f582d760 @offset=5984 fp=0xffff8801f582d600
Bytes b4 ffff8801f582d750: ae 01 ff ff 00 00 00 00 5a 5a 5a 5a 5a 5a 5a 5a ........ZZZZZZZZ
Object ffff8801f582d760: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Object ffff8801f582d770: 6b 6b 6b 6b 6b 6b 6b a5 kkkkkkk.
Redzone ffff8801f582d778: bb bb bb bb bb bb bb bb ........
Padding ffff8801f582d8b8: 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZ
Memory state around the buggy address:
ffff8801f582d600: fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8801f582d680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff8801f582d700: fc fc fc fc fc fc fc fc fc fc fc fc fb fb fb fc
!shared memory policy is not protected against parallel removal by other
thread which is normally protected by the mmap_sem. do_get_mempolicy,
however, drops the lock midway while we can still access it later.
Early premature up_read is a historical artifact from times when
put_user was called in this path see https://lwn.net/Articles/124754/
but that is gone since
|
||
Prakash Gupta
|
da094e4284 |
mm/cma_debug.c: fix stack corruption due to sprintf usage
name[] in cma_debugfs_add_one() can only accommodate 16 chars including
NULL to store sprintf output. It's common for cma device name to be
larger than 15 chars. This can cause stack corrpution. If the gcc
stack protector is turned on, this can cause a panic due to stack
corruption.
Below is one example trace:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:
ffffff8e69a75730
Call trace:
dump_backtrace+0x0/0x2c4
show_stack+0x20/0x28
dump_stack+0xb8/0xf4
panic+0x154/0x2b0
print_tainted+0x0/0xc0
cma_debugfs_init+0x274/0x290
do_one_initcall+0x5c/0x168
kernel_init_freeable+0x1c8/0x280
Fix the short sprintf buffer in cma_debugfs_add_one() by using
scnprintf() instead of sprintf().
Link: http://lkml.kernel.org/r/1502446217-21840-1-git-send-email-guptap@codeaurora.org
Fixes:
|
||
Jamie Iles
|
eb61b5911b |
signal: don't remove SIGNAL_UNKILLABLE for traced tasks.
When forcing a signal, SIGNAL_UNKILLABLE is removed to prevent recursive faults, but this is undesirable when tracing. For example, debugging an init process (whether global or namespace), hitting a breakpoint and SIGTRAP will force SIGTRAP and then remove SIGNAL_UNKILLABLE. Everything continues fine, but then once debugging has finished, the init process is left killable which is unlikely what the user expects, resulting in either an accidentally killed init or an init that stops reaping zombies. Link: http://lkml.kernel.org/r/20170815112806.10728-1-jamie.iles@oracle.com Signed-off-by: Jamie Iles <jamie.iles@oracle.com> Acked-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
Michal Hocko
|
6b31d5955c |
mm, oom: fix potential data corruption when oom_reaper races with writer
Wenwei Tao has noticed that our current assumption that the oom victim
is dying and never doing any visible changes after it dies, and so the
oom_reaper can tear it down, is not entirely true.
__task_will_free_mem consider a task dying when SIGNAL_GROUP_EXIT is set
but do_group_exit sends SIGKILL to all threads _after_ the flag is set.
So there is a race window when some threads won't have
fatal_signal_pending while the oom_reaper could start unmapping the
address space. Moreover some paths might not check for fatal signals
before each PF/g-u-p/copy_from_user.
We already have a protection for oom_reaper vs. PF races by checking
MMF_UNSTABLE. This has been, however, checked only for kernel threads
(use_mm users) which can outlive the oom victim. A simple fix would be
to extend the current check in handle_mm_fault for all tasks but that
wouldn't be sufficient because the current check assumes that a kernel
thread would bail out after EFAULT from get_user*/copy_from_user and
never re-read the same address which would succeed because the PF path
has established page tables already. This seems to be the case for the
only existing use_mm user currently (virtio driver) but it is rather
fragile in general.
This is even more fragile in general for more complex paths such as
generic_perform_write which can re-read the same address more times
(e.g. iov_iter_copy_from_user_atomic to fail and then
iov_iter_fault_in_readable on retry).
Therefore we have to implement MMF_UNSTABLE protection in a robust way
and never make a potentially corrupted content visible. That requires
to hook deeper into the PF path and check for the flag _every time_
before a pte for anonymous memory is established (that means all
!VM_SHARED mappings).
The corruption can be triggered artificially
(http://lkml.kernel.org/r/201708040646.v746kkhC024636@www262.sakura.ne.jp)
but there doesn't seem to be any real life bug report. The race window
should be quite tight to trigger most of the time.
Link: http://lkml.kernel.org/r/20170807113839.16695-3-mhocko@kernel.org
Fixes:
|
||
|
Michal Hocko
|
5b53a6ea88 |
mm: fix double mmap_sem unlock on MMF_UNSTABLE enforced SIGBUS
Tetsuo Handa has noticed that MMF_UNSTABLE SIGBUS path in
handle_mm_fault causes a lockdep splat
Out of memory: Kill process 1056 (a.out) score 603 or sacrifice child
Killed process 1056 (a.out) total-vm:4268108kB, anon-rss:2246048kB, file-rss:0kB, shmem-rss:0kB
a.out (1169) used greatest stack depth: 11664 bytes left
DEBUG_LOCKS_WARN_ON(depth <= 0)
------------[ cut here ]------------
WARNING: CPU: 6 PID: 1339 at kernel/locking/lockdep.c:3617 lock_release+0x172/0x1e0
CPU: 6 PID: 1339 Comm: a.out Not tainted 4.13.0-rc3-next-20170803+ #142
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/02/2015
RIP: 0010:lock_release+0x172/0x1e0
Call Trace:
up_read+0x1a/0x40
__do_page_fault+0x28e/0x4c0
do_page_fault+0x30/0x80
page_fault+0x28/0x30
The reason is that the page fault path might have dropped the mmap_sem
and returned with VM_FAULT_RETRY. MMF_UNSTABLE check however rewrites
the error path to VM_FAULT_SIGBUS and we always expect mmap_sem taken in
that path. Fix this by taking mmap_sem when VM_FAULT_RETRY is held in
the MMF_UNSTABLE path.
We cannot simply add VM_FAULT_SIGBUS to the existing error code because
all arch specific page fault handlers and g-u-p would have to learn a
new error code combination.
Link: http://lkml.kernel.org/r/20170807113839.16695-2-mhocko@kernel.org
Fixes:
|
||
Vladimir Davydov
|
f6ba488073 |
slub: fix per memcg cache leak on css offline
To avoid a possible deadlock, sysfs_slab_remove() schedules an
asynchronous work to delete sysfs entries corresponding to the kmem
cache. To ensure the cache isn't freed before the work function is
called, it takes a reference to the cache kobject. The reference is
supposed to be released by the work function.
However, the work function (sysfs_slab_remove_workfn()) does nothing in
case the cache sysfs entry has already been deleted, leaking the kobject
and the corresponding cache.
This may happen on a per memcg cache destruction, because sysfs entries
of a per memcg cache are deleted on memcg offline if the cache is empty
(see __kmemcg_cache_deactivate()).
The kmemleak report looks like this:
unreferenced object 0xffff9f798a79f540 (size 32):
comm "kworker/1:4", pid 15416, jiffies 4307432429 (age 28687.554s)
hex dump (first 32 bytes):
6b 6d 61 6c 6c 6f 63 2d 31 36 28 31 35 39 39 3a kmalloc-16(1599:
6e 65 77 72 6f 6f 74 29 00 23 6b c0 ff ff ff ff newroot).#k.....
backtrace:
kmemleak_alloc+0x4a/0xa0
__kmalloc_track_caller+0x148/0x2c0
kvasprintf+0x66/0xd0
kasprintf+0x49/0x70
memcg_create_kmem_cache+0xe6/0x160
memcg_kmem_cache_create_func+0x20/0x110
process_one_work+0x205/0x5d0
worker_thread+0x4e/0x3a0
kthread+0x109/0x140
ret_from_fork+0x2a/0x40
unreferenced object 0xffff9f79b6136840 (size 416):
comm "kworker/1:4", pid 15416, jiffies 4307432429 (age 28687.573s)
hex dump (first 32 bytes):
40 fb 80 c2 3e 33 00 00 00 00 00 40 00 00 00 00 @...>3.....@....
00 00 00 00 00 00 00 00 10 00 00 00 10 00 00 00 ................
backtrace:
kmemleak_alloc+0x4a/0xa0
kmem_cache_alloc+0x128/0x280
create_cache+0x3b/0x1e0
memcg_create_kmem_cache+0x118/0x160
memcg_kmem_cache_create_func+0x20/0x110
process_one_work+0x205/0x5d0
worker_thread+0x4e/0x3a0
kthread+0x109/0x140
ret_from_fork+0x2a/0x40
Fix the leak by adding the missing call to kobject_put() to
sysfs_slab_remove_workfn().
Link: http://lkml.kernel.org/r/20170812181134.25027-1-vdavydov.dev@gmail.com
Fixes:
|
||
Pavel Tatashin
|
3010f87650 |
mm: discard memblock data later
There is existing use after free bug when deferred struct pages are
enabled:
The memblock_add() allocates memory for the memory array if more than
128 entries are needed. See comment in e820__memblock_setup():
* The bootstrap memblock region count maximum is 128 entries
* (INIT_MEMBLOCK_REGIONS), but EFI might pass us more E820 entries
* than that - so allow memblock resizing.
This memblock memory is freed here:
free_low_memory_core_early()
We access the freed memblock.memory later in boot when deferred pages
are initialized in this path:
deferred_init_memmap()
for_each_mem_pfn_range()
__next_mem_pfn_range()
type = &memblock.memory;
One possible explanation for why this use-after-free hasn't been hit
before is that the limit of INIT_MEMBLOCK_REGIONS has never been
exceeded at least on systems where deferred struct pages were enabled.
Tested by reducing INIT_MEMBLOCK_REGIONS down to 4 from the current 128,
and verifying in qemu that this code is getting excuted and that the
freed pages are sane.
Link: http://lkml.kernel.org/r/1502485554-318703-2-git-send-email-pasha.tatashin@oracle.com
Fixes:
|
||
Luis R. Rodriguez
|
768dc4e484 |
test_kmod: fix description for -s -and -c parameters
The descriptions were reversed, correct this.
Link: http://lkml.kernel.org/r/20170809234635.13443-4-mcgrof@kernel.org
Fixes:
|
||
|
Luis R. Rodriguez
|
2ba293c9e7 |
kmod: fix wait on recursive loop
Recursive loops with module loading were previously handled in kmod by restricting the number of modprobe calls to 50 and if that limit was breached request_module() would return an error and a user would see the following on their kernel dmesg: request_module: runaway loop modprobe binfmt-464c Starting init:/sbin/init exists but couldn't execute it (error -8) This issue could happen for instance when a 64-bit kernel boots a 32-bit userspace on some architectures and has no 32-bit binary format hanlders. This is visible, for instance, when a CONFIG_MODULES enabled 64-bit MIPS kernel boots a into o32 root filesystem and the binfmt handler for o32 binaries is not built-in. After commit |
||
|
Luis R. Rodriguez
|
8ada92799e |
wait: add wait_event_killable_timeout()
These are the few pending fixes I have queued up for v4.13-final. One is a a generic regression fix for recursive loops on kmod and the other one is a trivial print out correction. During the v4.13 development we assumed that recursive kmod loops were no longer possible. Clearly that is not true. The regression fix makes use of a new killable wait. We use a killable wait to be paranoid in how signals might be sent to modprobe and only accept a proper SIGKILL. The signal will only be available to userspace to issue *iff* a thread has already entered a wait state, and that happens only if we've already throttled after 50 kmod threads have been hit. Note that although it may seem excessive to trigger a failure afer 5 seconds if all kmod thread remain busy, prior to the series of changes that went into v4.13 we would actually *always* fatally fail any request which came in if the limit was already reached. The new waiting implemented in v4.13 actually gives us *more* breathing room -- the wait for 5 seconds is a wait for *any* kmod thread to finish. We give up and fail *iff* no kmod thread has finished and they're *all* running straight for 5 consecutive seconds. If 50 kmod threads are running consecutively for 5 seconds something else must be really bad. Recursive loops with kmod are bad but they're also hard to implement properly as a selftest without currently fooling current userspace tools like kmod [1]. For instance kmod will complain when you run depmod if it finds a recursive loop with symbol dependency between modules as such this type of recursive loop cannot go upstream as the modules_install target will fail after running depmod. These tests already exist on userspace kmod upstream though (refer to the testsuite/module-playground/mod-loop-*.c files). The same is not true if request_module() is used though, or worst if aliases are used. Likewise the issue with 64-bit kernels booting 32-bit userspace without a binfmt handler built-in is also currently not detected and proactively avoided by userspace kmod tools, or kconfig for all architectures. Although we could complain in the kernel when some of these individual recursive issues creep up, proactively avoiding these situations in userspace at build time is what we should keep striving for. Lastly, since recursive loops could happen with kmod it may mean recursive loops may also be possible with other kernel usermode helpers, this should be investigated and long term if we can come up with a more sensible generic solution even better! [0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=20170809-kmod-for-v4.13-final [1] https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git This patch (of 3): This wait is similar to wait_event_interruptible_timeout() but only accepts SIGKILL interrupt signal. Other signals are ignored. Link: http://lkml.kernel.org/r/20170809234635.13443-2-mcgrof@kernel.org Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Ingo Molnar <mingo@redhat.com> Cc: Kees Cook <keescook@chromium.org> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: Jessica Yu <jeyu@redhat.com> Cc: Rusty Russell <rusty@rustcorp.com.au> Cc: Michal Marek <mmarek@suse.com> Cc: Petr Mladek <pmladek@suse.com> Cc: Miroslav Benes <mbenes@suse.cz> Cc: Josh Poimboeuf <jpoimboe@redhat.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Shuah Khan <shuah@kernel.org> Cc: Matt Redfearn <matt.redfearn@imgtec.com> Cc: Dan Carpenter <dan.carpenter@oracle.com> Cc: Colin Ian King <colin.king@canonical.com> Cc: Daniel Mentz <danielmentz@google.com> Cc: David Binderman <dcb314@hotmail.com> Cc: Matt Redfearn <matt.redfearn@imgetc.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
Nicholas Piggin
|
92e5aae457 |
kernel/watchdog: fix Kconfig constraints for perf hardlockup watchdog
Commit |
||
Johannes Weiner
|
739f79fc9d |
mm: memcontrol: fix NULL pointer crash in test_clear_page_writeback()
Jaegeuk and Brad report a NULL pointer crash when writeback ending tries
to update the memcg stats:
BUG: unable to handle kernel NULL pointer dereference at 00000000000003b0
IP: test_clear_page_writeback+0x12e/0x2c0
[...]
RIP: 0010:test_clear_page_writeback+0x12e/0x2c0
Call Trace:
<IRQ>
end_page_writeback+0x47/0x70
f2fs_write_end_io+0x76/0x180 [f2fs]
bio_endio+0x9f/0x120
blk_update_request+0xa8/0x2f0
scsi_end_request+0x39/0x1d0
scsi_io_completion+0x211/0x690
scsi_finish_command+0xd9/0x120
scsi_softirq_done+0x127/0x150
__blk_mq_complete_request_remote+0x13/0x20
flush_smp_call_function_queue+0x56/0x110
generic_smp_call_function_single_interrupt+0x13/0x30
smp_call_function_single_interrupt+0x27/0x40
call_function_single_interrupt+0x89/0x90
RIP: 0010:native_safe_halt+0x6/0x10
(gdb) l *(test_clear_page_writeback+0x12e)
0xffffffff811bae3e is in test_clear_page_writeback (./include/linux/memcontrol.h:619).
614 mod_node_page_state(page_pgdat(page), idx, val);
615 if (mem_cgroup_disabled() || !page->mem_cgroup)
616 return;
617 mod_memcg_state(page->mem_cgroup, idx, val);
618 pn = page->mem_cgroup->nodeinfo[page_to_nid(page)];
619 this_cpu_add(pn->lruvec_stat->count[idx], val);
620 }
621
622 unsigned long mem_cgroup_soft_limit_reclaim(pg_data_t *pgdat, int order,
623 gfp_t gfp_mask,
The issue is that writeback doesn't hold a page reference and the page
might get freed after PG_writeback is cleared (and the mapping is
unlocked) in test_clear_page_writeback(). The stat functions looking up
the page's node or zone are safe, as those attributes are static across
allocation and free cycles. But page->mem_cgroup is not, and it will
get cleared if we race with truncation or migration.
It appears this race window has been around for a while, but less likely
to trigger when the memcg stats were updated first thing after
PG_writeback is cleared. Recent changes reshuffled this code to update
the global node stats before the memcg ones, though, stretching the race
window out to an extent where people can reproduce the problem.
Update test_clear_page_writeback() to look up and pin page->mem_cgroup
before clearing PG_writeback, then not use that pointer afterward. It
is a partial revert of
|
||
Intiyaz Basha
|
d2896116db |
liquidio: fix Smatch error
Fix Smatch error by not dereferencing iq pointer if it's NULL.
See http://marc.info/?l=kernel-janitors&m=150296723301129&w=2
Also, remove unnecessary parentheses.
Fixes:
|
||
|
Eric Dumazet
|
9620fef27e |
ipv4: convert dst_metrics.refcnt from atomic_t to refcount_t
refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
Matthew Dawson
|
a0917e0bc6 |
datagram: When peeking datagrams with offset < 0 don't skip empty skbs
Due to commit
|
||
Arnd Bergmann
|
2ad93fa37f |
Non-urgent fixes for omaps for v4.14 merge window. These all
can wait for the merge window as we have not seemed to hit any of these so far: - Fix error handling in omap_ocp2scp_probe affecting runtime PM error path - Drop broken RPM status update for omap_device - Two fixes for of_irq_get() usage that can return 0 -----BEGIN PGP SIGNATURE----- iQJFBAABCAAvFiEEkgNvrZJU/QSQYIcQG9Q+yVyrpXMFAlmV1ZwRHHRvbnlAYXRv bWlkZS5jb20ACgkQG9Q+yVyrpXOggBAAww/zeW/QgmQjVgcDlVRYYM+ZgJNnhZB8 BMZzXXr0+OGmpdC6oV3134Ww+ZDRacRWZIAL8fTqLm1eoCb0BJDGcwh3yleLoVqG AS96ogWrZjlLvu2KQXnJeZCksEpkgxm+8HJTn2uw3x3TRIqx8s//vA39wufV3BN0 mWSiolH0ri4/ucIPYVCLXJMF6/h0L8yVg8xmNxUlSAAgvBgewDjgp85WF/vsdiG1 /gzbO7cgy0mUxH0uBpi0LoSr3cFkzO6/p5oM4+613BoI7qK3KRQFt3hWB5JG0Z0C ldRfFSANjzKTadzxjh74fWIoItIKw1Pa8vnuqMtXP8Rse9/h9fukbdlwDJfeH2lA 7fZC033SLvHcY8xwhwohtzKEM8FhdIWis8pZIA8AL8u/B4tRFKKjDq0ePWfWNvTF ceuC/7DdbmmVejFTie6ddSHl/BqCNV7p+L9obAdIrxfZqFXA2OdAlBc49vUeByeP SlrfwXDOsYqOyuDmgQXZtOW2ZobbVbQjV16YLN5myZfkMACALdt2mpr/Lpg0lwSg tmkmeXwLSmwFtJbJpLYt+Fh08Pgh05q27y5h3xyAyGn1x2Ie7fpNqlS7X5lYn/9f 7oHykqzNbVzVvioBl6DBfYdofoBt1OXK8zi/ThaMeqAo0IclTfhrJwGwfJWnGMyi rklzIc0WwKQ= =+wbL -----END PGP SIGNATURE----- Merge tag 'omap-for-v4.14/fixes-not-urgent-v2-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into next/cleanup Pull "non-urgent fixes for omaps for v4.14" from Tony Lindgren: Non-urgent fixes for omaps for v4.14 merge window. These all can wait for the merge window as we have not seemed to hit any of these so far: - Fix error handling in omap_ocp2scp_probe affecting runtime PM error path - Drop broken RPM status update for omap_device - Two fixes for of_irq_get() usage that can return 0 * tag 'omap-for-v4.14/fixes-not-urgent-v2-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap: ARM: OMAP4+: PRM: fix of_irq_get() result checks ARM: OMAP3+: PRM: fix of_irq_get() result check ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq bus: omap-ocp2scp: Fix error handling in omap_ocp2scp_probe |
||
|
Arnd Bergmann
|
f4da0ed9d6 |
Qualcomm ARM64 Based defconfig Updates for v4.14
* Enable Qualcomm IPQ8074 clocks and pinctrl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZl1NOAAoJEFKiBbHx2RXVQ4sP/i9r8j6VhdoSSbJH2Lyp3J1X Rz8j11MoD5sNB1invy0jNKjO9SPTljyZQFl9HWtlp5A/bMpt3PxN1u1N+musdhvn tdt76L/9x2IvdjqNz8OYex4NGidFhpP07Ji4z1HBG/OqCmD4LBurxkaRalUzp3Fx 4hF5YuQ2c++JKibb5myFqIsB3xcSVqs5jX8eQQMT53oNJrQvBVFQiX8TE2/vyq3O /TSDu3t1pnKkgdPkw9SQdij42oFITkI9XnB8jBY8MSFcIbwgIRFd1A/d9SacUVc1 kJHb+UvoMJuyH1jqrerGxCNRXSaPJ7XyiFJTVu9fYmkiMCHHg7FL59bkNHJLjkyg uIjhrjghzLuh98klEkOdi/GLo5Y9gO7eaZDROGQg82a7Q8gNkf0xx+rmG+RSor1X eHz/LjBPngmihX/cHgqL1jT9wq/PJR1bghHyPtrPPyAgGj5mwsGNyiPAE+0Y9Nys N+0k1pmrvv7mpfEVpX1I6aOpKUnRfydS1L4lAOXQFNXh6Ey2ksaAUX6fdfze+tEJ s8Irs+hxQW3rGwXjfaYykHIGAlmt0SQC/SQNhLplGbkJcFZzhRU+s/OtppC8XNB0 bxFJAUZ0//PzxijdvqXX3Qj8HuSTu3rDSLyhvXu65ohRL7jVI386xsD4H1mp4geS i+ZU3K5MsnPULGIFEG/r =cSAn -----END PGP SIGNATURE----- Merge tag 'qcom-arm64-defconfig-for-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux into next/arm64 Pull "Qualcomm ARM64 Based defconfig Updates for v4.14" from Andy Gross: * Enable Qualcomm IPQ8074 clocks and pinctrl * tag 'qcom-arm64-defconfig-for-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux: arm64: defconfig: Enable QCOM IPQ8074 clock and pinctrl |
||
|
Arnd Bergmann
|
e517030e26 |
Reset controller changes for v4.14
- constify zx2967 reset_ops
- add a convenience API to manage an array of resets
- let deassert report success and let assert report success for shared resets
if the reset controller driver does not implement (de)assert.
- add HSDKv1 reset driver
- remove Gemini reset controller, the driver is made obsolete
by a combined clock/reset driver in drivers/clk
- fix the total number of reset lines in the sunxi driver
- various uniphier updates and fixes:
- remove sLD3 SoC support
- simplify system reset register and bit definitions
- add audio systems, video input subsystem, and analog amplifiers reset
controls
-----BEGIN PGP SIGNATURE-----
iQJMBAABCAA2FiEEBsBxhV1FaKwXuCOBUMKIHHCeYOsFAlmWg5MYHHBoaWxpcHAu
emFiZWxAZ21haWwuY29tAAoJEFDCiBxwnmDrEqoQAKSQDhwA5ZyBd216PoUSaLqf
tTGrJc/atfs+cDiqSyQDQ5vN0dTMnPV+YjGmwITg55ZGQTJRTq5nVhwM6y0CaASN
PE7U/9Ma/8GWOjtC+6hun6tAHeuX3fMq2cYK8BSL+D7MQr+zkIgEQx3YsbR/0Np7
qmawpZSKAvIxrpVkQiVrsxmVvxi23GdncGUPDHtKhAW4N1T3ywogpW/7t6AcDZZl
XIa09fIRxfB9VECIXPfe/CDkTHPcKgrxP80/AQJksRmWKBtFU3dRktYVscqUplz7
gS3EelAJ3NYscqWQevCXSvGsSpiNJfePKNLRrDSTKX+eKbAignHvcRhJ6YuP4QrY
t7ZGm7VZf+HSY/XYXbcXEO8zcaf3LFT1lO3KAQ3/nmFie/CuVCC+Dpl74OPsBvcD
+3uhQHqvm8AwnxBmTRtMNH3AtaDFPxT9hbebhsoJKujSb5+5aC4ygDAnY0E6QWfJ
wYG/qKz6+dtrFVIOZG3TFjz2/kgjXRd8zegYtxn20KH1Qk/i+JqaIofbwPvPWAKS
A5vi6sLt6AruRUh213E9+Pi+EWQs1Qhexqjk1rtna9RUkMmu2Qbx50hKkgdgE4Q7
EWcQSB43bpGRo5xt4zhy7fnBPj3zxjJK9gAzeGNrbN16z5gulHarpLWb9X5ujli4
9zv7wk00SQIaSqlVFKBM
=YW4N
-----END PGP SIGNATURE-----
Merge tag 'reset-for-4.14' of git://git.pengutronix.de/git/pza/linux into next/drivers
Pull "Reset controller changes for v4.14" from Philipp Zabel:
- constify zx2967 reset_ops
- add a convenience API to manage an array of resets
- let deassert report success and let assert report success for shared resets
if the reset controller driver does not implement (de)assert.
- add HSDKv1 reset driver
- remove Gemini reset controller, the driver is made obsolete
by a combined clock/reset driver in drivers/clk
- fix the total number of reset lines in the sunxi driver
- various uniphier updates and fixes:
- remove sLD3 SoC support
- simplify system reset register and bit definitions
- add audio systems, video input subsystem, and analog amplifiers reset
controls
* tag 'reset-for-4.14' of git://git.pengutronix.de/git/pza/linux:
reset: uniphier: add analog amplifiers reset control
reset: uniphier: add video input subsystem reset control
reset: uniphier: add audio systems reset control
reset: sunxi: fix number of reset lines
reset: uniphier: do not use per-SoC macro for system reset block
reset: uniphier: remove sLD3 SoC support
Revert "reset: Add a Gemini reset controller"
ARC: reset: introduce HSDKv1 reset driver
reset: make (de)assert report success for self-deasserting reset drivers
reset: Add APIs to manage array of resets
reset: zx2967: constify zx2967_reset_ops.
|
||
|
Arnd Bergmann
|
354865087b |
ZTE SoC updates for 4.14:
- Select PINCTRL for ZTE platform, so that pinctrl driver for ZX296718
can be enabled.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABAgAGBQJZlpAcAAoJEFBXWFqHsHzOsIUIAJ1AonMc+E4nx4Y1TC02QCxL
I0ddb8fZRYhttW/o/6bkSAi1kxeaR2c1KfgtshgRRTQbs3+PFIu5TNDtIlSKhaAy
aDeTLqJCBdqxHk6e3dqAuOWY+3g/3cIgx8UYxHf49l5D5AwjHIb3y3x+GkC9Ne27
nsTFDWiJx05eZ01oT6w6FbXjFjR7FgUx5ckONIoE6Xpts4NccUh5cgyh7yTk77GP
Nu49eur9zBX4Dp3VeeKeuQouxXFfsCblqd1Yl2bHzNdqIfokxockIl+45u/uu49b
eltyVBDDWLdCGf/s+SZtnHyKUOXrjMaTuXiOUshTWv0tn3r3Q5EhWyLh1TullAE=
=hSae
-----END PGP SIGNATURE-----
Merge tag 'zte-soc-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into next/arm64
Pull "ZTE SoC updates for 4.14" from Shawn Guo:
- Select PINCTRL for ZTE platform, so that pinctrl driver for ZX296718
can be enabled.
* tag 'zte-soc-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux:
arm64: select PINCTRL for ZTE platform
|
||
|
Arnd Bergmann
|
32f4049a1f |
This pull request contains ARM64 defconfig changes for Broadcom ARM64-based
SoCs for 4.14, please pull the following: - Markus enables the Broadcom STB AVS thermal monitoring driver as a module which is currently queued in Rui Zhang's tree -----BEGIN PGP SIGNATURE----- iQIcBAABCAAGBQJZldFbAAoJEIfQlpxEBwcEZQcP/2XN6xFj3M+O2Ynl9IQmy30L E7liU0F+I2jjl8oFlZs2MtHykKYPvcInMPCuA0AsImJRVfabFEZVG6/vE1IVkOt/ YCVcnxuA22HHjY+XJdRqL8WbvaHl9EqRaZApAs0XNiZzBTSkG56aYkT/HehdAh19 OaX0zpBHY4xS3D0UTQzorlQbpH572nqPZeG2QBNLGrJ/+N7gv1+2SXxIyRPPgJKg cCLJH2FQqkJBfKL0U+mfDNhJGHeOvg67gcScDIbV6kyhTUqldyWeNt3gcGtjKUZa /2wcsC/0mXnXAfi9xt4ocU4hs6+HrihDG1wkxCVs21FTS6h7Hh1tTst0+I3oO29Z Uo0Ktg3RNfKglylSSKxJYtz0pyKz3lhjq9iJzWSZxR5LoFDPuBMgGlall1xDF3LV IEkmYw9kMRCJ6MQQvrRWRaVnr4YW6k5aI99rh19wzKYCNqvq1TyEO60EDY4S+/Xv 986unwlKpQvA/xAX7Na6B03M1MGSK1uTN6FTJdVR3yrprMafjs7JpVceAQojOwAP 6BS4tXkyxJ3QtYtHFfbWWzrv3W4FxkmFb5vgDMUGTDTuI4rtnTVPfVoBrb5niAKA Q1DIOxfxCpgXjAho/8dTcnFyG5AyekzZULHcl2T/3+dV1EQLhpyAPlvlw0Aylxz4 0Pou+My6cZnyZF58liR2 =xrY6 -----END PGP SIGNATURE----- Merge tag 'arm-soc/for-4.14/defconfig-arm64' of http://github.com/Broadcom/stblinux into next/arm64 Pull "Broadcom defconfig-arm64 changes for 4.14" from Florian Fainelli: This pull request contains ARM64 defconfig changes for Broadcom ARM64-based SoCs for 4.14, please pull the following: - Markus enables the Broadcom STB AVS thermal monitoring driver as a module which is currently queued in Rui Zhang's tree * tag 'arm-soc/for-4.14/defconfig-arm64' of http://github.com/Broadcom/stblinux: arm64: defconfig: add CONFIG_BRCMSTB_THERMAL |
||
|
Arnd Bergmann
|
ac9ae4dfff |
ARM: tegra: Changes for v4.14-rc1
Contains a single fix for platforms with more than 2 GiB of memory running on a kernel with LPAE enabled. -----BEGIN PGP SIGNATURE----- iQJHBAABCAAxFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAlmW+8ATHHRyZWRpbmdA bnZpZGlhLmNvbQAKCRDdI6zXfz6zocORD/9yp/PI/vuF1pn5fZ/pNomw3MzMbvT3 am+w3L42Rt3JMfnX6hZyFgD7CeMuFeZu6HxeXmift7hWirmLeGlExPG2K44goBjr a3x520XVGkZ/sIRNtJ+5bXx+7de4+7b08s6Prrdx0wfGNhmQtpbr3ghDnd6GUKp3 phThCBGJf2t2wozc0vmXa5GUhJWf5yHOsp69U3U46uxW3Xm5o8EzSh21J+2uO35Z spFkJvfbHcK957UrWkjaMUd9G2Hhj21305axJUy1uu9okFpwMEbqVEus4NgkxME4 PGwM6922FQtplLs9rWNe2yTPz9YJzTw6qyv54tr0xaeoOERk4VC8nmSYcwQ5UCs6 QuwcvpfCsmPQDo4cduvrTuRBBgQZENOH9jHUP9V2NqOISmGE8yUBGeDsVQnI38C7 gSIQkBkeJzbVIY8ykAb5LdiiJwfbBBuon0CQtcXC6E9ZAO+kp/N0F7xQU5L1YGBN L5p8RApFOyRTqi7986XdOju91oGRg/GK/lkf7AifL5jsYaKA/SoQALi9QiGeluOW Fc1uUUu8gR6FrMPKRXgnDOzw1M9cLXrWKpKHCpEKDG5cbJB5yJzSoBr45v75GtZj dXW6mGmjpyFoVMCvvQ5W6b818wwqV0E3E4fXPDCQyrY6oBKGuvqolih4ncrPI3Si CyTV0Ec9dy+1NQ== =1dt0 -----END PGP SIGNATURE----- Merge tag 'tegra-for-4.14-arm-core' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into next/soc Pull "ARM: tegra: Changes for v4.14-rc1" from Thierry Reding: Contains a single fix for platforms with more than 2 GiB of memory running on a kernel with LPAE enabled. * tag 'tegra-for-4.14-arm-core' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux: ARM: tegra: Select appropriate DMA options for LPAE |
||
|
Arnd Bergmann
|
03f8935992 |
firmare: Changes for v4.14-rc1
This contains a single bug fix that can lead to a crash in some rare situations. Since this has never been reported to happen with the level of support that exists upstream, this isn't considered critical. -----BEGIN PGP SIGNATURE----- iQJHBAABCAAxFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAlmW+vsTHHRyZWRpbmdA bnZpZGlhLmNvbQAKCRDdI6zXfz6zoe6TD/wOig/uUCC0l84fsDMVFMXdLYwqiL6o n+ZaxLzh8Ncm5lppanTxaGybVX5uC3LPv0YatzdTUPDTA67tw68jf/o6gJBk+0XM nl++uW+f47DuNEUjCTt+Uem7nQl1JcaLLCn/+tlSpp/b1yhFIdf0PY/+UzR9ZPpf H+qmWlL7g3K846TtHTysnoXINru38mPdQDcX6eeCB7vke+hV7hIsvvwZrI3GrTWf JXr7kXrplVFbTWtn/M2LlMgVhEwB6YUK0gSEvv91QDsxqPdjSJaNCrmqx5vZk7b0 n78PbQ05tnVCSioAmegOZB8wyGiLsYshollyHaPtbrQCoom/Zz0kA5x7lIaaXX5h VvOF+XqKwqYcfOwz1Iijo3olj3P/KGjC15orGKSsXwuOtfgFxLGojFejUOklkmmu 5/Ip82gcD9Daszts1RywSoMU2RZmJnYn4i+P9KHefLQtpBRcqtL8GP1lZCoZLfIu DI8oVG4prYXssla/t3gVF/CfSrAzmwd5g7z49Dxfb8P9Cqy6JsqCVEBe06NReN44 xDWKI/FZY3KZGXh2okuz6LDVCBZhc89Q9ArJik9KBg+oUaW7gl2DUqXcqfiiWI8x TxqNj+L4ohHFkTXlXV/ikRctE+ope9djA5Kvu+ClAdQXBHWJc7E3hyluJNR9wRoG tOYeDHz0/NfSMA== =Kxki -----END PGP SIGNATURE----- Merge tag 'tegra-for-4.14-firmware' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into next/drivers Pull "firmare: Changes for v4.14-rc1" from Thierry Reding: This contains a single bug fix that can lead to a crash in some rare situations. Since this has never been reported to happen with the level of support that exists upstream, this isn't considered critical. * tag 'tegra-for-4.14-firmware' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux: firmware: tegra: set drvdata earlier |
||
|
Arnd Bergmann
|
f2970be50a |
soc/tegra: Changes for v4.14-rc1
Contains a fix for unbalanced reference counting of device tree nodes in the PMC-based generic power domains code. A second change moves the SoC device registration code from its old location in arch/arm/mach-tegra to drivers/soc/tegra so that it can be shared between 32-bit and 64-bit ARM Tegra SoCs. -----BEGIN PGP SIGNATURE----- iQJHBAABCAAxFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAlmW+3ITHHRyZWRpbmdA bnZpZGlhLmNvbQAKCRDdI6zXfz6zocmaEACeb9YuHAXaLz4ujzE8JiDmjIIKTtbd 16d75z/d29vVfxCzKAV7yzqugJjPsvc1J6IsWA5g9m+0O36chgpqaQq6AOmTP4us zE9WRXG922aGu3++9YQVFA3I+ew/9SKBMDJ53JptP8oQsHNERolgNgV5OAeX1SQ7 XBrGLvsnLWtYIj4QjtkbTQhRy8/O7r4kl/mNWuh5LP+dmYA5dfd8v2d2w2xBGKua 4w9f1iLK8fJnBoRXNZj+e/d4LFsYuZcElsqQ46fHN0APAjg9TBuTvYGTAmWeAP8b VEKjTR1Jaix8XLxyjjIivEUT591BnO15NLfZ3yC8/1wY64daRtE3oFuH3VLM5fgt E1mrIAd3SJSt2zD/ubh1+Dm21e7bXehajsb+AL6t6wheHbVlM4jf0rjszzGGZof6 s76IY1WcuSYQYx0u0S3upPGBcjPqw+JEf/4hJQ8H/RXpx70v1KDP4dUW6PR58jxk cPZeOtcqLGWvCfg04/U20OjWn2mpVDU1Gbr7nO5J0xyam/IG7fiDgU4hFLC7HqoE q67QI7/kssGRmYuWQMBu+cqLj6saOXTUDLvGCrN508r04HbuVwhK4t42P+tmaK8G ujDNcsdcekjvWn7tgxm5LV7m0puCWbblBwV2WTaFaR5Jv/EKRBQisBByDndNxy8h lFV8tbUTL8tvNw== =Qbm4 -----END PGP SIGNATURE----- Merge tag 'tegra-for-4.14-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into next/drivers Pull "soc/tegra: Changes for v4.14-rc1" from Thierry Reding: Contains a fix for unbalanced reference counting of device tree nodes in the PMC-based generic power domains code. A second change moves the SoC device registration code from its old location in arch/arm/mach-tegra to drivers/soc/tegra so that it can be shared between 32-bit and 64-bit ARM Tegra SoCs. * tag 'tegra-for-4.14-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux: soc/tegra: Register SoC device soc/tegra: Fix bad of_node_put() in powergate init |
||
|
Arnd Bergmann
|
9da95d8f5b |
- add mt7623a smp support
- scpsys: reduce code duplication - scpsys: add mt7622 support - pmic wrapper: make of_device_ids constant -----BEGIN PGP SIGNATURE----- iQJLBAABCAA1FiEEiUuSfQSYnG8EMsBltDliWyzx00MFAlmVfMEXHG1hdHRoaWFz LmJnZ0BnbWFpbC5jb20ACgkQtDliWyzx00MGyw//b1Ax9tAl+eX1phkU5r/sdyd6 KS72i4pMo4yyyuoPCLKhpwH2rL1UrgY/T6f6bEyVf6KNhzgUvx1P4Y5PSpo2R+Jv AJ9lIypXCxUvmrQL5FOuQ+8SY694SSm1IBsoJ70pNA+/m7//Yfk0eiueUa7epNI0 dhrHOvNaZPQbnCUjFa+qdkK8x04MoAKUQcq9sp1vpcvYTL7V6OrW2V6kc0iqwaN1 G91QW2r+XAgO1KA1PIMqC8E9v06dhYWuaPI3SMCIqp/NFnNZA8j58KySzW7+nB/B 7IlDARYDyzokw/JTUuWSlOOPh425xVSExidkTbCgb7m0Lt8i3CvW89yXsqKSL/+U Ezek9w/rJNGb5OoLhT1xQfy6XrXFCW78gl9HKZhbrM1eBiEeJctLlmQula57nyJH qIlCMjuueKYHUKTGT5LXidNbGesfx4vLt6v803XouF4D3NCIqPahdFqtBnEfsOEO l1xwbTSq44VSFtUKSdRrgt6e8Uxa25ftOkbKlS8vIPcsYJ7gnK7r2/ERWNJF8F+f x4toGOKhOVRTRwAZIx9ncKnQp08g6jegiRHW4JrJNmPnUwwC00I06+Jiltg5KJIP ZqgfjXesdjD660pWl70YGMRtdUNLuNgZRnyXg1CM94CfOimUBZi2PXhoK1Wm/7sj Db0QrPV4DQHti15Q0ig= =IW3o -----END PGP SIGNATURE----- Merge tag 'v4.13-next-soc' of https://github.com/mbgg/linux-mediatek into next/drivers Pull "arm: mediatek: soc updates for v4.14" from Matthias Brugger: - add mt7623a smp support - scpsys: reduce code duplication - scpsys: add mt7622 support - pmic wrapper: make of_device_ids constant * tag 'v4.13-next-soc' of https://github.com/mbgg/linux-mediatek: soc: mediatek: add SCPSYS power domain driver for MediaTek MT7622 SoC soc: mediatek: add header files required for MT7622 SCPSYS dt-binding soc: mediatek: reduce code duplication of scpsys_probe across all SoCs dt-bindings: soc: update the binding document for SCPSYS on MediaTek MT7622 SoC soc: mtk-pmic-wrap: make of_device_ids const. ARM: mediatek: add MT7623a smp bringup code |
||
Linus Torvalds
|
cc28fcdc01 |
Changes since last time:
- Don't leak resources when mount fails - Don't accidentally clobber variables when looking for free inodes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABCgAGBQJZlfFsAAoJEPh/dxk0SrTrTmQP/1Yga+FXQ1vjsyi0SyPRupwd 6beHGDEyLSmYaZKqye8v/nJlNVT8nmJofM20Hyu04f41K4oShQrzrI7jOOscOaYY jGEpgbx9fpLPD7AupgDvEDcrZyzZD/j3XxoSsOEGe5D6m3t2X0B4RtHz3jtj2s3e wkaBTE7GpzwrhC+9L+3AAtlpNlwkbjcCz0Wfrqlo8DjvRHTlutbYF51fthLJACtz U5XgNlxrjQlxGxn4IRHEqxmxWKz2iF4aQHGIX8OEGyt8J3YEO2t3K+nSalWduiBc mynExqVFIdGddNWoW4au6IKkPEahytsPVAiyt1TQMNvgkOMCO6DfUz+WmyQbd483 2r/xUbMdP78RQsUDXdrIEcTiHs/GEfQmIxUongf/0au3r2wmpQfbqzQuBxhuVbzW 1tQQsDKrO3r+GeEEoBPehtWVF/QPlQvlpT6pfft69kcgp5ukPDvOyOoM0ZEbKy72 zBWEs5O/kHUOBBXXdV2cqazplq3LyLuBMok1y+gUXXOyXfEd2w9LPqmoK3RmqSQ2 FnZc2A6tjko1NDLrSkq/uYRXIGi7ZAfxzqhP0L6XLUnu+kjN/A2Xb6pdfB9Wngl2 8nLVbBL/d28lMVPLJ5M3yxoVcQbIfcNqNA5QmWVCmPUqEwgMQFCsbBdYMKILI0ok B76xb0VyZBP5l9QJ514S =vJe/ -----END PGP SIGNATURE----- Merge tag 'xfs-4.13-fixes-5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux Pull xfs fixes from Darrick Wong: "A handful more bug fixes for you today. Changes since last time: - Don't leak resources when mount fails - Don't accidentally clobber variables when looking for free inodes" * tag 'xfs-4.13-fixes-5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux: xfs: don't leak quotacheck dquots when cow recovery xfs: clear MS_ACTIVE after finishing log recovery iomap: fix integer truncation issues in the zeroing and dirtying helpers xfs: fix inobt inode allocation search optimization |
||
|
Arnd Bergmann
|
6d6776e140 |
mvebu dt64 for 4.14 (part 2)
- Enable uSD on ESPRESSObin (Armada 37xx based board) - Add NAND support on Armada 7K/8K SoCs - Enable USB host on Armada-7040-DB and Armada-8040-DB boards -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlmWtIYACgkQCwYYjhRyO9V67ACfUFPrkPl8Qn34OAjklU+hVPR9 YJIAn0EI8S47gAuQe0bzEmU45qALL/Xv =Vf0A -----END PGP SIGNATURE----- Merge tag 'mvebu-dt64-4.14-2' of git://git.infradead.org/linux-mvebu into next/dt64 Pull "mvebu dt64 for 4.14 (part 2)" from Gregory CLEMENT: - Enable uSD on ESPRESSObin (Armada 37xx based board) - Add NAND support on Armada 7K/8K SoCs - Enable USB host on Armada-7040-DB and Armada-8040-DB boards * tag 'mvebu-dt64-4.14-2' of git://git.infradead.org/linux-mvebu: ARM64: dts: marvell: enable USB host on Armada-8040-DB ARM64: dts: marvell: enable USB host on Armada-7040-DB ARM64: dts: marvell: add NAND support on the CP110 ARM64: dts: marvell: armada-37xx: Enable uSD on ESPRESSObin arm64: dts: marvell: Fully re-order nodes in Marvell CP110 dtsi files |
||
Rob Herring
|
6b5fc336c4 |
arm64: dts: apm: fix PCI bus dtc warnings
dtc recently added PCI bus checks. Fix these warnings. Signed-off-by: Rob Herring <robh@kernel.org> Cc: Duc Dang <dhdang@apm.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de> |
||
|
Rob Herring
|
2666797050 |
ARM: dts: versatile: fix PCI bus dtc warnings
dtc recently added PCI bus checks. Fix these warnings. Signed-off-by: Rob Herring <robh@kernel.org> Cc: Russell King <linux@armlinux.org.uk> Signed-off-by: Arnd Bergmann <arnd@arndb.de> |
||
|
Rob Herring
|
a7a34d116f |
ARM: dts: spear13xx: fix PCI bus dtc warnings
dtc recently added PCI bus checks. Fix these warnings. Signed-off-by: Rob Herring <robh@kernel.org> Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Cc: Shiraz Hashim <shiraz.linux.kernel@gmail.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de> |
||
|
Arnd Bergmann
|
fc9cc2797a |
Second Round of Renesas ARM64 Based SoC DT Updates for v4.14
* Add PFC device node to R-Car D3 (r8a77995) This is a step towards enabling devices that use multiplexed pins - including ethernet - on boards that use the r8a7796 SoC. * Add USB nodes to R-Car M3-W (r8a7796) This is a step towards enabling USB devices on boards that use the r8a7796 SoC. * Use newly added Gen-3 fallback compat string This is consistent with ongoing efforts to use per-generation fallback strings where appropriate across devices found on R-Car SoCs. The aim of the effort being to strike a balance between the limited information available about the compatibility of devices found on different SoCs and the desire to ease enabling devices on new SoCs. This has no run-time effect due to the presence of a per-SoC compat string. * Cleanup whitespace and extra LVDS port label Minor cleanups, no run-time effect. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZlV36AAoJENfPZGlqN0++cwMQAIieFfQzDET0/2dGSWB6oDAt fSCCHh4l6B5vufUyhV4rDjm8drKgT5sMTkAYh4Y1oq69NV3BFnFb0gr3BY58Qwyv yz4s2o3UNShVcCuSK8rJaMdr8BOBmKoS2WBMjIOBO+znfhfP1zCbBgDNIanSGMY2 8fmBBB3CF76NM0Juh5FmD1bUsxvzX3ZboyWxQY9u5aIrvcvhau4dcifkKJpcp5gT b/0z0Vi2ZraPE1JOlIHghc0ph10TYVl1pYINgWhhtybNSd9D2TXgGFfn5XZkdk2+ +Az+mookjAsXIm7hj/3la1KflnT67oWNb6rJkz3TWHkNSFW0AbZb0iEnzP02mIMX 6DsUW8jaAxxviMavLB8+Qi5UMM4q7PY78AWB4VA4etkQf5GL/98Lr/jLayd4vyOt tJLeE+c89J+eEbql4UfrTl/fdUIjJzH5P9RMG/DUpqAZpw8GlFjx5ZttPKOMUU7V dN5wuG+ujneedn6Kb0RHeI09/q4MVPcEjxbOGq/Xqljp1wYPf44tkDkBd9ecs047 A9fXEuv3qgU5N8iNyT31nudzNbDTIfDYFg7XBcX5pY7BAnXKbTvfl1mFzHyX9Pm8 GBGFndOrX4b9aPj3JqXMldQOVpKT5YMyFbA2vl4Z1bbqFqE3cdgHSEp5NcC93qRv 1colO4fJ/JaDLKsP5dfH =6XqO -----END PGP SIGNATURE----- Merge tag 'renesas-arm64-dt2-for-v4.14' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/dt64 Pull "Second Round of Renesas ARM64 Based SoC DT Updates for v4.14" from Simon Horman: * Add PFC device node to R-Car D3 (r8a77995) This is a step towards enabling devices that use multiplexed pins - including ethernet - on boards that use the r8a7796 SoC. * Add USB nodes to R-Car M3-W (r8a7796) This is a step towards enabling USB devices on boards that use the r8a7796 SoC. * Use newly added Gen-3 fallback compat string This is consistent with ongoing efforts to use per-generation fallback strings where appropriate across devices found on R-Car SoCs. The aim of the effort being to strike a balance between the limited information available about the compatibility of devices found on different SoCs and the desire to ease enabling devices on new SoCs. This has no run-time effect due to the presence of a per-SoC compat string. * Cleanup whitespace and extra LVDS port label Minor cleanups, no run-time effect. * tag 'renesas-arm64-dt2-for-v4.14' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas: arm64: dts: r8a77995: add pfc device node arm64: dts: r8a7796: Add HSUSB device node arm64: dts: r8a7796: Add USB-DMAC device nodes arm64: dts: r8a7796: Add USB3.0 host device node arm64: dts: r8a7796: add USB2.0 Host (EHCI/OHCI) device nodes arm64: dts: r8a7796: add usb2_phy device nodes arm64: dts: r8a7795: correct whitespace of companion property arm64: dts: r8a7795: Use R-Car SATA Gen3 fallback compat string arm64: dts: salvator-common: Remove extra LVDS port label |
||
|
Linus Torvalds
|
70bfc741f8 |
Merge branch 'for-linus' of git://git.kernel.dk/linux-block
Pull block fixes from Jens Axboe:
"A small set of fixes that should go into this release. This contains:
- An NVMe pull request from Christoph, with a few select fixes.
One of them fix a polling regression in this series, in which it's
trivial to cause the kernel to disable most of the hardware queue
interrupts.
- Fixup for a blk-mq queue usage imbalance on request allocation,
from Keith.
- A xen block pull request from Konrad, fixing two issues with
xen/xen-blkfront"
* 'for-linus' of git://git.kernel.dk/linux-block:
blk-mq-pci: add a fallback when pci_irq_get_affinity returns NULL
nvme-pci: set cqe_seen on polled completions
nvme-fabrics: fix reporting of unrecognized options
nvmet-fc: eliminate incorrect static markers on local variables
nvmet-fc: correct use after free on list teardown
nvmet: don't overwrite identify sn/fr with 0-bytes
xen-blkfront: use a right index when checking requests
xen: fix bio vec merging
blk-mq: Fix queue usage on failed request allocation
|
||
|
Arnd Bergmann
|
1e95f2ca6e |
Second Round of Renesas ARM Based SoC DT Bindings Updates for v4.14
* Add RZ/G1M (r8a7743) binding to apmu driver This allows SMP to be supported on the RZ/G1M SoC * Add bindings for iW-RainboW-G22D-SODIMM RZ/G1E SODIMM development kit This is in preparation for adding DTS to support this hardware -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZlWDoAAoJENfPZGlqN0++u+IP/097qIrO8k05/G4pulox3N+H bRa8FF6UNQq5XIKy3I/jz19zNDo0FxnqF23kVaDzakrgS0A/B9cTL3k9XNEsPaty 1D5BOj4Dv53rpMJjXrVpaM54wRmdvVCk8VVHPwoduJgn9TTv6vOFa8TxN4L7aI6T pu/RjKOVN4V31b+0dENs0Uz4u/AEcpTfrjuzrVseO2zBfLnJHSRUnxXhnuCUC6qd db7xDVVvwhd6B0GuAzu2c0EBhXKO/C6epF5aqiGN0auZgeNcjT6EEOUpmhmQxFOm 9iURVNUtwUQPcqzHvJ4bJdLN0OltSIxiBySvd59YTu62v4gvBxfPS4HE1lx9B/F2 PWbQWX4s+38vB5qmZSznFDavVRYEUPdvjuk9OdkzhNyYyRVie010+qcqcdALB5rj ehB/3V0J+yr+7RfwNECiWSqZZWACZHtCsMXz1VK/AE8P9Ltr7IinvgJ/+6aRGONa BGOn5NTuTKh7fFrwJ64Pt8vcSjOHBXX4dMbQkENYQloYPjFY9ClkhMHsacG8kxdZ 27EXAZcFgSTLfWdbL6nzjRf5Np6JNn6CSSr7z/8Iw8KEPgj5D0MKSyVjHZPNyvbI U+SDDnXt99nDcZSifWzf/U4Vfhoe+cybfc2umz4OkjOTI6Ep8jRdrsEEf+xy+wmN 40ipe1aPB1oyqKR1AG44 =uw/C -----END PGP SIGNATURE----- Merge tag 'renesas-dt-bindings2-for-v4.14' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/dt Pull "Second Round of Renesas ARM Based SoC DT Bindings Updates for v4.14" from Simon Horman: * Add RZ/G1M (r8a7743) binding to apmu driver This allows SMP to be supported on the RZ/G1M SoC * Add bindings for iW-RainboW-G22D-SODIMM RZ/G1E SODIMM development kit This is in preparation for adding DTS to support this hardware * tag 'renesas-dt-bindings2-for-v4.14' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas: dt-bindings: apmu: Document r8a7743 support ARM: shmobile: document iW-RainboW-G22D SODIMM SOM Development Platform ARM: shmobile: document iW-RainboW-G22M-SM SODIMM System on Module |
||
|
Arnd Bergmann
|
81f794d701 |
Second Round of Renesas ARM Based SoC DT Updates for v4.14
* Use newly added Gen-3 fallback compat string This is consistent with ongoing efforts to use per-generation fallback strings where appropriate across devices found on R-Car SoCs. The aim of the effort being to strike a balance between the limited information available about the compatibility of devices found on different SoCs and the desire to ease enabling devices on new SoCs. This has no run-time effect due to the presence of a per-SoC compat string. * Enable second CPU core on RZ/G1M (r8a7743) The RZ/G1M has two CA15 cores running at up to 1.5GHz * Enable frequency scaling on RZ/G1M (r8a7743) * Add six I2C cores to RZ/G1M (r8a7743) SoC DT This is a step towards enabling these cores on boards that use this SoC * Add CEC clock for HDMI transmitter to R-Car M2-W (r8a7791) Koelsch Hans Verkuil says "The adv7511 on the Koelsch board has a 12 MHz fixed clock for the CEC block. Specify this in the dts to enable CEC support." * Add PFC support to RZ/G1E (r8a7745) SoC and add Ethernet and SCIF2 pins to SK-RZG1E board. This allows the kernel to control multiplexed pins for Ethernet and SCIF2 rather than relying on setup inherited at boot. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZlWSzAAoJENfPZGlqN0++hzgQAK58yzDkHbv4fyI0Y/9sflVW V+xHtpXEr6hHiBLejrxoahUD1ljdYOroeADRnO0td6DVdCwQDVs1MlcoDGzfSLM9 9PKwhsCEUDWXW72AZMym8P/sng8LzFffLJx8m71aMTHAGLiLGCis3aUxiDtqNWNG kx9Ouc1fGXLVm2WmKGDPF1QphAH03zhZIzqaPjNJfZoqZVPmnsIpjTbmRFjCZFbv l3R/Ys9O1gBarO1USww4kRsBGYhRbWHZKiPbL0iZ4T5cSiAiu9i2584opdE+Z0ty OXsrAMTZPXmkwOVguypjPA+H77Hk4+/ACO2RVnOJ1Ois5qeVSDdPaOPdbq1pw7mn 3WJtgyO5bfHqrniRQsAi5K2uDlL19hHc//R8lwZA2mRF23Tz/UkiCXnEkzxlAM03 3UI7lkJvp1umK1fMZwG6sDwxj+jQ17p6M+S9LinA1vnVxK7ucLRf05IehlZHYUx0 R6SoAhHauxjx4ZKYwB0cGpKGvwSmXCFRy/zsNdeawgjuCJKIAgPKXd0HoNkH9VoA eJ+qVopj9xZSHrrgkhRKKggig91/24STwzgVjhdY16cXZgYL+iN6+epXItGd6IZK xx0cCYarDMTPjWcICwdM4krKE/boshX9e/Ts05RQv1W4TwQ08eA8Ro5JhQDGRz4L Tb5gC7Wnpi0sCvyicxeD =G9vX -----END PGP SIGNATURE----- Merge tag 'renesas-dt2-for-v4.14' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/dt Pull "Second Round of Renesas ARM Based SoC DT Updates for v4.14" from Simon Horman: * Use newly added Gen-3 fallback compat string This is consistent with ongoing efforts to use per-generation fallback strings where appropriate across devices found on R-Car SoCs. The aim of the effort being to strike a balance between the limited information available about the compatibility of devices found on different SoCs and the desire to ease enabling devices on new SoCs. This has no run-time effect due to the presence of a per-SoC compat string. * Enable second CPU core on RZ/G1M (r8a7743) The RZ/G1M has two CA15 cores running at up to 1.5GHz * Enable frequency scaling on RZ/G1M (r8a7743) * Add six I2C cores to RZ/G1M (r8a7743) SoC DT This is a step towards enabling these cores on boards that use this SoC * Add CEC clock for HDMI transmitter to R-Car M2-W (r8a7791) Koelsch Hans Verkuil says "The adv7511 on the Koelsch board has a 12 MHz fixed clock for the CEC block. Specify this in the dts to enable CEC support." * Add PFC support to RZ/G1E (r8a7745) SoC and add Ethernet and SCIF2 pins to SK-RZG1E board. This allows the kernel to control multiplexed pins for Ethernet and SCIF2 rather than relying on setup inherited at boot. * tag 'renesas-dt2-for-v4.14' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas: ARM: dts: r8a7791: Use R-Car SATA Gen2 fallback compat string ARM: dts: r8a7790: Use R-Car SATA Gen2 fallback compat string ARM: dts: r8a7743: Add OPP table for frequency scaling ARM: dts: r8a7743: Add APMU node and second CPU core ARM: dts: koelsch: Add CEC clock for HDMI transmitter ARM: dts: sk-rzg1e: add Ether pins ARM: dts: sk-rzg1e: add SCIF2 pins ARM: dts: r8a7745: add PFC support ARM: dts: r8a7743: Add I2C DT support |
||
|
Arnd Bergmann
|
a282ac2d41 |
Qualcomm ARM64 Updates for v4.14 Part 2
* Add IPQ8074 SoC and HK01 board support -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZl1PKAAoJEFKiBbHx2RXVq40QAIoFRYmWBywq/UquEf0qH6UF y7Y0Ig7ba6lXLhKJlUx8bQYXtU97CLDuJXw9pIvh8IxPZmYKWQd9zG3FfZZIaRSf /zN9SDBZV7Q8JyZXL7u1GCxFC4bouhc6L9n8ttYUGjeiYh4Xq2ZqwOL+YAQhnSQn UuYS3eb21/0rCZmWzkdOU7rYSutkhhaCtRWh9QcndZKoOquvnvQgWlVkOELnTbND 4kc2txOJ8juRnzwpvlfYsOnFet4XQC/RCz1vGSgu3ljXCC5rTYMKd7AstHnsAc2x NNJCyi0fdMEbPSAvI3nK7fFinS8rppKfNmAG4T4UjmAtu19wCKmlPblRYhIgZwk9 YngZh2FbHLSdV/rDJG4E6UoktvV+PeRlajTZofT0su4wLJPxFiTTZWlOPmg/Y9Gf dVBw+FRFJRj2L4gu5n+8pKvsQsc9zAv1h+YMJoVRv8Zz45M9QoihPMapAjwDu2hz PtCSjKO9ebnl6J8GpI3FaKtzjywLCG12/xp+6NUmSa8lz6sxkTPFwcgRU4Dm+bj6 xa8Tt63lz/rEfuOBj/+niadSh/mATEiOvUlt0AEVNt/JfjOIxq/s0FDpGwYzJRFE z63TvqNZ7V+irEweJPmkyvMR2huqYHo32FqGkXkZQIIyUHzEnnQJWJn3D1wmhYWX btJBe1OV0SKm9+xc8XwY =JCl4 -----END PGP SIGNATURE----- Merge tag 'qcom-arm64-for-4.14-2' of git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux into next/dt64 Pull "Qualcomm ARM64 Updates for v4.14 Part 2" from Andy Gross: * Add IPQ8074 SoC and HK01 board support * tag 'qcom-arm64-for-4.14-2' of git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux: arm64: dts: Add ipq8074 SoC and HK01 board support |
||
|
Arnd Bergmann
|
f928e1030b |
ARM: tegra: Device tree changes for v4.14-rc1
One fix for Tegra124 to hook the host1x device up with the SMMU. The remainder of this enables USB device mode on a couple of boards where the port is currently unused. -----BEGIN PGP SIGNATURE----- iQJHBAABCAAxFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAlmW/EYTHHRyZWRpbmdA bnZpZGlhLmNvbQAKCRDdI6zXfz6zodegD/0Ql+A5xvkH6spXD9ElDHU0GFDSsBxz 0m5k/G3SeLy0X01LTbrT+aQYwu+TbGlUMFfWoTzc2AZCc4dJdCcyVUc5iHLbZDlR ZkwW+x7jSYYGxzVCjw7iWUVWIV4nzYlK9gKVPNoy8wObBvkp47eLhoEbuMjTm6/p AXziTVu5CSe513Gktw6jnXyreARy1zGAbp/nrRt4zl1dFfZvuForQmVYhxqEJgvl ZV76Dz4UAf29tKVi2Qzv884sK7mNI0PiRk5zxo3uHMzWB4mPeDU7cfy4OsRr5Epe gzoKmx+Aagjlznr4C3qhH4ZgNiXki4JDSVRljMpZkd18ugGDdkjuE/EjEAvVFG6+ hu9kx3AIrwo1A2xGvE3QzmFOlZufo6rAoosbsX/6wtJW/X9B6auGxI1NXjJmcXCC U/6QMtFwYreRyck5mitEoOMbvXCtriABVBKkq4VvXKAWp3g63d/cK5aZTlVoiaPj w6I/rQ3CdZhkGWtRDqzDglFs+28vbfsoYVsAR8g7iHYg5+BixtDudzb6BP96IOU1 So49JjqNpOYIT4iEJQzeG7QYumHIFV/rW9OSfHS5J4tB6icrwbKjX78boen7YDqN VoVfSUJwNgLPBB9iQKhEo2QVbOoHOxd/88/0BkS3C3IqsWmyCroTG4vTfHWBVR2Y O3nMCfR5pifpOg== =0VoF -----END PGP SIGNATURE----- Merge tag 'tegra-for-4.14-arm-dt' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into next/dt Pull "ARM: tegra: Device tree changes for v4.14-rc1" from Thierry Reding: One fix for Tegra124 to hook the host1x device up with the SMMU. The remainder of this enables USB device mode on a couple of boards where the port is currently unused. * tag 'tegra-for-4.14-arm-dt' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux: ARM: tegra: Enable UDC on AC100 ARM: tegra: Enable UDC on Jetson TK1 ARM: tegra: Enable UDC on Dalmore ARM: tegra: Enable UDC on Beaver ARM: tegra: Register host1x node with IOMMU binding on Tegra124 |
||
|
Arnd Bergmann
|
fdccc4fc45 |
ZTE device tree updates for 4.14:
- A clean up patch from Shawn Lin to remove the deprecated dwmmc
property 'num-slots'.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABAgAGBQJZloxmAAoJEFBXWFqHsHzOmiYH/3dBPc18iMgsEjHJ73FUJCb8
RvIxN/o4W60Kokm+vsrNHx3LfZYUCfgQCeHlYCHpL1jFGpwD0DBxNQ9QlMDG+TCa
IN+c32aB0a0U0RHl+c5jKLqPy4eVvD4NNDWGVpwjSpK/MARrsKjhEwr/Yjcrj87c
+miIiXBmTsUhzwXQF1UkK719rXI7tgZQNqO06qxJN0QxwKajZPyZzRbe1kgI1xQK
k7F8WG3OGxyRJYRt/qnovnCv7lDX1Jk4S0ySqhocEyyqkqUOXElRARWZOyP3D8CY
wJQIHRzlM/ffqDpbQDa17YuGmnMgsHZ/+Fa8tHvdL353Ow0TM6KkjoRGTd8F4GI=
=WoGP
-----END PGP SIGNATURE-----
Merge tag 'zte-dt-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into next/dt
Pull "ZTE device tree updates for 4.14" from Shawn Guo:
- A clean up patch from Shawn Lin to remove the deprecated dwmmc
property 'num-slots'.
* tag 'zte-dt-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux:
ARM: dts: zte: remove num-slots from zx296702-ad1
|
||
|
Arnd Bergmann
|
3d12971ebd |
i.MX device tree updates for 4.14:
- A series from Andrew Lunn updating imx6-rdu2 board to enable
on-board Marvell switch support.
- A series from Jagan Teki updating imx6ul-isiot and imx6ul-geam to
enable audio card and FEC support.
- Add support for Toradex Ixora V1.1 and Apalis Evaluation Board
along with some cleanups.
- Enable DRM display support for imx6ul-evk and imx7d-sdb board.
- Add i.MX53 based Beckhoff CX9020 board support.
- Add GPMI NAND and APBH DMA devices for i.MX7 and enables NAND support
for imx7-colibri board.
- Enables the ADV7180 analog video decoder sensor connected to the
IMX6 IPU on various Gateworks Ventana boards.
- Minor updates on misc boards and some random cleanups.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABAgAGBQJZloV7AAoJEFBXWFqHsHzOeIAH/ieM8fZEeUHO9waD4aoQJulp
kQHbJFKlEaQrB/y9LVUmNae0w/dpOaf5k/NVtfLQAZQhMqN6Y9XFQA0fnUAgiNbs
fknQpL6VnrO7nGUDEbIUommrRDPEVN9SEiiPpLpD938QjUDxTAibb8++QQOHC/S6
NLQbYMvubDTaUXkOiRodLQU6U/RQ5Byzmu+ytuKjlB1la0OzMegebD/OMXZtgysx
hcEDVBIEZmQO1TPrl5p6IZjjdHs1ua4gfRLQWq1RPXECakHJuyCPKILibyRID15j
w0C+sTxP1uIN950VYzufrbLIdyheWHSrx0FZSWa7tnus8W+h8kBAUd6NxyHLiyU=
=0Cwx
-----END PGP SIGNATURE-----
Merge tag 'imx-dt-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into next/dt
Pull "i.MX device tree updates for 4.14" from Shawn Guo:
- A series from Andrew Lunn updating imx6-rdu2 board to enable
on-board Marvell switch support.
- A series from Jagan Teki updating imx6ul-isiot and imx6ul-geam to
enable audio card and FEC support.
- Add support for Toradex Ixora V1.1 and Apalis Evaluation Board
along with some cleanups.
- Enable DRM display support for imx6ul-evk and imx7d-sdb board.
- Add i.MX53 based Beckhoff CX9020 board support.
- Add GPMI NAND and APBH DMA devices for i.MX7 and enables NAND support
for imx7-colibri board.
- Enables the ADV7180 analog video decoder sensor connected to the
IMX6 IPU on various Gateworks Ventana boards.
- Minor updates on misc boards and some random cleanups.
* tag 'imx-dt-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux: (47 commits)
ARM: dts: imx6q-bx50v3: Enable i2c recovery mechanism
ARM: dts: imx6q-apalis-eval: add support for Apalis Evaluation Board
ARM: dts: imx6: add support for Toradex Ixora V1.1 carrier board
ARM: dts: imx6qdl-apalis: imx6q-apalis-ixora: use i2c from dwc hdmi
ARM: dts: imx6q-apalis-ixora: add camera i2c bus definition
ARM: dts: imx6q-apalis-ixora: get rid of obsolete fusion comment
ARM: dts: imx6qdl-apalis: reword cam i2c comment
ARM: dts: imx6qdl-apalis: imx6q-apalis-ixora: get rid of tegra legacy gen1_i2c comment
ARM: dts: imx6q-apalis-ixora: combine aliases
ARM: dts: imx6qdl-apalis: split usdhc1 pinctrl to support 4- and 8-bit
ARM: dts: imx6q-apalis-ixora: fix usdhc2 pinctrl property
ARM: dts: imx6ul-liteboard: Support poweroff
ARM: dts: imx: add CX9020 Embedded PC device tree
ARM: dts: imx53: add alternative UART2 configuration
ARM: dts: imx53: add srtc node
dt-bindings: arm: Add entry for Beckhoff CX9020
ARM: dts: i.MX25: add RNGB node to dtsi
ARM: dts: imx6ul-14x14-evk: Remove unrelated pin from ENET group
ARM: dts: imx7d-sdb: Add flexcan support
ARM: dts: imx7-colibri: add NAND support
...
|
||
|
Arnd Bergmann
|
522a6efef2 |
This pull request contains Broadcom ARM-based SoCs Device Tree changes for
4.14, please pull the following: - Eric moves the bcm2837 DT file from arm64 to arm because it created a maintenance problem and would have required either duplication or cross merges - Stefan changes how the pinmuxing is defined and pushes it at the board level to support Raspberry Pi Zero Wireless. He then adds supports for the actual Raspberry Pi Zero Wireless board along with binding documentation. Stefan also defines a proper SMP enable-method property and binding for BCM2836 (Raspbery Pi 2) - Rafal describes the BCM5301X USB ports correctly in Device Tree such that it becomes possible to assign them to specific LED triggers (e.g: USB activity). He does the same thing for BCM53573 and defines default LED triggers for USB. - Jon provides a fix for Northstar Plus which consists in correctly defining the "dma-coherent" property for peripherals which are DMA coherent. He also does a bit of re-arrangement of the USB DT nodes and finally adds USB 3 PHY and host controller support for NorthStar Plus - Florian adds support for Broadcom's BCM947189ACDBMR reference board which is based on BCM47182/53573 and which supports external MoCA (BCM6802) - Ray fixes the wrong UART2 base address for Cygnus - Scott moves the v3d node in the proper unit address order and defines the correct UART alias for the BCM91130_entphn reference board to be UART3 - Jason adds the DT node for the Cygnus Cortex-A9 Performance Monitoring Unit - Jonathan adds a bunch of additional peripherals to the Cygnus DTS include file: SDHCI, Keypad, SPI, DMA and pinmux configurations - Raveendra adds the Cygnus OHCI and EHCI Device Tree nodes -----BEGIN PGP SIGNATURE----- iQIcBAABCAAGBQJZldUgAAoJEIfQlpxEBwcEUIgQAIdyDJn+q+mxVhtY8m5xd7ru +pnSvzJoL0nNUALPez4SGRBSBsv8oH3zO77aLQcPEcy1W+FCvjGI3eh22bm5PkOO UASbrw5c5RfwYI/fVVkTqoZT3d4Xo4ZXTe+ML0wVS7x9Hw8ozQPBCc5hRJ7PQYaO U1Ttvpud354xgCFXnvtadDwwTa2W9MdPtsTkrk42Q+p06KZTlONUslAL+DI1RlUw Zf81r/93YzmEbsPpnG4nlW1dJTTILPE7AFQfJQ47Fg+aJ/suhYMlEH2EvxqgXhh0 FzAWd0Zo1p83chArSQdKGEkS+RvSGuSX1D1n1ZVMO2NJZd3RSqLVy6zUB38f+5Eu 0nOxwxWaG/isyGJ9DtMSyM7ZdgZhYSEI847DC3zOah3/kNquF/NmFFUOPzW79D53 WJ/qvjxYZ9fcy3p2W3Vk8LSNiBeiQGQ+zodpRjTrHIBocqQUf2yxSeepGV9zeHk8 ZwwUmtSE/qZd+MAqiki1DdUIWqHvkvOx0BbYZHLqA3ND2Vz6n6hVvMMMDo2+TyN7 WNhOdrM7Gwt+LNYyW6Gjrvxe5wIYn6Gw3+wPbxTSZH7lBbBC/c56cR0V3nJkpuiS C5OwCx1Miocz61GPjKtkaYat3cnRum96X5hsadTLJ/cNscNKdIXqUkPtZ6jLs7VI SbSQS4Im7fdGaGeRRsj1 =WUr3 -----END PGP SIGNATURE----- Merge tag 'arm-soc/for-4.14/devicetree' of http://github.com/Broadcom/stblinux into next/dt Pull "Broadcom devicetree changes for 4.14" from Florian Fainelli: This pull request contains Broadcom ARM-based SoCs Device Tree changes for 4.14, please pull the following: - Eric moves the bcm2837 DT file from arm64 to arm because it created a maintenance problem and would have required either duplication or cross merges - Stefan changes how the pinmuxing is defined and pushes it at the board level to support Raspberry Pi Zero Wireless. He then adds supports for the actual Raspberry Pi Zero Wireless board along with binding documentation. Stefan also defines a proper SMP enable-method property and binding for BCM2836 (Raspbery Pi 2) - Rafal describes the BCM5301X USB ports correctly in Device Tree such that it becomes possible to assign them to specific LED triggers (e.g: USB activity). He does the same thing for BCM53573 and defines default LED triggers for USB. - Jon provides a fix for Northstar Plus which consists in correctly defining the "dma-coherent" property for peripherals which are DMA coherent. He also does a bit of re-arrangement of the USB DT nodes and finally adds USB 3 PHY and host controller support for NorthStar Plus - Florian adds support for Broadcom's BCM947189ACDBMR reference board which is based on BCM47182/53573 and which supports external MoCA (BCM6802) - Ray fixes the wrong UART2 base address for Cygnus - Scott moves the v3d node in the proper unit address order and defines the correct UART alias for the BCM91130_entphn reference board to be UART3 - Jason adds the DT node for the Cygnus Cortex-A9 Performance Monitoring Unit - Jonathan adds a bunch of additional peripherals to the Cygnus DTS include file: SDHCI, Keypad, SPI, DMA and pinmux configurations - Raveendra adds the Cygnus OHCI and EHCI Device Tree nodes * tag 'arm-soc/for-4.14/devicetree' of http://github.com/Broadcom/stblinux: ARM: BCM53573: Specify ports for USB LED for Tenda AC9 ARM: dts: cygnus: Add generic-ehci/ohci nodes ARM: dts: cygnus: add serial0 alias for uart3 on bcm91130_entphn ARM: dts: cygnus: Add additional peripherals to dtsi ARM: dts: cygnus: Enable Performance Monitoring Unit ARM: dts: cygnus: place v3d in proper address ordered location ARM: dts: cygnus: Fix incorrect UART2 register base ARM: dts: bcm283x: Add 32-bit enable method for SMP dt-bindings: arm: add SMP enable-method for BCM2836 ARM: dts: BCM53573: Add Broadcom BCM947189ACDBMR board support ARM: dts: BCM5301X: Specify USB ports for USB LEDs of few devices ARM: dts: NSP: Add USB3 and USB3 PHY to NSP ARM: dts: NSP: Rearrage USB entries ARM: dts: NSP: Add dma-coherent to relevant DT entries ARM: dts: bcm2835: Add Raspberry Pi Zero W dt-bindings: bcm: Add Raspberry Pi Zero W ARM: bcm283x: Define UART pinmuxing on board level ARM: dts: BCM5301X: Specify USB ports for each controller ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm. |