On Fri, May 22, 2026 at 9:09 PM Matthew Wilcox <[email protected]> wrote: > > On Fri, May 22, 2026 at 10:33:05AM +0800, Barry Song (Xiaomi) wrote: > > need to touch `filemap.c` at all (probably because you are already > > maintaining `filemap.c` perfectly): > > I'm going to give you one chance to apologise for that.
Apologies if my wording caused any misunderstanding. That was not my intention at all. What I meant is that filemap.c already has a very solid design. For memory.c, I had to touch several places for the blacklist; otherwise, the kernel would hang. But for filemap.c, I basically didn't need to touch anything, and preliminary testing shows no issues after moving it from the whitelist to the blacklist. This is probably because the current filemap.c design is already handling some aspects really well. That is all I meant.
