From: Johannes Weiner <hannes@cmpxchg.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Oliver Sang <oliver.sang@intel.com>,
David Hildenbrand <david@redhat.com>,
Alistair Popple <apopple@nvidia.com>,
linux-mm@kvack.org, Christian Brauner <brauner@kernel.org>,
Hannes Reinecke <hare@suse.de>,
oe-lkp@lists.linux.dev, lkp@intel.com,
John Garry <john.g.garry@oracle.com>,
linux-block@vger.kernel.org, ltp@lists.linux.it,
Pankaj Raghav <p.raghav@samsung.com>,
Daniel Gomez <da.gomez@samsung.com>,
David Bueso <dave@stgolabs.net>
Subject: Re: [linux-next:master] [block/bdev] 3c20917120: BUG:sleeping_function_called_from_invalid_context_at_mm/util.c
Date: Sat, 22 Mar 2025 19:14:40 -0400 [thread overview]
Message-ID: <20250322231440.GA1894930@cmpxchg.org> (raw)
In-Reply-To: <Z9wF57eEBR-42K9a@bombadil.infradead.org>
Hey Luis,
On Thu, Mar 20, 2025 at 05:11:19AM -0700, Luis Chamberlain wrote:
> On Wed, Mar 19, 2025 at 07:24:23PM +0000, Matthew Wilcox wrote:
> > On Wed, Mar 19, 2025 at 12:16:41PM -0700, Luis Chamberlain wrote:
> > > On Wed, Mar 19, 2025 at 09:55:11AM -0700, Luis Chamberlain wrote:
> > > > FWIW, I'm not seeing this crash or any kernel splat within the
> > > > same time (I'll let this run the full 2.5 hours now to verify) on
> > > > vanilla 6.14.0-rc3 + the 64k-sector-size patches, which would explain why I
> > > > hadn't seen this in my earlier testing over 10 ext4 profiles on fstests. This
> > > > particular crash seems likely to be an artifact on the development cycle on
> > > > next-20250317.
> > >
> > > I confirm that with a vanilla 6.14.0-rc3 + the 64k-sector-size patches a 2.5
> > > hour run generic/750 doesn't crash at all. So indeed something on the
> > > development cycle leads to this particular crash.
> >
> > We can't debug two problems at once.
> >
> > FOr the first problem, I've demonstrated what the cause is, and that's
> > definitely introduced by your patch, so we need to figure out a
> > solution.
>
> Sure, yeah I followed that.
>
> > For the second problem, we don't know what it is. Do you want to bisect
> > it to figure out which commit introduced it?
>
> Sure, the culprit is the patch titled:
>
> mm: page_alloc: trace type pollution from compaction capturing
>
> Johannes, any ideas? You can reproduce easily (1-2 minutes) by running
> fstests against ext4 with a 4k block size filesystem on linux-next
> against the test generic/750.
Sorry for the late reply, I just saw your emails now.
> Below is the splat decoded.
>
> Mar 20 11:52:55 extra-ext4-4k kernel: Linux version 6.14.0-rc6+ (mcgrof@beefy) (gcc (Debian 14.2.0-16) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #51 SMP PREEMPT_DYNAMIC Thu Mar 20 11:50:32 UTC 2025
> Mar 20 11:52:55 extra-ext4-4k kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.14.0-rc6+ root=PARTUUID=503fa6f2-2d5b-4d7e-8cf8-3a811de326ce ro console=tty0 console=tty1 console=ttyS0,115200n8 console=ttyS0
>
> < -- etc -->
>
> Mar 20 11:55:27 extra-ext4-4k unknown: run fstests generic/750 at 2025-03-20 11:55:27
> Mar 20 11:55:28 extra-ext4-4k kernel: EXT4-fs (loop5): mounted filesystem c20cbdee-a370-4743-80aa-95dec0beaaa2 r/w with ordered data mode. Quota mode: none.
> Mar 20 11:56:29 extra-ext4-4k kernel: BUG: unable to handle page fault for address: ffff93098000ba00
> Mar 20 11:56:29 extra-ext4-4k kernel: #PF: supervisor read access in kernel mode
> Mar 20 11:56:29 extra-ext4-4k kernel: #PF: error_code(0x0000) - not-present page
> Mar 20 11:56:29 extra-ext4-4k kernel: PGD 3a201067 P4D 3a201067 PUD 0
> Mar 20 11:56:29 extra-ext4-4k kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
> Mar 20 11:56:29 extra-ext4-4k kernel: CPU: 0 UID: 0 PID: 74 Comm: kcompactd0 Not tainted 6.14.0-rc6+ #51
> Mar 20 11:56:29 extra-ext4-4k kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2024.11-5 01/28/2025
> Mar 20 11:56:29 extra-ext4-4k kernel: RIP: 0010:__zone_watermark_ok (mm/page_alloc.c:3256)
> Mar 20 11:56:29 extra-ext4-4k kernel: Code: 00 00 00 41 f7 c0 38 02 00 00 0f 85 2c 01 00 00 48 8b 4f 30 48 63 d2 48 01 ca 85 db 0f 84 f3 00 00 00 49 29 d1 bb 80 00 00 00 <4c> 03 54 f7 38 31 d2 4d 39 ca 0f 8d d2 00 00 00 ba 01 00 00 00 85
> All code
> ========
> 0: 00 00 add %al,(%rax)
> 2: 00 41 f7 add %al,-0x9(%rcx)
> 5: c0 38 02 sarb $0x2,(%rax)
> 8: 00 00 add %al,(%rax)
> a: 0f 85 2c 01 00 00 jne 0x13c
> 10: 48 8b 4f 30 mov 0x30(%rdi),%rcx
> 14: 48 63 d2 movslq %edx,%rdx
> 17: 48 01 ca add %rcx,%rdx
> 1a: 85 db test %ebx,%ebx
> 1c: 0f 84 f3 00 00 00 je 0x115
> 22: 49 29 d1 sub %rdx,%r9
> 25: bb 80 00 00 00 mov $0x80,%ebx
> 2a:* 4c 03 54 f7 38 add 0x38(%rdi,%rsi,8),%r10 <-- trapping instruction
This looks like the same issue the bot reported here:
https://lore.kernel.org/all/20250321135524.GA1888695@cmpxchg.org/
There is a fix for it queued in next-20250318 and later. Could you
please double check with your reproducer against a more recent next?
Thanks
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Pankaj Raghav <p.raghav@samsung.com>,
Daniel Gomez <da.gomez@samsung.com>,
Christian Brauner <brauner@kernel.org>,
David Bueso <dave@stgolabs.net>, Jan Kara <jack@suse.cz>,
lkp@intel.com, David Hildenbrand <david@redhat.com>,
Alistair Popple <apopple@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
linux-block@vger.kernel.org, linux-mm@kvack.org,
Oliver Sang <oliver.sang@intel.com>,
Hannes Reinecke <hare@suse.de>,
John Garry <john.g.garry@oracle.com>,
oe-lkp@lists.linux.dev, ltp@lists.linux.it
Subject: Re: [LTP] [linux-next:master] [block/bdev] 3c20917120: BUG:sleeping_function_called_from_invalid_context_at_mm/util.c
Date: Sat, 22 Mar 2025 19:14:40 -0400 [thread overview]
Message-ID: <20250322231440.GA1894930@cmpxchg.org> (raw)
In-Reply-To: <Z9wF57eEBR-42K9a@bombadil.infradead.org>
Hey Luis,
On Thu, Mar 20, 2025 at 05:11:19AM -0700, Luis Chamberlain wrote:
> On Wed, Mar 19, 2025 at 07:24:23PM +0000, Matthew Wilcox wrote:
> > On Wed, Mar 19, 2025 at 12:16:41PM -0700, Luis Chamberlain wrote:
> > > On Wed, Mar 19, 2025 at 09:55:11AM -0700, Luis Chamberlain wrote:
> > > > FWIW, I'm not seeing this crash or any kernel splat within the
> > > > same time (I'll let this run the full 2.5 hours now to verify) on
> > > > vanilla 6.14.0-rc3 + the 64k-sector-size patches, which would explain why I
> > > > hadn't seen this in my earlier testing over 10 ext4 profiles on fstests. This
> > > > particular crash seems likely to be an artifact on the development cycle on
> > > > next-20250317.
> > >
> > > I confirm that with a vanilla 6.14.0-rc3 + the 64k-sector-size patches a 2.5
> > > hour run generic/750 doesn't crash at all. So indeed something on the
> > > development cycle leads to this particular crash.
> >
> > We can't debug two problems at once.
> >
> > FOr the first problem, I've demonstrated what the cause is, and that's
> > definitely introduced by your patch, so we need to figure out a
> > solution.
>
> Sure, yeah I followed that.
>
> > For the second problem, we don't know what it is. Do you want to bisect
> > it to figure out which commit introduced it?
>
> Sure, the culprit is the patch titled:
>
> mm: page_alloc: trace type pollution from compaction capturing
>
> Johannes, any ideas? You can reproduce easily (1-2 minutes) by running
> fstests against ext4 with a 4k block size filesystem on linux-next
> against the test generic/750.
Sorry for the late reply, I just saw your emails now.
> Below is the splat decoded.
>
> Mar 20 11:52:55 extra-ext4-4k kernel: Linux version 6.14.0-rc6+ (mcgrof@beefy) (gcc (Debian 14.2.0-16) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #51 SMP PREEMPT_DYNAMIC Thu Mar 20 11:50:32 UTC 2025
> Mar 20 11:52:55 extra-ext4-4k kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.14.0-rc6+ root=PARTUUID=503fa6f2-2d5b-4d7e-8cf8-3a811de326ce ro console=tty0 console=tty1 console=ttyS0,115200n8 console=ttyS0
>
> < -- etc -->
>
> Mar 20 11:55:27 extra-ext4-4k unknown: run fstests generic/750 at 2025-03-20 11:55:27
> Mar 20 11:55:28 extra-ext4-4k kernel: EXT4-fs (loop5): mounted filesystem c20cbdee-a370-4743-80aa-95dec0beaaa2 r/w with ordered data mode. Quota mode: none.
> Mar 20 11:56:29 extra-ext4-4k kernel: BUG: unable to handle page fault for address: ffff93098000ba00
> Mar 20 11:56:29 extra-ext4-4k kernel: #PF: supervisor read access in kernel mode
> Mar 20 11:56:29 extra-ext4-4k kernel: #PF: error_code(0x0000) - not-present page
> Mar 20 11:56:29 extra-ext4-4k kernel: PGD 3a201067 P4D 3a201067 PUD 0
> Mar 20 11:56:29 extra-ext4-4k kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
> Mar 20 11:56:29 extra-ext4-4k kernel: CPU: 0 UID: 0 PID: 74 Comm: kcompactd0 Not tainted 6.14.0-rc6+ #51
> Mar 20 11:56:29 extra-ext4-4k kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2024.11-5 01/28/2025
> Mar 20 11:56:29 extra-ext4-4k kernel: RIP: 0010:__zone_watermark_ok (mm/page_alloc.c:3256)
> Mar 20 11:56:29 extra-ext4-4k kernel: Code: 00 00 00 41 f7 c0 38 02 00 00 0f 85 2c 01 00 00 48 8b 4f 30 48 63 d2 48 01 ca 85 db 0f 84 f3 00 00 00 49 29 d1 bb 80 00 00 00 <4c> 03 54 f7 38 31 d2 4d 39 ca 0f 8d d2 00 00 00 ba 01 00 00 00 85
> All code
> ========
> 0: 00 00 add %al,(%rax)
> 2: 00 41 f7 add %al,-0x9(%rcx)
> 5: c0 38 02 sarb $0x2,(%rax)
> 8: 00 00 add %al,(%rax)
> a: 0f 85 2c 01 00 00 jne 0x13c
> 10: 48 8b 4f 30 mov 0x30(%rdi),%rcx
> 14: 48 63 d2 movslq %edx,%rdx
> 17: 48 01 ca add %rcx,%rdx
> 1a: 85 db test %ebx,%ebx
> 1c: 0f 84 f3 00 00 00 je 0x115
> 22: 49 29 d1 sub %rdx,%r9
> 25: bb 80 00 00 00 mov $0x80,%ebx
> 2a:* 4c 03 54 f7 38 add 0x38(%rdi,%rsi,8),%r10 <-- trapping instruction
This looks like the same issue the bot reported here:
https://lore.kernel.org/all/20250321135524.GA1888695@cmpxchg.org/
There is a fix for it queued in next-20250318 and later. Could you
please double check with your reproducer against a more recent next?
Thanks
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-03-22 23:14 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:43 [linux-next:master] [block/bdev] 3c20917120: BUG:sleeping_function_called_from_invalid_context_at_mm/util.c kernel test robot
2025-03-10 7:43 ` [LTP] " kernel test robot
2025-03-11 12:10 ` Christian Brauner
2025-03-11 12:10 ` [LTP] " Christian Brauner via ltp
2025-03-12 5:02 ` Luis Chamberlain
2025-03-12 5:02 ` [LTP] " Luis Chamberlain via ltp
2025-03-18 5:28 ` Oliver Sang
2025-03-18 5:28 ` [LTP] " Oliver Sang
2025-03-18 8:15 ` Luis Chamberlain
2025-03-18 8:15 ` [LTP] " Luis Chamberlain via ltp
2025-03-18 14:37 ` Matthew Wilcox
2025-03-18 14:37 ` [LTP] " Matthew Wilcox
2025-03-18 23:17 ` Luis Chamberlain
2025-03-18 23:17 ` [LTP] " Luis Chamberlain via ltp
2025-03-19 2:58 ` Matthew Wilcox
2025-03-19 2:58 ` [LTP] " Matthew Wilcox
2025-03-19 16:55 ` Luis Chamberlain
2025-03-19 16:55 ` [LTP] " Luis Chamberlain via ltp
2025-03-19 19:16 ` Luis Chamberlain
2025-03-19 19:16 ` [LTP] " Luis Chamberlain via ltp
2025-03-19 19:24 ` Matthew Wilcox
2025-03-19 19:24 ` [LTP] " Matthew Wilcox
2025-03-20 12:11 ` Luis Chamberlain
2025-03-20 12:11 ` [LTP] " Luis Chamberlain via ltp
2025-03-20 12:18 ` Luis Chamberlain
2025-03-20 12:18 ` [LTP] " Luis Chamberlain via ltp
2025-03-22 23:14 ` Johannes Weiner [this message]
2025-03-22 23:14 ` Johannes Weiner
2025-03-23 1:02 ` Luis Chamberlain
2025-03-23 1:02 ` [LTP] " Luis Chamberlain via ltp
2025-03-23 7:07 ` Luis Chamberlain
2025-03-23 7:07 ` [LTP] " Luis Chamberlain via ltp
2025-03-25 6:52 ` Oliver Sang
2025-03-25 6:52 ` [LTP] " Oliver Sang
2025-03-28 1:44 ` Luis Chamberlain
2025-03-28 1:44 ` [LTP] " Luis Chamberlain via ltp
2025-03-28 4:21 ` Luis Chamberlain
2025-03-28 4:21 ` [LTP] " Luis Chamberlain via ltp
2025-03-28 9:47 ` Luis Chamberlain
2025-03-28 9:47 ` [LTP] " Luis Chamberlain via ltp
2025-03-28 19:09 ` Luis Chamberlain
2025-03-28 19:09 ` [LTP] " Luis Chamberlain via ltp
2025-03-29 0:08 ` Luis Chamberlain
2025-03-29 0:08 ` [LTP] " Luis Chamberlain via ltp
2025-03-29 1:06 ` Luis Chamberlain
2025-03-29 1:06 ` [LTP] " Luis Chamberlain via ltp
2025-03-31 7:45 ` Sebastian Andrzej Siewior
2025-03-31 7:45 ` [LTP] " Sebastian Andrzej Siewior
2025-04-08 16:43 ` Darrick J. Wong
2025-04-08 16:43 ` [LTP] " Darrick J. Wong via ltp
2025-04-08 17:06 ` Luis Chamberlain
2025-04-08 17:06 ` [LTP] " Luis Chamberlain via ltp
2025-04-08 17:24 ` Luis Chamberlain
2025-04-08 17:24 ` [LTP] " Luis Chamberlain via ltp
2025-04-08 17:48 ` Darrick J. Wong
2025-04-08 17:48 ` [LTP] " Darrick J. Wong via ltp
2025-04-08 17:51 ` Matthew Wilcox
2025-04-08 17:51 ` [LTP] " Matthew Wilcox
2025-04-08 18:02 ` Darrick J. Wong
2025-04-08 18:02 ` [LTP] " Darrick J. Wong via ltp
2025-04-08 18:51 ` Matthew Wilcox
2025-04-08 18:51 ` [LTP] " Matthew Wilcox
2025-04-08 19:13 ` Luis Chamberlain
2025-04-08 19:13 ` [LTP] " Luis Chamberlain via ltp
2025-04-08 19:13 ` Luis Chamberlain
2025-04-08 19:13 ` [LTP] " Luis Chamberlain via ltp
2025-04-08 18:06 ` Luis Chamberlain
2025-04-08 18:06 ` [LTP] " Luis Chamberlain via ltp
2025-03-20 1:24 ` Lai, Yi
2025-03-20 1:24 ` [LTP] " Lai, Yi
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=20250322231440.GA1894930@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=apopple@nvidia.com \
--cc=brauner@kernel.org \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=mcgrof@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=p.raghav@samsung.com \
--cc=willy@infradead.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.