diff options
| author | Jeff Layton <jlayton@primarydata.com> | 2014-10-31 08:28:29 -0400 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2014-11-06 14:47:33 -0500 |
| commit | 9af94fc4e470deab3427d07551725f0bf844ebc8 (patch) | |
| tree | 9153754b378bd383b798f256be80f6ff1ebc736e | |
| parent | eb63192bb8cc0186265aad4f79fa4fd49c22b021 (diff) | |
lockd: ratelimit "lockd: cannot monitor" messages
When lockd can't talk to a remote statd, it'll spew a warning message
to the ring buffer. If the application is really hammering on locks
however, it's possible for that message to spam the logs. Ratelimit it
to minimize the potential for harm.
Reported-by: Ian Collier <imc@cs.ox.ac.uk>
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
| -rw-r--r-- | fs/lockd/mon.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/lockd/mon.c b/fs/lockd/mon.c index 9106f42c472c..1cc6ec51e6b1 100644 --- a/fs/lockd/mon.c +++ b/fs/lockd/mon.c @@ -214,7 +214,7 @@ int nsm_monitor(const struct nlm_host *host) if (unlikely(res.status != 0)) status = -EIO; if (unlikely(status < 0)) { - printk(KERN_NOTICE "lockd: cannot monitor %s\n", nsm->sm_name); + pr_notice_ratelimited("lockd: cannot monitor %s\n", nsm->sm_name); return status; } |