Date: Sun, 12 Apr 2009 15:44:13 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: Maksim Yevmenkin <emax@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: svn commit: r190857 - head/sys/dev/kbdmux Message-ID: <20090412154413.1e250cc7@kan.dnsalias.net> In-Reply-To: <bb4a86c70904121000p60b48632q22a5b92fc791f4f8@mail.gmail.com> References: <200904082052.n38KqU9p075633@svn.freebsd.org> <20090412170335.5a8a3169@fabiankeil.de> <bb4a86c70904121000p60b48632q22a5b92fc791f4f8@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, 12 Apr 2009 10:00:35 -0700 Maksim Yevmenkin <emax@freebsd.org> wrote: > On Sun, Apr 12, 2009 at 8:03 AM, Fabian Keil > > > How about turning this into a compile-time or sysctl option > > or at least mentioning the change in /usr/src/UPDATING? > > i do not believe that compile-time nor sysctl option is the right > choice here as it is never allowed to use locks in low-level keyboard > drivers. entry in UPDATING is probably a good idea. > > > With this commit, providing the geli key phrase on > > boot is impossible on my AMD64 dual core system. > > right, i really hate to say this, but the amount of bug reports, lor's > etc.that were submitted after this change is far more (imo) than > amount of people that ran relatively uncommon setup with encrypted > root (which, btw, prompted the original commit). of course, there is > no question, it has to be fixed. This also affects DDB prompts, correct? What is the timeframe for fixing this? -- Alexander Kabaev [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iD8DBQFJ4kSRQ6z1jMm+XZYRAhivAJwJSDjs2mHRaLYwxBCChqRBmZf5JACeNOR+ ZSbXLkWk3i2JykJil7jjUuQ= =2Aur -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090412154413.1e250cc7>