[tip:x86/urgent] x86/vdso: Fix flip/flop vdso build bug

Commit-ID: e9a1379f9219be439f47a0f063431a92dc529eda Gitweb: https://git.kernel.org/tip/e9a1379f9219be439f47a0f063431a92dc529eda Author: Naohiro Aota AuthorDate: Fri, 12 Jul 2019 19:15:55 +0900 Committer: Thomas Gleixner CommitDate: Fri, 12 Jul 2019 17:35:07 +0200 x86/vdso: Fix flip

[PATCH v2 2/2] arm64/vdso: fix flip/flop vdso build bug

function. Cc: Masahiro Yamada Fixes: 28b1a824a4f4 ("arm64: vdso: Substitute gettimeofday() with C implementation") Signed-off-by: Naohiro Aota --- arch/arm64/kernel/vdso/Makefile | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/arch/arm64/kernel/vdso/Makefile

[PATCH v2 1/2] x86/vdso: fix flip/flop vdso build bug

into one function. Cc: Masahiro Yamada Fixes: 7ac870747988 ("x86/vdso: Switch to generic vDSO implementation") Signed-off-by: Naohiro Aota --- arch/x86/entry/vdso/Makefile | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/entry/vdso/Makefile

Re: [PATCH] x86/vdso, arm64/vdso: fix flip/flop vdso build bug

On Fri, Jul 12, 2019 at 03:24:01PM +0900, Masahiro Yamada wrote: On Fri, Jul 12, 2019 at 2:46 PM Naohiro Aota wrote: Two consecutive "make" on an already compiled kernel tree will show different behavior: $ make CALLscripts/checksyscalls.sh CALLscripts/atomic/check-

[PATCH] x86/vdso, arm64/vdso: fix flip/flop vdso build bug

is causing "LD vmlinux" once every two times even without any modifications. This is the same bug fixed in commit 92a4728608a8 ("x86/boot: Fix if_changed build flip/flop bug"). We cannot use two "if_changed" in one target. Fix this build bug by merging two commands in

Re: [PATCH 02/19] btrfs: Get zone information of zoned block devices

On 2019/06/13 22:58, Josef Bacik wrote: > On Fri, Jun 07, 2019 at 10:10:08PM +0900, Naohiro Aota wrote: >> If a zoned block device is found, get its zone information (number of zones >> and zone size) using the new helper function btrfs_get_dev_zonetypes(). To >> avoid costly

[PATCH 10/12] btrfs-progs: mkfs: Zoned block device support

tory setup. Signed-off-by: Naohiro Aota --- mkfs/common.c | 12 +++- mkfs/common.h | 1 + mkfs/main.c | 45 +++-- 3 files changed, 47 insertions(+), 11 deletions(-) diff --git a/mkfs/common.c b/mkfs/common.c index f7e3badcf2b9..12af54c1d886 100644

[PATCH 05/12] btrfs-progs: load and check zone information

This patch checks if a device added to btrfs is a zoned block device. If it is, load zones information and the zone size for the device. For a btrfs volume composed of multiple zoned block devices, all devices must have the same zone size. Signed-off-by: Naohiro Aota --- utils.c | 10

[PATCH 11/12] btrfs-progs: device-add: support HMZONED device

This patch check if the target file system is flagged as HMZONED. If it is, the device to be added is flagged PREP_DEVICE_HMZONED. Also add checks to prevent mixing non-zoned devices and zoned devices. Signed-off-by: Naohiro Aota --- cmds-device.c | 29 +++-- 1 file

[PATCH 07/19] btrfs: do sequential extent allocation in HMZONED mode

ps track of the size of once allocated then freed region. Such region is never usable until resetting underlying zones. Signed-off-by: Naohiro Aota --- fs/btrfs/ctree.h| 24 +++ fs/btrfs/extent-tree.c | 378 ++-- fs/btrfs/free-space-cache.c | 33

[PATCH 04/19] btrfs: disable fallocate in HMZONED mode

supported when in HMZONED mode for now. In the future, we may be able to implement "in-memory" fallocate() in HMZONED mode by utilizing space_info->bytes_may_use or so. Signed-off-by: Naohiro Aota --- fs/btrfs/file.c | 4 1 file changed, 4 insertions(+) diff --git a/fs/btrf

[PATCH 05/19] btrfs: disable direct IO in HMZONED mode

Direct write I/Os can be directed at existing extents that have already been written. Such write requests are prohibited on host-managed zoned block devices. So disable direct IO support for a volume with HMZONED mode enabled. Signed-off-by: Naohiro Aota --- fs/btrfs/inode.c | 3 +++ 1 file

[PATCH 03/19] btrfs: Check and enable HMZONED mode

with sequential block groups: all the free space is located after the allocation pointer and no free space before the pointer. There is no need to have such cache. Signed-off-by: Damien Le Moal Signed-off-by: Naohiro Aota --- fs/btrfs/ctree.h | 3 ++ fs/btrfs/dev-replace.c | 7 +++ fs

Re: [PATCH][RESEND] fs: always set I_DIRTY_TIME to fsync correctly on lazytime

Hello, all What is the status of this patch? Can this be picked up for some tree? Regards, Naohiro 2016-11-01 7:46 GMT+09:00 Jan Kara : > On Tue 01-11-16 04:02:45, Naohiro Aota wrote: >> While lazytime states that "The on-disk timestamps are updated only >> when: ... - the

[PATCH] uapi: add missing install of userio.h

While commit 5523662edd4f ("Input: add userio module") added userio.h under the uapi/ directory, it forgot to add the header file to Kbuild. Thus, the file is missing from header installation. This patch just resolve the issue by adding the missing entry. Signed-off-by: Naohiro Aota --

[PATCH][RESEND] fs: always set I_DIRTY_TIME to fsync correctly on lazytime

jbd2/loop0-8-1879 [003] 208.347618: jbd2_end_commit: dev 7,0 transaction 5367 sync 0 head 3343 ... Reported-by: Asraa Ali Mardan Signed-off-by: Naohiro Aota --- fs/fs-writeback.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback

[PATCH] fs: always set I_DIRTY_TIME to fsync correctly on lazytime

jbd2/loop0-8-1879 [003] 208.347618: jbd2_end_commit: dev 7,0 transaction 5367 sync 0 head 3343 ... Reported-by: Asraa Ali Mardan Signed-off-by: Naohiro Aota --- fs/fs-writeback.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback

Re: [PATCH] btrfs: let btrfs_delete_unused_bgs() to clean relocated bgs

2016-09-02 (金) の 09:35 -0400 に Josef Bacik さんは書きました: > On 09/02/2016 03:46 AM, Naohiro Aota wrote: > > > > Currently, btrfs_relocate_chunk() is removing relocated BG by > > itself. But > > the work can be done by btrfs_delete_unused_bgs() (and it's better >

[PATCH] btrfs: let btrfs_delete_unused_bgs() to clean relocated bgs

"ro" flag set (to keep balancing BG intact). On the other hand, btrfs cannot drop "ro" flag here to prevent additional writes. So this patch make use of "removed" flag. btrfs_delete_unused_bgs() now detect the flag to distinguish whether a read-only BG is relocat

[tip:perf/urgent] perf probe: Support signedness casting

Commit-ID: 19f00b011729417f69e4df53cc3fe5ecc25134a4 Gitweb: http://git.kernel.org/tip/19f00b011729417f69e4df53cc3fe5ecc25134a4 Author: Naohiro Aota AuthorDate: Tue, 9 Aug 2016 11:40:08 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 9 Aug 2016 10:52:22 -0300 perf probe

[PATCH v3] perf probe: Support signedness casting

98611: submit_bio: (submit_bio+0x0/0x140) bi_sector=30208 This commit also update perf-probe.txt to describe "types". Most parts are based on existing documentation: Documentation/trace/kprobetrace.txt Signed-off-by: Naohiro Aota --- tools/perf/Documentation/perf-probe.txt | 10 ++

[PATCH v2] perf probe: Support signedness casting

98611: submit_bio: (submit_bio+0x0/0x140) bi_sector=30208 This commit also update perf-probe.txt to describe "types". Most parts are based on existing documentation: Documentation/trace/kprobetrace.txt Signed-off-by: Naohiro Aota --- tools/perf/Documentation/perf-probe.txt | 10 ++

Re: [PATCH] perf probe: support signedness casting

2016-08-05 (金) の 18:10 +0900 に Masami Hiramatsu さんは書きました: > On Fri, 5 Aug 2016 14:33:53 +0900 > Naohiro Aota wrote: > > > > > Perf-probe detects a variable's type and use the detected type to > > add new > > probe. Then, kprobes prints its variable in hexa

[PATCH] perf probe: support signedness casting

). In that case, we need to investigate variable's size manually to specify just signedness. This patch add signedness casting support. By specifying "s" or "u" as a type, perf-probe will investigate variable size as usual and use the specified signedness. Signed-off-by: Naoh

Re: [PATCH][RESEND] btrfs: fix search key advancing condition

Hello, list. Could any one take a look at on this? I believe this is a issue slowing down ioctl(BTRFS_IOC_TREE_SEARCH) if the target key is missing. On Tue, Jun 30, 2015 at 11:25 AM, Naohiro Aota wrote: > The search key advancing condition used in copy_to_sk() is loose. It can > advance t

[PATCH][RESEND] btrfs: fix search key advancing condition

ctl() to take unexpectedly long time scanning all the leaf a blocks one by one. This commit fix the problem using standard way of key comparison: btrfs_comp_cpu_keys() Signed-off-by: Naohiro Aota --- fs/btrfs/ioctl.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --gi

[PATCH] btrfs: tweak key advancing condition

to take a lot of time scanning all the leaf a blocks one by one. This commit fix the problem using standard way of key comparison: btrfs_comp_cpu_keys() Signed-off-by: Naohiro Aota --- fs/btrfs/ioctl.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/ioct

[tip:perf/urgent] perf probe: Find compilation directory path for lazy matching

Commit-ID: 09ed8975c4b13be4469899b210f0e0936021ee8f Gitweb: http://git.kernel.org/tip/09ed8975c4b13be4469899b210f0e0936021ee8f Author: Naohiro Aota AuthorDate: Fri, 13 Mar 2015 14:18:40 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Apr 2015 20:11:05 -0300 perf probe

[PATCH v3] perf probe: Find compilation directory path for lazy matching

t;probe -L" can solve the souce directory by themselves. Let's make it possible for lazy matching too! Signed-off-by: Naohiro Aota --- tools/perf/util/probe-event.c | 59 --- tools/perf/util/probe-finder.c | 71

Re: Re: [PATCH v2] perf probe: Find compilation directory path for lazy matching

On Thu, Mar 12, 2015 at 10:42 AM, Masami Hiramatsu wrote: > (2015/03/11 22:30), Arnaldo Carvalho de Melo wrote: >> Em Wed, Mar 04, 2015 at 09:34:38PM +0900, Masami Hiramatsu escreveu: >>> (2015/03/04 16:52), Naohiro Aota wrote: >>>> If we use lazy matching, it faile

[PATCH v2] perf probe: Find compilation directory path for lazy matching

t;probe -L" can solve the souce directory by themselves. Let's make it possible for lazy matching too! Signed-off-by: Naohiro Aota --- tools/perf/util/probe-event.c | 59 --- tools/perf/util/probe-finder.c | 71

[PATCH 1/2] perf probe: export get_real_path

Export it to use from util/probe-finder.c Signed-off-by: Naohiro Aota --- tools/perf/util/probe-event.c | 2 +- tools/perf/util/probe-event.h | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c index 919937e

[PATCH 2/2] perf probe: Find compilation directory path for lazy matching

t;probe -L" can solve the souce directory by themselves. Let's make it possible for lazy matching too! Signed-off-by: Naohiro Aota --- tools/perf/util/probe-finder.c | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/tools/perf/util/probe-finder.c b/tools

[PATCH] btrfs: clear bio reference after submit_one_bio()

cat ${dmesgout} exit 1 fi done umount $directory exit 0 Signed-off-by: Naohiro Aota --- fs/btrfs/extent_io.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c index 4ebabd2..4421161 10

[tip:perf/core] perf python: Fix dependency for python/perf.so

Commit-ID: 707ef2e69a53f2dc60cfa2ff5cb4bf5474206f33 Gitweb: http://git.kernel.org/tip/707ef2e69a53f2dc60cfa2ff5cb4bf5474206f33 Author: Naohiro Aota AuthorDate: Sun, 24 Mar 2013 22:37:54 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 1 Apr 2013 12:23:01 -0300 perf python

[PATCH] perf: Fix dependency for python/perf.so

annot stat 'python_ext_build/lib/perf.so': No such file or directory make: *** [python/perf.so] Error 1 Signed-off-by: Naohiro Aota --- tools/perf/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/Makefile b/tools/perf/Makefile index bb74c79..d10ccda 100