On Thu, Sep 12, 2019 at 9:24 AM James Harvey <jamespharve...@gmail.com> wrote: > > On Thu, Sep 12, 2019 at 3:51 AM Filipe Manana <fdman...@gmail.com> wrote: > > ... > > > > Until the fix gets merged to 5.2 kernels (and 5.3), I don't really > > recommend running 5.2 or 5.3. > > What is your recommendation for distributions that have been shipping > 5.2.x for quite some time, where a distro-wide downgrade to 5.1.x > isn't really an option that will be considered, especially because > many users aren't using BTRFS? Can/should your patch be backported to > 5.2.13/5.2.14?
It's meant to be backported to 5.2.x and 5.3.x (probably not to 5.3 since we are at rc8 and too close to merge window for 5.4). > Or, does it really need to be applied to 5.3rc or git > master? Or, is it possibly not the right fix for the corruption risk, > and should a flashing neon sign be given to users to just run 5.1.x > even though the distribution repos have 5.2.x? > > What is your recommendation for users who have been running 5.2.x and > running into a lot of hangs? Would you say to apply your patch to a > custom-compiled kernel, or to downgrade to 5.1.x? Sorry, I can't advise on that. That depends a lot on the distro and user needs. Going back to 5.1 might be ok for some, but not for others due to important fixes or new features/drivers in 5.2 for example. It's really up to the distro and user to choose according to their needs. -- Filipe David Manana, “Whether you think you can, or you think you can't — you're right.”
