xfs
[Top] [All Lists]

TAKE 980888 - Fix check for block zero access in xfs_write_iomap_allocat

To: sgi.bugs.xfs@xxxxxxxxxxxx
Subject: TAKE 980888 - Fix check for block zero access in xfs_write_iomap_allocate
From: dgc@xxxxxxx (David Chinner)
Date: Mon, 28 Apr 2008 16:34:13 +1000 (EST)
Cc: xfs@xxxxxxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
Fix check for block zero access in xfs_write_iomap_allocate()

The check for block zero access should be done on non-realtime
inodes. Fix the logic error in xfs_write_iomap_allocate(), and
simplify the logic on all checks for block zero access in
xfs_iomap.c

Date:  Mon Apr 28 16:33:53 AEST 2008
Workarea:  chook.melbourne.sgi.com:/build/dgc/isms/2.6.x-xfs
Inspected by:  lachlan@xxxxxxx

The following file(s) were checked into:
  longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb


Modid:  xfs-linux-melb:xfs-kern:30998a
fs/xfs/xfs_iomap.c - 1.64 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iomap.c.diff?r1=text&tr1=1.64&r2=text&tr2=1.63&f=h
        - Fix check for block zero access in xfs_write_iomap_allocate().



<Prev in Thread] Current Thread [Next in Thread>
  • TAKE 980888 - Fix check for block zero access in xfs_write_iomap_allocate, David Chinner <=