linux-kernel - Re: [PATCH V2 1/2] fs: include device name in error messages about freezing

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 15 May 2014 08:07:36 +1000
From:	Dave Chinner <david@...morbit.com>
To:	Jan Kara <jack@...e.cz>
Cc:	Mateusz Guzik <mguzik@...hat.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, Josef Bacik <jbacik@...com>,
	Al Viro <viro@...IV.linux.org.uk>,
	Eric Sandeen <esandeen@...hat.com>
Subject: Re: [PATCH V2 1/2] fs: include device name in error messages about
 freezing

On Wed, May 14, 2014 at 01:10:48PM +0200, Jan Kara wrote:
> On Wed 14-05-14 00:04:42, Mateusz Guzik wrote:
> > While here use pr_err instead of printk(KERN_ERR...)
>   The patch looks good. Just one nit below:
> 
> > Signed-off-by: Mateusz Guzik <mguzik@...hat.com>
> > Cc: linux-fsdevel@...r.kernel.org
> > Cc: Josef Bacik <jbacik@...com>
> > Cc: Jan Kara <jack@...e.cz>
> > Cc: Al Viro <viro@...IV.linux.org.uk>
> > Cc: Eric Sandeen <esandeen@...hat.com>
> > ---
> >  fs/super.c | 6 ++----
> >  1 file changed, 2 insertions(+), 4 deletions(-)
> > 
> > diff --git a/fs/super.c b/fs/super.c
> > index 48377f7..017e10a 100644
> > --- a/fs/super.c
> > +++ b/fs/super.c
> > @@ -1323,8 +1323,7 @@ int freeze_super(struct super_block *sb)
> >  	if (sb->s_op->freeze_fs) {
> >  		ret = sb->s_op->freeze_fs(sb);
> >  		if (ret) {
> > -			printk(KERN_ERR
> > -				"VFS:Filesystem freeze failed\n");
> > +			pr_err("VFS:Filesystem %s freeze failed\n", sb->s_id);
>   I'd somewhat prefer to have the format like:
> VFS (device %s): Filesystem freeze failed\n
>
>   That should easy to programatically parse if necessary and also more
> consistent with how filesystems report errors. Now VFS itself doesn't have
> any unified style but still...

I'd suggest that filesystems should be outputting a failure message
if something goes wrong during a freeze. As you mention, they
already have their own device tailored log messages, but they also
have a much better idea of what the failure actually is. And some
filesystems will have already outputted an error if something went
wrong during the freeze....

Further, the freeze failure errno is is sent back to the caller
(i.e. userspace), so the user should already be getting a message
saying the freeze failed (just like for remount,ro). So why do we
need dmesg output for something that already has a working error
reporting path?

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/