On 3/30/22 12:50 PM, Song Liu wrote: > On Wed, Mar 30, 2022 at 8:58 AM Roger Heflin <rogerheflin@xxxxxxxxx> wrote: >> >> If someone sends a patch that will apply for 5.16 I can patch and compile, and run normal IO and a few raid checks tests. >> >> On Wed, Mar 30, 2022 at 10:39 AM Jens Axboe <axboe@xxxxxxxxx> wrote: >>> >>> On 3/30/22 9:17 AM, Greg Kroah-Hartman wrote: >>>> On Wed, Mar 30, 2022 at 08:49:07AM -0600, Jens Axboe wrote: >>>>> On 3/30/22 8:39 AM, Larkin Lowrey wrote: >>>>>> Thank you for investigating and resolving this issue. Your effort is >>>>>> very much appreciated. >>>>>> >>>>>> I am interested in when this patch will end up in a release. Is it >>>>>> going to make it into a 5.17.x release or will it not come until 5.18? >>>>> >>>>> The two patches are merged for 5.18, and I just checked and they apply >>>>> directly to 5.17 as well. >>>>> >>>>> Greg, care to queue up the two attached patches for 5.17-stable? >>>> >>>> Now queued up, but shouldn't they also work for 5.16? They don't apply >>>> there, but the Fixes: tag says it should. >>> >>> Yes, they should go to 5.16-stable as well. Song, do you have time to >>> port and test on 5.16? > > I ported the two patches on top of 5.16.18 (attached). They look good > in my tests. Thanks! -- Jens Axboe
