From: "Theodore Tso" <tytso@mit.edu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mark Brown <broonie@kernel.org>, Jan Kara <jack@suse.cz>,
Francesco Dolcini <francesco@dolcini.it>,
Brian Foster <bfoster@redhat.com>,
Yongjian Sun <sunyongjian1@huawei.com>,
Matthew Wilcox <willy@infradead.org>,
Gou Hao <gouhao@uniontech.com>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Zhang Yi <yi.zhang@huawei.com>, Baokun Li <libaokun1@huawei.com>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.1 000/481] 6.1.167-rc1 review
Date: Wed, 25 Mar 2026 08:11:10 -0500 [thread overview]
Message-ID: <20260325131110.GC2107@macsyma.local> (raw)
In-Reply-To: <2026032535-casino-cable-e039@gregkh>
On Wed, Mar 25, 2026 at 10:49:43AM +0100, Greg Kroah-Hartman wrote:
> > I don't have time to investigate further, but Greg, if you could drop
> > these three patches, that should address this issue.
>
> All now dropped, thanks!
Thanks! Just as another heads up, I decided to run a full regression
test suite on 6.1.167-rc1 with those three reverts, and there ar still
some crashes with generic/051 and ext4/039:
ext4/4k: 711 tests, 1 errors, 83 skipped, 4645 seconds
Errors: generic/051
ext4/1k: 636 tests, 7 failures, 1 errors, 78 skipped, 5612 seconds
Errors: ext4/039
ext4/encrypt: 679 tests, 1 errors, 215 skipped, 3343 seconds
Errors: generic/051
ext4/ext3conv: 706 tests, 1 errors, 85 skipped, 5282 seconds
Errors: generic/051
ext4/adv: 713 tests, 13 failures, 1 errors, 91 skipped, 4944 seconds
Errors: generic/051
ext4/dioread_nolock: 711 tests, 1 failures, 1 errors, 83 skipped, 5518 seconds
Errors: generic/051
ext4/data_journal: 635 tests, 6 failures, 1 errors, 151 skipped, 4105 seconds
Errors: ext4/039
ext4/bigalloc_4k: 604 tests, 1 errors, 79 skipped, 4876 seconds
Errors: ext4/039
ext4/bigalloc_1k: 682 tests, 6 failures, 1 errors, 106 skipped, 5454 seconds
Errors: generic/051
ext4/dax: 705 tests, 10 failures, 1 errors, 207 skipped, 3249 seconds
Errors: generic/051
I'll start trying to bisect this as I have time today. Are you going
to put out another rc and restart the 48 hour testing clock?
- Ted
P.S. A sample crash:
BUG: unable to handle page fault for address: ffffffffffffffec
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 300d067 P4D 300d067 PUD 300f067 PMD 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 1 PID: 326494 Comm: fsstress Not tainted 6.1.167-rc1-xfstests-00485-gb12a69d9770b #50
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:ext4_ext_map_blocks+0x190/0xa50
Code: 48 89 ef 48 8d 54 24 60 e8 9d 71 ff ff 85 c0 41 89 c3 89 44 24 28 0f 84 51 02 00 00 48 8b 44 24 30 48 85 c0 0f 84 72 04 00 00 <44> 0f b7 78 08 48 89 1c 24 49 89 c5 31 db 49 89 c6 49 8b 7d 28 48
RSP: 0018:ffffd16f045b7968 EFLAGS: 00010286
RAX: ffffffffffffffe4 RBX: ffffd16f045b7ac8 RCX: 00000000000005ea
RDX: ffffffff9b2407d0 RSI: 0000000000000000 RDI: ffff8e671ae1c410
RBP: ffff8e66f8b72688 R08: ffffffff9b4a7024 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8e676f1e2ff0 R12: 0000000000000001
R13: 00000000000f6422 R14: ffff8e66c244c000 R15: ffff8e66c0fd3080
FS: 00007f67932c6740(0000) GS:ffff8e6799500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffec CR3: 000000013d210000 CR4: 0000000000350ee0
Call Trace:
<TASK>
ext4_map_blocks+0x237/0x690
ext4_iomap_begin+0x2af/0x320
iomap_iter+0xb1/0x130
__iomap_dio_rw+0x21e/0x650
? aio_fsync_work+0xf0/0xf0
iomap_dio_rw+0xe/0x30
ext4_dio_write_iter+0x612/0x6f0
? filename_lookup+0xde/0x1a0
? mntput_no_expire+0x4e/0x260
aio_write+0x159/0x2a0
? fget+0x7a/0xa0
? io_submit_one+0xef/0x3b0
io_submit_one+0xef/0x3b0
__x64_sys_io_submit+0xac/0x1d0
do_syscall_64+0x35/0x80
entry_SYSCALL_64_after_hwframe+0x6e/0xd8
RIP: 0033:0x7f67933d7779
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 67 76 0d 00 f7 d8 64 89 01 48
RSP: 002b:00007fff8d7191f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d1
RAX: ffffffffffffffda RBX: 00007f67932c66c8 RCX: 00007f67933d7779
RDX: 00007fff8d719248 RSI: 0000000000000001 RDI: 00007f67934c6000
RBP: 00007f67934c6000 R08: 0000000000000001 R09: 0000000000007c38
R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000019 R14: 00007fff8d719248 R15: 0000000000019000
</TASK>
CR2: ffffffffffffffec
---[ end trace 0000000000000000 ]---
next prev parent reply other threads:[~2026-03-25 13:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:39 [PATCH 6.1 000/481] 6.1.167-rc1 review Greg Kroah-Hartman
2026-03-23 15:20 ` Brett A C Sheffield
2026-03-23 16:39 ` Peter Schneider
2026-03-23 19:16 ` Florian Fainelli
2026-03-23 19:18 ` Pavel Machek
2026-03-23 22:14 ` Shuah Khan
2026-03-24 0:31 ` Slade Watkins
2026-03-24 7:34 ` Francesco Dolcini
2026-03-24 11:57 ` Greg Kroah-Hartman
2026-03-24 13:40 ` Jan Kara
2026-03-24 15:36 ` Mark Brown
2026-03-25 3:59 ` Theodore Tso
2026-03-25 9:49 ` Greg Kroah-Hartman
2026-03-25 13:11 ` Theodore Tso [this message]
2026-03-25 13:31 ` Greg Kroah-Hartman
2026-04-07 3:37 ` Theodore Tso
2026-03-25 9:03 ` Sun Yongjian
2026-03-25 13:34 ` Theodore Tso
2026-03-26 3:01 ` Sun Yongjian
2026-03-24 8:41 ` Ron Economos
2026-03-24 9:03 ` Jon Hunter
2026-03-24 15:38 ` Mark Brown
2026-03-24 23:53 ` Miguel Ojeda
2026-03-30 8:32 ` Guenter Roeck
2026-03-30 9:20 ` Greg Kroah-Hartman
2026-03-30 15:20 ` Guenter Roeck
2026-03-30 9:12 ` Guenter Roeck
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=20260325131110.GC2107@macsyma.local \
--to=tytso@mit.edu \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=francesco@dolcini.it \
--cc=gouhao@uniontech.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jack@suse.cz \
--cc=jonathanh@nvidia.com \
--cc=libaokun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shikemeng@huaweicloud.com \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=sunyongjian1@huawei.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
--cc=yi.zhang@huawei.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