[LU-7748] sanity test_133f: upstream kernel timeout writing to /sys Created: 05/Feb/16 Updated: 02/Feb/19 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | staging | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
This issue was created by maloo for Andreas Dilger <andreas.dilger@intel.com> This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/2c32de50-cbab-11e5-a59a-5254006e85c2. The sub-test test_133f failed with the following error: test failed to respond and timed out This test is writing random garbage to /sys files, but it shouldn't be possible to crash the client. Info required for matching: sanity 133f |
| Comments |
| Comment by Oleg Drokin [ 05/Feb/16 ] |
|
This is a bug in the upstream kernel, I have a patch in the works. |
| Comment by Oleg Drokin [ 08/Feb/16 ] |
|
http://www.gossamer-threads.com/lists/linux/kernel/2364175 - already adopted by Greg. Now, it no longer hags, but it still fails because in fedora find fails if it gets a dir that does not exist. |
| Comment by Andreas Dilger [ 02/Feb/19 ] |
|
Oleg, I see sanity 133f hang on Ubuntu. Is there a patch we are missing in our tree? https://testing.whamcloud.com/test_sets/0bd272ea-26a4-11e9-a318-52540065bddc |