public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug stdio/29126] New: libio: _IO_MTSAFE_IO is not assumed on some places
@ 2022-05-06 20:10 adhemerval.zanella at linaro dot org
2022-05-06 20:47 ` [Bug stdio/29126] " schwab@linux-m68k.org
2022-05-06 21:06 ` adhemerval.zanella at linaro dot org
0 siblings, 2 replies; 3+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2022-05-06 20:10 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=29126
Bug ID: 29126
Summary: libio: _IO_MTSAFE_IO is not assumed on some places
Product: glibc
Version: 2.36
Status: NEW
Severity: normal
Priority: P2
Component: stdio
Assignee: unassigned at sourceware dot org
Reporter: adhemerval.zanella at linaro dot org
Target Milestone: ---
The libio/libio.h defines internal macros to optimize _IO_peekc, _IO_flockfile,
and_IO_funlockfile. However, it only defines it to check for lock if
_IO_MTSAFE_IO is defined.
Some file does not set _IO_MTSAFE_IO (for instance malloc.c and putgrent.c)
which makes stdio stream usage wrong regarding locking (since
_IO_flockfile/_IO_funlockfile will be empty definitions).
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug stdio/29126] libio: _IO_MTSAFE_IO is not assumed on some places
2022-05-06 20:10 [Bug stdio/29126] New: libio: _IO_MTSAFE_IO is not assumed on some places adhemerval.zanella at linaro dot org
@ 2022-05-06 20:47 ` schwab@linux-m68k.org
2022-05-06 21:06 ` adhemerval.zanella at linaro dot org
1 sibling, 0 replies; 3+ messages in thread
From: schwab@linux-m68k.org @ 2022-05-06 20:47 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=29126
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
grp/Makefile:CFLAGS-putgrent.c += -fexceptions $(libio-mtsafe)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug stdio/29126] libio: _IO_MTSAFE_IO is not assumed on some places
2022-05-06 20:10 [Bug stdio/29126] New: libio: _IO_MTSAFE_IO is not assumed on some places adhemerval.zanella at linaro dot org
2022-05-06 20:47 ` [Bug stdio/29126] " schwab@linux-m68k.org
@ 2022-05-06 21:06 ` adhemerval.zanella at linaro dot org
1 sibling, 0 replies; 3+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2022-05-06 21:06 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=29126
--- Comment #2 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Andreas Schwab from comment #1)
> grp/Makefile:CFLAGS-putgrent.c += -fexceptions $(libio-mtsafe)
Indeed, I haven't checked all the code that is affected by the missing
_IO_MTSAFE_IO. In any case my intended fix to assume _IO_MTSAFE_IO.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-05-06 21:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-06 20:10 [Bug stdio/29126] New: libio: _IO_MTSAFE_IO is not assumed on some places adhemerval.zanella at linaro dot org
2022-05-06 20:47 ` [Bug stdio/29126] " schwab@linux-m68k.org
2022-05-06 21:06 ` adhemerval.zanella at linaro dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).