[GFS2] Fix lock ordering bug in page fault path

Browse source

Mmapped files were able to trigger a lock ordering bug. Private
maps do not need to take the glock so early on. Shared maps do
unfortunately, however we can get around that by adding a flag
into the flags for the struct gfs2_file. This only works because
we are taking an exclusive lock at this point, so we know that
nobody else can be racing with us.

Fixes Red Hat bugzilla: #201196

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>

...

This commit is contained in:

Steven Whitehouse 2006-08-04 15:41:22 -04:00

parent 899bb26450

commit 59a1cc6bda

5 changed files with 32 additions and 25 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

fs/gfs2/incore.h

View file

4

fs/gfs2/log.c

View file

23

fs/gfs2/ops_address.c

View file

20

fs/gfs2/ops_vm.c

View file

9

fs/gfs2/recovery.c

View file