linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@scylladb.com>
To: Yang Shi <shy828301@gmail.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: Possible regression with file madvise(MADV_COLLAPSE)
Date: Sat, 12 Oct 2024 18:38:15 +0300	[thread overview]
Message-ID: <cfeac8a2f1c57e215e7c5a70dbd6945c3d50cff3.camel@scylladb.com> (raw)
In-Reply-To: <CAHbLzkpwQaDe-G=NLa+ekO=Q_67Gz2wHayQYSUx+Wdf-pw5R6g@mail.gmail.com>

On Fri, 2024-10-11 at 15:29 -0700, Yang Shi wrote:
> On Wed, Oct 9, 2024 at 9:04 AM Avi Kivity <avi@scylladb.com> wrote:
> > 
> > On Linux 6.10.10 with CONFIG_READ_ONLY_THP_FOR_FS=y,
> > madvise(MADV_COLLAPSE) on  program text fails with EINVAL.
> > 
> > To reproduce, compile the reproducer with
> > 
> > clang -g -o text-hugepage  text-hugepage.c \
> >         -fuse-ld=lld \
> >         -Wl,-zcommon-page-size=2097152 -Wl,-zmax-page-size=2097152
> > \
> >         -Wl,-z,separate-loadable-segments
> > 
> > and run:
> 
> Didn't clang make the page cache dirty?
> 
> Having sync between clang and the execution made the problem go away
> for me.
> 

I see it even with sync (and msync just before the madvise calls).


Tracing shows this (last lines before syscall exit):

|          hpage_collapse_scan_file() {
|            __rcu_read_lock();
|            __rcu_read_unlock();
|          }


so, it's not clear what the root cause is.



  reply	other threads:[~2024-10-12 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 15:54 Avi Kivity
2024-10-11  6:32 ` Gavin Shan
2024-10-11 22:29 ` Yang Shi
2024-10-12 15:38   ` Avi Kivity [this message]
2024-10-12 20:05     ` Yang Shi
2024-10-12 20:24       ` Avi Kivity
2024-10-12 23:50         ` Yang Shi
2024-10-13 11:04           ` Avi Kivity
2024-10-13 13:25             ` Avi Kivity
2024-10-14 22:06               ` Yang Shi

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=cfeac8a2f1c57e215e7c5a70dbd6945c3d50cff3.camel@scylladb.com \
    --to=avi@scylladb.com \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@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