TAKE 970241 - kill BMAPI_UNWRITTEN

DISCUSSION [email protected] 1 participant 1 message Sep 13, 2007

Share & tools

[email protected]

author

2007-09-13 04:45 UTC #0 lore raw

kill BMAPI_UNWRITTEN

There is no reason to go through xfs_iomap for the BMAPI_UNWRITTEN because it has nothing in common with the other cases. Instead check for the shutdown filesystem in xfs_end_bio_unwritten and perform a direct call to xfs_iomap_write_unwritten (which should be renamed to something more sensible one day)

Signed-off-by Christoph Hellwig <[email protected]>

Date:  Thu Sep 13 14:44:43 AEST 2007
Workarea:  linuxbuild.melbourne.sgi.com:/home/donaldd/isms/2.6.x-xfs
Inspected by:  [email protected]

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

Modid: xfs-linux-melb:xfs-kern:29681a
fs/xfs/xfs_iomap.h - 1.12 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iomap.h.diff?r1=text&tr1=1.12&r2=text&tr2=1.11&f=h
- kill BMAPI_UNWRITTEN

fs/xfs/xfs_iomap.c - 1.56 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iomap.c.diff?r1=text&tr1=1.56&r2=text&tr2=1.55&f=h
- kill BMAPI_UNWRITTEN

fs/xfs/linux-2.6/xfs_aops.c - 1.155 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.155&r2=text&tr2=1.154&f=h
- kill BMAPI_UNWRITTEN