summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorHugh Dickins <hughd@google.com>2021-05-05 04:32:57 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2021-05-05 21:27:20 +0300
commit786b31121a2ce4309a81a7f36d63f02ca588839e (patch)
tree06e57daf451657c0a621521303bdbce732b58969 /arch
parent8bc3c481b3d0dcef2cf8e1b7c6b780af6725f7e3 (diff)
downloadlinux-786b31121a2ce4309a81a7f36d63f02ca588839e.tar.xz
mm: remove nrexceptional from inode: remove BUG_ON
clear_inode()'s BUG_ON(!mapping_empty(&inode->i_data)) is unsafe: we know of two ways in which nodes can and do (on rare occasions) get left behind. Until those are fixed, do not BUG_ON() nor even WARN_ON(). Yes, this will then leak those nodes (or the next user of the struct inode may use them); but this has been happening for years, and the new BUG_ON(!mapping_empty) was only guilty of revealing that. A proper fix will follow, but no hurry. Link: https://lkml.kernel.org/r/alpine.LSU.2.11.2104292229380.16080@eggly.anvils Signed-off-by: Hugh Dickins <hughd@google.com> Cc: Matthew Wilcox <willy@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions