aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2010-09-22 13:04:54 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2010-09-22 17:22:38 -0700
commitc227e69028473c7c7994a9b0a2cc0034f3f7e0fe (patch)
treee11e51f5eec4c2c82a8ef7839de74407f470176c /include
parenta9e31765e7d528858e1b0c202b823cf4df7577ca (diff)
downloadmrst-s0i3-test-c227e69028473c7c7994a9b0a2cc0034f3f7e0fe.tar.gz
mrst-s0i3-test-c227e69028473c7c7994a9b0a2cc0034f3f7e0fe.tar.xz
mrst-s0i3-test-c227e69028473c7c7994a9b0a2cc0034f3f7e0fe.zip
/proc/vmcore: fix seeking
Commit 73296bc611 ("procfs: Use generic_file_llseek in /proc/vmcore") broke seeking on /proc/vmcore. This changes it back to use default_llseek in order to restore the original behaviour. The problem with generic_file_llseek is that it only allows seeks up to inode->i_sb->s_maxbytes, which is zero on procfs and some other virtual file systems. We should merge generic_file_llseek and default_llseek some day and clean this up in a proper way, but for 2.6.35/36, reverting vmcore is the safer solution. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Cc: Frederic Weisbecker <fweisbec@gmail.com> Reported-by: CAI Qian <caiqian@redhat.com> Tested-by: CAI Qian <caiqian@redhat.com> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions