Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758243Ab3DXKPM (ORCPT ); Wed, 24 Apr 2013 06:15:12 -0400 Received: from am1ehsobe005.messaging.microsoft.com ([213.199.154.208]:45985 "EHLO am1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758209Ab3DXKPK (ORCPT ); Wed, 24 Apr 2013 06:15:10 -0400 X-Forefront-Antispam-Report: CIP:157.56.236.101;KIP:(null);UIP:(null);IPV:NLI;H:BY2PRD0510HT002.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -2 X-BigFish: PS-2(zz98dI936eIzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275dhz2fh2a8h668h839h93fhd24he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1155h) From: Matthew Garrett To: joeyli CC: "matt.fleming@intel.com" , "linux-efi@vger.kernel.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH V6 3/3] efi: Distinguish between "remaining space" and actually used space Thread-Topic: [PATCH V6 3/3] efi: Distinguish between "remaining space" and actually used space Thread-Index: AQHOOhU89r+iw6MpjUmtexdARM4dfpjlMy2AgAABzIA= Date: Wed, 24 Apr 2013 10:14:57 +0000 Message-ID: <1366798497.13667.25.camel@x230.lan> References: <1365561717-12343-1-git-send-email-matthew.garrett@nebula.com> <1366056587-24414-1-git-send-email-matthew.garrett@nebula.com> <1366056587-24414-4-git-send-email-matthew.garrett@nebula.com> <1366798111.23707.293.camel@linux-s257.site> In-Reply-To: <1366798111.23707.293.camel@linux-s257.site> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.84.4] Content-Type: text/plain; charset="utf-8" Content-ID: MIME-Version: 1.0 X-OriginatorOrg: nebula.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id r3OAFKwr020179 Content-Length: 728 Lines: 15 On Wed, 2013-04-24 at 18:08 +0800, joeyli wrote: > It causes the garbage size increased and remaining_size decreased. But > we still can create new variable because active_size doesn't increase > due to we delete variable before create new. So, the condition > "remaining_size - size < storage_size / 2" will not really hit because > active_size condition is pass. That's fine - the (limited) information we have from Samsung is that there's no problem if all the space is dirty, only if all the space is marked as active. -- Matthew Garrett | mjg59@srcf.ucam.org ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?