Skip to contentSkip to conversation

proc: #68991 Fix GPF in /proc/$PID/map_files

PATCH In review Artem Fetishev 4 participants 4 messages Mar 7, 2014 Proc filesystem

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 proc: #68991 Fix GPF in /proc/$PID/map_files

https://bugzilla.kernel.org/show_bug.cgi?id=68991

The expected logic of proc_map_files_get_link() is either to return 0 and initialize 'path' or return an error and leave 'path' uninitialized. By the time dname_to_vma_addr() returns 0 the corresponding vma may have already be gone. In this case the path is not initialized but the return value is still 0. This results in 'general protection fault' inside d_path().

Steps to reproduce:
CONFIG_CHECKPOINT_RESTORE=y

fd = open(...);

while (1) {
	mmap(fd, ...);
	munmap(fd, ...);
}

ls -la /proc/$PID/map_files

---

fs/proc/base.c +1 -0
index 5150706..b976062 100644
@@ -1824,6 +1824,7 @@ static int proc_map_files_get_link(struct dentry *dentry, struct path *path)
 	if (rc)
 		goto out_mmput;
 
+	rc = -ENOENT;
 	down_read(&mm->mmap_sem);
 	vma = find_exact_vma(mm, vm_start, vm_end);
 	if (vma && vma->vm_file) {
Acked-by on v1 1/1
#1 lore raw
Quoted 17 lines · Artem Fetishev

https://bugzilla.kernel.org/show_bug.cgi?id=68991

The expected logic of proc_map_files_get_link() is either to return 0 and initialize 'path' or return an error and leave 'path' uninitialized. By the time dname_to_vma_addr() returns 0 the corresponding vma may have already be gone. In this case the path is not initialized but the return value is still 0. This results in 'general protection fault' inside d_path().

Steps to reproduce:
CONFIG_CHECKPOINT_RESTORE=y

fd = open(...);

while (1) {
	mmap(fd, ...);
	munmap(fd, ...);
}
Quoted 4 lines

ls -la /proc/$PID/map_files

Quoted 15 lines

---

fs/proc/base.c +1 -0
index 5150706..b976062 100644
@@ -1824,6 +1824,7 @@ static int proc_map_files_get_link(struct dentry *dentry, struct path *path)
 	if (rc)
 		goto out_mmput;
 
+	rc = -ENOENT;
 	down_read(&mm->mmap_sem);
 	vma = find_exact_vma(mm, vm_start, vm_end);
 	if (vma && vma->vm_file) {

.

#2 lore raw
Quoted 18 lines · Pavel Emelyanov
Quoted 17 lines · Artem Fetishev

https://bugzilla.kernel.org/show_bug.cgi?id=68991

The expected logic of proc_map_files_get_link() is either to return 0 and initialize 'path' or return an error and leave 'path' uninitialized. By the time dname_to_vma_addr() returns 0 the corresponding vma may have already be gone. In this case the path is not initialized but the return value is still 0. This results in 'general protection fault' inside d_path().

Steps to reproduce:
CONFIG_CHECKPOINT_RESTORE=y

fd = open(...);

while (1) {
	mmap(fd, ...);
	munmap(fd, ...);
}
Quoted 6 lines
Quoted 4 lines

ls -la /proc/$PID/map_files

Good catch, thanks!

I suppose this is a stable@ material.

Reviewed-by on v1 1/1
#3 lore raw
In reply to Artem Fetishev
Quoted 17 lines · Artem Fetishev

https://bugzilla.kernel.org/show_bug.cgi?id=68991

The expected logic of proc_map_files_get_link() is either to return 0 and initialize 'path' or return an error and leave 'path' uninitialized. By the time dname_to_vma_addr() returns 0 the corresponding vma may have already be gone. In this case the path is not initialized but the return value is still 0. This results in 'general protection fault' inside d_path().

Steps to reproduce:
CONFIG_CHECKPOINT_RESTORE=y

fd = open(...);

while (1) {
	mmap(fd, ...);
	munmap(fd, ...);
}
Quoted 4 lines

ls -la /proc/$PID/map_files

Quoted 17 lines

---

fs/proc/base.c +1 -0
index 5150706..b976062 100644
@@ -1824,6 +1824,7 @@ static int proc_map_files_get_link(struct dentry *dentry, struct path *path)
 	if (rc)
 		goto out_mmput;
 
+	rc = -ENOENT;
 	down_read(&mm->mmap_sem);
 	vma = find_exact_vma(mm, vm_start, vm_end);
 	if (vma && vma->vm_file) {

_______________________________________________
Containers mailing list Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers