In-Reply-To: <4cefeab80705230703vdb3c414s250a61c4c2d70c51@mail.gmail.com>
References: <4cefeab80705230127r58e8f9e1sa644092e95eb81eb@mail.gmail.com> <0F6CEFD7-86F2-4903-B4F7-F723DF88BE9A@cam.ac.uk> <4cefeab80705230439n6bbb1259le3c3b9704ce49b75@mail.gmail.com> <624FD7A7-5552-415F-96D8-4353453EA2A3@cam.ac.uk> <4cefeab80705230703vdb3c414s250a61c4c2d70c51@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1CF43BBC-79EF-449B-A398-AE374E399573@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, "Richard Purdie" <richard@openedhand.com>,
       linux-mm-cc@laptop.org
Content-Transfer-Encoding: 7bit
From: Michael-Luke Jones <mlj28@cam.ac.uk>
Subject: Re: [RFC] LZO de/compression support - take 3
Date: Wed, 23 May 2007 15:10:03 +0100
To: Nitin Gupta <nitingupta910@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 679
Lines: 21

On 23 May 2007, at 15:03, Nitin Gupta wrote:

>> Perhaps a rename is in order:
>> lzo1x_decompress() => lzo1x_decompress_unsafe()
>> lzo1x_decompress_safe => lzo1x_decompress()
>
> Or perhaps make reiserfs use _safe() instead - I think Richard has
> already submitted patch for same.

If someone's already made this mistake once, then it'll happen again.  
In-kernel memory corruption is no fun.

Safe/Secure == Default

Michael-Luke

-
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/