Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1510631
| From | David Miller <davem@davemloft.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] kalmia: avoid potential uninitialized variable use |
| Date | 2016-10-27 22:30 +0200 |
| Message-ID | <swZtf-6Gr-11@gated-at.bofh.it> (permalink) |
| References | <svPPj-1bs-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: Arnd Bergmann <arnd@arndb.de> Date: Mon, 24 Oct 2016 17:54:18 +0200 > The kalmia_send_init_packet() returns zero or a negative return > code, but gcc has no way of knowing that there cannot be a > positive return code, so it determines that copying the ethernet > address at the end of kalmia_bind() will access uninitialized > data: > > drivers/net/usb/kalmia.c: In function ‘kalmia_bind’: > arch/x86/include/asm/string_32.h:78:22: error: ‘*((void *)ðernet_addr+4)’ may be used uninitialized in this function [-Werror=maybe-uninitialized] > *((short *)to + 2) = *((short *)from + 2); > ^ > drivers/net/usb/kalmia.c:138:5: note: ‘*((void *)ðernet_addr+4)’ was declared here > > This warning is harmless, but for consistency, we should make > the check for the return code match what the driver does everywhere > else and just progate it, which then gets rid of the warning. > > Signed-off-by: Arnd Bergmann <arnd@arndb.de> Applied, thanks.
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH] kalmia: avoid potential uninitialized variable use David Miller <davem@davemloft.net> - 2016-10-27 22:30 +0200
csiph-web