From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1W5Wu7-0001G9-R9 for mharc-grub-devel@gnu.org; Tue, 21 Jan 2014 03:41:51 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40173) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W5Wu1-0001Fu-Ht for grub-devel@gnu.org; Tue, 21 Jan 2014 03:41:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W5Wtw-0006AT-PP for grub-devel@gnu.org; Tue, 21 Jan 2014 03:41:45 -0500 Received: from mail-lb0-x235.google.com ([2a00:1450:4010:c04::235]:35477) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W5Wtw-0006AP-Gd for grub-devel@gnu.org; Tue, 21 Jan 2014 03:41:40 -0500 Received: by mail-lb0-f181.google.com with SMTP id z5so5599826lbh.26 for ; Tue, 21 Jan 2014 00:41:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=CeJPWtvvDAmF81HjU3OjnzjSD+PqTzZ0H83vd03dfXs=; b=AGZf+P318C/HiC/PmW7qsp2EUfGBkRS2iYeS5gNeih/VrdmPzvwFuTo9LEUmFf581x SXI0ZD5rWvRi/adqDH2ONtja6ZBS969y9PWquZU6IbLTmQpPDimjxSjb0nz+y5IVr6pF DFCpg4SX1CBE1nt13qbanFpF7QlchHg8JKoOhUyDT4uTYwYXVIscfhB75Q79SPG2TunH 2nfC7x8pE0s2Yf+hrIPkF6n5EGvpC2qZDX9o4UcBAsSK8VGt6uLPwqC9ZEcgt2gg4v0C 1IjW5d2qzc4mbP0P0nS9QCXouFUlfYk9tv+Exbvk8Eb6Xs/7qVw6XPSHaxXfh0O4hTSk 33Ag== MIME-Version: 1.0 X-Received: by 10.112.164.5 with SMTP id ym5mr302546lbb.48.1390293699334; Tue, 21 Jan 2014 00:41:39 -0800 (PST) Received: by 10.112.26.174 with HTTP; Tue, 21 Jan 2014 00:41:39 -0800 (PST) In-Reply-To: <52DE30AD.9030301@gmail.com> References: <1389301657-8236-1-git-send-email-tilmann@bubecks.de> <52CF282C.4070408@gmail.com> <52CFA5FF.7070200@bubecks.de> <52DE2C79.2000507@gmail.com> <52DE30AD.9030301@gmail.com> Date: Tue, 21 Jan 2014 12:41:39 +0400 Message-ID: Subject: Re: [PATCH] Improve ext2 driver to allow embedding of the boot loader code. From: Andrey Borzenkov To: The development of GNU GRUB Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::235 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 08:41:50 -0000 On Tue, Jan 21, 2014 at 12:32 PM, Vladimir '=F6-coder/phcoder' Serbinenko wrote: > On 21.01.2014 09:28, Andrey Borzenkov wrote: >> On Tue, Jan 21, 2014 at 12:14 PM, Vladimir '=F6-coder/phcoder' >> Serbinenko wrote: >>> On 10.01.2014 08:49, Dr. Tilmann Bubeck wrote: >>>> >>>> The blocklist is fixed and stable and will never change. >>> What guarantees that it won't change on grub-setup invocation? I'm unde= r >>> impression that it will change on every grub-setup invocation as file >>> gets recreated. >>> >> >> If I read code correctly, it checks current size and if new core.img >> fits, space is reused. So we could effectively make it preallocate >> reasonable size (or even unreasonable - I guess 10MB will be enough >> for foreseeable future) the very first time it is done. >> > It still doesn't solve the problem that during operations file becomes a > normal file and OS is allowed to rearrange the blocks as it sees fit. Would this be acceptable - use external utility to allocate EXT2_BOOT_LOADER_INO space of sufficient size once (outside of grub at all) and allow embedding into extX if this space exists? Do not mess with with it in grub-setup itself? We could then speak with ext2 folks to add option to mke2fs/une2fs in the long run it it does not exist yet.