The patch titled proc: fix return value of proc_reg_open() in "too late" case has been removed from the -mm tree. Its filename was proc-fix-return-value-of-proc_reg_open-in-too-late-case.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: proc: fix return value of proc_reg_open() in "too late" case From: Alexey Dobriyan <adobriyan@xxxxxxxxx> If ->open() wasn't called, returning 0 is misleading and, theoretically, oopsable: 1. remove_proc_entry clears ->proc_fops, drops lock, 2. ->open "succeeds", 3. ->release oopses, because it assumes ->open was called (single_release()). Signed-off-by: Alexey Dobriyan <adobriyan@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/proc/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN fs/proc/inode.c~proc-fix-return-value-of-proc_reg_open-in-too-late-case fs/proc/inode.c --- a/fs/proc/inode.c~proc-fix-return-value-of-proc_reg_open-in-too-late-case +++ a/fs/proc/inode.c @@ -350,7 +350,7 @@ static int proc_reg_open(struct inode *i if (!pde->proc_fops) { spin_unlock(&pde->pde_unload_lock); kfree(pdeo); - return rv; + return -EINVAL; } pde->pde_users++; open = pde->proc_fops->open; _ Patches currently in -mm which might be from adobriyan@xxxxxxxxx are origin.patch tags-skip-in-filenames.patch mpt-remove-unused-struct-mpt_proc_entry_t.patch cpuset-use-seq_cpumask-seq_nodemask.patch compat_binfmt_elf-definition-tweak.patch proc-move-sysrq-trigger-out-of-fs-proc.patch sysctl-simplify-strategy.patch fs-kconfig-move-ext2-ext3-ext4-jbd-jbd2-out.patch fs-kconfig-move-cifs-out.patch proc-use-non-racy-method-for-proc-page_owner-creation-page_owner.patch likely_prof-changed-to-use-proc_create.patch proc-remove-proc_root-from-drivers-likelyprof.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html