From: "Michal Koutný" <mkoutny@suse.com>
To: Breno Leitao <leitao@debian.org>
Cc: axboe@kernel.dk, tj@kernel.org, josef@toxicpanda.com,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
aherrmann@suse.de, linux-kernel@vger.kernel.org, hch@lst.de,
leit@fb.com
Subject: Re: [PATCH] blk-iocost: initialize rqos before accessing it
Date: Fri, 24 Feb 2023 19:51:26 +0100 [thread overview]
Message-ID: <20230224185126.bxkreilofbp2t4on@blackpad> (raw)
In-Reply-To: <20230224160714.172884-1-leitao@debian.org>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On Fri, Feb 24, 2023 at 08:07:14AM -0800, Breno Leitao <leitao@debian.org> wrote:
> ---
> block/blk-iocost.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Well done.
Reviewed-by: Michal Koutný <mkoutny@suse.com>
[...]
> blk_iocost_init (include/asm-generic/qspinlock.h:128
> include/linux/spinlock.h:203
> include/linux/spinlock_api_smp.h:158
> include/linux/spinlock.h:400
> block/blk-iocost.c:2884)
> ioc_qos_write (block/blk-iocost.c:3198)
> ? kretprobe_perf_func (kernel/trace/trace_kprobe.c:1566)
> ? kernfs_fop_write_iter (include/linux/slab.h:584 fs/kernfs/file.c:311)
> ? __kmem_cache_alloc_node (mm/slab.h:? mm/slub.c:3452 mm/slub.c:3491)
> ? _copy_from_iter (arch/x86/include/asm/uaccess_64.h:46
> arch/x86/include/asm/uaccess_64.h:52
> lib/iov_iter.c:183 lib/iov_iter.c:628)
> ? kretprobe_dispatcher (kernel/trace/trace_kprobe.c:1693)
> cgroup_file_write (kernel/cgroup/cgroup.c:4061)
> kernfs_fop_write_iter (fs/kernfs/file.c:334)
> vfs_write (include/linux/fs.h:1849 fs/read_write.c:491
> fs/read_write.c:584)
> ksys_write (fs/read_write.c:637)
> do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)
> entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)
BTW, out of curiosity what tool did you use to list stack with line
numbers?
Thanks,
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-24 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:07 Breno Leitao
2023-02-24 18:51 ` Michal Koutný [this message]
2023-02-26 7:59 ` Breno Leitao
2023-02-26 16:55 ` Tejun Heo
2023-02-26 20:18 ` Jens Axboe
2023-02-26 20:18 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230224185126.bxkreilofbp2t4on@blackpad \
--to=mkoutny@suse.com \
--cc=aherrmann@suse.de \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=leit@fb.com \
--cc=leitao@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®