All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hughes <john@calvaedi.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: John Hughes <john@calva.com>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS errors
Date: Fri, 18 Nov 2011 20:17:31 +0100	[thread overview]
Message-ID: <4EC6AF4B.5050604@calvaedi.com> (raw)
In-Reply-To: <1321641010.2653.10.camel@lade.trondhjem.org>

On 11/18/2011 07:30 PM, Trond Myklebust wrote:
> On Fri, 2011-11-18 at 17:20 +0100, John Hughes wrote:
>    
>> Don't write anything to the log if a user Kerberos ticket expires or is missing,
>> these are not kernel problems.
>>
>> Signed-off-by: John Hughes<john@calva.com>
>>
>> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
>> index 39914be..18897cb 100644
>> --- a/fs/nfs/nfs4state.c
>> +++ b/fs/nfs/nfs4state.c
>> @@ -1339,14 +1339,6 @@ static void nfs4_state_start_reclaim_nograce(struct nfs_client *clp)
>>    	nfs4_state_mark_reclaim_helper(clp, nfs4_state_mark_reclaim_nograce);
>>    }
>>
>> -static void nfs4_warn_keyexpired(const char *s)
>> -{
>> -	printk_ratelimited(KERN_WARNING "Error: state manager"
>> -			" encountered RPCSEC_GSS session"
>> -			" expired against NFSv4 server %s.\n",
>> -			s);
>> -}
>>      
> NACK. This is useful.
>
>    
>> -
>>    static int nfs4_recovery_handle_error(struct nfs_client *clp, int error)
>>    {
>>    	switch (error) {
>> @@ -1378,7 +1370,6 @@ static int nfs4_recovery_handle_error(struct nfs_client *clp, int error)
>>    			return 0;
>>    		case -EKEYEXPIRED:
>>    			/* Nothing we can do */
>> -			nfs4_warn_keyexpired(clp->cl_hostname);
>>    			return 0;
>>    	}
>>    	return error;
>>      


>> @@ -1620,7 +1611,6 @@ static void nfs4_set_lease_expired(struct nfs_client *clp, int status)
>>    		break;
>>
>>    	case -EKEYEXPIRED:
>> -		nfs4_warn_keyexpired(clp->cl_hostname);
>>      
> NACK. This means that the server can't even recover it's lease. It
> shouldn't even trigger if you install a machine credential.
>    

Ok, couldn't see why there were two such warnings.  Maybe the error 
should be more alarming in this case?

>    
>> 	case -NFS4ERR_NOT_SAME: /* FixMe: implement recovery
>>    				 * in nfs4_exchange_id */
>>    	default:
>> @@ -1728,8 +1718,9 @@ static void nfs4_state_manager(struct nfs_client *clp)
>>    	} while (atomic_read(&clp->cl_count)>   1);
>>    	return;
>>    out_error:
>> -	printk(KERN_WARNING "Error: state manager failed on NFSv4 server %s"
>> -			" with error %d\n", clp->cl_hostname, -status);
>> +	if (status != -EACCESS)
>> +		printk(KERN_WARNING "Error: state manager failed on NFSv4 server %s"
>> +				" with error %d\n", clp->cl_hostname, -status);
>>      
> Obviously not even compile tested...
>    

Oh dear, my sins have found me out.  Sorry.

  reply	other threads:[~2011-11-18 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 16:20 [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS errors John Hughes
2011-11-18 16:27 ` peter.staubach
2011-11-18 16:34   ` Bryan Schumaker
2011-11-18 16:51   ` John Hughes
2011-11-18 17:50     ` peter.staubach
2011-11-18 18:30 ` Trond Myklebust
2011-11-18 19:17   ` John Hughes [this message]
     [not found] <1020589474.75.1321635498473.JavaMail.root@thunderbeast.private.linuxbox.com>
2011-11-18 16:58 ` Matt W. Benjamin

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=4EC6AF4B.5050604@calvaedi.com \
    --to=john@calvaedi.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=john@calva.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.