Andreas Gruenbacher 1c185c02f4 gfs2: Remove dirty buffer warning from gfs2_releasepage ... Unlike what its documentation suggests, the releasepage address space operation can currently be called on dirty pages via shrink_active_list. This may eventually be changed when the remaining code relying on the current behavior has been fixed, but until then, it makes no sense to warn on dirty buffers in gfs2_releasepage. Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> Signed-off-by: Bob Peterson <rpeterso@redhat.com>		2016-08-18 08:57:04 -05:00
..
acl.c
acl.h
aops.c	gfs2: Remove dirty buffer warning from gfs2_releasepage	2016-08-18 08:57:04 -05:00
bmap.c	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
bmap.h
dentry.c
dir.c	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
dir.h
export.c
file.c
gfs2.h
glock.c	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
glock.h
glops.c
glops.h
incore.h
inode.c
inode.h	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
Kconfig
lock_dlm.c
log.c
log.h
lops.c
lops.h
main.c
Makefile
meta_io.c
meta_io.h
ops_fstype.c	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
quota.c	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
quota.h
recovery.c
recovery.h
rgrp.c
rgrp.h
super.c	GFS2: use BIT() macro	2016-08-02 12:05:27 -05:00
super.h
sys.c
sys.h
trace_gfs2.h
trans.c
trans.h
util.c
util.h
xattr.c
xattr.h