Re: [PATCH 01/12] blkcg: obtaining blkg should be enclosed insidercu_read_lock()

[Vivek Goyal]

On Wed, Jan 18, 2012 at 05:11:19PM -0800, Tejun Heo wrote:
> When looking up or creating blkg's, both blk-throttle and cfq-iosched
> drops rcu_read_lock() right after lookup is complete.  This isn't
> safe.  Refcnt isn't incremented at that point and rcu lock is the only
> thing holding the blkg.  It shouldn't be dropped until after refcnt is
> incremented by the caller.

Hi Tejun,

throtl_get_tg() and cfq_get_cfqg() are called with queue lock held and
tg and cfqg are protected by queue lock as they can not go away as long
as queue lock is held.

If the group is already created, then caller accesses it under queue
lock and does not pass the pointer around. In case of throttling, caller
can use it under rcu also just to do update of stats (when there are
no rules).

I had used rcu read lock to access blkcg pointer here. That's why when
we are done with accessing blkcg, we drop rcu read lock and return back
to caller with group pointer, which is aready holding either a queue
lock or rcu read lock to protect returned group pointer.

So if we are protecting blkcg using rcu, then it should make sense to
take that lock inside throtl_get_tg() and cfq_get_cfqg() respectively and
it should not be left to the caller?

Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/