linux-kernel - Re: [PATCH] fs/proc/: fix input sanity check.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090811150528.a9bc7719.akpm@linux-foundation.org>
Date:	Tue, 11 Aug 2009 15:05:28 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Vincent Li <macli@....ubc.ca>
Cc:	linux-kernel@...r.kernel.org, kosaki.motohiro@...fujitsu.com,
	mel@....ul.ie, mpm@...enic.com, macli@....ubc.ca
Subject: Re: [PATCH] fs/proc/: fix input sanity check.

On Tue, 11 Aug 2009 14:34:26 -0700
Vincent Li <macli@....ubc.ca> wrote:

> fix fs/proc/task_mmu.c clear_refs_write(), fs/proc/base.c proc_fault_inject_write()
>  and proc_fault_inject_operations() input sanity check by following the disccusion of
> http://marc.info/?l=linux-mm&m=124938168905463&w=2.

Would prefer that the changelog not consist of a link to another patch
which is already quite poorly changelogged, please!

What, precisely was wrong with the old code and how does the patch
change its behaviour.

This matters.  The patch potentially changes the kernel<->userspace
interface and we must fully understand the nature of that change so as
to minimise the risk of breaking existing userspace application code.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/