Add linux 5.10.22 #2047
Merged
Add linux 5.10.22 #2047
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create bee file with
cp linux-5.4.97-368.bee linux-5.10.21-373.bee
Update patch URL for 5.10.21 kernel.
Remove patch, which is no longer required for kernel 5.10.21.
Remove patch, which is no longer required for kernel 5.10.21.
Remove patch, which is no longer required for kernel 5.10.21.
Remove patch, which is no longer quired for kernel 5.1.21.
Update patch URL for 5.10.21 kernel.
When a mdraid recovery/check is paused by writing "idle" to sync_action, sometimes the system deadlocks [1]. The latest fix proposed by the maintainer is not valid [2]. Use the fix we proposed ourself [3] until upstream comes up with something better. [1]: https://lore.kernel.org/linux-raid/5ed54ffc-ce82-bf66-4eff-390cb23bc1ac@molgen.mpg.de/T/#m28b00fdf4749f55c83282b20485c554ec199a108 [2]: https://lore.kernel.org/linux-raid/7fdb9726-4b1f-e04c-2451-f47139ddc05b@cloud.ionos.com/T/#m78c755f6b43a9c06d2c85b9d4e49c19657ddb155 [3]: https://lore.kernel.org/linux-raid/5ed54ffc-ce82-bf66-4eff-390cb23bc1ac@molgen.mpg.de/T/#m8a1d4c25781b8c3032ef38e3ffec425714515a16
Add patch, which should avoid spurious xfs deadlocks xfs: Wake CIL push waiters more reliably Threads, which committed items to the CIL, wait in the xc_push_wait waitqueue when used_space in the push context goes over a limit. These threads need to be woken when the CIL is pushed. The CIL push worker tries to avoid the overhead of calling wake_all() when there are no waiters waiting. It does so by checking the same condition which caused the waits to happen. This, however, is unreliable, because ctx->space_used can actually decrease when items are recommitted. If the value goes below the limit while some threads are already waiting but before the push worker gets to it, these threads are not woken. Always wake all CIL push waiters. Test with waitqueue_active() as an optimization. This is possible, because we hold the xc_push_lock spinlock, which prevents additions to the waitqueue.
smartpqi: Set host_tagset = 1 Set host_tagset = 1 as suggested in [1] to avoid the problem of controller command overrun under certain load conditions. [1] https://lore.kernel.org/linux-scsi/20210120184548.20219-1-mwilck@suse.com/T/#u
donald
force-pushed
the
add-linux-5.10.21
branch
from
8009078
to
4438866
Compare
Create bee file with
cp nvidia_linux-5.4.97-368-460.39-0.bee nvidia_linux-5.10.22-373-460.39-0.bee
|
Tests are running on deadbird, claptrap, done, gone and theinternet. |
|
So I guess it's OK if I start a mdcheck on gone & done now...
*Dodge*, no thumbs-up, and hoping that tests will succeed.
|
|
Yes, go ahead. But if you want to test the change, you'd need to pause and restart it. I've run though the high I/O load test on deadbird ( smartpqi + xfs). I'll start another test on it to pause and continue the mdcheck in a loop. If that is okay now, we need to decide, how we continue. We'd like to restart the regular mdcheck on all nodes, I assume. |
|
Fine! But, I guess you know that I won't :)
As for the check-revival. What about checking at 6:01 if the
stripe-header condition looks 'strange', and then issue an 'active' to
the RAID in question. This would avoid fiddling with mdcheck, and should
help in most of the scenarios met so far.
|
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.