linux-kernel - Re: Re: cgroup: Fix split bio been throttled more than once

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160706150629.GA31684@mtj.duckdns.org>
Date:	Wed, 6 Jul 2016 11:06:29 -0400
From:	Tejun Heo <tj@...nel.org>
To:	aaronlee0817 <aaronlee0817@....com>
Cc:	axboe@...nel.dk, mlin@...nel.org, shli@...nel.org,
	linux-kernel@...r.kernel.org, cgroup@...r.kernel.org,
	jiale0817.li@...sung.com, yanzi.zhang@...sung.com,
	zhen1.zhang@...sung.com, linux-block@...r.kernel.org
Subject: Re: Re: cgroup: Fix split bio been throttled more than once

Hello,

On Wed, Jul 06, 2016 at 10:58:55PM +0800, aaronlee0817 wrote:
> >But that said, can't we just copy BIO_THROTLED while splitting?
> 
> In my opinion， copying BIO_THROTLED while splitting doesn't work
> with this, because, the bio within the limit will not set BIO_THROTLED
> but will be split, and back to call generic_make_request(), and will be 
> count twice.

I see.  It's just a bit weird that we're marking this from clone site
when it's an issue which is specific to throttling.  The thing is
depending on how bio clone is used, it could misbehave in the other
direction (bio not accounted at all).  What we want to know is whether
a bio has been previously accounted or not, rather than whether a bio
is a result of splitting.  I think it'd be better to track that
instead.

Thanks.

-- 
tejun