[PATCH v3] Fix FORTIFY_SOURCE false positive
Volker Weißmann
volker.weissmann@gmx.de
Wed Feb 12 14:52:03 GMT 2025
Shall I implement it or is there anyone else who wants to do that?
On 11/02/2025 09.17, Florian Weimer wrote:
> * Volker Weißmann:
>
>> How about we revert my commit, but change the error message from
>>
>> "*** %n in writable segment detected ***\n"
>>
>> to
>>
>> "*** %n in writable segment detected or maximum number of open files
>> reached ***\n"
> I think we should provide different messages based on the situation.
>
> For read-only memory in ELF objects, we don't even know to go to
> /proc/self/maps, we can use the dynamic linker data structures directly.
>
> It's a pity that we can't just tell the CPU to fault when we're trying
> to load from writable memory.
>
> Thanks,
> Florian
>
More information about the Libc-alpha
mailing list