Most recent kernel where this bug did *NOT* occur:
Single AMD64 3500+, 1GB RAM
Stock FC6 with latest updates
After some time of activity I get
BUG: at /home/andrew/src/linux-2.6/mm/truncate.c:425 invalidate_inode_pages2_range()
Steps to reproduce:
I have some NFS mounted fileystems including my home dir
/dev/sda1 on / type ext3 (rw)
/dev/proc on /proc type proc (rw)
/dev/sys on /sys type sysfs (rw)
/dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/shm on /dev/shm type tmpfs (rw)
homes.systems.pccl.info:/home/andrew on /home/andrew type nfs
homes.systems.pccl.info:/home/storage/apps on /mnt/autofs/apps type nfs
I was last using 2.6.19 where this didn't occur. I then updated to 2.6.20-rc4
where I noticed this BUG.
This morning I updated to 2.6.20-rc5. It seemed to take a bit longer for this
BUG to happen, before it seemed to happen with sylpheed-claws where its mail
files are stored in my NFS mounted home dir, this time I noticed it after I had
started mplayer on an ogg vorbis file out of my NFS mounted home dir.
Not a bug!
It is perfectly legal and acceptable for the user to ^C out of a hanging
process. In that case, the NFS client will also abandon the attempt to
invalidate the page cache, and just defer doing so until the next process needs
to access that data.
That WARN_ON crap that Andrew merged into invalidate_inode_pages2_range() needs
to be thrown out.
Agreed, this is not a bug if the callers handle it correctly. Can we send a
patch to remove the WARN_ON_ONCE, and close this?
we already did, I think.