Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757530AbbGGNtx (ORCPT ); Tue, 7 Jul 2015 09:49:53 -0400 Received: from mail-pd0-f171.google.com ([209.85.192.171]:33651 "EHLO mail-pd0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755460AbbGGNto (ORCPT ); Tue, 7 Jul 2015 09:49:44 -0400 Message-ID: <559BD8F5.4080700@kernel.dk> Date: Tue, 07 Jul 2015 07:49:41 -0600 From: Jens Axboe User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Arianna Avanzini , linux-kernel@vger.kernel.org CC: kaminsky@cs.cmu.edu Subject: Re: [PATCH] block/blk-cgroup.c: free per-blkcg data when freeing the blkcg References: <1436231295-21713-1-git-send-email-avanzini.arianna@gmail.com> In-Reply-To: <1436231295-21713-1-git-send-email-avanzini.arianna@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1053 Lines: 24 On 07/06/2015 07:08 PM, Arianna Avanzini wrote: > Currently, per-blkcg data is freed each time a policy is deactivated, > that is also upon scheduler switch. However, when switching from a > scheduler implementing a policy which requires per-blkcg data to > another one, that same policy might be active on other devices, and > therefore those same per-blkcg data could be still in use. > This commit lets per-blkcg data be freed when the blkcg is freed > instead of on policy deactivation. > > Signed-off-by: Arianna Avanzini > Reported-and-tested-by: Michael Kaminsky > Fixes: e48453c3 ("block, cgroup: implement policy-specific per-blkcg data") Thanks Arianna, applied! Hopefully this is the end of the per-policy data issues for 4.2. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/