Re: [PATCH] fbdev: potential information leak in do_fb_ioctl()
From: Joe Perches <joe@perches.com>
Date: 2019-10-31 18:16:54
Also in:
dri-devel, kernel-janitors, lkml
Possibly related (same subject, not in this thread)
- 2020-01-15 · Re: [PATCH] fbdev: potential information leak in do_fb_ioctl() · Arnd Bergmann <arnd@arndb.de>
- 2020-01-15 · Re: [PATCH] fbdev: potential information leak in do_fb_ioctl() · Bartlomiej Zolnierkiewicz <hidden>
- 2020-01-13 · Re: [PATCH] fbdev: potential information leak in do_fb_ioctl() · Arnd Bergmann <arnd@arndb.de>
- 2020-01-03 · Re: [PATCH] fbdev: potential information leak in do_fb_ioctl() · Bartlomiej Zolnierkiewicz <hidden>
- 2019-10-31 · Re: [PATCH] fbdev: potential information leak in do_fb_ioctl() · Eric W. Biederman <hidden>
On Wed, 2019-10-30 at 21:12 +0100, Andrea Righi wrote:
Then memset() + memcpy() is probably the best option, since copying all those fields one by one looks quite ugly to me...
A memset of an automatic before a memcpy to the same automatic is unnecessary.