linux-kernel - Re: [PATCH] Edwin T??r??k found the following, so fix it

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] [day] [month] [year] [list]

Date:	Thu, 26 Nov 2009 09:47:15 -0800
From:	Greg KH <gregkh@...e.de>
To:	??ric Piel <E.A.B.Piel@...elft.nl>
Cc:	Alan Cox <alan@...ux.intel.com>, mchehab@...hat.com,
	linux-kernel@...r.kernel.org, Hank Janssen <hjanssen@...rosoft.com>
Subject: Re: [PATCH] Edwin T??r??k found the following, so fix it

On Thu, Nov 26, 2009 at 05:46:03PM +0100, ??ric Piel wrote:
> Op 26-11-09 16:22, Alan Cox schreef:
> > In function ???memset???,
> > inlined from ???ir_input_init??? at drivers/media/common/ir-functions.c:67:
> > /home/edwin/builds/linux-2.6/arch/x86/include/asm/string_64.h:61:
> > warning: call to ???__warn_memset_zero_len??? declared with attribute
> > warning: memset used with constant zero length parameter; this could be
> > due to transposed parameters
> > memset(ir->ir_codes, sizeof(ir->ir_codes), 0);
> Hello,
> A "grep -E "memset.*,.*, 0\\)" -r" also reports
> drivers/staging/hv/StorVsc.c as a suspect:
> memset(request, sizeof(struct storvsc_request_extension), 0);
> memset(vstorPacket, sizeof(struct vstor_packet), 0);
> memset(vstorPacket, sizeof(struct vstor_packet), 0);
> memset(vstorPacket, sizeof(struct vstor_packet), 0);
> 
> Maybe someone cares about fixing it too?

It's already fixed in linux-next and will be sent to Linus soon.

thanks,

greg k-h
--
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/