On Wednesday, 30 March 2022 19:49:03 CEST Laurent Bonnaud wrote: > Thanks for looking at the problem and pointing to this commit! > > The affected system is a production system and a lot of people depend on it. > Therefore I am not comfortable to run a self-patched kernel on it, and I > would consider it a last resort.
Understandable. Usually a patch to the kernel is proposed and discussed on a mailing list. The commit didn't reference one and I also don't know on what list to search for it (maybe someone else (here) does). But it may be useful to search for it yourself and add your findings (and a link to the bug report) to that mailing list thread. They are the subject matter experts and can possibly tell you whether it is a genuine issue or a harmless warning and whether something needs to be done with it. Normally, searching for"nfsd: fix crash on COPY_NOTIFY with special stateid" (primary commit msg) would give a useful result, but _I_ could only find things for applying it to 5.15/5.16 kernels, which I think is not/less useful.
signature.asc
Description: This is a digitally signed message part.
