Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1633279
| From | SF Markus Elfring <elfring@users.sourceforge.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: SATA: Fine-tuning for two function implementations |
| Date | 2017-04-29 10:40 +0200 |
| Message-ID | <tBw54-3X5-7@gated-at.bofh.it> (permalink) |
| References | <txHBL-22s-5@gated-at.bofh.it> <tBm5H-55J-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> Hmmm, allocs -> callocs. Are these actually beneficial? If so, why? > Because one multiplication is rolled into the call? Did the previous size calculations contain the general possibility for integer overflows? https://cwe.mitre.org/data/definitions/190.html * Will the computed values usually stay within the limits of the used data types so far? * How much do you care for corresponding checks and source code annotations by functions like “devm_kcalloc”? Regards, Markus
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 0/3] SATA: Fine-tuning for two function implementations Tejun Heo <tj@kernel.org> - 2017-04-29 00:00 +0200 Re: SATA: Fine-tuning for two function implementations SF Markus Elfring <elfring@users.sourceforge.net> - 2017-04-29 10:40 +0200 Re: [PATCH 0/3] SATA: Fine-tuning for two function implementations Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> - 2017-05-11 17:10 +0200
csiph-web