Re: _FORTIFY_SOURCE by default?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: _FORTIFY_SOURCE by default?
Дата
Msg-id 430.1347770475@sss.pgh.pa.us
обсуждение исходный текст
Ответ на _FORTIFY_SOURCE by default?  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: _FORTIFY_SOURCE by default?  (Andrew Dunstan <andrew@dunslane.net>)
Re: _FORTIFY_SOURCE by default?  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> _FORTIFY_SOURCE=2 appears to be the default for package building on many
> Linux distributions now, as part of harding or security options.  But we
> often hear about problems related to this only when we hand the source
> over to the packagers.  So I think we might as well add this to our
> standard compilation options, for example in src/include/port/linux.h.
> What do you think?

Doesn't seem like a good idea to me to add platform-specific options
with unspecified effects to platform-independent upstream sources.

To the extent that this option finds anything useful (which in my
experience is a negligibly small percentage anyway), it's the
responsibility of the packagers (including me) to report it.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Следующее
От: Amit kapila
Дата:
Сообщение: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown