All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Weißschuh " <thomas@t-8ch.de>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: util-linux@vger.kernel.org
Subject: Re: RFH: fincore/count lsfd/column-xmode failing on sparc64
Date: Sat, 11 Nov 2023 20:10:19 +0100 (GMT+01:00)	[thread overview]
Message-ID: <b5dcde27-d08d-4b2e-80df-1a1edf8e447b@t-8ch.de> (raw)
In-Reply-To: <dfb16443d2e030e2738d83a886572fdddc64f7ba.camel@physik.fu-berlin.de>

Nov 11, 2023 19:46:08 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>:

> Hi Thomas,
>
> On Sat, 2023-11-11 at 19:37 +0100, Thomas Weißschuh wrote:
>> Hi,
>>
>> Nov 11, 2023 19:23:20 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>:
>>
>>> Hello!
>>>
>>> On sparc64 running Linux 6.5.0, the following two tests are failing:
>>
>> Which version of util-linux is this?
>
> This is on git master, so e0f3b02d5.
>
>> For the fincore test:
>> Can you check with strace if it is using the mincore or cachestat syscall?
>
> I can't seem to spot neither in the strace log:
>
>> https://people.debian.org/~glaubitz/fincore-strace-sparce64.log
>
> Log created with "strace -o ~/fincore-strace-sparce64.log ./tests/ts/fincore/count".

The log is missing the calls to the fincore binary itself.
Can you add a "-f"?

Did it work with an older Kernel?
Since 6.5 it should use cachestat. Before it was mincore().
Or disable cachestat via "enosys" from util-linux.

I can also take a look on Monday.

  reply	other threads:[~2023-11-11 19:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 18:23 RFH: fincore/count lsfd/column-xmode failing on sparc64 John Paul Adrian Glaubitz
2023-11-11 18:37 ` Thomas Weißschuh 
2023-11-11 18:46   ` John Paul Adrian Glaubitz
2023-11-11 19:10     ` Thomas Weißschuh  [this message]
2023-11-12  7:53       ` John Paul Adrian Glaubitz
2023-11-13 17:50         ` Thomas Weißschuh
2023-11-13 18:06           ` John Paul Adrian Glaubitz
2023-11-13 20:10             ` Thomas Weißschuh
2023-11-13 20:36               ` John Paul Adrian Glaubitz
2023-11-12 17:54 ` Masatake YAMATO
2023-11-12 19:04   ` John Paul Adrian Glaubitz

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=b5dcde27-d08d-4b2e-80df-1a1edf8e447b@t-8ch.de \
    --to=thomas@t-8ch.de \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.