• Michal Hocko's avatar
    jbd2: do not fail journal because of frozen_buffer allocation failure · 490c1b44
    Michal Hocko authored
    Journal transaction might fail prematurely because the frozen_buffer
    is allocated by GFP_NOFS request:
    [   72.440013] do_get_write_access: OOM for frozen_buffer
    [   72.440014] EXT4-fs: ext4_reserve_inode_write:4729: aborting transaction: Out of memory in __ext4_journal_get_write_access
    [   72.440015] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4735: Out of memory
    (...snipped....)
    [   72.495559] do_get_write_access: OOM for frozen_buffer
    [   72.495560] EXT4-fs: ext4_reserve_inode_write:4729: aborting transaction: Out of memory in __ext4_journal_get_write_access
    [   72.496839] do_get_write_access: OOM for frozen_buffer
    [   72.496841] EXT4-fs: ext4_reserve_inode_write:4729: aborting transaction: Out of memory in __ext4_journal_get_write_access
    [   72.505766] Aborting journal on device sda1-8.
    [   72.505851] EXT4-fs (sda1): Remounting filesystem read-only
    
    This wasn't a problem until "mm: page_alloc: do not lock up GFP_NOFS
    allocations upon OOM" because small GPF_NOFS allocations never failed.
    This allocation seems essential for the journal and GFP_NOFS is too
    restrictive to the memory allocator so let's use __GFP_NOFAIL here to
    emulate the previous behavior.
    Signed-off-by: default avatarMichal Hocko <mhocko@suse.com>
    Signed-off-by: Theodore Ts'o's avatarTheodore Ts'o <tytso@mit.edu>
    490c1b44
transaction.c 78.4 KB