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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 24 Jul 2014 20:20:16 +0200 From: Toralf Förster <toralf.foerster@....de> To: linux-ia64@...r.kernel.org, ceph-devel@...r.kernel.org CC: Linux Kernel <linux-kernel@...r.kernel.org> Subject: sizeof (struct tYpO *) : it is just a typo or rather a bug ? Inspired by this "typo" fix http://article.gmane.org/gmane.linux.kernel/1754640 I grep'ed the current git tree of linus for similar issues. For these 4 places I'm wondering where the appropriate struct definition is located : arch/ia64/sn/kernel/io_acpi_init.c: sizeof(struct pci_devdev_info *)) { tools/perf/builtin-sched.c: sched->tasks = realloc(sched->tasks, sched->nr_tasks * sizeof(struct task_task *)); fs/ceph/xattr.c: xattrs = kcalloc(numattr, sizeof(struct ceph_xattr *), fs/ceph/xattr.c: memset(xattrs, 0, numattr*sizeof(struct ceph_xattr *)); Nevertheless I was told, that gcc doesn't complain about such things due to eventually evaluating it to "sizeof(null)". I'm however curious if at least a warning should be emitted in such a case, or? -- Toralf -- 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