From: Oscar Salvador <osalvador@suse.de>
To: Oscar Salvador <osalvador.vilardaga@gmail.com>
Cc: Gavin Guo <gavinguo@igalia.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Muchun Song <muchun.song@linux.dev>, Peter Xu <peterx@redhat.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] mm,hugetlb: Change mechanism to detect a COW on private mapping
Date: Sun, 29 Jun 2025 22:12:06 +0200 [thread overview]
Message-ID: <aGGeFrPwAxsu-f3F@localhost.localdomain> (raw)
In-Reply-To: <aGF8v50STTr3fV57@localhost.localdomain>
On Sun, Jun 29, 2025 at 07:49:51PM +0200, Oscar Salvador wrote:
> Are there any considerations to be taken before kicking in the test?
> I don't seem to be able to reproduce the issue.
Nevermind, I just wrote my own reproducer.
I see two ways of fixing this, the simpler being a trylock instead of a
lock, like the original code did.
I'll sleep on it and fix it tomorrow.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2025-06-29 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 10:28 [PATCH v3 0/5] Misc rework on hugetlb faulting path Oscar Salvador
2025-06-27 10:29 ` [PATCH v3 1/5] mm,hugetlb: Change mechanism to detect a COW on private mapping Oscar Salvador
2025-06-28 9:22 ` Gavin Guo
[not found] ` <CAOXBz7gP9Zur3804zJhxFhSjprNc-gfi4vg7w2g07HA2S9EkcA@mail.gmail.com>
2025-06-29 17:49 ` Oscar Salvador
2025-06-29 20:12 ` Oscar Salvador [this message]
2025-06-30 13:26 ` Oscar Salvador
2025-06-27 10:29 ` [PATCH v3 2/5] mm,hugetlb: Sort out folio locking in the faulting path Oscar Salvador
2025-06-27 10:29 ` [PATCH v3 3/5] mm,hugetlb: Rename anon_rmap to new_anon_folio and make it boolean Oscar Salvador
2025-06-27 10:29 ` [PATCH v3 4/5] mm,hugetlb: Drop obsolete comment about non-present pte and second faults Oscar Salvador
2025-06-27 10:29 ` [PATCH v3 5/5] mm,hugetlb: Drop unlikelys from hugetlb_fault Oscar Salvador
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=aGGeFrPwAxsu-f3F@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gavinguo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador.vilardaga@gmail.com \
--cc=peterx@redhat.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;
as well as URLs for NNTP newsgroup(s).