On 01/04, Greg Kroah-Hartman wrote: > On Tue, Jan 04, 2022 at 10:56:28AM +0100, Salvatore Bonaccorso wrote: > > Hi, > > > > On Tue, Jan 04, 2022 at 05:29:30PM +0800, Chao Yu wrote: > > > On 2022/1/4 5:11, Salvatore Bonaccorso wrote: > > > > Hi, > > > > > > > > On Mon, Dec 27, 2021 at 04:31:15PM +0100, Greg Kroah-Hartman wrote: > > > > > From: Chao Yu <chao@xxxxxxxxxx> > > > > > > > > > > commit 5598b24efaf4892741c798b425d543e4bed357a1 upstream. > > > > > > I've no idea. > > > > > > I didn't add this line from v1 to v3: > > > > > > https://lore.kernel.org/lkml/20211211154059.7173-1-chao@xxxxxxxxxx/T/ > > > https://lore.kernel.org/all/20211212071923.2398-1-chao@xxxxxxxxxx/T/ > > > https://lore.kernel.org/all/20211212091630.6325-1-chao@xxxxxxxxxx/T/ > > > > > > Am I missing anything? > > > > The line is added when a commit from "upstream" is added to the stable > > series to identify the upstream commit it is taken from for > > cherry-pick (or backport). > > > > Strange so, that the fix is not in mainline actually yet. > > I thought it was about to be sent to Linus. Why has the f2fs maintainer > not sent a merge request to him to get this merged properly yet? It's very surprising that -stable can cherry-pick non-upstreamed patches based on the stable maintainer's self assumption. Please wait for being upstreamed. The patch is on track via -next. https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=5598b24efaf4892741c798b425d543e4bed357a1 > > thanks, > > greg k-h
