The patch titled fbdev: correct buffer size limit in fbmem_read_proc() has been added to the -mm tree. Its filename is fbdev-correct-buffer-size-limit-in-fbmem_read_proc.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: fbdev: correct buffer size limit in fbmem_read_proc() From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Address http://bugzilla.kernel.org/show_bug.cgi?id=7189 It should check `clen', not `len'. Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Cc: <jurij@xxxxxxxxx> Cc: "Antonino A. Daplas" <adaplas@xxxxxxx> Cc: <stable@xxxxxxxxxx> Cc: Willy Tarreau <w@xxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- drivers/video/fbmem.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletion(-) diff -puN drivers/video/fbmem.c~fbdev-correct-buffer-size-limit-in-fbmem_read_proc drivers/video/fbmem.c --- a/drivers/video/fbmem.c~fbdev-correct-buffer-size-limit-in-fbmem_read_proc +++ a/drivers/video/fbmem.c @@ -554,7 +554,8 @@ static int fbmem_read_proc(char *buf, ch int clen; clen = 0; - for (fi = registered_fb; fi < ®istered_fb[FB_MAX] && len < 4000; fi++) + for (fi = registered_fb; fi < ®istered_fb[FB_MAX] && clen < 4000; + fi++) if (*fi) clen += sprintf(buf + clen, "%d %s\n", (*fi)->node, _ Patches currently in -mm which might be from geert@xxxxxxxxxxxxxx are make-prot_write-imply-prot_read.patch simplify-update_times-avoid-jiffies-jiffies_64-aliasing-problem-2.patch kill-wall_jiffies.patch introduce-kernel_execve.patch rename-the-provided-execve-functions-to-kernel_execve.patch provide-kernel_execve-on-all-architectures.patch provide-kernel_execve-on-all-architectures-fix.patch remove-the-use-of-_syscallx-macros-in-uml.patch sh64-remove-the-use-of-kernel-syscalls.patch remove-remaining-errno-and-__kernel_syscalls__-references.patch fbdev-correct-buffer-size-limit-in-fbmem_read_proc.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