Date: Fri, 8 Feb 2013 12:20:01 GMT From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= <uqs@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/174831: [PATCH] geli(8) segfaults with the new locked memory limit default Message-ID: <201302081220.r18CK11A073505@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/174831; it has been noted by GNATS. From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= <uqs@FreeBSD.org> To: bug-followup@FreeBSD.org, fk@fabiankeil.de, zont@FreeBSD.org, avg@FreeBSD.org Cc: Subject: Re: bin/174831: [PATCH] geli(8) segfaults with the new locked memory limit default Date: Fri, 8 Feb 2013 13:16:37 +0100 While geli should definitely be fixed to provide a meaningful error message instead of a crash, we also need to keep it working out of the box. For me, 256K seems to be enough to make it work, but I guess this is a function of the used crypto algorithms and key sizes. Can you maybe adapt the check to figure out how much memory actually needs to be mlocked? Once we come up with a better upper limit, the default in login.conf should be bumped accordingly.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201302081220.r18CK11A073505>