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, 10 Nov 2015 16:49:17 -0800 From: Dan Williams <dan.j.williams@...el.com> To: Jerry Hoemann <Jerry.Hoemann@....com> Cc: Jeff Moyer <jmoyer@...hat.com>, Ross Zwisler <ross.zwisler@...ux.intel.com>, "Rafael J. Wysocki" <rjw@...ysocki.net>, Len Brown <lenb@...nel.org>, Linux ACPI <linux-acpi@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-nvdimm <linux-nvdimm@...1.01.org> Subject: Re: [PATCH 1/4] nvdimm: Add wrapper for IOCTL pass thru. On Tue, Nov 10, 2015 at 4:44 PM, Jerry Hoemann <jerry.hoemann@....com> wrote: > On Tue, Nov 10, 2015 at 03:26:38PM -0500, Jeff Moyer wrote: [..] >> I see. I misread that, because you didn't actually make buf a zero >> length array (see the structure definition quoted above). I guess you >> meant to write this: >> >> unsigned char buf[0]; >> > > The ndn_pkg.buf struct uses a flexible array definition. This is in C99. > An explicit zero length array is a gcc extension that has been around much > longer. They behave in a similar fashion, but aren't identical. In my > limited use they behave the same. "buf[0]" is more idiomatic for Linux. I know I expressed concern about compiler compatibility for ACPICA, but this path does not have ACPICA interactions. -- 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