From: Jens Axboe <axboe@kernel.dk>
To: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] blk-throttle: check stats_cpu before reading it from sysfs
Date: Wed, 18 Feb 2015 10:50:07 -0800 [thread overview]
Message-ID: <54E4DEDF.1010102@kernel.dk> (raw)
In-Reply-To: <1424114206-17504-1-git-send-email-cascardo@linux.vnet.ibm.com>
On 02/16/2015 11:16 AM, Thadeu Lima de Souza Cascardo wrote:
> When reading blkio.throttle.io_serviced in a recently created blkio
> cgroup, it's possible to race against the creation of a throttle policy,
> which delays the allocation of stats_cpu.
>
> Like other functions in the throttle code, just checking for a NULL
> stats_cpu prevents the following oops caused by that race.
Applied for this series, thanks.
--
Jens Axboe
prev parent reply other threads:[~2015-02-18 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 19:16 [PATCH] blk-throttle: check stats_cpu before reading it from sysfs Thadeu Lima de Souza Cascardo
2015-02-18 18:50 ` Jens Axboe [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=54E4DEDF.1010102@kernel.dk \
--to=axboe@kernel.dk \
--cc=cascardo@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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