From: Matthew Wilcox <willy@infradead.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: bugzilla-daemon@kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
decedion@gmail.com, mmp.dux@gmail.com
Subject: Re: [Bug 216646] having TRANSPARENT_HUGEPAGE enabled hangs some applications (supervisor read access in kernel mode)
Date: Fri, 2 Dec 2022 16:58:42 +0000 [thread overview]
Message-ID: <Y4ouwhqSyDV7I+D9@casper.infradead.org> (raw)
In-Reply-To: <220fd094-7cf1-9d17-8380-98d5663dc5da@leemhuis.info>
On Fri, Dec 02, 2022 at 12:56:40PM +0100, Thorsten Leemhuis wrote:
> On 21.11.22 21:54, Andrew Morton wrote:
> > On Mon, 21 Nov 2022 18:34:34 +0000 bugzilla-daemon@kernel.org wrote:
> >
> >> https://bugzilla.kernel.org/show_bug.cgi?id=216646
> >>
> >> --- Comment #6 from Mikhail Pletnev (mmp.dux@gmail.com) ---
> >> i can't figure out how to use git send-email, so i will post this here instead
> >>
> >>>>> git bisect good 1854bc6e2420472676c5c90d3d6b15f6cd640e40
> >>
> >>> I suspect this is where your bisection went astray. This should have
> >>> been bad and it led you to the wrong commit.
> >>
> >> so i've applied your suggestion and did some more bisecting and arrived at
> >> this:
>
> That was 793917d997df ("mm/readahead: Add large folio readahead") which
> is also from Matthew.
>
> > Folks, thanks for continuing to work on this.
>
> Well, since then nothing happened. :-/ Or have I missed something?
>
> Matthew, do you still have this on your radar?
No, things tend to fall off my radar after a week or two of inactivity.
Particularly since I went on holiday. Since I wasn't cc'd on the bug,
the activity was completely invisible to me.
Landing on 793917d997df makes a lot more sense. That's where we
actually start using large folios. It doesn't really help narrow
down the problem. I have an idea for what it might be; patch to
try will follow. But I'll need feedback by email.
next prev parent reply other threads:[~2022-12-02 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216646-27@https.bugzilla.kernel.org/>
[not found] ` <bug-216646-27-o4jKola2S5@https.bugzilla.kernel.org/>
2022-11-21 20:54 ` [Bug 216646] having TRANSPARENT_HUGEPAGE enabled hangs some applications (supervisor read access in kernel mode) Andrew Morton
2022-11-22 9:22 ` Bugzilla (was: Re: [Bug 216646] having TRANSPARENT_HUGEPAGE enabled hangs some applications (supervisor read access in kernel mode)) Thorsten Leemhuis
2022-12-02 11:56 ` [Bug 216646] having TRANSPARENT_HUGEPAGE enabled hangs some applications (supervisor read access in kernel mode) Thorsten Leemhuis
2022-12-02 16:58 ` Matthew Wilcox [this message]
2022-12-02 21:56 ` Mikhail Pletnev
2022-12-02 21:57 ` Matthew Wilcox
2022-12-02 22:44 ` Mikhail Pletnev
2022-12-05 20:25 ` Matthew Wilcox
2022-12-06 2:08 ` Mikhail Pletnev
2022-12-16 5:23 ` Thorsten Leemhuis
2023-02-24 10:21 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-24 18:08 ` Mikhail Pletenv
2023-03-14 10:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-17 11:12 ` Linux regression tracking (Thorsten Leemhuis)
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=Y4ouwhqSyDV7I+D9@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@kernel.org \
--cc=decedion@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mmp.dux@gmail.com \
--cc=regressions@leemhuis.info \
/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).