[PATCH v5 12/27] x86: um, annotate data appropriatelly

Use the new SYM_DATA_START and SYM_DATA_END_LABEL macros for vdso_start. We get: 2376 OBJECT GLOBAL DEFAULT4 vdso_start 0948 0 OBJECT GLOBAL DEFAULT4 vdso_end Signed-off-by: Jiri Slaby Cc: Jeff Dike Cc: Richard Weinberger

[PATCH v5 10/27] x86: head, annotate data appropriatelly

Use the new SYM_DATA, SYM_DATA_START, and SYM_DATA_END in both 32 and 64 bit heads. In the 64-bit version, define also SYM_DATA_START_PAGE_ALIGNED locally using the new SYM_START. It is used in the code instead of NEXT_PAGE() which was defined in this file and has been using the obsolete macro

[PATCH v5 08/27] x86: assembly, annotate aliases

_key_expansion_128 is an alias to _key_expansion_256a, __memcpy to memcpy, xen_syscall32_target to xen_sysenter_target, and so on. Annotate them all using the new SYM_FUNC_START_ALIAS, SYM_FUNC_START_LOCAL_ALIAS, and SYM_FUNC_END_ALIAS. This will make the tools generating the debuginfo happy.

[PATCH v5 00/27] New macros for assembler symbols

This series introduces new macros for assembly as was discussed [1]. The macros are introduced in the first patch of the series. The rest of patches start using these new macros in x86, converting *all* uses of the old macros to the new ones throughout the last patch. With every last user of some

[PATCH v5 06/27] x86: crypto, annotate local functions

Use the newly added SYM_FUNC_START_LOCAL to annotate starts of all functions which do not have ".globl" annotation, but their ends are annotated by ENDPROC. This is needed to balance ENDPROC for tools that are about to generate debuginfo. To be symmetric, we also convert their ENDPROCs to the new

[PATCH v5 07/27] x86: boot, annotate local functions

relocated and no_longmode are self-standing local functions, annotate them as such. Signed-off-by: Jiri Slaby Cc: "H. Peter Anvin" Cc: Thomas Gleixner Cc: Ingo Molnar Cc: x...@kernel.org ---

[PATCH v5 02/27] x86: assembly, use SYM_DATA for data

We make proper use of SYM_DATA on global data instead of marking them as ENTRY. ENTRY is intended for functions and shall be paired with ENDPROC. ENTRY also aligns symbols which creates unnecessary holes here between data. ENTRY from saved_eip in wakeup_32 and many saved_* in wakeup_64 is simply

[PATCH v5 05/27] x86: assembly, annotate local pseudo-functions

Use the newly added SYM_CODE_START_LOCAL* to annotate starts of all pseudo-functions (those ending END) which do not have ".globl" annotation. This is needed to balance END for tools that are about to generate debuginfo. Note that we switch from END to SYM_CODE_END so that everybody can see the

Re: [PATCH, RESEND 1/2] dvb-frontends: fix i2c access helpers for KASAN

Em Thu, 30 Nov 2017 15:06:15 +0100 Arnd Bergmann escreveu: > On Thu, Nov 30, 2017 at 1:49 PM, Mauro Carvalho Chehab > wrote: > >> Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81715 > >> Signed-off-by: Arnd Bergmann > >> --- > >> I'm

[PATCH v5 03/27] x86: assembly, annotate relocate_kernel

There are functions in relocate_kernel which are not annotated. This will not allow for automatic DWARF annotations. So annotate all the functions now. Note that these are not C-like functions, so we do not use FUNC, but CODE. Also they are not aligned, so we use NOALIGN versions: -

[PATCH v5 01/27] linkage: new macros for assembler symbols

Introduce new C macros for annotations of functions and data in assembly. There is a long-standing mess in macros like ENTRY, END, ENDPROC and similar. They are used in different manners and sometimes incorrectly. So introduce macros with clear use to annotate assembly as follows: a) Support

[PATCH] nvme-fc: don't require user to enter host_traddr

One major usability difference between NVMf RDMA and FC is resolving the default host transport address in RDMA. This is perfectly doable in FC as well, as we already have all possible lport <-> rport combinations pre-populated so we can pick the first lport that has a connection to our desired

Re: [PATCH 3/3] trace-cmd: Making stat to report when the stack tracer is ON

On Thu, 30 Nov 2017 13:26:55 +0200 Vladislav Valtchev wrote: > I proposed die() because, by looking at the original code of read_proc(): > > static char read_proc(void) > { > char buf[1]; > int fd; > int n; > > fd = open(PROC_FILE,

Re: [PATCH v2 0/5] Memory hotplug support for arm64 - complete patchset v2

On Thu 23-11-17 17:33:31, Andrea Reale wrote: > On Thu 23 Nov 2017, 17:02, Michal Hocko wrote: > > Hi Michal, > > > I will try to have a look but I do not expect to understand any of arm64 > > specific changes so I will focus on the generic code but it would help a > > _lot_ if the cover letter

Re: [PATCH] usbip: fix usbip attach to find a port that matches the requested speed

On 11/30/2017 01:20 AM, Greg KH wrote: > On Wed, Nov 29, 2017 at 03:24:22PM -0700, Shuah Khan wrote: >> usbip attach fails to find a free port when the device on the first port >> is a USB_SPEED_SUPER device and non-super speed device is being attached. >> It keeps checking the first port and

[PATCH] x86/build: Don't verify mtools configuration file for isoimage

From: Changbin Du If mtools.conf is not generated before, 'make isoimage' could complain: Kernel: arch/x86/boot/bzImage is ready (#597) GENIMAGE arch/x86/boot/image.iso *** Missing file: arch/x86/boot/mtools.conf arch/x86/boot/Makefile:144: recipe for target

Re: [PATCH] usbip: Fix USB device hang due to wrong enabling of scatter-gather

On 11/29/2017 07:22 PM, Yuyang Du wrote: > The previous USB3 SuperSpeed enabling patches mistakenly enabled > URB scatter-gather chaining, which is actually not supported by > the VHCI HCD. This patch fixes that. > > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197867 > Fixes:

Re: [PATCH] of: overlay: fix memory leak of ovcs on error exit path

On 11/30/17 08:37, Frank Rowand wrote: > Hi Colin, Rob, > > On 11/30/17 07:18, Colin Ian King wrote: >> On 30/11/17 12:14, Frank Rowand wrote: >>> On 11/29/17 14:17, Colin King wrote: From: Colin Ian King Currently if the call to of_resolve_phandles fails

Re: [PATCH/trivial] ledtrig-activity: Grammar s/a immediate/an immediate/

On Thu 2017-11-30 14:36:41, Geert Uytterhoeven wrote: > Fixes: 7df4f9a9f0667ee6 ("leds: ledtrig-activity: Add a system activity LED > trigger") > Signed-off-by: Geert Uytterhoeven ACK. Is it time we create scripts to pull all the english texts from kernel, so that we

Re: [PATCH] nvme-fc: don't require user to enter host_traddr

On 11/30/2017 03:56 PM, Johannes Thumshirn wrote: > One major usability difference between NVMf RDMA and FC is resolving > the default host transport address in RDMA. This is perfectly doable > in FC as well, as we already have all possible lport <-> rport > combinations pre-populated so we can

Re: [PATCH net-next 0/3] rxrpc: Fixes

From: David Howells Date: Wed, 29 Nov 2017 15:33:43 + > Here are three patches for AF_RXRPC. One removes some whitespace, one > fixes terminal ACK generation and the third makes a couple of places > actually use the timeout value just determined rather than ignoring it.

Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info

On 30/11/2017 15:08, Alex Williamson wrote: On Thu, 30 Nov 2017 12:34:38 +0100 Pierre Morel wrote: When userland VFIO defines a new IOMMU for a guest it may want to specify to the guest the physical limits of the underlying host IOMMU to avoid access to forbidden

[PATCH v2] nvme-fc: don't require user to enter host_traddr

One major usability difference between NVMf RDMA and FC is resolving the default host transport address in RDMA. This is perfectly doable in FC as well, as we already have all possible lport <-> rport combinations pre-populated so we can pick the first lport that has a connection to our desired

Re: [Pv-drivers] [PATCH net-next] vmxnet3: increase default rx ring sizes

From: Boon Ang Date: Wed, 29 Nov 2017 16:25:16 + > I hope the above explains our motivation. Let us know if you have > more questions. Please add these descriptive details to your commit message and resubmit.

Re: [PATCH v6 2/4] KVM: X86: Add Paravirt TLB Shootdown

2017-11-30 14:24+0800, Wanpeng Li: > 2017-11-30 0:21 GMT+08:00 Radim Krčmář : > > 2017-11-27 20:05-0800, Wanpeng Li: > >> From: Wanpeng Li > >> diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c > >> @@ -498,6 +498,37 @@ static void __init

Re: [PATCH v7 2/4] KVM: X86: Add Paravirt TLB Shootdown

2017-11-29 22:01-0800, Wanpeng Li: > From: Wanpeng Li > --- > diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c > @@ -498,6 +498,34 @@ static void __init kvm_apf_trap_init(void) > update_intr_gate(X86_TRAP_PF, async_page_fault); > } > > +static

Re: [kernel-hardening] Re: [PATCH v3 2/2] Protected O_CREAT open in sticky directories

On Thu, 2017-11-30 at 15:39 +0100, Salvatore Mesoraca wrote: > 2017-11-27 1:26 GMT+01:00 Solar Designer : > > On Fri, Nov 24, 2017 at 12:43:47PM +0100, Salvatore Mesoraca wrote: > > > 2017-11-24 11:53 GMT+01:00 David Laight > > > : > > > > From: Alan

Re: [PATCH RT] crypto: limit more FPU-enabled sections

On Thu, 30 Nov 2017 15:22:17 +0100 Sebastian Andrzej Siewior wrote: > diff --git a/arch/x86/crypto/camellia_aesni_avx2_glue.c > b/arch/x86/crypto/camellia_aesni_avx2_glue.c > index 60907c139c4e..d7502c023475 100644 > --- a/arch/x86/crypto/camellia_aesni_avx2_glue.c > +++

Re: Unlock-lock questions and the Linux Kernel Memory Model

On Wed, 29 Nov 2017, Daniel Lustig wrote: > On 11/29/2017 12:42 PM, Paul E. McKenney wrote: > > On Wed, Nov 29, 2017 at 02:53:06PM -0500, Alan Stern wrote: > >> On Wed, 29 Nov 2017, Peter Zijlstra wrote: > >> > >>> On Wed, Nov 29, 2017 at 11:04:53AM -0800, Daniel Lustig wrote: > >>> > While

Re: [PATCH] mmc: sdhci-of-arasan: Add sdhci_arasan_set_power

On 28/11/17 02:02, Milan Stevanovic wrote: > The power register needs to have a valid voltage set > even when the power supply is managed by an external regulator. > > Signed-off-by: Milan Stevanovic Acked-by: Adrian Hunter > --- >

Re: [PATCH] mm: Make count list_lru_one::nr_items lockless

On 30.11.2017 03:27, Shakeel Butt wrote: > On Fri, Sep 29, 2017 at 1:15 AM, Kirill Tkhai wrote: >> On 29.09.2017 00:02, Andrew Morton wrote: >>> On Thu, 28 Sep 2017 10:48:55 +0300 Kirill Tkhai >>> wrote: >>> >> This patch aims to make

Re: [alsa-devel] Applied "ALSA: pcm: add SNDRV_PCM_FORMAT_{S, U}20" to the asoc tree

On Wed, Nov 29, 2017 at 10:23:23PM +0100, Takashi Iwai wrote: > Mark, I already took this into my tree, as it's a change in ALSA core > stuff. As mentioned in another mail, the branch was exposed to > topic/pcm-20bit branch, so that you can pull cleanly. That's what this is reporting - the

Re: [PATCH v3 0/4] Fixes for omapdrm on OpenPandora and GTA04

On 28/11/17 17:48, H. Nikolaus Schaller wrote: > Changes V3: > * stay compatible with old DTB files which still use "toppoly" (suggested by > Tomi Valkeinen) > * replaced MODULE_ALIAS entries by MODULE_DEVICE_TABLE (suggested by Andrew > F. Davis) > * removed DSI VDDS patch as it has already

Re: [PATCH net v2] tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()

On 11/29/2017 06:48 PM, Tommi Rantala wrote: > Remove the second tipc_rcv() call in tipc_udp_recv(). We have just > checked that the bearer is not up, and calling tipc_rcv() with a bearer > that is not up leads to a TIPC div-by-zero crash in > tipc_node_calculate_timer(). The crash is rare in

[PATCH, RESEND 2/2] r820t: fix r820t_write_reg for KASAN

With CONFIG_KASAN, we get an overly long stack frame due to inlining the register access functions: drivers/media/tuners/r820t.c: In function 'generic_set_freq.isra.7': drivers/media/tuners/r820t.c:1334:1: error: the frame size of 2880 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]

Re: [PATCH] rtc: add mxc driver for i.MX53

Hi, On Tue, 28 Nov 2017 08:39:27 +0100 linux-kernel-...@beckhoff.com wrote: > From: Patrick Bruenn [...] > +/*! > + * This function is the RTC interrupt service routine. > + * > + * @param irq RTC IRQ number > + * @param dev_id device ID which is not used

Re: BSOD with [PATCH 00/13] mmu_notifier kill invalidate_page callback

On 30/11/2017 10:33, Fabian Grünbichler wrote: > > It was reverted in 785373b4c38719f4af6775845df6be1dfaea120f after which > the symptoms disappeared until this series was merged, which contains > > 369ea8242c0fb5239b4ddf0dc568f694bd244de4 mm/rmap: update to new mmu_notifier > semantic v2 > >

Re: general protection fault in proc_flush_task

On 11/30/17, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 0c86a6bd85ff0629cd2c5141027fc1c8bb6cde9c > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1

[PATCH] crypto: cryptd: make cryptd_max_cpu_qlen module parameter static

From: Colin Ian King The cryptd_max_cpu_qlen module parameter is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: crypto/cryptd.c:35:14: warning: symbol 'cryptd_max_cpu_qlen' was not declared. Should it be

[PATCH v4] f2fs: obsolete free nid list approach

Previously, we use free nid list to manage free nid entry, so during nid allocation, we can just pick up one entry from list header, which has quite low overhead. But sadly, during initialization of free nid list, we should do lookup combining with lots of different inner caches, including NAT

[PATCH 6/7] f2fs: clean up f2fs_map_blocks

f2fs_map_blocks(): if (blkaddr == NEW_ADDR || blkaddr == NULL_ADDR) { if (create) { ... } else { ... if (flag == F2FS_GET_BLOCK_FIEMAP && blkaddr == NULL_ADDR) { ...

[PATCH 4/7] f2fs: fix error handling in fill_super

In fill_super, if we fail to call f2fs_build_stats(), it needs to detach from global f2fs shrink list, otherwise once system starts to shrink slab cache, we will encounter below panic: BUG: unable to handle kernel paging request at 7d35 Oops: 0002 [#1] PREEMPT SMP EIP:

[PATCH] crypto: chelsio: make arrays sgl_ent_len and dsgl_ent_len static

From: Colin Ian King The arrays sgl_ent_len and dsgl_ent_len are local to the source and do not need to be in global scope, so make them static. Also re-format the declarations to match the following round_constant array declaration style. Cleans up sparse warnings:

Re: general protection fault in show_timer

On Thu, Nov 30, 2017 at 12:08 PM, Alexey Dobriyan wrote: > On 11/30/17, syzbot > > wrote: >> Hello, >> >> syzkaller hit the following crash on >> 43570f0383d6d5879ae585e6c3cf027ba321546f >>

[PATCH] mmc: block: make function mmc_cqe_issue_type static

From: Colin Ian King The function mmc_cqe_issue_type is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: drivers/mmc/core/queue.c:62:21: warning: symbol 'mmc_cqe_issue_type' was not declared. Should it be static?

Re: [PATCH 1/2] powerpc/lib/code-patching: refactor patch_instruction()

On Fri, Nov 24, 2017 at 6:31 PM, Christophe Leroy wrote: > patch_instruction() uses almost the same sequence as > __patch_instruction() > > This patch refactor it so that patch_instruction() uses > __patch_instruction() instead of duplicating code. > > Signed-off-by:

[PATCH v3 4/6] sched/rt: fast switch to maximum frequency when RT tasks are scheduled

Currently schedutil updates are triggered for the RT class using a single call place, which is part of the rt::update_curr_rt() used in: - dequeue_task_rt: but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in case the next task should not be an RT one - put_prev_task_rt:

[PATCH v3 2/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks

The policy in use for RT/DL tasks sets the maximum frequency when a task in these classes calls for a cpufreq_update_util(). However, the current implementation might cause a frequency drop while a RT/DL task is still running, just because for example a FAIR task wakes up and it's enqueued in the

[PATCH v2] PM / Domains: Remove obsolete "samsung,power-domain" check

Currently the generic PM Domain code code checks for the presence of both (generic) "power-domains" and (Samsung Exynos legacy) "samsung,power-domain" properties in all device tree nodes representing devices. There are two issues with this: 1. This imposes a small boot-time penalty on all

Re: [RFC PATCH] ipc, mqueue: lazy call kern_mount_data in new namespaces

Andrew Morton writes: > On Wed, 29 Nov 2017 11:33:28 +0100 Giuseppe Scrivano > wrote: > >> Andrew Morton writes: >> >> > OK, but this simply moves the expense so it happens later on. Why is >> > that better? >> >>

Re: [PATCH v3 02/15] soundwire: Add SoundWire bus type

On Thu, Nov 30, 2017 at 12:42:30PM +0100, Philippe Ombredanne wrote: > On Thu, Nov 30, 2017 at 10:56 AM, Vinod Koul wrote: > [] > > diff --git a/drivers/soundwire/bus.h b/drivers/soundwire/bus.h > > new file mode 100644 > > index ..2af05b21961e > > --- /dev/null

Re: [PATCH v3 9/9] KVM: x86: Implement Intel Processor Trace context switch

On 27/11/2017 21:24, Luwei Kang wrote: > + if (pt_mode == PT_MODE_HOST_GUEST) { > + u32 eax, ebx, ecx, edx; > + > + cpuid_count(0x14, 1, , , , ); Since it's used in many places, it's better if you cache CPUID[14,1].EAX. Thanks, Paolo > + memset(>pt_desc,

Re: [PATCH v18 05/10] xbitmap: add more operations

Wei Wang wrote: > /** > + * xb_clear_bit - clear a range of bits in the xbitmap Name mismatch. > + * @start: the start of the bit range, inclusive > + * @end: the end of the bit range, inclusive > + * > + * This function is used to clear a bit in the xbitmap. If all the bits of > the > + *

RE: [patch v12 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Thnaks for point Best Regards, Oleksandr Shamray > -Original Message- > From: Philippe Ombredanne [mailto:pombreda...@nexb.com] > Sent: Thursday, November 30, 2017 10:21 AM > To: Kun Yi > Cc: Oleksandr Shamray ; Greg Kroah-Hartman >

Re: [alsa-devel] Applied "ALSA: pcm: add SNDRV_PCM_FORMAT_{S, U}20" to the asoc tree

On Thu, 30 Nov 2017 11:41:59 +0100, Mark Brown wrote: > > On Wed, Nov 29, 2017 at 10:23:23PM +0100, Takashi Iwai wrote: > > > Mark, I already took this into my tree, as it's a change in ALSA core > > stuff. As mentioned in another mail, the branch was exposed to > > topic/pcm-20bit branch, so

Re: linux-next: Signed-off-by missing for commits in the mfd-fixes tree

On Wed, Nov 29, 2017 at 04:31:42PM +, Lee Jones wrote: > On Wed, 29 Nov 2017, Johan Hovold wrote: > > > On Thu, Nov 30, 2017 at 01:43:05AM +1100, Stephen Rothwell wrote: > > > Hi Lee, > > > > > > Commits > > > > > > 5f6bf7b9f96e ("mfd: twl4030-audio: Fix sibling-node lookup") > > >

Re: general protection fault in show_timer

On 11/30/17, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 43570f0383d6d5879ae585e6c3cf027ba321546f > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1

[PATCH 5/7] f2fs: clean up hash codes

f2fs_chksum and f2fs_crc32 use the same 'crc32' crypto engine, also their implementation are almost the same, except with different shash description context. Introduce __f2fs_crc32 to wrap the common codes, and reuse it in f2fs_chksum and f2fs_crc32. Signed-off-by: Chao Yu

Re: general protection fault in proc_flush_task

On Thu, Nov 30, 2017 at 12:21 PM, Alexey Dobriyan wrote: > On 11/30/17, syzbot > > wrote: >> Hello, >> >> syzkaller hit the following crash on >> 0c86a6bd85ff0629cd2c5141027fc1c8bb6cde9c >>

[PATCH 3/7] f2fs: spread f2fs_k{m,z}alloc

Use f2fs_k{m,z}alloc as much as possible to increase fault injection points. Signed-off-by: Chao Yu --- fs/f2fs/segment.c | 2 +- fs/f2fs/super.c | 16 +--- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c

[PATCH 2/7] f2fs: inject fault to kvmalloc

This patch supports to inject fault into kvmalloc/kvzalloc. Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h| 19 +++ fs/f2fs/file.c| 6 -- fs/f2fs/node.c| 6 +++--- fs/f2fs/segment.c | 16 +--- fs/f2fs/super.c | 1 + 5 files

Re: [PATCH v2] clk: stm32-h7: fix copyright

On Thu, Nov 30, 2017 at 9:41 AM, Benjamin Gaignard wrote: > Uniformize STMicroelectronics copyrights header > Add SPDX identifier > > Signed-off-by: Benjamin Gaignard > Acked-by: Alexandre TORGUE > CC: Gabriel

[PATCH 1/7] f2fs: inject fault to kzalloc

This patch introduces f2fs_kzalloc based on f2fs_kmalloc in order to support error injection for kzalloc(). Signed-off-by: Chao Yu --- fs/f2fs/checkpoint.c | 2 +- fs/f2fs/debug.c | 2 +- fs/f2fs/f2fs.h | 6 ++ fs/f2fs/namei.c | 2 +- fs/f2fs/node.c

[PATCH 7/7] f2fs: don't return value in truncate_data_blocks_range

There is no caller cares about return value of truncate_data_blocks_range, remove it. Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h | 2 +- fs/f2fs/file.c | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index

Re: [PATCH v3 02/15] soundwire: Add SoundWire bus type

On Thu, Nov 30, 2017 at 10:56 AM, Vinod Koul wrote: [] > diff --git a/drivers/soundwire/bus.h b/drivers/soundwire/bus.h > new file mode 100644 > index ..2af05b21961e > --- /dev/null > +++ b/drivers/soundwire/bus.h > @@ -0,0 +1,57 @@ > +/* > + * This file is

Re: [PATCH v2 1/8] ASoC: tlv320aic31xx: Fix typo in DT binding documentation

On Wed, Nov 29, 2017 at 11:13:52AM -0600, Andrew F. Davis wrote: > The property used to specify a GPIO intended for reset is "reset-gpios", > this binding uses "gpio-reset", as almost all other bindings use the > former name this use of the latter was certainly not intended. It is not > compatible

[PATCH] bus: simple-pm-bus: convert bool SIMPLE_PM_BUS to tristate

From: Paul Gortmaker The Kconfig currently controlling compilation of this code is: config SIMPLE_PM_BUS bool "Simple Power-Managed Bus Driver" ...meaning that it currently is not being built as a module by anyone. In removing the orphaned modular support

[PATCH] KVM: x86: MMU: make array audit_point_name static

From: Colin Ian King The array audit_point_name is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: arch/x86/kvm/mmu_audit.c:22:12: warning: symbol 'audit_point_name' was not declared. Should it be static?

Re: [RFC 0/2] of: Add whitelist

On 11/29/17 08:31, Rob Herring wrote: > On Wed, Nov 29, 2017 at 3:20 AM, Frank Rowand wrote: >> On 11/27/17 15:58, Alan Tull wrote: >>> Here's a proposal for a whitelist to lock down the dynamic device tree. >>> >>> For an overlay to be accepted, all of its targets are

Re: [PATCH] of: overlay: fix memory leak of ovcs on error exit path

On 30/11/17 12:14, Frank Rowand wrote: > On 11/29/17 14:17, Colin King wrote: >> From: Colin Ian King >> >> Currently if the call to of_resolve_phandles fails then then ovcs >> is not kfree'd on the error exit path. Rather than try and make >> the clean up exit path

Re: [PATCH v3 4/9] KVM: x86: Add Intel Processor Trace cpuid emulation

On 27/11/2017 21:23, Luwei Kang wrote: > + int t, times = entry->eax & 0x; This AND is not necessary. Paolo > + > + if (!f_intel_pt) > + break; > + > + entry->flags |= KVM_CPUID_FLAG_SIGNIFCANT_INDEX; > + for (t = 1; t

Re: [PATCH v3 8/9] KVM: x86: Disable Intel Processor Trace when VMXON in L1 guest

On 27/11/2017 21:24, Luwei Kang wrote: > > + if (pt_mode == PT_MODE_HOST_GUEST) { > + vmx->pt_desc.guest.ctl &= ~RTIT_CTL_TRACEEN; > + pt_disable_intercept_for_msr(FALSE); > + vmcs_write64(GUEST_IA32_RTIT_CTL, vmx->pt_desc.guest.ctl); > + } > + Using

Re: [PATCH 2/3] kbuild: add cc-if-name-version and compiler-specific variants

2017-11-29 9:00 GMT+09:00 Sami Tolvanen : > This change adds macros for testing both compiler name and > version. Current cc-version, cc-ifversion etc. macros that test > gcc version are left unchanged to prevent compatibility issues > with existing tests. > >

Re: [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

Em Tue, 10 Oct 2017 09:59:42 +0200 Sean Young escreveu: > If you try to store u64 in a kfifo (or a struct with u64 members), > then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes > padding due to alignment (note that struct __kfifo is 20 bytes > on 32 bit). > > That in

Re: [PATCH v18 07/10] virtio-balloon: VIRTIO_BALLOON_F_SG

Wei Wang wrote: > +static inline int xb_set_page(struct virtio_balloon *vb, > +struct page *page, > +unsigned long *pfn_min, > +unsigned long *pfn_max) > +{ > + unsigned long pfn = page_to_pfn(page); > +

drivers/input/touchscreen/hideep.c:670:3: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'?

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a0908a1b7d68706ee52ed4a039756e70c8e956e9 commit: 842ff286166e8512450573f6b6eb5e04e626a07f Input: add support for HiDeep touchscreen date: 3 weeks ago config: x86_64-randconfig-s4-11301716 (attached as

Re: [PATCH v3 0/6] ARM: ep93xx: ts72xx: Add support for BK3 board

On Thu, Nov 30, 2017 at 10:57 AM, Alexander Sverdlin wrote: > Hello Arnd! > > On Thu Nov 30 10:02:26 2017 Arnd Bergmann wrote: >> Can we clarify who is picking up ep93xx patches these days? The >> last time I think Linus Walleij offered to do it for

Re: [PATCH v5] mfd: syscon: Add hardware spinlock support

On 30 November 2017 at 18:38, Vladimir Zapolskiy wrote: > On 11/30/2017 11:10 AM, Baolin Wang wrote: >> Some system control registers need hardware spinlock to synchronize >> between the multiple subsystems, so we should add hardware spinlock >> support for syscon.

Re: [PATCH v3] doc: add maintainer book

On Thu, Nov 30, 2017 at 07:01:19AM -0200, Mauro Carvalho Chehab wrote: > Em Thu, 30 Nov 2017 12:55:07 +1100 > "Tobin C. Harding" escreveu: > > > There is currently very little documentation in the kernel on maintainer > > level tasks. In particular there are no documents on

[PATCH] kernel-docs.rst: update broken linuxjournal links

Signed-off-by: Nguyễn Thái Ngọc Duy --- Documentation/process/kernel-docs.rst | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Documentation/process/kernel-docs.rst b/Documentation/process/kernel-docs.rst index b8cac85a4001..66040404ac9f

Re: [PATCH] rtc: add mxc driver for i.MX53

Hi, On Thu, 30 Nov 2017 10:50:47 +0100 Sascha Hauer wrote: > On Tue, Nov 28, 2017 at 08:39:27AM +0100, linux-kernel-...@beckhoff.com wrote: [...] > > +/*! MXC RTC Power management control */ > > +static int mxc_rtc_probe(struct platform_device *pdev) > > +{ > > + struct timespec tv; > > +

Re: [PATCH v3] doc: add maintainer book

Em Thu, 30 Nov 2017 21:47:44 +1100 "Tobin C. Harding" escreveu: > On Thu, Nov 30, 2017 at 07:01:19AM -0200, Mauro Carvalho Chehab wrote: > > Em Thu, 30 Nov 2017 12:55:07 +1100 > > "Tobin C. Harding" escreveu: > > > +So, by way of an example, Greg gives; a pull

RE: [PATCH 1/2] mm: NUMA stats code cleanup and enhancement

Of course, we should do that AFAP. Thanks for your comments :) -Original Message- From: owner-linux...@kvack.org [mailto:owner-linux...@kvack.org] On Behalf Of Michal Hocko Sent: Thursday, November 30, 2017 5:45 PM To: Wang, Kemi Cc: Greg Kroah-Hartman

[PATCH] crypto: stm32: fix module device table name

This patch fix the following build failure: CC [M] drivers/crypto/stm32/stm32-cryp.o In file included from drivers/crypto/stm32/stm32-cryp.c:11:0: drivers/crypto/stm32/stm32-cryp.c:1049:25: error: 'sti_dt_ids' undeclared here (not in a function) MODULE_DEVICE_TABLE(of, sti_dt_ids); Let's

Re: [PATCH] crypto: stm32: fix module device table name

Hi Corentin Thank you for the patch. On 30/11/17 12:04, Corentin Labbe wrote: > This patch fix the following build failure: >CC [M] drivers/crypto/stm32/stm32-cryp.o > In file included from drivers/crypto/stm32/stm32-cryp.c:11:0: > drivers/crypto/stm32/stm32-cryp.c:1049:25: error:

Re: [RFC v2 2/2] backlight: pwm_bl: compute brightness of LED linearly to human eye.

On 30/11/17 00:44, Doug Anderson wrote: Hi, On Thu, Nov 16, 2017 at 6:11 AM, Enric Balletbo i Serra wrote: When you want to change the brightness using a PWM signal, one thing you need to consider is how human perceive the brightness. Human perceive the

Re: [PATCH 3/3] trace-cmd: Making stat to report when the stack tracer is ON

On Wed, 2017-11-29 at 11:18 -0500, Steven Rostedt wrote: > > In other words, I expect a tool to behave like: > > "I don't know what is that, so I cannot take any decisions. > >Here's the detailed problem (err msg, data). Now only a human may help > > now". > > > > The other approach is

[PATCH 3/3] f2fs: allocate full free nat block in prior

In this patch, during alloc_nid, we start to allocate free nid from nat block which contains the most free nids, it will make all dirty nat entries locating in the same nat block, result in reducing nat writes during checkpoint. Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h | 2

[PATCH 1/3] f2fs: avoid unneeded free nid building

This patch adds nm_i::valid_bitmap_count to count current valid free nid bitmap, with it we can skip running into __build_free_nids more early. Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h | 1 + fs/f2fs/node.c | 14 ++ 2 files changed, 15 insertions(+) diff --git

[PATCH 2/3] f2fs: refactor __build_free_nids

Previously, in __build_free_nids we try to load bitmap from next_scan_nid pointed NAT block, but actually, due to nat_bits bitmap, current NAT blocks readed can be already ran out, so it makes __build_free_nids low efficiency. This patch refactors __build_free_nids a bit to search

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, Nov 30, 2017 at 9:53 AM, Alan Kao wrote: [] > diff --git a/arch/riscv/include/asm/ftrace.h b/arch/riscv/include/asm/ftrace.h > new file mode 100644 > index ..38beadb07ad5 > --- /dev/null > +++ b/arch/riscv/include/asm/ftrace.h > @@ -0,0 +1,23 @@ > +/* > + *

Re: general protection fault in show_timer

On Thu, Nov 30, 2017 at 12:31 PM, Dmitry Vyukov wrote: > On Thu, Nov 30, 2017 at 12:08 PM, Alexey Dobriyan wrote: >> On 11/30/17, syzbot >> >> wrote: >>> Hello, >>> >>> syzkaller hit

Re: [PATCH v3 4/9] KVM: x86: Add Intel Processor Trace cpuid emulation

On 27/11/2017 21:23, Luwei Kang wrote: > From: Chao Peng > > Expose Intel Processor Trace to guest only when PT work in > HOST_GUEST mode. > > Signed-off-by: Chao Peng > Signed-off-by: Luwei Kang > Signed-off-by:

Re: [PATCH] of: overlay: fix memory leak of ovcs on error exit path

On 11/29/17 14:17, Colin King wrote: > From: Colin Ian King > > Currently if the call to of_resolve_phandles fails then then ovcs > is not kfree'd on the error exit path. Rather than try and make > the clean up exit path more convoluted, fix this by just kfree'ing >

[PATCH] btrfs: make function update_share_count static

From: Colin Ian King The function update_share_count is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: fs/btrfs/backref.c:219:6: warning: symbol 'update_share_count' was not declared. Should it be static?

Re: [PATCH v5 next 3/5] modules:capabilities: automatic module loading restriction

On Thu, Nov 30, 2017 at 2:23 AM, Luis R. Rodriguez wrote: > On Mon, Nov 27, 2017 at 06:18:36PM +0100, Djalal Harouni wrote: >> diff --git a/include/linux/module.h b/include/linux/module.h >> index 5cbb239..c36aed8 100644 >> --- a/include/linux/module.h >> +++

Re: [BUILD FAILURE] nfs4state.c fails to compile with gcc 4.5.4

On Thu, Nov 30, 2017 at 4:39 AM, Andrew Morton wrote: > On Wed, 29 Nov 2017 19:27:45 -0800 Linus Torvalds > wrote: > >> On Wed, Nov 29, 2017 at 6:58 PM, Steven Rostedt wrote: >> > >> > Seems it can't handle the

Re: [PATCH v3 0/9] Intel Processor Trace virtulization enabling

On 27/11/2017 21:23, Luwei Kang wrote: > From v2: > - replace *_PT_SUPPRESS_PIP to *_PT_CONCEAL_PIP; > - clean SECONDARY_EXEC_PT_USE_GPA, VM_EXIT_CLEAR_IA32_RTIT_CTL and > VM_ENTRY_LOAD_IA32_RTIT_CTL in SYSTEM mode. These bits must be all set or all > clean; > - move processor tracing out of

Re: [PATCH v2 01/19] ASoC: tlv320aic31xx: File header and copyright cleanup

On Wed, Nov 29, 2017 at 03:32:42PM -0600, Andrew F. Davis wrote: > Fix header copyright tags, while we are here, also switch to SPDX > and fixup MODULE tags to match. > - * The TLV320AIC31xx series of audio codec is a low-power, highly integrated > - * high performance codec which provides a

Re: [PATCH RFC 1/2] sched: Minimize the idle cpu selection race window.

On Wed, Nov 29, 2017 at 07:15:21PM +0100, Mike Galbraith wrote: > On Wed, 2017-11-29 at 11:41 +0100, Uladzislau Rezki wrote: > > On Tue, Nov 28, 2017 at 11:49:11AM +0100, Mike Galbraith wrote: > > > On Tue, 2017-11-28 at 10:34 +0100, Uladzislau Rezki wrote: > > > > On Fri, Nov 24, 2017 at

<    3   4   5   6   7   8   9   10   11   12   >