linux-kernel - /proc/kcore: fix seeking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4D2B1505.5070404@redhat.com>
Date:	Mon, 10 Jan 2011 09:17:41 -0500
From:	Dave Anderson <anderson@...hat.com>
To:	linux-kernel@...r.kernel.org
CC:	fweisbec@...il.com
Subject: /proc/kcore: fix seeking

From: Dave Anderson <anderson@...hat.com>

Commit 34aacb2920667d405a8df15968b7f71ba46c8f18
("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@...hat.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>
---

View attachment "kcore.patch" of type "text/x-patch" (341 bytes)