> On Sep 12, 2024, at 11:06 AM, Benjamin Coddington <bcodding@xxxxxxxxxx> wrote: > > On 12 Sep 2024, at 10:01, Chuck Lever III wrote: > >> For the NFSD and exportfs hunks: >> >> Acked-by: Chuck Lever <chuck.lever@xxxxxxxxxx <mailto:chuck.lever@xxxxxxxxxx>> >> >> "lockd: introduce safe async lock op" is in v6.10. Does this >> series need to be backported to v6.10.y ? Should the series >> have "Fixes: 2dd10de8e6bc ("lockd: introduce safe async lock >> op")" ? > > Thanks Chuck! Probably yes, if we want notifications fixed up there. It > should be sufficient to add this to the signoff area for at least the first > three (and fourth for cleanup): > > Cc: <stable@xxxxxxxxxxxxxxx> # 6.10.x 2dd10de8e6bc landed in v6.7. I suppose that since v6.10.y is likely to be closed by the time this series is applied upstream, this tag might be confusing. Thus Fixes: 2dd10de8e6bc and a plain Cc: stable should work best. Then whichever stable kernel is open when your fixes are merged upstream will automatically get fixed. None of the current LTS kernels have 2dd10de8e6bc so they aren't relevant at this point. -- Chuck Lever
