From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Qu Wenruo <wqu@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: Kmap-related crashes and memory leaks on 32bit arch (5.15+)
Date: Fri, 5 Nov 2021 20:50:04 +0100 [thread overview]
Message-ID: <20211105195004.GJ28560@suse.cz> (raw)
In-Reply-To: <CAHk-=whBOXM3mh-QtzK-EQtDEHQLcziAXu07KxU1crUc5jiQUg@mail.gmail.com>
On Thu, Nov 04, 2021 at 04:37:25PM -0700, Linus Torvalds wrote:
> On Thu, Nov 4, 2021 at 3:09 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > If (a) works, but (b) still fails, then it must be some odd
> > interaction issug withs-----ing else. Which sounds unlikely, since I
> > don't think we really had anything that should affect kmap or anything
> > in this area, but who knows...
>
> And bisection ends up perhaps somewhat painful, but sounds like the
> way to go if there's no other path forward.
Just to give an update, I tested several merge commits and the btrfs
merge is the first bad (037c50bfbeb33b4c).
Last good is the one right before that,
9c6e8d52a7299 Merge tag 'exfat-for-5.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat
(plus the fixup to make it compile e66435936756d9bce)
The remaining test to do is the merge conflict resolved by me, as you
suggested.
next prev parent reply other threads:[~2021-11-05 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 11:50 Kmap-related crashes and memory leaks on 32bit arch (5.15+) David Sterba
[not found] ` <CAHk-=whYQvExYESEOJoSj4Jy7t+tSZgbCWuNpdwXYh+3zq2itw@mail.gmail.com>
2021-11-04 23:37 ` Linus Torvalds
2021-11-04 23:48 ` Linus Torvalds
2021-11-05 0:01 ` Qu Wenruo
2021-11-05 16:07 ` Ira Weiny
2021-11-05 19:50 ` David Sterba [this message]
2021-11-16 15:43 ` David Sterba
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=20211105195004.GJ28560@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=wqu@suse.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