]> git.kernelconcepts.de Git - karo-tx-linux.git/commit
/proc/kcore: fix seeking
authorDave Anderson <anderson@redhat.com>
Thu, 13 Jan 2011 01:00:36 +0000 (17:00 -0800)
committerGreg Kroah-Hartman <gregkh@suse.de>
Thu, 17 Feb 2011 22:47:04 +0000 (14:47 -0800)
commit14a03186beb1a7156937a14d97f139979b7ee336
tree8e78a765f2755a1c151f12b3a18bca252e9197b0
parent2a0e113ddab7184bc895e30a5de692cae6313a33
/proc/kcore: fix seeking

commit ceff1a770933e2ca2bf995b453dade4ec47a9878 upstream.

Commit 34aacb2920 ("procfs: Use generic_file_llseek in /proc/kcore") broke
seeking on /proc/kcore.  This changes it back to use default_llseek in
order to restore the original behavior.

The problem with generic_file_llseek is that it only allows seeks up to
inode->i_sb->s_maxbytes, which is 2GB-1 on procfs, where the memory file
offset values in the /proc/kcore PT_LOAD segments may exceed or start
beyond that offset value.

A similar revert was made for /proc/vmcore.

Signed-off-by: Dave Anderson <anderson@redhat.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
fs/proc/kcore.c