From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p1MKfZRm257947 for ; Tue, 22 Feb 2011 14:41:35 -0600 Received: from cf--amer001e--3.americas.sgi.com (cf--amer001e--3.americas.sgi.com [137.38.100.5]) by relay3.corp.sgi.com (Postfix) with ESMTP id 17F31AC008 for ; Tue, 22 Feb 2011 12:44:16 -0800 (PST) Subject: [PATCH] xfs_repair: validate inode di_flaaags field From: Alex Elder Date: Tue, 22 Feb 2011 14:43:39 -0600 Message-ID: <1298407419.1960.48.camel@doink> Mime-Version: 1.0 Reply-To: aelder@sgi.com List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com (I may have missed it, but I don't believe Dave posted this patch so I'm doing it for him to get it on the list. -Alex) xfs-reapir is not validating the di_flags field in the inode for sanity. Block fuzzing indicates that we are not picking situations like the RT bit being set on filesystems without realtime devices. Signed-off-by: Dave Chinner _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs