atom feed42 messages in org.freebsd.freebsd-fsRe: [review request] zfsboot/zfsloade...
FromSent OnAttachments
Andriy GaponApr 14, 2012 8:37 am 
Andriy GaponApr 14, 2012 10:35 am 
Bob FriesenhahnApr 14, 2012 6:00 pm 
Garrett CooperApr 14, 2012 7:30 pm 
John BaldwinApr 16, 2012 6:55 am 
vermadenApr 16, 2012 10:34 pm 
Andriy GaponApr 17, 2012 1:21 pm 
John BaldwinApr 17, 2012 1:43 pm 
Andriy GaponApr 17, 2012 11:01 pm 
Andriy GaponApr 18, 2012 1:57 am 
Andriy GaponApr 18, 2012 2:18 am 
John BaldwinApr 18, 2012 6:41 am 
Ian LeporeApr 18, 2012 7:22 am 
Andriy GaponApr 18, 2012 7:36 am 
Ian LeporeApr 18, 2012 7:39 am 
Andriy GaponApr 18, 2012 7:59 am 
John BaldwinApr 18, 2012 10:47 am 
Marius StroblApr 22, 2012 2:20 pm 
Andrey V. ElsukovApr 22, 2012 11:23 pm 
Andriy GaponApr 27, 2012 2:05 am 
Andriy GaponApr 27, 2012 2:13 am 
Andrey V. ElsukovApr 27, 2012 3:37 am 
Andriy GaponApr 27, 2012 7:06 am 
Marius StroblApr 29, 2012 9:46 am 
Andriy GaponApr 30, 2012 12:03 am 
Marius StroblMay 1, 2012 1:20 pm 
Andriy GaponMay 3, 2012 8:02 am 
Andriy GaponMay 3, 2012 8:23 am 
John BaldwinMay 4, 2012 8:24 am 
Andriy GaponMay 5, 2012 2:30 am 
Andriy GaponMay 5, 2012 2:52 am 
Bruce EvansMay 5, 2012 3:49 am 
John BaldwinMay 7, 2012 6:52 am 
Andriy GaponMay 7, 2012 7:34 am 
Andriy GaponMay 7, 2012 7:46 am 
Andriy GaponMay 7, 2012 8:15 am 
John BaldwinMay 7, 2012 10:37 am 
John BaldwinMay 7, 2012 10:43 am 
Andriy GaponMay 8, 2012 12:14 am 
John BaldwinMay 8, 2012 7:15 am 
Andriy GaponMay 8, 2012 11:34 am 
Andriy GaponMay 11, 2012 3:31 pm 
Subject:Re: [review request] zfsboot/zfsloader: support accessing filesystems within a pool
From:Ian Lepore (free@damnhippie.dyndns.org)
Date:Apr 18, 2012 7:39:44 am
List:org.freebsd.freebsd-fs

On Wed, 2012-04-18 at 17:36 +0300, Andriy Gapon wrote:

on 18/04/2012 17:22 Ian Lepore said the following:

YES! A size field (preferably as the first field in the struct) along with a flag to indicate that it's a new-style boot info struct that starts with a size field, will allow future changes without a lot of drama. It can allow code that has to deal with the struct without interpretting it (such as trampoline code that has to copy it to a new stack or memory area as part of loading the kernel) to be immune to future changes.

Yeah, placing the new field at front would immediately break compatibility and even access to the flags field :-)

Code would only assume the new field was at the front of the struct if the new flag is set, otherwise it would use the historical struct layout.

-- Ian