public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "petre.rodan at subdimension dot ro" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31212] seekdir() unexected directory stream positioning on 32bit arm
Date: Fri, 05 Jan 2024 08:49:52 +0000	[thread overview]
Message-ID: <bug-31212-131-1p2BJCHIVO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31212-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31212

--- Comment #1 from Petre Rodan <petre.rodan at subdimension dot ro> ---
Created attachment 15286
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15286&action=edit
output of emerge --info

for a bit of context, the bug started here

https://lkml.org/lkml/2024/1/4/281

and for the Gentoo toolchain devs I will attach the emerge --info and the glibc
USE flags

[ebuild   R    ] sys-libs/glibc-2.37-r7:2.2::gentoo  USE="caps gd multiarch ssp
static-libs -audit -cet -compile-locales -crypt -custom-cflags -doc
-hash-sysv-compat -headers-only -multilib -multilib-bootstrap -nscd -perl
-profile (-selinux) -stack-realign -suid -systemd -systemtap -test -vanilla"
18308 KiB

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-01-05  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 21:53 [Bug libc/31212] New: " petre.rodan at subdimension dot ro
2024-01-05  8:33 ` [Bug libc/31212] " sam at gentoo dot org
2024-01-05  8:33 ` sam at gentoo dot org
2024-01-05  8:49 ` petre.rodan at subdimension dot ro [this message]
2024-01-05 10:15 ` [Bug libc/31212] seekdir() unexpected " petre.rodan at subdimension dot ro
2024-01-06  9:32 ` dilfridge at gentoo dot org
2024-01-21 19:11 ` dilfridge at gentoo 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-31212-131-1p2BJCHIVO@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).