Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267507AbUJRUNY (ORCPT ); Mon, 18 Oct 2004 16:13:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267502AbUJRUKM (ORCPT ); Mon, 18 Oct 2004 16:10:12 -0400 Received: from mx1.redhat.com ([66.187.233.31]:17582 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S267700AbUJRTfc (ORCPT ); Mon, 18 Oct 2004 15:35:32 -0400 Date: Mon, 18 Oct 2004 15:35:16 -0400 (EDT) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: Matt Domsch cc: davem@davemloft.net, , Oleg Makarenko Subject: Re: using crypto_digest() on non-kmalloc'd memory failures In-Reply-To: <20041018192952.GB8607@lists.us.dell.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 716 Lines: 25 On Mon, 18 Oct 2004, Matt Domsch wrote: > James, David, > > Oleg noted that when we call crypto_digest() on memory allocated as a > static array in a module, rather than kmalloc(GFP_KERNEL), it returns > incorrect data, and with other functions, a kernel panic. > > Thoughts as to why this may be? Oleg's test patch appended. I don't recall the exact details, but it's related to using kmap in the core crypto code. - James -- James Morris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/