Searched refs:ubifs_writepage (Results 1 - 2 of 2) sorted by relevance
| /kernel/linux/linux-5.10/fs/ubifs/ |
| H A D | file.c | 27 * implement. However, this is not true for 'ubifs_writepage()', which may be
29 * background write-back, it calls 'ubifs_writepage()' with unlocked @i_mutex.
30 * At "normal" work-paths the @i_mutex is locked in 'ubifs_writepage()', e.g.
32 * 'ubifs_writepage()' we are only guaranteed that the page is locked.
973 * Some locking issues explanation. 'ubifs_writepage()' first is called with
980 * with @ui_mutex locked, because it would deadlock with 'ubifs_writepage()'.
987 * But in 'ubifs_writepage()' we have to guarantee that we do not write beyond
989 * are in the middle of 'ubifs_writepage()'? The UBIFS solution is the
1000 static int ubifs_writepage(struct page *page, struct writeback_control *wbc) in ubifs_writepage() function
1645 .writepage = ubifs_writepage,
[all...] |
| /kernel/linux/linux-6.6/fs/ubifs/ |
| H A D | file.c | 27 * implement. However, this is not true for 'ubifs_writepage()', which may be
29 * background write-back, it calls 'ubifs_writepage()' with unlocked @i_mutex.
30 * At "normal" work-paths the @i_mutex is locked in 'ubifs_writepage()', e.g.
32 * 'ubifs_writepage()' we are only guaranteed that the page is locked.
974 * Some locking issues explanation. 'ubifs_writepage()' first is called with
981 * with @ui_mutex locked, because it would deadlock with 'ubifs_writepage()'.
988 * But in 'ubifs_writepage()' we have to guarantee that we do not write beyond
990 * are in the middle of 'ubifs_writepage()'? The UBIFS solution is the
1001 static int ubifs_writepage(struct page *page, struct writeback_control *wbc) in ubifs_writepage() function
1472 * making it happened. ubifs_writepage skippe in ubifs_release_folio()
[all...] |
Completed in 8 milliseconds