[PATCH 1/2 v6] typec: tcpm: Validate source and sink caps

The source and sink caps should follow the following rules. This patch validates whether the src_caps/snk_caps adheres to it. 6.4.1 Capabilities Message A Capabilities message (Source Capabilities message or Sink Capabilities message) shall have at least one Power Data Object for vSafe5V. The

Re: [RFC PATCH 0/2] apply write hints to select the type of segments

On 11/10/2017 03:42 PM, Chao Yu wrote: > On 2017/11/10 8:23, Hyunchul Lee wrote: >> Hello, Chao >> >> On 11/09/2017 06:12 PM, Chao Yu wrote: >>> On 2017/11/9 13:51, Hyunchul Lee wrote: From: Hyunchul Lee Using write hints[1], applications can inform the life time

[PATCH 2/2 v6] typec: tcpm: Only request matching pdos

At present, TCPM code assumes that local device supports variable/batt pdos and always selects the pdo with highest possible power within the board limit. This assumption might not hold good for all devices. To overcome this, this patch makes TCPM only accept a source_pdo when there is a matching

Re: [PATCH net-next] net: dsa: lan9303: Fix lan9303_alr_del_port()

From: Egil Hjelmeland Date: Wed, 8 Nov 2017 11:44:36 +0100 > Fix embarrassing bug in lan9303_alr_del_port(): Instead of zeroing > entr->mac_addr, I destroyed the next cache entry. Affected .port_fdb_del and > .port_mdb_del. > > Fixes: 0620427ea0d6 ("net: dsa:

Re: [f2fs-dev] [RFC PATHC 2/2] f2fs: apply write hints to select the type of segment for direct write

On 2017/11/13 8:07, Hyunchul Lee wrote: > On 11/11/2017 09:38 AM, Chao Yu wrote: >> On 2017/11/9 13:51, Hyunchul Lee wrote: >>> From: Hyunchul Lee >>> >>> Select the type of the segment using write hints, when blocks are >>> allocated for direct write. >>> >>> There are

Re: [PATCH] x86 / CPU: Avoid unnecessary IPIs in arch_freq_get_on_cpu()

On 11/13/17 at 02:15P, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Even though aperfmperf_snapshot_khz() caches the samples.khz value > to return if called again in a sufficiently short time, its caller, > arch_freq_get_on_cpu(), still uses

[PATCH v4 3/3] hwmon: (w83773g) Add documentation

Add documentation for the w83773g driver. Signed-off-by: Lei YU --- v2: - Add notes for offset and update_interval --- Documentation/hwmon/w83773g | 33 + 1 file changed, 33 insertions(+) create mode 100644 Documentation/hwmon/w83773g

[PATCH v4 1/3] DT: i2c: W83773G is a trivial device

Signed-off-by: Lei YU --- Documentation/devicetree/bindings/trivial-devices.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/trivial-devices.txt b/Documentation/devicetree/bindings/trivial-devices.txt index af284fb..63ad2f1 100644

RE: [PATCH] drm/amdgpu/virt: remove redundant variable pf2vf_ver

+ Horace -Original Message- From: Colin King [mailto:colin.k...@canonical.com] Sent: 2017年11月11日 19:51 To: Deucher, Alexander ; Koenig, Christian ; David Airlie ; Liu, Monk ; Yu, Xiangliang

Re: [PATCH v2 1/3] dt-bindings: phy: Add Cygnus usb phy binding

Hi, On Sat, Nov 11, 2017 at 3:14 AM, Rob Herring wrote: > On Wed, Nov 08, 2017 at 01:16:41PM +0530, Raveendra Padasalagi wrote: >> Add devicetree binding document for broadcom's >> Cygnus SoC specific usb phy controller driver. >> >> Signed-off-by: Raveendra Padasalagi

Re: [PATCH v5 2/5] clk: aspeed: Register core clocks

On Mon, 2017-10-30 at 16:32 +1030, Joel Stanley wrote: > This registers the core clocks; those which are required to calculate > the rate of the timer peripheral so the system can load a clocksource > driver. > > Signed-off-by: Joel Stanley > > --- > v5: > - Add Andrew's

Re: [PATCH v5 3/5] clk: aspeed: Add platform driver and register PLLs

On Mon, 2017-10-30 at 16:32 +1030, Joel Stanley wrote: > This registers a platform driver to set up all of the non-core > clocks. > > The clocks that have configurable rates are now registered. > > Signed-off-by: Joel Stanley Reviewed-by: Andrew Jeffery > --

Re: linux-next: manual merge of the staging tree with the media tree

Hi all, On Mon, 9 Oct 2017 19:26:54 +0100 Mark Brown wrote: > > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css_firmware.c > > between commit: > >866af46e6ebbc ("media:

RE: [PATCH] mm/hugetlb: Implement ASLR and topdown for hugetlb mappings

Hi, Russell, Have you any time to check this patch? I found this issue/missing in my works, the application cannot mmap big hugepage (about 360MB) due to no more contiguous vm from the default "TASK_UNMMAPPED_AREA" by legacy bottom-up. We need this patch to fix this issue. Could you please

Re: linux-next: manual merge of the tip tree with the FIXME tree

Hi Mark, On Wed, 11 Oct 2017 17:10:35 +0100 Mark Brown wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > arch/s390/include/asm/spinlock.h > > between a series of commits adding wait queuing to s390 spinlocks > from the s390 tree: > >

[PATCH v2] coccinelle: orplus: reorganize to improve performance

Adding two #define constants is less common than performing & and | operations on them, so put the addition first to reduce the set of cases that have to be considered in detail. At the same time, add & and | patterns for both arguments of +, to account for commutativity and obtain more results.

Improving documentation of parent-ID field in /proc/PID/mountinfo

Hello Ram, Long ago (2.6.29) you added the /proc/PID/mountinfo file and associated documentation in Documentation/filesystems/proc.txt. Later, I pasted much of that documentation into the proc(5) manual page. That documentation says of the second field in the file: [[ This file contains lines

[PATCH IMPROVEMENT/BUGFIX 0/4] block, bfq: increase sustainable IOPS and fix a bug

Hi, these patches address the following issue, raised and discussed in [1]. BFQ provides a proportional share policy for the blkio controller. In this respect, BFQ updates the I/O accounting related to its policy, i.e., the statistics contained in the special files blkio.bfq.* in blkio groups

[PATCH BUGFIX/IMPROVEMENT 2/4] block, bfq: add missing invocations of bfqg_stats_update_io_add/remove

From: Luca Miccio bfqg_stats_update_io_add and bfqg_stats_update_io_remove are to be invoked, respectively, when an I/O request enters and when an I/O request exits the scheduler. Unfortunately, bfq does not fully comply with this scheme, because it does not invoke these

Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl

On Mon, Nov 13, 2017 at 11:38 AM, Tobin C. Harding wrote: > On Mon, Nov 13, 2017 at 11:16:28AM +0530, kaiwan.billimo...@gmail.com wrote: >> On Mon, 2017-11-13 at 09:21 +1100, Tobin C. Harding wrote: >> > On Fri, Nov 10, 2017 at 07:26:34PM +0530, kaiwan.billimo...@gmail.com >> >

Re: [PATCHv4 3/6] powerpc64: Add .opd based function descriptor dereference

* Sergey Senozhatsky wrote (on 2017-11-10 08:48:27 +0900): > We are moving towards separate kernel and module function descriptor > dereference callbacks. This patch enables it for powerpc64. > > For pointers that belong to the kernel > - Added __start_opd and

Re: [PATCH 4/4] kbuild: optimize object directory creation for incremental build

Hi Cao, 2017-11-10 19:58 GMT+09:00 Cao jin : > Masahiro-san > > On 11/09/2017 11:41 PM, Masahiro Yamada wrote: >> The previous commit largely optimized the object directory creation. >> We can optimize it more for incremental build. >> >> There are already *.cmd files

Re: [PATCH] net: realtek: r8169: remove redundant assignment to giga_ctrl

From: Colin King Date: Wed, 8 Nov 2017 13:23:23 + > From: Colin Ian King > > The variable giga_ctrl is being assigned to zero however this is > never read and hence the assignment is redundant, so remove it. > Cleans up clang warning: >

Re: [PATCH V2 net] net: hns3: Updates MSI/MSI-X alloc/free APIs(depricated) to new APIs

From: Salil Mehta Date: Thu, 9 Nov 2017 16:38:13 + > This patch migrates the HNS3 driver code from use of depricated PCI > MSI/MSI-X interrupt vector allocation/free APIs to new common APIs. > > Signed-off-by: Salil Mehta > Suggested-by:

Re: [RFC PATCH 0/2] apply write hints to select the type of segments

On 2017/11/13 8:24, Hyunchul Lee wrote: > On 11/10/2017 03:42 PM, Chao Yu wrote: >> On 2017/11/10 8:23, Hyunchul Lee wrote: >>> Hello, Chao >>> >>> On 11/09/2017 06:12 PM, Chao Yu wrote: On 2017/11/9 13:51, Hyunchul Lee wrote: > From: Hyunchul Lee > > Using

Re: CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

[...] > Oh - and talking about "big step forward" - does the 0day robot do > any > suspend/resume testing at all? Yes, we do. CC Rui and Aaron on power testing. yes, we have added suspend/resume test in 0day, including both functionality and suspend/resume performance. It is not widely run

Fwd: FW: [PATCH 15/31] nds32: System calls handling

>>On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote: >> From: Greentime Hu > >> +#endif /* __ASM_NDS32_SYSCALLS_H */ >> diff --git a/arch/nds32/include/asm/unistd.h >> b/arch/nds32/include/asm/unistd.h new file mode 100644 index >> 000..b30adca

Re: [PATCH 1/2] sched/swait: allow swake_up() to return

On Fri, Nov 10, 2017 at 09:05:20AM +0100, Peter Zijlstra wrote: > On Fri, Nov 10, 2017 at 03:10:17PM +0800, Peter Xu wrote: > > I came to this when reading kvm_vcpu_wake_up(), so that only affects > > some statistic which may not be that critical. However I don't know > > whether there would be

[PATCH] quota: be aware of error from dquot_initialize

Commit 6184fc0b8dd7 ("quota: Propagate error from ->acquire_dquot()") missed to handle error from dquot_initialize in dquot_file_open, fix it. Signed-off-by: Chao Yu --- fs/quota/dquot.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/quota/dquot.c

Re: [PATCH v8 1/6] x86/tsc: remove tsc_disabled flag

Hi Pavel, At 11/09/2017 11:01 AM, Pavel Tatashin wrote: tsc_disabled is set when notsc is passed as kernel parameter. The reason we have notsc is to avoid timing problems on multi-socket systems. We already have a mechanism, however, to detect and resolve these issues by invoking tsc unstable

Re: [PATCH] radix-tree: replace with

Hi Andrew, 2017-10-13 22:03 GMT+09:00 Masahiro Yamada : > This header contains references to spinlock_t and lockdep_is_held(), > both of which are defined in > > Signed-off-by: Masahiro Yamada I have not got any comment on this

Re: [PATCH 1/2] sched/swait: allow swake_up() to return

On Mon, Nov 13, 2017 at 11:33:43AM +0800, Peter Xu wrote: > On Fri, Nov 10, 2017 at 09:05:20AM +0100, Peter Zijlstra wrote: > > On Fri, Nov 10, 2017 at 03:10:17PM +0800, Peter Xu wrote: > > > I came to this when reading kvm_vcpu_wake_up(), so that only affects > > > some statistic which may not be

linux-next: Tree for Nov 13

Hi all, Please do not add any v4.16 material to your linux-next included trees until v4.15-rc1 has been released. Changes since 20171110: The powerpc tree still had its build failure for which I applied a patch The keys tree gained a build failure so I used the version from next-20171110.

[PATCH] KVM: X86: Avoid to handle first-time write when updating the pv stuffs each time

From: Wanpeng Li There is a logic to handle first-time write when updating the pvclock/wall clock/steal time shared memory pages each time, actually we should do this logic during pv stuffs setup if we suspect the version-field can't be guranteed to be initialized to

[GIT PULL] RCU updates for v4.15

Linus, Please pull the latest core-rcu-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus # HEAD: 72bc286b81d21404cdfecddf76b64c7163aac764 Merge branch 'for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into

Re: [PATCH] perf/core: fast breakpoint modification via _IOC_MODIFY_BREAKPOINT

On Sun, Nov 12, 2017 at 11:09:23AM -0800, Milind Chabbi wrote: > , > > On Thu, Nov 9, 2017 at 10:59 AM, Milind Chabbi > wrote: > > SNIP > > > > On Thu, Nov 9, 2017 at 5:12 AM, Jiri Olsa wrote: > >> > >> > >> how about something like below (untested)

[PATCH] perf tool: Fix build failure when NO_AUXTRACE=1

Perf tool fails with following build failure when AUXTRACE is not set: $ make NO_AUXTRACE=1 builtin-script.c: In function 'perf_script__process_auxtrace_info': util/auxtrace.h:608:44: error: called object is not a function or function pointer #define perf_event__process_auxtrace_info 0

[GIT PULL] fscrypt updates for 4.15

The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff: Linux 4.14-rc3 (2017-10-01 14:54:54 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git tags/fscrypt-for-linus for you to fetch changes up to

[PATCH] vmbus: unregister device_obj->channels_kset

Fixes: c2e5df616e1a ("vmbus: add per-channel sysfs info") Without the patch, a device can't be thoroughly destroyed, because vmbus_device_register() -> kset_create_and_add() still holds a reference to the hv_device's device.kobj. Signed-off-by: Dexuan Cui Cc: Stephen

Re: [RFC PATCH 0/2] apply write hints to select the type of segments

On 11/13/2017 10:59 AM, Chao Yu wrote: > On 2017/11/13 9:35, Hyunchul Lee wrote: >> On 11/13/2017 10:26 AM, Chao Yu wrote: >>> On 2017/11/13 8:24, Hyunchul Lee wrote: On 11/10/2017 03:42 PM, Chao Yu wrote: > On 2017/11/10 8:23, Hyunchul Lee wrote: >> Hello, Chao >> >> On

Re: [PATCH v3 2/3] drivers: hwmon: Add W83773G driver

On Fri, Nov 10, 2017 at 10:49 PM, Guenter Roeck wrote: > On 11/08/2017 11:09 PM, Lei YU wrote: >> >> Nuvoton W83773G is a hardware monitor IC providing one local >> temperature and two remote temperature sensors. >> >> Signed-off-by: Lei YU > > > Nicely

Re: [PATCH 7/7] blk-throtl: don't throttle the same IO multiple times

On Sun, Nov 12, 2017 at 02:26:13PM -0800, Tejun Heo wrote: > BIO_THROTTLED is used to mark already throttled bios so that a bio > doesn't get throttled multiple times. The flag gets set when the bio > starts getting dispatched from blk-throtl and cleared when it leaves > blk-throtl. > >

Re: [PATCH] net: dsa: lan9303: correctly check return value of devm_gpiod_get_optional

On 12/11/2017 23:38, Pan Bian wrote: Function devm_gpiod_get_optional() returns an ERR_PTR on failure. Its return value should not be validated by a NULL check. Instead, use IS_ERR. Signed-off-by: Pan Bian --- drivers/net/dsa/lan9303-core.c | 2 +- 1 file changed, 1

Re: [PATCH 1/2] blk-throtl: make latency= absolute

On Fri, Nov 10, 2017 at 07:43:14AM -0800, Tejun Heo wrote: > Hello, Shaohua. > > On Thu, Nov 09, 2017 at 08:27:13PM -0800, Shaohua Li wrote: > > I think the absolute latency would only work for HD. For a SSD, a 4k latency > > probably is 60us and 1M latency is 500us. The disk must be very

Re: linux-next: manual merge of the drivers-x86 tree with the net-next tree

Hi all, On Mon, 9 Oct 2017 18:56:33 +0100 Mark Brown wrote: > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > Documentation/admin-guide/thunderbolt.rst > > between commit: > >e69b6c02b4c3b ("net: Add support for networking over Thunderbolt

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: In file included from include/linux/mmzone.h:17:0, from include/linux/mempolicy.h:10, from mm/mempolicy.c:70: mm/mempolicy.c: In function

Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl

On Mon, 2017-11-13 at 09:21 +1100, Tobin C. Harding wrote: > On Fri, Nov 10, 2017 at 07:26:34PM +0530, kaiwan.billimo...@gmail.com > wrote: > > On Tue, 2017-11-07 at 21:32 +1100, Tobin C. Harding wrote: > > > Currently we are leaking addresses from the kernel to user space. > > > This > > >

Re: [PATCH 2/3] Input: twl6040-vibra: fix child-node lookup

On 2017-11-11 17:43, Johan Hovold wrote: > Fix child-node lookup during probe, which ended up searching the whole > device tree depth-first starting at parent rather than just matching on > its children. > > Later sanity checks on node properties (which would likely be missing) > should prevent

Re: [PATCH 1/3] Input: twl4030-vibra: fix sibling-node lookup

On 2017-11-11 17:43, Johan Hovold wrote: > A helper purported to look up a child node based on its name was using > the wrong of-helper and ended up prematurely freeing the parent of-node > while searching the whole device tree depth-first starting at the parent > node. > > Fixes: 64b9e4d803b1

RE: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

Hello Michal, > Date: Fri, 13 Oct 2017 14:00:12 +0200 > > From: Michal Hocko > > Michael has noticed that the memory offline tries to migrate kernel code > pages when doing echo 0 > /sys/devices/system/memory/memory0/online > > The current implementation will fail the

Re: Improving documentation of parent-ID field in /proc/PID/mountinfo

On Mon, Nov 13, 2017 at 07:02:21AM +0100, Michael Kerrisk (man-pages) wrote: > Hello Ram, > > Long ago (2.6.29) you added the /proc/PID/mountinfo file and > associated documentation in Documentation/filesystems/proc.txt. Later, > I pasted much of that documentation into the proc(5) manual page. >

Re: [PATCH 2/2 v5] typec: tcpm: Only request matching pdos

On Tue, Nov 7, 2017 at 4:07 AM, Heikki Krogerus wrote: > On Sat, Nov 04, 2017 at 12:22:13PM -0700, Badhri Jagan Sridharan wrote: >> At present, TCPM code assumes that local device supports >> variable/batt pdos and always selects the pdo with highest >> possible

Re: [PATCH v3 4/4] KVM: Add flush_on_enter before guest enter

2017-11-10 18:07 GMT+08:00 Peter Zijlstra : > On Fri, Nov 10, 2017 at 01:49:47AM -0800, Wanpeng Li wrote: >> @@ -2116,7 +2122,13 @@ static void record_steal_time(struct kvm_vcpu *vcpu) >> >arch.st.steal, sizeof(struct kvm_steal_time >> return;

Re: [PATCH net-next] net: dsa: lan9303: Documentation: Add missing word "Mbps"

From: Egil Hjelmeland Date: Wed, 8 Nov 2017 11:55:14 +0100 > Signed-off-by: Egil Hjelmeland Applied.

Re: [ftrace-bpf 1/5] add BPF_PROG_TYPE_FTRACE to bpf

On Sun, Nov 12, 2017 at 07:28:24AM +, yupeng0...@gmail.com wrote: > Add a new type BPF_PROG_TYPE_FTRACE to bpf, let bpf can be attached to > ftrace. Ftrace pass the function parameters to bpf prog, bpf prog > return 1 or 0 to indicate whether ftrace can trace this function. The > major propose

[PATCH v2 1/2] arm64: Define cputype macros for Falkor CPU

Add cputype definition macros for Qualcomm Datacenter Technologies Falkor CPU in cputype.h. It's unfortunate that the first revision of the Falkor CPU used the wrong part number 0x800, got fixed in v2 chip with part number 0xC00, and would be used the same value for future revisions.

[PATCH v2 2/2] arm64: Add software workaround for Falkor erratum 1041

The ARM architecture defines the memory locations that are permitted to be accessed as the result of a speculative instruction fetch from an exception level for which all stages of translation are disabled. Specifically, the core is permitted to speculatively fetch from the 4KB region containing

[PATCH v2 0/2] Implement a software workaround for Falkor erratum 1041

On Falkor CPU, we’ve discovered a hardware issue which might lead to a kernel crash or the unexpected behavior. The Falkor core may errantly access memory locations on speculative instruction fetches. This may happen whenever MMU translation state, SCTLR_ELn[M] bit is being changed from enabled to

Re: [PATCH v4] af_netlink: ensure that NLMSG_DONE never fails in dumps

From: David Miller Date: Sat, 11 Nov 2017 23:21:01 +0900 (KST) > Aha, that's what I missed. Indeed, it cannot happen. Applied and queued up for -stable.

Re: [RFC PATCH 0/2] apply write hints to select the type of segments

On 2017/11/13 9:35, Hyunchul Lee wrote: > On 11/13/2017 10:26 AM, Chao Yu wrote: >> On 2017/11/13 8:24, Hyunchul Lee wrote: >>> On 11/10/2017 03:42 PM, Chao Yu wrote: On 2017/11/10 8:23, Hyunchul Lee wrote: > Hello, Chao > > On 11/09/2017 06:12 PM, Chao Yu wrote: >> On

[PATCH 4/4] x86/umip: Warn if UMIP-protected instructions are used

Issue a rate-limited warning whenever any of the instructions that UMIP protects (i.e., sgdt, sidt, sldt, str and smsw) are used by user space programs. This is useful because, with UMIP enabled, the few programs that use such instructions will start receiving a SIGSEGV signal. In the specific

Re: [PATCH] drm/rockchip: analogix_dp: Use mutex rather than spinlock

On 2017年11月10日 20:07, Enric Balletbo Serra wrote: 2017-10-04 19:53 GMT+02:00 Emil Renner Berthing : On the Samsung Chromebook Plus I get this error with 4.14-rc3: BUG: scheduling while atomic: kworker/3:1/50/0x0002 Modules linked in: CPU: 3 PID: 50 Comm: kworker/3:1 Not

[PATCH 1/4] x86/umip: Select X86_INTEL_UMIP by default

UMIP does not incur in a significant performance penalty. Furthermore, it is triggered only when a small group of instructions are used from user space programs. While here, provide more details on the benefits UMIP provides and the behavior that can expect the few applications that use the

[PATCH 0/4] x86: Tweaks for UMIP

Now that the support for UMIP [1], [2] has been merged in the tip tree, this series add a couple of tweaks. Ingo asked for two small additions to select UMIP by default when building and inform of this feature being enabled [3]. Also, Linus suggested to issue a rate-limited warning whenever the

[PATCH 3/4] x86/umip: Identify the str and sldt instructions

The instructions str and sldt are not emulated in any case. Thus, it made sense to not implement functionality to identify them. However, a subsequent commit will introduce functionality to warn about the use of all the instructions that UMIP protect, not only those that are emulated. A first step

[PATCH 2/4] x86/umip: Inform that UMIP has been enabled

Let us have an indication that this feature has been enabled. Cc: Andy Lutomirski Cc: H. Peter Anvin Cc: Borislav Petkov Cc: Tony Luck Cc: Paolo Bonzini Cc: Ravi V. Shankar Cc:

[PATCH net-next V2] vhost_net: conditionally enable tx polling

We always poll tx for socket, this is sub optimal since this will slightly increase the waitqueue traversing time and more important, vhost could not benefit from commit 9e641bdcfa4e ("net-tun: restructure tun_do_read for better sleep/wakeup efficiency") even if we've stopped rx polling during

Re: [kernel-hardening] Re: [PATCH v4] scripts: add leaking_addresses.pl

On Mon, Nov 13, 2017 at 10:05 AM, Tobin C. Harding wrote: > On Mon, Nov 13, 2017 at 06:37:28AM +0300, Kirill A. Shutemov wrote: >> On Mon, Nov 13, 2017 at 10:06:46AM +1100, Tobin C. Harding wrote: >> > On Sun, Nov 12, 2017 at 02:10:07AM +0300, Kirill A. Shutemov wrote: ... >> > >>

Re: linux-next: manual merge of the integrity tree with the jc-docs tree

Hi all, On Wed, 18 Oct 2017 11:50:25 +0100 Mark Brown wrote: > > Today's linux-next merge of the integrity tree got a conflict in: > > Documentation/ABI/testing/evm > > between commit: > > c7f66400f504fd5 ("Documentation: fix security related doc refs") > > from the

[PATCH BUGFIX/IMPROVEMENT 3/4] block, bfq: update blkio stats outside the scheduler lock

bfq invokes various blkg_*stats_* functions to update the statistics contained in the special files blkio.bfq.* in the blkio controller groups, i.e., the I/O accounting related to the proportional-share policy provided by bfq. The execution of these functions takes a considerable percentage, about

[PATCH BUGFIX/IMPROVEMENT 4/4] block, bfq: move debug blkio stats behind CONFIG_DEBUG_BLK_CGROUP

From: Luca Miccio BFQ currently creates, and updates, its own instance of the whole set of blkio statistics that cfq creates. Yet, from the comments of Tejun Heo in [1], it turned out that most of these statistics are meant/useful only for debugging. This commit makes BFQ

[PATCH BUGFIX/IMPROVEMENT 1/4] doc, block, bfq: update max IOPS sustainable with BFQ

We have investigated more deeply the performance of BFQ, in terms of number of IOPS that can be processed by the CPU when BFQ is used as I/O scheduler. In more detail, using the script [1], we have measured the number of IOPS reached on top of a null block device configured with zero latency, as a

Re: [PATCH] KVM: x86: inject exceptions produced by x86_decode_insn

2017-11-10 17:49 GMT+08:00 Paolo Bonzini : > Sometimes, a processor might execute an instruction while another > processor is updating the page tables for that instruction's code page, > but before the TLB shootdown completes. The interesting case happens > if the page is in

Re: [PATCH] arch, mm: introduce arch_tlb_gather_mmu_lazy (was: Re: [RESEND PATCH] mm, oom_reaper: gather each vma to prevent) leaking TLB entry

On Fri, Nov 10, 2017 at 01:26:35PM +0100, Michal Hocko wrote: > On Fri 10-11-17 11:15:29, Michal Hocko wrote: > > On Fri 10-11-17 09:19:33, Minchan Kim wrote: > > > On Tue, Nov 07, 2017 at 09:54:53AM +, Wang Nan wrote: > > > > tlb_gather_mmu(, mm, 0, -1) means gathering the whole virtual

[PATCH] x86 / CPU: Avoid unnecessary IPIs in arch_freq_get_on_cpu()

From: Rafael J. Wysocki Even though aperfmperf_snapshot_khz() caches the samples.khz value to return if called again in a sufficiently short time, its caller, arch_freq_get_on_cpu(), still uses smp_call_function_single() to run it which may allow user space to trigger

Re: [RFC PATCH 0/2] apply write hints to select the type of segments

On 11/13/2017 10:26 AM, Chao Yu wrote: > On 2017/11/13 8:24, Hyunchul Lee wrote: >> On 11/10/2017 03:42 PM, Chao Yu wrote: >>> On 2017/11/10 8:23, Hyunchul Lee wrote: Hello, Chao On 11/09/2017 06:12 PM, Chao Yu wrote: > On 2017/11/9 13:51, Hyunchul Lee wrote: >> From:

Re: [f2fs-dev] [RFC PATHC 2/2] f2fs: apply write hints to select the type of segment for direct write

On 11/13/2017 10:24 AM, Chao Yu wrote: > On 2017/11/13 8:07, Hyunchul Lee wrote: >> On 11/11/2017 09:38 AM, Chao Yu wrote: >>> On 2017/11/9 13:51, Hyunchul Lee wrote: From: Hyunchul Lee Select the type of the segment using write hints, when blocks are

RE: [PATCHv4 1/3] ARMv8: dts: ls1046a: add the property of IB and OB

> -Original Message- > From: Leo Li > Sent: Saturday, November 11, 2017 5:21 AM > To: Kishon Vijay Abraham I ; Xiaowei Bao > ; robh...@kernel.org; mark.rutl...@arm.com; > catalin.mari...@arm.com; will.dea...@arm.com; bhelg...@google.com; >

Fwd: FW: [PATCH 17/31] nds32: Signal handling support

>> +static int restore_sigframe(struct pt_regs *regs, >> + struct rt_sigframe __user * sf) { > >[snip] > >> + err |= !valid_user_regs(regs); > >IDGI... Where do you modify ->ipsw at all and how can valid_user_regs() come >to be false here? > Thanks. This code is

Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL

On Fri, Nov 10, 2017 at 3:04 PM, Dave Hansen wrote: > On 11/10/2017 02:06 PM, Andy Lutomirski wrote: >> On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen >> wrote: >>> On 11/09/2017 06:25 PM, Andy Lutomirski wrote: Here are two proposals

Re: [PATCH RFC] kbuild: fixes in Makefile.lib

Hi Cao, 2017-11-10 16:35 GMT+09:00 Cao jin : > commit > > cf4f21938e13e ("kbuild: Allow to specify composite modules with modname-m") > > add modname-m support, but miss to update the corresponding multi-objs-m > defination. Commit cf4f21938e13 ("kbuild: Allow to

[GIT PULL] RAS updates for v4.15

Linus, Please pull the latest ras-core-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus # HEAD: 783ca517bfd62ca516178712775e4b273292d5b1 x86/MCE/AMD: Fix mce_severity_amd_smca() signature Two minor updates to AMD SMCA support, plus a

Re: 4.14 kernel and acpi INT3400:00: Unsupported event [0x86]

On Sun, 2017-11-12 at 23:25 +0100, Arkadiusz Miskiewicz wrote: > Hello. > > On Dell XPS 9530 and 4.14 kernel dmesg is flooded with: > > [  292.580807] acpi INT3400:00: Unsupported event [0x86] > [  299.284648] acpi INT3400:00: Unsupported event [0x86] > [  305.648079] acpi INT3400:00:

[PATCH] uapi: fix linux/kfd_ioctl.h userspace compilation errors

Consistently use types provided by via to fix the following linux/kfd_ioctl.h userspace compilation errors: /usr/include/linux/kfd_ioctl.h:236:2: error: unknown type name 'uint64_t' uint64_t va_addr; /* to KFD */ /usr/include/linux/kfd_ioctl.h:237:2: error: unknown type name 'uint32_t'

[PATCH] uapi: fix linux/rxrpc.h userspace compilation errors

Consistently use types provided by to fix the following linux/rxrpc.h userspace compilation errors: /usr/include/linux/rxrpc.h:24:2: error: unknown type name 'u16' u16 srx_service; /* service desired */ /usr/include/linux/rxrpc.h:25:2: error: unknown type name 'u16' u16 transport_type; /*

CONFIG_DEBUG_INFO_SPLIT impacts on faddr2line

CC Andi and more DEBUG_INFO_SPLIT people. On Sun, Nov 12, 2017 at 11:31:56AM -0800, Linus Torvalds wrote: On Wed, Nov 8, 2017 at 9:12 AM, Fengguang Wu wrote: OK. Here is the original faddr2line output: $ ~/linux/scripts/faddr2line vmlinux

Re: [PATCH v4] f2fs: fix out-of-free problem caused by atomic write

ping... On 2017/11/8 10:17, Yunlong Song wrote: f2fs_balance_fs only actives once in the commit_inmem_pages, but there are more than one page to commit, so all the other pages will miss the check. This will lead to out-of-free problem when commit a very large file. However, we cannot do

[lkp-robot] [x86/asm/64] e04a713254: double_fault:#[##]

FYI, we noticed the following commit (built with gcc-6): commit: e04a713254ef50629d1ae9558ddd4c118b7cb807 ("x86/asm/64: Use a percpu trampoline stack for IDT entries") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_stack.wip in testcase: boot on test machine:

linux-next: build warnings after merge of the keys tree

Hi David, After merging the keys tree, today's linux-next build (arm multi_v7_defconfiga) produced these warning: certs/system_keyring.c:39:23: warning: 'trusted_keyring_acl' defined but not used [-Wunused-variable] static struct key_acl trusted_keyring_acl = { ^

[PATCH v4 0/3] Add W83773G hwmon sensor driver and doc

Nuvoton W83773G is a hardware monitoring chip, which integrates two remote and one local temperature sensors. --- v2: - The driver is re-written as v1's comment, so the author is changed to me. - Added the device to trivial-devices.txt v3: - Update the driver to use new API

[PATCH v4 2/3] drivers: hwmon: Add W83773G driver

Nuvoton W83773G is a hardware monitor IC providing one local temperature and two remote temperature sensors. Signed-off-by: Lei YU --- v2: - Rewrite the driver using regmap - Add offset and update_interval v3: - Use devm_hwmon_device_register_with_info() with

Re: [PATCH] coccinelle: orplus: reodganize to improve performance

Hi Julia, 2017-11-13 3:41 GMT+09:00 Julia Lawall : > Adding two #define constants is less common than performing & and | > operations on them, so put the addition first to reduce the set of cases > that have to be considered in detail. At the same time, add & and | >

Re: [PATCH 2/3] X86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEM

On 10/24/17 at 01:31pm, Dave Young wrote: > Now crashkernel=X will fail if there's not enough memory at low region > (below 896M) when trying to reserve large memory size. One can use > crashkernel=xM,high to reserve it at high region (>4G) but it is more > convinient to improve crashkernel=X to:

[git pull] m68knommu changes for v4.15

Hi Linus, Can you please pull the m68knommu git tree, for-next branch. The bulk of the changes are to support the ColdFire 5441x SoC family with their MMU enabled. The parts have been supported for a long time now, but only in no-MMU mode. Angelo Dureghello has a new board with a 5441x and we

Re: linux-next: manual merge of the cgroup tree with the net-next tree

Hi Mark, On Mon, 9 Oct 2017 19:38:36 +0100 Mark Brown wrote: > > Hi Tejun, > > Today's linux-next merge of the cgroup tree got a conflict in: > > kernel/cgroup/cgroup.c > > between commit: > > 324bda9e6c5ad ("bpf: multi program support for cgroup+bpf") > > from the

[PATCH] powerpc/perf: Add debugfs interface for imc run-mode and run-status

In memory Collection (IMC) counter pmu driver controls the ucode's execution state. At the system boot, IMC perf driver pause the ucode. Ucode state is changed to "running" only when any of the nest units are monitored or profiled using perf tool.

Re: linux-next: manual merge of the powerpc tree with Linus' tree

Hi all, On Mon, 30 Oct 2017 12:51:33 + Mark Brown wrote: > > Hi all, > > Today's linux-next merge of the powerpc tree got a conflict in: > > arch/powerpc/kvm/powerpc.c > > between commit: > > ac64115a66c1 ("KVM: PPC: Fix oops when checking KVM_CAP_PPC_HTM") > >

Re: linux-next: manual merge of the ext4 tree with the fscrypt tree

Hi all, On Mon, 30 Oct 2017 14:48:04 + Mark Brown wrote: > > Today's linux-next merge of the ext4 tree got a conflict in: > > fs/ext4/inode.c > > between commit: > > 2ee6a576be564272 ("fs, fscrypt: add an S_ENCRYPTED inode flag") > > from the fscrypt tree and

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/printk.h:7:0, from include/linux/kernel.h:14, from lib/test_find_bit.c:28: lib/test_find_bit.c: In function

Re: [PATCH v4 4/4] ARM64: dts: meson: drop "sana" clock from SAR ADC

Hi Kevin & others I'd like to just re-send the patch [4/4] (while leave others[1-3/4] unchanged), to have separated DT patch the for 32bit / 64bit platform. is this ok for you? On 11/12/17 09:33, Martin Blumenstingl wrote: > Hi Yixun, > > On Tue, Nov 7, 2017 at 3:10 PM, Yixun Lan

  1   2   3   4   5   6   7   >