From: Jeff Moyer <jmoyer@redhat.com>
To: Zach Brown <zab@redhat.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] bdi: add a user-tunable cpu_list for the bdi flusher threads
Date: Mon, 03 Dec 2012 10:49:25 -0500 [thread overview]
Message-ID: <x49zk1vnnju.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20121130221542.GM18574@lenny.home.zabbo.net> (Zach Brown's message of "Fri, 30 Nov 2012 14:15:42 -0800")
Zach Brown <zab@redhat.com> writes:
>> + ret = cpulist_parse(buf, newmask);
>> + if (!ret) {
>> + spin_lock(&bdi->wb_lock);
>> + task = wb->task;
>> + get_task_struct(task);
>> + spin_unlock(&bdi->wb_lock);
>> + if (task)
>> + ret = set_cpus_allowed_ptr(task, newmask);
>> + put_task_struct(task);
>
> If that test for a non-null task is needed then surely the get and put
> need to be similarly protected :).
How embarrassing.
>> + bdi->flusher_cpumask = kmalloc(sizeof(cpumask_t), GFP_KERNEL);
>> + if (!bdi->flusher_cpumask)
>> + return -ENOMEM;
>
> The bare GFP_KERNEL raises an eyebrow. Some bdi_init() callers like
> blk_alloc_queue_node() look like they'll want to pass in a gfp_t for the
> allocation.
I'd be surprised if that was necessary, seeing how every single caller
of blk_alloc_queue_node passes in GFP_KERNEL. I'll make the change,
though, there aren't too many callers of bdi_init out there.
> And shouldn't this be freed in the error path of bdi_init()?
Yes. ;-)
Thanks!
Jeff
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-12-03 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 23:23 [patch] bdi: add a user-tunable cpu_list for the bdi flusher threads Jeff Moyer
2012-11-30 22:15 ` Zach Brown
2012-12-03 15:49 ` Jeff Moyer [this message]
2012-12-03 16:22 ` Jeff Moyer
2012-12-03 19:07 ` Zach Brown
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=x49zk1vnnju.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zab@redhat.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;
as well as URLs for NNTP newsgroup(s).