On Wed, Dec 21, 2022 at 4:03 PM HAGIO KAZUHITO(萩尾 一仁) <k-hagio-ab@xxxxxxx> wrote:
On 2022/12/21 16:46, lijiang wrote:
> With the warning as below:
>
> + error(WARNING, "cannot get super_block from vfsmnt:
> 0x%lx\n", *vfsmnt);
>
> The output looks like this:
>
> crash> mount
> MOUNT SUPERBLK TYPE DEVNAME DIRNAME
> ffff97a4818a3480 ffff979500013800 rootfs none /
> ffff97e4846ca700 ffff97e484653000 sysfs sysfs /sys
> ffff97e4846cab80 ffff979500017000 proc proc /proc
> ...
> ffff97f482966e80 ffff97f4824e7800 ext4 /dev/sda1 /boot
> ...
> ffff9804839e4480 ffff9804842b5800 autofs auto.hwlnx.ah /tnet/agoura/hwnet
> ffff9804839e5680 ffff98048343c000 autofs auto.hwlnx.odc /tnet/odc/hwnet
> ffff9804839e6700 ffff9804f55a9800 autofs auto.hwlnx.mun /tnet/mun/hwnet
> ffff97a501d57a80 ffff97b484c2a800 autofs auto.hwlnx.mdc /tnet/mdc/hwnet
> mount: WARNING: cannot get super_block from vfsmnt: 0xffff97b484753420
> ...
> ffff97f514bec600 ffff9806d74ab800 mvfs /dev/mvfs /vobs/matrix_fpga
> crash>
Thanks, looks good. Let's go with this.
Thanks for the review, Kazu.
I will post v2 later with the above change.
Thanks.
Lianbo
Thanks,
Kazu
-- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/crash-utility Contribution Guidelines: https://github.com/crash-utility/crash/wiki
