From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750765AbWG1AcF (ORCPT ); Thu, 27 Jul 2006 20:32:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750919AbWG1AcF (ORCPT ); Thu, 27 Jul 2006 20:32:05 -0400 Received: from cantor.suse.de ([195.135.220.2]:32135 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1750765AbWG1AcE (ORCPT ); Thu, 27 Jul 2006 20:32:04 -0400 From: NeilBrown To: Andrew Morton Date: Fri, 28 Jul 2006 10:31:20 +1000 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Currently, and file handle with a bad inode number in it can cause ext2 to go to readonly (as it looks like a corrupted filesystem) and could allow remote access to ext3 special files like the journal. These patches give ext2/3 their own get_dentry method which checks the inode number early before other bits of the code can be freaked out by it. These are revised versions of earlier patches. Rather than exporting export_iget, we open code it and simplify it slightly. This avoids and extra module dependancy. NeilBrown To follow: [PATCH 001 of 2] knfsd: Have ext2 reject file handles with bad inode numbers early. [PATCH 002 of 2] knfsd: Make ext3 reject filehandles referring to invalid inode numbers