From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tk3kh7LGMQpr for ; Sat, 8 Dec 2012 01:35:31 +0100 (CET) Received: from mail-ea0-f178.google.com (mail-ea0-f178.google.com [209.85.215.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 8 Dec 2012 01:35:31 +0100 (CET) Received: by mail-ea0-f178.google.com with SMTP id k11so449393eaa.37 for ; Fri, 07 Dec 2012 16:35:31 -0800 (PST) Message-ID: <50C28B4F.3010801@gmail.com> Date: Sat, 08 Dec 2012 01:35:27 +0100 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] crypt_load() crash when 3 argument is NULL List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." Cc: dm-crypt@saout.de On 12/08/2012 01:06 AM, .. ink .. wrote: > This is something i noticed last night but forgot to mention in my previous email. > > Just updated from git to test and the behavior is still there. > > calling crypt_load() with the third argument as NULL segfaults. params is required for TCRYPT type (you need to provide password/keyfiles here). Should be fixed in git to return EINVAL instead, thanks. (I'll revisit docs later, still a lot of other changes ahead.) Milan