linux-ext4 - Re: Upgraded from 3.4 to 3.5.1 kernel: machine does not boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 11 Aug 2012 00:14:51 -0400
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	linux-kernel@...r.kernel.org, ap@...arrain.com,
	linux-ext4@...r.kernel.org
Subject: Re: Upgraded from 3.4 to 3.5.1 kernel: machine does not boot

On Fri, Aug 10, 2012 at 7:07 PM, Justin Piszcz
>
> Hi,
>
> Found the root cause, the 3.5.1 kernel cannot mount my ext4 filesystem
> (60TB).
>
> The 3.4 kernel works fine.
>
> This is proven by commenting out the filesystem in /etc/fstab with
> 3.5.1, and all is OK.
>
> --
>
> Hi again,
>
> I tested with linux-3.6-rc1:
>
> The same problem, here is what I get from the strace:
>
> irectory)
> 4434  readlink("/dev", 0x7fff3b05c670, 4096) = -1 EINVAL (Invalid argument)
> 4434  readlink("/dev/sda1", 0x7fff3b05c670, 4096) = -1 EINVAL (Invalid
> argument)
> 4434  readlink("/r1", 0x7fff3b05c670, 4096) = -1 EINVAL (Invalid argument)
> 4434  getuid()                          = 0
> 4434  geteuid()                         = 0
> 4434  getgid()                          = 0
> 4434  getegid()                         = 0
> 4434  prctl(PR_GET_DUMPABLE)            = 1
> 4434  lstat("/etc/mtab", {st_mode=S_IFLNK|0777, st_size=12, ...}) = 0
> 4434  getuid()                          = 0
> 4434  geteuid()                         = 0
> 4434  getgid()                          = 0
> 4434  getegid()                         = 0
> 4434  prctl(PR_GET_DUMPABLE)            = 1
> 4434  stat("/run", {st_mode=S_IFDIR|0755, st_size=820, ...}) = 0
> 4434  lstat("/run/mount/utab", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> 4434  open("/run/mount/utab", O_RDWR|O_CREAT, 0644) = 3
> 4434  close(3)                          = 0
> 4434  mount("/dev/sda1", "/r1", "ext4", MS_MGC_VAL|MS_NOATIME, NULL
>
> --
>
> (w/ 3.6-rc1)
>
> [   89.868843] mount           R  running task        0  4434   4433
> 0x00000009
> [   89.868847]  ffff880c246b7b68 ffffffff816c9279 ffff880c246b7aa8
> ffff880c246b7fd8
> [   89.868851]  ffff880c246b7fd8 0000000000004000 ffff88062720cdb0
> ffff880c246862d0
> [   89.868855]  00000000000116c0 ffff880623a863c0 ffff880623a863c0
> 00000000ffffffff
> [   89.868855] Call Trace:
> [   89.868858]  [<ffffffff816c9279>] ? __schedule+0x299/0x770
> [   89.868860]  [<ffffffff816c9279>] ? __schedule+0x299/0x770
> [   89.868864]  [<ffffffff8114a729>] ? ext4_get_group_desc+0x49/0xb0
> [   89.868868]  [<ffffffff81161d41>] ? ext4_calculate_overhead+0x131/0x3e0
> [   89.868871]  [<ffffffff81163a3b>] ? ext4_fill_super+0x1a4b/0x28d0
> [   89.868875]  [<ffffffff810cc301>] ? mount_bdev+0x1a1/0x1e0
> [   89.868877]  [<ffffffff81161ff0>] ? ext4_calculate_overhead+0x3e0/0x3e0
> [   89.868880]  [<ffffffff8115dd00>] ? ext4_mount+0x10/0x20
> [   89.868882]  [<ffffffff810cc55b>] ? mount_fs+0x1b/0xd0
> [   89.868885]  [<ffffffff810e57af>] ? vfs_kern_mount+0x6f/0x110
> [   89.868888]  [<ffffffff810e58cf>] ? do_kern_mount+0x4f/0x100
> [   89.868890]  [<ffffffff810e6dae>] ? do_mount+0x2fe/0x8a0
> [   89.868894]  [<ffffffff8109c0a3>] ? strndup_user+0x53/0x70
> [   89.868896]  [<ffffffff810e73e0>] ? sys_mount+0x90/0xe0
> [   89.868899]  [<ffffffff816cafa1>] ? tracesys+0xd4/0xd9
>
> Justin.
>
>
>

CC: linux-ext4

Any ideas here (kernel 3.4 and below can mount 60TB ext4 no issues)
but > 3.5.1 (did not try 3.5) cannot mount the filesystem.

Justin.

Justin.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html