Hello;
On 26/08/2016 11:00, Konstantin Belousov wrote:
On Fri, Aug 26, 2016 at 10:00:58AM -0500, Pedro Giffuni wrote:
On 08/26/16 05:56, Konstantin Belousov wrote:
On Thu, Aug 25, 2016 at 05:50:31PM -0500, Pedro Giffuni wrote:
Hello;
GNU RELRO support was committed in r230784 (2012-01-30) but we never
enabled it by default.
There was some discussion about it on
https://reviews.freebsd.org/D3001
By now, all Linux distributions, NetBSD and DragonFly support it and
it is the default for most systems in binutils 2.27.
This doesn't affect performance, I ran it through an exp-run last
year, no other OS has had issues etc ... seems safe and can be
disabled if needed when linking.
Exp-run does not test anything interesting about relro. If all testing
that was done is basically just an exp-run, then there was no useful
runtime testing done.
The exp-run does cover Java and other VM-type thingies that bootstrap.
For upstream binutils this is now the default (at least for linux,
they never ask us if we want to follow). So the change has been tested
extensively but perhaps not on cases that are relevant to us.
Note that the "fix" for any port is ultimately trivial:
LDFLAGS+= "-z norelro"
I think it's time to enable it be default in our base binutils. If
there are no objections, I will just commit the attached patch over
the weekend.
There are objections, the change must be runtime tested on large and
representative set of real-world applications before turning the knob.
You are not giving any hint on what would be a "representative set of
real-world applications". Given that you committed the initial support
your objection stands very high and is a blocker. :(
Well, I indeed do not think that 'works on my desktop' is good enough
testing for this change. I understand that it is impossible to test
all ports at runtime, or even a significant percentage of them, not to
mention programs which sit on the user's storage.
What actually worries me in the fate of such changes is that submitter
never starts monitoring user complains and see whether the change causes
some delayed random breakage. It just ends up in the 'BSD is broken'
basket with one more supportive case.
The change is now in linux too, so they will be saying "BSD and Linux
are broken". ;)
I understand the concern, and admittedly there's no way to catch all
issues, but that's why we have -current and -stable, so we can isolate
all of those cases before the users in a release get hit by it.
I see this change pretty much in the lines of the
"stack-protector-strong" change: FreeBSD 11 will be the first release to
include the change (only in base). I recall there was one overflow in
the FAT filesystem which was caught by the change and by now I hope/wish
we have figured out any issue. Had we committed the change earlier it
might have received more testing.
There is no perfect time to make such changes but it's better to try to
keep in line with
the changes upstream (binutils in this case) than to stay still while
the rest of the world
moves on.
As I see it committing it now would give ample time to test this in
current before it hits any release. If you want more extensive testing
merging it in -stable right after the 11-Release is guaranteed to help
weed out any remaining update ports may need.
It is useless 'testing' when the cause of breakage is not actively
looked for and identified. You commit it now, five months later some
unlucky user reports that his application coredumps. What next ?
Unlucky user must be running -current to be affected: if we don't MFC
the change it will take more than one year until it hits end users in a
release. If the breakage is in base, we want to know as early as we can,
if the breakage is in third party ports, they will benefit from upstream
getting the BSD and linux breakage reports.
BTW, I wonder how lld handles RELRO, is it supported or even the default?
Pedro.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
