Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 889884 - gentoo-sources 6.0.17 results in kernel stack corrupted, cifs_get_inode_info
Summary: gentoo-sources 6.0.17 results in kernel stack corrupted, cifs_get_inode_info
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal major (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-05 19:22 UTC by programming
Modified: 2023-01-27 17:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
kernel panic screen (cifs_get_inode_info.jpg,172.44 KB, image/jpeg)
2023-01-05 19:22 UTC, programming 		Details
emerge --info (einfo.txt,5.92 KB, text/plain)
2023-01-05 19:24 UTC, programming 		Details
kernel config (config.txt,109.49 KB, text/plain)
2023-01-05 19:25 UTC, programming 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description programming 2023-01-05 19:22:22 UTC 
Created attachment 847550 [details]
kernel panic screen

VM running kernel 6.0.17. When I mount cifs shares, I get a kernel panic. I've attached a kernel panic screenshot.
Comment 1 programming 2023-01-05 19:24:47 UTC 
Created attachment 847552 [details]
emerge --info
Comment 2 programming 2023-01-05 19:25:07 UTC 
Created attachment 847554 [details]
kernel config
Comment 3 Mike Pagano gentoo-dev 2023-01-05 19:25:41 UTC 
This seems to be fixed in 6.1.2.  Can you test the latest 6.1.X which is 6.1.3 as of this writing.
Comment 4 programming 2023-01-06 20:55:49 UTC 
6.1.3 no longer has the issue. Thanks.
Comment 5 Mike Pagano gentoo-dev 2023-01-07 14:50:31 UTC 
(In reply to maurice.volaski from comment #4)
> 6.1.3 no longer has the issue. Thanks.

Thanks for testing.  I'm going to leave this open in case I see fixes come down to 6.0.X or 6.0.X goes EOL so anyone else having the problem see's the suggestion of moving to 6.1.

There's a lot of commits in 6.1 in this area and it's not obvious which one or combination of commits would suffice.
Comment 6 Mike Pagano gentoo-dev 2023-01-27 17:13:47 UTC 
Closing as 6.0.X is now EOL'd by upstream. This issue is fixed in >= linux 6.1.2