public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/29126] New: libio: _IO_MTSAFE_IO is not assumed on some places
Date: Fri, 06 May 2022 20:10:39 +0000 [thread overview]
Message-ID: <bug-29126-131@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2022-05-06 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 20:10 adhemerval.zanella at linaro dot org [this message]
2022-05-06 20:47 ` [Bug stdio/29126] " schwab@linux-m68k.org
2022-05-06 21:06 ` adhemerval.zanella at linaro dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29126-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).