Date: Sat, 16 Dec 2017 12:05:45 -0500 From: Thomas Laus <lausts@acm.org> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: GPTZFSBOOT in Current r326622 has problems - FIXED Message-ID: <79db33b4-c422-cc2c-d6ba-9192c783e3d5@acm.org> In-Reply-To: <CANCZdfruJdb6wwYZqSDYR0ckA06x_BDbZz5BuSXwPTE9pbphCg@mail.gmail.com> References: <d92d0e84-72c5-e240-a1b5-18cef53dcbff@acm.org> <CANCZdfqHZidf%2BZvf3Pqpr1BHuyRPBP9zLSzkw_CcFqJde2KzYw@mail.gmail.com> <CANCZdfruJdb6wwYZqSDYR0ckA06x_BDbZz5BuSXwPTE9pbphCg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/15/17 18:37, Warner Losh wrote: > > I believe that these issues have been corrected in r326888. My > refactoring to make it easier to bring in the lua boot loader in r326593 > (after breaking the build in r326584 accidentally) uncovered some latent > subtle ordering issues. This cause GELI-enabled (but not even using) ZFS > boot loaders to fail. This was related to an odd interaction between zfs > and geli implementation files in gptzfsboot (and zfsboot) which caused > us to have two different implementations of malloc, with all the fun > you'd expect when the second one got called. > > If you have issues after r326888, please let me know. > Warner & Group I updated my system this morning to r326897 and can confirm that this problem has been solved. Good work Warner! Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79db33b4-c422-cc2c-d6ba-9192c783e3d5>