From: Chao Yu <yuchao0@huawei.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] fs/f2fs: a possible sleep-in-atomic bug in f2fs_trace_pid
Date: Tue, 12 Dec 2017 10:00:54 +0800 [thread overview]
Message-ID: <9272d87c-ef9b-a19d-ffe1-1db2b8785d74@huawei.com> (raw)
In-Reply-To: <8e7328d3-2df3-e79d-9558-a9b3713751c4@gmail.com>
Hi Jia-Ju,
Thanks for your report. :)
On 2017/12/12 8:59, Jia-Ju Bai wrote:
> According to fs/f2fs/trace.c, the kernel module may sleep under a spinlock.
> The function call path is:
> f2fs_trace_pid (acquire the spinlock)
> f2fs_radix_tree_insert
> cond_resched --> may sleep
>
> I do not find a good way to fix it, so I only report.
> This possible bug is found by my static analysis tool (DSAC) and my code
> review.
That's a known issue, and there are other problems in IO trace related codes,
so I want to refactor the code directly, you could check the code in below link:
https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev&id=d895154be1733e2bd29c9e64b57e4e201f0e8a0c
But the patch still needs debugging so far. Since the IO trace feature is off
by default, I expect the impaction is limited, so I pend the debug job on this
patch.
Anyway, I think this issue you reported should be fixed first, let me make the
fixing part independent from original patch for fixing.
Thanks,
>
>
> Thanks,
> Jia-Ju Bai
>
>
prev parent reply other threads:[~2017-12-12 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 0:59 [BUG] fs/f2fs: a possible sleep-in-atomic bug in f2fs_trace_pid Jia-Ju Bai
2017-12-12 2:00 ` Chao Yu [this message]
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=9272d87c-ef9b-a19d-ffe1-1db2b8785d74@huawei.com \
--to=yuchao0@huawei.com \
--cc=baijiaju1990@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).