mirror of
https://github.com/torvalds/linux.git
synced 2026-05-12 16:18:45 +02:00
fs/buffer: add alert in try_to_free_buffers() for folios without buffers
try_to_free_buffers() can be called on folios with no buffers attached when filemap_release_folio() is invoked on a folio belonging to a mapping with AS_RELEASE_ALWAYS set but no release_folio operation defined. In such cases, folio_needs_release() returns true because of the AS_RELEASE_ALWAYS flag, but the folio has no private buffer data. This causes try_to_free_buffers() to call drop_buffers() on a folio with no buffers, leading to a null pointer dereference. Adding a check in try_to_free_buffers() to return early if the folio has no buffers attached, with WARN_ON_ONCE() to alert about the misconfiguration. This provides defensive hardening. Signed-off-by: Deepakkumar Karn <dkarn@redhat.com> Link: https://patch.msgid.link/20251211131211.308021-1-dkarn@redhat.com Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Christian Brauner <brauner@kernel.org>
This commit is contained in:
parent
961b2ad1b4
commit
b68f91ef3b
|
|
@ -2948,6 +2948,10 @@ bool try_to_free_buffers(struct folio *folio)
|
|||
if (folio_test_writeback(folio))
|
||||
return false;
|
||||
|
||||
/* Misconfigured folio check */
|
||||
if (WARN_ON_ONCE(!folio_buffers(folio)))
|
||||
return true;
|
||||
|
||||
if (mapping == NULL) { /* can this still happen? */
|
||||
ret = drop_buffers(folio, &buffers_to_free);
|
||||
goto out;
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user