On Thu, 23 Dec 2021 19:15:09 +0100 Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> wrote: > On 2021-12-23 17:17:09 [+0000], David Howells wrote: > > Thanks, but this is gone in the upcoming fscache rewrite. I'm hoping that > > will get in the next merge window. > > Yes, I noticed that. What about current tree, v5.16-rc6 and less? > Shouldn't this be addressed? If the bug is serious enough to justify a -stable backport then yes, we should merge a fix such as this ahead of the fscache rewrite, so we have something suitable for backporting. Is the bug serious enough? Or is the bug in a not-yet-noticed state? In other words, is it possible that four years from now, someone will hit this bug in a 5.15-based kernel and will then wish we'd backported a fix? -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/linux-cachefs
