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
| ||
|
Date: Tue, 6 Mar 2012 20:01:58 -0800 From: Arve Hjønnevåg <arve@...roid.com> To: Zhengwang Ruan <ruan.zhengwang@...il.com> Cc: gregkh@...uxfoundation.org, chris+android@...thought.org, devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org Subject: Re: [PATCH 2/2 v2] Staging:android: Initialise buffer and buffer_size before used On Tue, Mar 6, 2012 at 6:36 PM, Zhengwang Ruan <ruan.zhengwang@...il.com> wrote: > GCC warns 'buffer' and 'buffer_size' are used with being uninitialized, and > 'buffer' is used as returned value, and 'buffer_size' is initialized using > uninitialized_var to clear warning. Why do you clear the warning on buffer_size with uninitialized_var() but not on buffer? Neither variable is used before being initialized. -- Arve Hjønnevåg -- 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