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
| ||
|
Message-ID: <20121229171801.GA1838@elie.Belkin> Date: Sat, 29 Dec 2012 09:18:01 -0800 From: Jonathan Nieder <jrnieder@...il.com> To: Ben Hutchings <ben@...adent.org.uk> Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, Kees Cook <keescook@...omium.org>, Fengguang Wu <fengguang.wu@...el.com>, David Howells <dhowells@...hat.com>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [ 016/173] use clamp_t in UNAME26 fix Ben Hutchings wrote: > On Sat, 2012-12-29 at 00:07 -0800, Jonathan Nieder wrote: >> Ben Hutchings wrote: >>> The min/max call needed to have explicit types on some architectures >>> (e.g. mn10300). Use clamp_t instead to avoid the warning: >>> >>> kernel/sys.c: In function 'override_release': >>> kernel/sys.c:1287:10: warning: comparison of distinct pointer types lacks a cast [enabled by default] >>> >>> Reported-by: Fengguang Wu <fengguang.wu@...el.com> >> [...] >>> - copy = min(sizeof(buf), max_t(size_t, 1, len)); >> >> I don't understand how this happens given that v2.6.36-rc1~68 >> (MN10300: Fix size_t and ssize_t, 2010-08-12) was supposed to fix this >> kind of thing. > [...] > > Neither do I, but I'm including it now just to be consistent with other > stable series. Thanks for explaining. That makes sense and the patch is harmless, so why not. The patch still leaves me worried that there might be more problems lurking on mn10300, but that's more of a question for upstream. -- 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/
Powered by blists - more mailing lists