Bug 219911
| Summary: | kernel panic when starting nfsd on OpenWrt snapshot with kernel 6.12.19 | ||
|---|---|---|---|
| Product: | File System | Reporter: | therealgraysky |
| Component: | NFSD | Assignee: | Filesystem/NFSD virtual assignee (filesystem_nfsd) |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
| Attachments: | dmesg output from intel machine | ||
Please consider adding the following to the 6.12-stable queue:
de71d4e211ed ("nfsd: fix legacy client tracking initialization")
When I apply this to my build of 6.12.19, I no longer experience the bug/nfsd appears fully functional.
Reference: https://lore.kernel.org/linux-nfs/75ec06ad-7472-4e83-a20e-28543ec2909d@oracle.com/T/#t
|
Created attachment 307885 [details] dmesg output from intel machine I am seeing a kernel panic when I start nfsd on OpenWrt running kernel 6.12.19. Using the 6.6.83 kernel is rock solid. I confirmed this on two Mini PCs, both x86/64. The first is an Intel-N150 based machine and the second is an AMD 8845H-based machine. The attachment is the output logged to dmesg upon starting nfsd and triggering the panic. This is from the Intel-based machine but a similar output is generated on the AMD one.