From: Tejun Heo <tj@kernel.org>
To: Shaohua Li <shli@fb.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] kthread: move the cgroup info initialization early
Date: Tue, 7 Nov 2017 10:05:58 -0800 [thread overview]
Message-ID: <20171107180558.GA4164960@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <28c1d60a523362bdf7db7a96a6b1ab80c8689141.1510077329.git.shli@fb.com>
On Tue, Nov 07, 2017 at 09:57:03AM -0800, Shaohua Li wrote:
> kthread() could bail out early before we initialize blkcg_css (if the
> kthread is killed very soon), which confuses free_kthread_struct. Move
> the blkcg_css initialization early.
>
> Reported-by: syzbot <syzkaller@googlegroups.com>
> Fix: 05e3db9(kthread: add a mechanism to store cgroup info)
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Tejun Heo <tj@kernel.org>
> Signed-off-by: Shaohua Li <shli@fb.com>
> ---
> kernel/kthread.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/kthread.c b/kernel/kthread.c
> index f87cd8b4..cf5c113 100644
> --- a/kernel/kthread.c
> +++ b/kernel/kthread.c
> @@ -205,6 +205,10 @@ static int kthread(void *_create)
> int ret;
>
> self = kmalloc(sizeof(*self), GFP_KERNEL);
> +#ifdef CONFIG_BLK_CGROUP
> + if (self)
> + self->blkcg_css = NULL;
> +#endif
That's not a big struct and I can't imagine that avoiding zeroing it
matters in anyway. Can't we just use kzalloc() instead and drop the
ugly ifdef?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-11-07 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 17:57 Shaohua Li
2017-11-07 18:05 ` Tejun Heo [this message]
2017-11-07 18:15 ` Andrew Morton
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=20171107180558.GA4164960@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=shli@fb.com \
/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®