Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] cifs: trivial: cleanup fscache cFYI and cERROR messages
Date: Mon, 20 Jun 2011 11:28:21 +0530	[thread overview]
Message-ID: <4DFEE17D.50000@suse.de> (raw)
In-Reply-To: <BANLkTim-T4PKGfsX-XQT5mP1EwLLkDMDwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 06/15/2011 08:12 PM, Steve French wrote:
> 
> The idea of the 1st parameter to cerror was to allow turning off log
> spam more easily if error turned out to be expected.  Gave some
> flexibility debugging too.

Ok, but still it doesn't allow us to turn off logs in the runtime (have
to be recompiled, right?). OTOH, wouldn't be easier to convert a cERROR
to cFYI in case if we found if the error is expected or use cifswarn()
instead?


> On Jun 15, 2011 8:08 AM, "Suresh Jayaraman" <sjayaraman-l3A5Bk7waGM@public.gmane.org
> <mailto:sjayaraman-l3A5Bk7waGM@public.gmane.org>> wrote:
>> On 06/15/2011 06:28 PM, Jeff Layton wrote:
>>> On Wed, 15 Jun 2011 15:10:45 +0530
>>> Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org <mailto:sjayaraman-l3A5Bk7waGM@public.gmane.org>> wrote:
>>>
>>>> On 06/14/2011 09:30 PM, Jeff Layton wrote:
>>>>> On Tue, 14 Jun 2011 21:07:47 +0530
>>>>> Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org <mailto:sjayaraman-l3A5Bk7waGM@public.gmane.org>>
> wrote:
>>>>>
>>>>>> ... for uniformity and cleaner debug logs.
>>>>>>
>>>>>> Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org
> <mailto:sjayaraman-l3A5Bk7waGM@public.gmane.org>>
>>>>>> ---
>>>>>> 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?
>>>>
>>>


-- 
Suresh Jayaraman

  parent reply	other threads:[~2011-06-20  5:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 15:37 [PATCH] cifs: trivial: cleanup fscache cFYI and cERROR messages Suresh Jayaraman
     [not found] ` <4DF7804B.8000502-l3A5Bk7waGM@public.gmane.org>
2011-06-14 16:00   ` Jeff Layton
     [not found]     ` <20110614120048.7c04567d-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-06-15  9:40       ` Suresh Jayaraman
     [not found]         ` <4DF87E1D.70802-l3A5Bk7waGM@public.gmane.org>
2011-06-15 12:58           ` Jeff Layton
     [not found]             ` <20110615085841.633bb3c3-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-06-15 13:08               ` Suresh Jayaraman
     [not found]                 ` <4DF8AEC5.5030703-l3A5Bk7waGM@public.gmane.org>
2011-06-15 15:54                   ` Steve French
     [not found]                 ` <BANLkTim-T4PKGfsX-XQT5mP1EwLLkDMDwg@mail.gmail.com>
     [not found]                   ` <BANLkTim-T4PKGfsX-XQT5mP1EwLLkDMDwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-20  5:58                     ` Suresh Jayaraman [this message]
     [not found]                       ` <4DFEE17D.50000-l3A5Bk7waGM@public.gmane.org>
2011-06-20 16:31                         ` Steve French
2011-06-20  6:33               ` Suresh Jayaraman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DFEE17D.50000@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox