- linux-bl...@vger.kernel.org <linux-bl...@vger.kernel.org> to reduce the noise.
I apologies Jens, I didn't apply and tested these patches before submitting the review and assumed that patches are compiled and tested, I'll do so for each patch before submitting the review. Xiaolinkui, Please send compiled and tested patch only on the latest kernel on the appropriate subsystem, otherwise mark the patch appropriately [RFC/Compile only] so reviewer would know without such a tag it is easy to assume that patch is compiled and tested. You have also sent out the couple of more patches with this fix. If they are not compiled and tested with right kernel branch for each subsystem, please update the appropriate mail thread either to ignore those patches (if they have compilation problem on appropriate branch) or mark them compile test only (this needs to be avoided for these patches), in either case please send updated patches for this fix if needed. Thanks. On 5/17/19 3:59 PM, Jens Axboe wrote: > On 5/17/19 3:17 PM, Jens Axboe wrote: >> On 5/17/19 3:12 AM, xiaolinkui wrote: >>> One of the more common cases of allocation size calculations is finding >>> the size of a structure that has a zero-sized array at the end, along >>> with memory for some number of elements for that array. For example: >>> >>> struct foo { >>> int stuff; >>> struct boo entry[]; >>> }; >>> >>> instance = kmalloc(sizeof(struct foo) + count * sizeof(struct boo), >>> GFP_KERNEL); >>> >>> Instead of leaving these open-coded and prone to type mistakes, we can >>> now use the new struct_size() helper: >>> >>> instance = kmalloc(struct_size(instance, entry, count), GFP_KERNEL); >> Applied, thanks. > I take that back, you obviously didn't even compile this patch. Never > send untested crap, without explicitly saying so. >