linux-kernel - Re: 2.6.36-rc3 NULL pointer dereference crypto_destroy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTin-NCqpaeOHw=EVFsNUg5zAJ_29ikLn3uiFLD8r@mail.gmail.com>
Date:	Mon, 6 Sep 2010 09:28:18 -0500
From:	Steve French <smfrench@...il.com>
To:	Jeff Layton <jlayton@...ba.org>
Cc:	Andrew Hendry <andrew.hendry@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-cifs@...r.kernel.org
Subject: Re: 2.6.36-rc3 NULL pointer dereference crypto_destroy_tfm+0x50/0x70

On Sun, Sep 5, 2010 at 7:45 AM, Jeff Layton <jlayton@...ba.org> wrote:
> On Sun, 5 Sep 2010 18:30:46 +1000
> Andrew Hendry <andrew.hendry@...il.com> wrote:
>
>> Started hitting this since rc3.
>>
>> System has 6 cifs mounts from the one server, during shutdown they get
>> unmounted and gives this error.
>> If manually unmounting one at a time with a gap inbetween it doesn't
>> seem to happen.
>>

yes - as Jeff indicated, a part of the cifs kernel crypto patches has problems.
Key question is whether it is better to back out the fix until next release
(which also will remove the change which moved cifs to using the kernel
crypto routines) or take Shirish's fixes for the problem you describe.



-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/