Searched refs:s_errno (Results 1 – 8 of 8) sorted by relevance
1 journal s_errno handling
556 int s_errno = 0; in main() local565 s_errno = errno; in main()585 errno = s_errno; in main()
717 journal->j_superblock->s_errno) { in ext2fs_check_ext3_journal()720 journal->j_superblock->s_errno = 0; in ext2fs_check_ext3_journal()753 journal->j_superblock->s_errno = -EINVAL; in recover_ext3_journal()839 journal->j_superblock->s_errno = -EINVAL; in ext2fs_open_journal()
908 journal->j_superblock->s_errno) { in e2fsck_check_ext3_journal()911 journal->j_superblock->s_errno = 0; in e2fsck_check_ext3_journal()948 journal->j_superblock->s_errno = -EINVAL; in recover_ext3_journal()
447 if (jsb->s_errno != 0) in print_inline_journal_information()449 (int) ntohl(jsb->s_errno)); in print_inline_journal_information()
1055 int s_errno; in get_ctl_fd() local1061 s_errno = errno; in get_ctl_fd()1068 errno = s_errno; in get_ctl_fd()
219 __s32 s_errno; member
1431 Fixed e2fsck's handling of the journal's s_errno field. E2fsck was1432 not properly propagating the journal's s_errno field to the superblock1441 The dumpe2fs will now display the journal's s_errno field if it is