bcachefs: Do not check folio_has_private()

folio_has_private() is an attractive nuisance; filesystem authors
generally don't realise that it actually checks two flags (one of which
is never set by bcachefs).  There's no need to check the private flag at
all; for folios owned by bcachefs, we know that folio->private is NULL
when the private flag is clear and non-NULL when the private flag is set.

Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
This commit is contained in:
Matthew Wilcox (Oracle) 2024-08-20 05:10:11 +01:00 committed by Kent Overstreet
parent fdbc9c390a
commit a8cdf0ff46

View File

@ -99,9 +99,7 @@ static inline void bch2_folio_release(struct folio *folio)
static inline struct bch_folio *__bch2_folio(struct folio *folio) static inline struct bch_folio *__bch2_folio(struct folio *folio)
{ {
return folio_has_private(folio) return folio_get_private(folio);
? (struct bch_folio *) folio_get_private(folio)
: NULL;
} }
static inline struct bch_folio *bch2_folio(struct folio *folio) static inline struct bch_folio *bch2_folio(struct folio *folio)