linux-kernel - Re: [PATCH 20/30] microblaze_mmu

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: <20090428225352.4a54f277.akpm@linux-foundation.org>
Date:	Tue, 28 Apr 2009 22:53:52 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	monstr@...str.eu
Cc:	linux-kernel@...r.kernel.org, john.williams@...alogix.com
Subject: Re: [PATCH 20/30] microblaze_mmu_v1: uaccess MMU update

On Mon, 27 Apr 2009 10:32:09 +0200 monstr@...str.eu wrote:

> +#define __clear_user(addr, n)	(memset((void *)(addr), 0, (n)), 0)

__clear_user() already takes a void* argument, so the cast is hopefully
unneeded and undesirable.  The same applies to many other
architectures.  If someone is passing a non-pointer type to
__clear_user() then that's potentially a bad thing which we want to
know about.

IOW, someone screwed up and everyone copied it :(

--
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/