linux-kernel - Re: [PATCH] cifs: Rename cERROR and cifserror to cifs_vfs

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]

Message-ID: <1363174614.2031.9.camel@joe-AO722>
Date:	Wed, 13 Mar 2013 04:36:54 -0700
From:	Joe Perches <joe@...ches.com>
To:	Steve French <sfrench@...ba.org>
Cc:	linux-cifs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cifs: Rename cERROR and cifserror to cifs_vfs_err

On Tue, 2013-03-12 at 15:44 -0700, Joe Perches wrote:
> The cERROR macro is always used as cERROR(1, and cifserror
> is just a printk(KERN_ERR "CIFS VFS: ".
> 
> Make a cifs_vfs_err function that uses the vsprintf %pV
> extension to avoid duplicating the "CIFS VFS: " prefix.
> 
> Remove the cERROR macro and use cifs_vfs_err directly.

Perhaps a better idea than this patch is to
change both the cERROR and cFYI macros to
a new use of cifs_dbg(type, fmt, ...)

cERROR(set, fmt, ...)   -> cifs_dbg(VFS, fmt, ...)
cFYI(set, fmt, ...)     -> cifs_dbg(FYI, fmt, ...)

This conversion would mark both these macros
as debug stataments as they are only enabled
with CONFIG_CIFS_DEBUG.

Also CONFIG_CIFS_DEBUG2 use of DBG could also
be integrated with the same style.

cFYI(DBG2, fmt, ...)    -> cifs_dbg(NOISY, fmt, ...)

The reduced object size would still apply.

This would also enable an easier conversion to
dynamic debugging of these debug macros.

I'd prefer to move the newline from the macro
to the format as that is more consistent with
the rest of the kernel.

Thoughts?

--
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/