summaryrefslogtreecommitdiffstats
path: root/fs/sysfs/mount.c
diff options
context:
space:
mode:
authorJan Beulich <JBeulich@suse.com>2013-12-13 02:12:22 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2013-12-13 03:19:26 +0100
commitae5758a1a7b7bdfdcfaf2d78a5a0f8675149dd79 (patch)
tree724d6af0adf51da4e34c09bb66c9586f0de945b6 /fs/sysfs/mount.c
parentmm: memcg: do not declare OOM from __GFP_NOFAIL allocations (diff)
downloadlinux-ae5758a1a7b7bdfdcfaf2d78a5a0f8675149dd79.tar.xz
linux-ae5758a1a7b7bdfdcfaf2d78a5a0f8675149dd79.zip
procfs: also fix proc_reg_get_unmapped_area() for !MMU case
Commit fad1a86e25e0 ("procfs: call default get_unmapped_area on MMU-present architectures"), as its title says, took care of only the MMU case, leaving the !MMU side still in the regressed state (returning -EIO in all cases where pde->proc_fops->get_unmapped_area is NULL). From the fad1a86e25e0 changelog: "Commit c4fe24485729 ("sparc: fix PCI device proc file mmap(2)") added proc_reg_get_unmapped_area in proc_reg_file_ops and proc_reg_file_ops_no_compat, by which now mmap always returns EIO if get_unmapped_area method is not defined for the target procfs file, which causes regression of mmap on /proc/vmcore. To address this issue, like get_unmapped_area(), call default current->mm->get_unmapped_area on MMU-present architectures if pde->proc_fops->get_unmapped_area, i.e. the one in actual file operation in the procfs file, is not defined" Signed-off-by: Jan Beulich <jbeulich@suse.com> Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com> Cc: Alexey Dobriyan <adobriyan@gmail.com> Cc: David S. Miller <davem@davemloft.net> Cc: <stable@vger.kernel.org> [3.12.x] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/sysfs/mount.c')
0 files changed, 0 insertions, 0 deletions