The patch titled Subject: c/r: ipc: uninitialized variable in compat_do_msg_fill() has been added to the -mm tree. Its filename is c-r-ipc-message-queue-receive-cleanup-fix.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Subject: c/r: ipc: uninitialized variable in compat_do_msg_fill() We never initialize "msgp". It's unfortunate that GCC doesn't warn about this. Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Cc: Stanislav Kinsbursky <skinsbursky@xxxxxxxxxxxxx> Cc: Cyrill Gorcunov <gorcunov@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- ipc/compat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN ipc/compat.c~c-r-ipc-message-queue-receive-cleanup-fix ipc/compat.c --- a/ipc/compat.c~c-r-ipc-message-queue-receive-cleanup-fix +++ a/ipc/compat.c @@ -336,7 +336,7 @@ long compat_sys_msgsnd(int first, int se long compat_do_msg_fill(void __user *dest, struct msg_msg *msg, size_t bufsz) { - struct compat_msgbuf __user *msgp; + struct compat_msgbuf __user *msgp = dest; size_t msgsz; if (put_user(msg->m_type, &msgp->mtype)) _ Subject: Subject: c/r: ipc: uninitialized variable in compat_do_msg_fill() Patches currently in -mm which might be from dan.carpenter@xxxxxxxxxx are origin.patch linux-next.patch debugobjects-fill_pool-returns-void-now.patch fsnotify-remove-unused-parameter-from-send_to_group.patch drivers-leds-leds-lp5521c-fix-lp5521_read-error-handling.patch hpfs-remove-printk-macro.patch c-r-ipc-message-queue-receive-cleanup-fix.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