Feature for lockd messages

Feature for lockd messages

[Jayaram Radhakrishnan]

Hello,

I would like to know if there are any chances to include the feature like, changing the error code instead of file name. As per the below error from lockd, it means its a NFS stale and throwing error code.  

~~~
<kern.warning> kernel:lockd: unexpected unlock status: 7
~~~

Behaviuor changes 

from: 
"lockd: unexpected unlock status: <unlock status code>"

to: 
"lockd: unexpected unlock status   <full path of the affected file>"

In RHEL7 kernel as well as the current upstream kernel shows a warning if the response for an unlock NFS call to the filer isn't "NLM_GRANTED".

Unfortunately the message is meaningless without the affected file. The filename is very important to do an correlation with an application or an user.

Please extend the message by printing the affected file additional to the unexpected lockd status

Is there any plans for modifying this message behavior into filename instead of throwing error code?

In general

>> NFS knows files and nothing about sockets.
>> RPC knows sockets and nothing about files. 

Awaiting for your reply

Thanks
Jayaram

Re: Feature for lockd messages

[Jayaram Radhakrishnan]

Hello,

Could you please provide me an update about my last update, whether this feature can include or not.

Thanks
Jayaram

----- Original Message -----
From: "Jayaram Radhakrishnan" <jradhakr@redhat.com>
To: linux-nfs@vger.kernel.org
Sent: Saturday, June 4, 2016 12:31:19 AM
Subject: Feature for lockd messages

Hello,

I would like to know if there are any chances to include the feature like, changing the error code instead of file name. As per the below error from lockd, it means its a NFS stale and throwing error code.  

~~~
<kern.warning> kernel:lockd: unexpected unlock status: 7
~~~

Behaviuor changes 

from: 
"lockd: unexpected unlock status: <unlock status code>"

to: 
"lockd: unexpected unlock status   <full path of the affected file>"

In RHEL7 kernel as well as the current upstream kernel shows a warning if the response for an unlock NFS call to the filer isn't "NLM_GRANTED".

Unfortunately the message is meaningless without the affected file. The filename is very important to do an correlation with an application or an user.

Please extend the message by printing the affected file additional to the unexpected lockd status

Is there any plans for modifying this message behavior into filename instead of throwing error code?

In general

>> NFS knows files and nothing about sockets.
>> RPC knows sockets and nothing about files. 

Awaiting for your reply

Thanks
Jayaram