From: "Petr Štetiar" <ynezz@true.cz>
To: Phil Auld <pauld@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, yury.norov@gmail.com,
rafael@kernel.org
Subject: Re: aarch64 5.15.68 regression in topology/thread_siblings (huge file size and no content)
Date: Thu, 22 Sep 2022 16:05:04 +0200 [thread overview]
Message-ID: <20220922140504.GA58265@meh.true.cz> (raw)
In-Reply-To: <Yyxgtx/Vr6Ar1xEe@lorien.usersys.redhat.com>
Phil Auld <pauld@redhat.com> [2022-09-22 09:18:47]:
Hi,
> I've seen the size cause problems for tools. Are we sure that it's the empty file and not
> the size causing issues? Maybe something is treating that as signed again for a count of
> -1 bytes (which seems like it would be a bug anyway)?
root@OpenWrt:/# strace cat /sys/devices/system/cpu/cpu1/topology/thread_siblings
...snip...
openat(AT_FDCWD, "/sys/devices/system/cpu/cpu1/topology/thread_siblings", O_RDONLY|O_LARGEFILE) = 3
sendfile(1, 3, NULL, 16777216) = 0
root@OpenWrt:/# strace md5sum /sys/devices/system/cpu/cpu1/topology/thread_sibli
...snip...
openat(AT_FDCWD, "/sys/devices/system/cpu/cpu1/topology/thread_siblings", O_RDONLY|O_LARGEFILE) = 3
read(3, "", 4096) = 0
root@OpenWrt:/# strace head /sys/devices/system/cpu/cpu1/topology/thread_siblings
...snip...
openat(AT_FDCWD, "/sys/devices/system/cpu/cpu1/topology/thread_siblings", O_RDONLY|O_LARGEFILE) = 3
read(3, "", 1024) = 0
Cheers,
Petr
next prev parent reply other threads:[~2022-09-22 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 11:32 aarch64 5.15.68 regression in topology/thread_siblings (huge file size and no content) Petr Štetiar
2022-09-22 12:32 ` Phil Auld
2022-09-22 12:40 ` Greg Kroah-Hartman
2022-09-22 13:18 ` Phil Auld
2022-09-22 14:05 ` Petr Štetiar [this message]
2022-09-22 17:18 ` Phil Auld
2022-09-22 20:05 ` Petr Štetiar
2022-09-23 9:16 ` Greg Kroah-Hartman
2022-09-23 13:02 ` Phil Auld
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=20220922140504.GA58265@meh.true.cz \
--to=ynezz@true.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pauld@redhat.com \
--cc=rafael@kernel.org \
--cc=yury.norov@gmail.com \
/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