On 06/15/2011 06:28 PM, Jeff Layton wrote:
> On Wed, 15 Jun 2011 15:10:45 +0530
> Suresh Jayaraman <sjayaraman@xxxxxxx> wrote:
>
>> On 06/14/2011 09:30 PM, Jeff Layton wrote:
>>> On Tue, 14 Jun 2011 21:07:47 +0530
>>> Suresh Jayaraman <sjayaraman@xxxxxxx> wrote:
>>>
>>>> ... for uniformity and cleaner debug logs.
>>>>
>>>> Signed-off-by: Suresh Jayaraman <sjayaraman@xxxxxxx>
>>>> ---
>>>> fs/cifs/cache.c | 6 +++---
>>>> fs/cifs/fscache.c | 53 +++++++++++++++++++++++++----------------------------
>>>> 2 files changed, 28 insertions(+), 31 deletions(-)
>>>>
>>>> diff --git a/fs/cifs/cache.c b/fs/cifs/cache.c
>>>> index dd8584d..545509c 100644
>>>> --- a/fs/cifs/cache.c
>>>> +++ b/fs/cifs/cache.c
>>>> @@ -92,7 +92,7 @@ static uint16_t cifs_server_get_key(const void *cookie_netfs_data,
>>>> break;
>>>>
>>>> default:
>>>> - cERROR(1, "CIFS: Unknown network family '%d'", sa->sa_family);
>>>> + cERROR(1, "Unknown network family '%d'", sa->sa_family);
>>> ^^^^^^^^^
>>> Maybe this would be a good time to add in a new
>>> cFYI/cERROR "flag" for fscache and convert all of these
>>> to use it?
>>
>> Sounds like a good idea to flag fsc debug messages separately but
>> flagging errors separately would be useful?
>>
>
> Good point. Now that you mention it, I'm not sure what purpose the
> first argument to cERROR serves. Might be a good thing to do a global
> search and replace -- "s/cERROR(1, /cERROR(/" and fix up the macro.
>
>> Also, I don't understand the idea behing the "set" currently.
>>
>> we have
>>
>> #define cFYI(set, fmt, arg...) \
>> do { \
>> if (set) \
>> cifsfyi(fmt, ##arg); \
>> } while (0)
>>
>> and we call cFYI with always pass like this:
>> cFYI(1, "..");
>>
>>
>
> I think for cFYI, the idea was to have a bitmask that would allow you
> to selectively turn on certain classes of debug messages (similar to
> how NFS' dfprintk macro works). In practice though, it's rarely set to
> anything but "1". Maybe we should consider eliminating that argument as
> well?
>
Currently the separate debug flags CIFS_RC and CIFS_TIMER doesn't look
justified. It would be a good idea to have different classes of debug
messages based on the functionality. The ones that comes to my mind are
DFS, Kerberos/Spnego, FS-Cache and Xattr/ACL etc. Of course we need to
see how GetXid()/FreeXid() that spans across can be handled.
Would it be worth the exercise or we would be better of with a single
debug flag that is used always?
Ideas/Thoughts/Comments?
--
Suresh Jayaraman
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
