[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191112120818.GA8858@lst.de>
Date: Tue, 12 Nov 2019 13:08:18 +0100
From: Christoph Hellwig <hch@....de>
To: Jan Stancek <jstancek@...hat.com>
Cc: Ian Kent <raven@...maw.net>,
kernel test robot <rong.a.chen@...el.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
LKML <linux-kernel@...r.kernel.org>, linux-xfs@...r.kernel.org,
lkp@...ts.01.org, Christoph Hellwig <hch@....de>,
ltp@...ts.linux.it
Subject: Re: [LTP] [xfs] 73e5fff98b: kmsg.dev/zero:Can't_open_blockdev
On Tue, Nov 12, 2019 at 07:02:23AM -0500, Jan Stancek wrote:
> https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/fs/fs_fill/fs_fill.c
>
> Setup of that test is trying different file system types, and it looks
> at errno code of "mount -t $fs /dev/zero /mnt/$fs".
>
> Test still PASSes. This report appears to be only about extra message in dmesg,
> which wasn't there before:
>
> # mount -t xfs /dev/zero /mnt/xfs
> # dmesg -c
> [ 897.177168] /dev/zero: Can't open blockdev
That message comes from fs/super.c:get_tree_bdev(), a common library
used by all block device based file systems using the new mount API.
It doesn't seem all that useful to me, but it is something we'll
need to discuss with David and Al, not the XFS maintainers.
Powered by blists - more mailing lists