diff options
author | Mike Frysinger <vapier@gentoo.org> | 2012-04-12 11:18:39 -0400 |
---|---|---|
committer | Mike Frysinger <vapier@gentoo.org> | 2012-05-08 01:51:22 -0400 |
commit | abb66a672f5575a328d05c0790403af673d0f76c (patch) | |
tree | 44834ee4c7ebbecdf5aab4eb8e1f95668d3c36f6 /cppflags-iterator.mk | |
parent | 05760585e0f74222d531dc9bb72d39d028857312 (diff) | |
download | glibc-abb66a672f5575a328d05c0790403af673d0f76c.tar.gz |
tftp.h: rework layout to work with fortification
The current tftp structure does not work when fortification is enabled.
Starting with gcc-4.5, more size checking was added to trigger these.
Older versions just didn't have enough information, so they returned -1
as the sizes.
First, the tu_stuff field is declared as 1 byte (when it's really an
arbitrary length C string), so attempting to strcpy() with it results
in crashes. This fails with _FORTIFY_SOURCE=1.
Second, even if we change that to [0] (since gcc does not allow flexible
array members in an union), gcc is not smart enough to see that they are
two overlapping flexible arrays (tu_stuff and tu_data), so it will still
trigger an abort with _FORTIFY_SOURCE=2. This is because it thinks that
tu_stuff is 0 bytes and tu_data comes after it.
Talking to upstream gcc, they don't seem terribly inclined to fix the
2nd issue, but even if they did, we still have plenty of 4.5 and 4.6
installs that would hit problems.
So, let's re-order with a few more anonymous structs & unions so that
the fields are laid out with a zero-length array always as the last
field. This seems to fix things with gcc-4.6, and the tftp-hpa pkg
continues to build & work.
URL: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/691345
URL: https://bugs.archlinux.org/task/28103
URL: https://bugs.gentoo.org/357083
URL: http://gcc.gnu.org/PR52944
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'cppflags-iterator.mk')
0 files changed, 0 insertions, 0 deletions