linux-kernel - Re: [PATCHSET v2 block/for-4.3] blkcg: blkcg

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 07 Jul 2015 22:31:14 +0200
From:	Arianna Avanzini <avanzini.arianna@...il.com>
To:	Tejun Heo <tj@...nel.org>, axboe@...nel.dk
CC:	jack@...e.cz, linux-kernel@...r.kernel.org,
	cgroups@...r.kernel.org, kernel-team@...com, vgoyal@...hat.com
Subject: Re: [PATCHSET v2 block/for-4.3] blkcg: blkcg_policy methods cleanup

Hi Tejun,

Il 07/07/2015 22:00, Tejun Heo ha scritto:
> On Tue, Jul 07, 2015 at 11:51:26AM -0400, Tejun Heo wrote:
>> This is v2 of blkcg_policy methods cleanup patchset.  Changes from the
>> last take [L] are
>>
>> * Rebased on top of v4.2-rc1 and other pending patches.  v4.2-rc1
>>    added a patch to add per-blkcg policy data which is allocated by
>>    blkcg core as per-blkcg_gq policy data was before this patchset
>>    making the two inconsistent.  I'll follow up with per-blkcg policy
>>    data update.
>
> While updating per-blkcg policy data handling, I discovered a couple
> bugs in policy data handling which should be backported through
> -stable.  I'll put those earlier in the series and repost this
> patchset.  Please ignore this one for now.
>

I think Jens just applied a bugfix for per-blkcg policy data handling. Please 
have a look at https://lkml.org/lkml/2015/7/6/950. Should have Cc'd you, sorry 
for that.

Thanks,
Arianna

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