On Mon, 3 Jul 2023 21:44:53 +0200 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Jul 03, 2023 at 07:27:04PM +0000, SeongJae Park wrote: [...] > > This patch is now in the mainline (e30f65c4b3d671115bf2a9d9ef142285387f2aff). > > However, this fix is not in 6.4.y yet, so the original issue is reproducible on > > 6.4.y. Could you please add this to 6.4.y? I confirmed the mainline commit > > can cleanly applied on latest 6.1.y tree, and it fixes the issue. > > As this was not specifically tagged with a "cc: stable..." marking, that > is why it was not picked up automatically. I understand that. I thought this would be merged into the mainline before v6.4 release, but I was wrong. > Also, we do not normally add patches to any stable releases until it is in a > released kernel from Linus (i.e. a -rc release), unless you have a specific > reason for it to be merged earlier. > > Should this be merged "now" into the stable trees and not wait for > 6.5-rc1? The problem is not urgent, so I can wait until 6.5-rc1. Thanks, SJ > > thanks, > > greg k-h
