The patch titled Subject: xtensa: fix incorrect memset has been removed from the -mm tree. Its filename was xtensa-fix-incorrect-memset.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Alan Cox <alan@xxxxxxxxxxxxxxx> Subject: xtensa: fix incorrect memset Addresses: https://bugzilla.kernel.org/show_bug.cgi?id=43871 Reported-by: <dcb314@xxxxxxxxxxx> Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx> Signed-off-by: Chris Zankel <chris@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/xtensa/kernel/process.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN arch/xtensa/kernel/process.c~xtensa-fix-incorrect-memset arch/xtensa/kernel/process.c --- a/arch/xtensa/kernel/process.c~xtensa-fix-incorrect-memset +++ a/arch/xtensa/kernel/process.c @@ -277,7 +277,7 @@ void xtensa_elf_core_copy_regs (xtensa_g /* Don't leak any random bits. */ - memset(elfregs, 0, sizeof (elfregs)); + memset(elfregs, 0, sizeof(*elfregs)); /* Note: PS.EXCM is not set while user task is running; its * being set in regs->ps is for exception handling convenience. _ Patches currently in -mm which might be from alan@xxxxxxxxxxxxxxx are origin.patch linux-next.patch fs-make-dumpable=2-require-fully-qualified-path.patch coredump-warn-about-unsafe-suid_dumpable-core_pattern-combo.patch kernel-sysc-avoid-argv_freenull.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