diff options
| author | Andi Kleen <ak@linux.intel.com> | 2022-11-18 15:43:57 -0800 |
|---|---|---|
| committer | Jeff Layton <jlayton@kernel.org> | 2022-11-30 05:08:10 -0500 |
| commit | f2f2494c8aa3cc317572c4674ef256005ebc092b (patch) | |
| tree | aec5b73f0ad8f703cbcb4a1c70a59b14101872f6 /fs/locks.c | |
| parent | 77c67530e1f95ac25c7075635f32f04367380894 (diff) | |
Add process name and pid to locks warning
It's fairly useless to complain about using an obsolete feature without
telling the user which process used it. My Fedora desktop randomly drops
this message, but I would really need this patch to figure out what
triggers is.
[ jlayton: print pid as well as process name ]
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'fs/locks.c')
| -rw-r--r-- | fs/locks.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/locks.c b/fs/locks.c index 8e48b3d5afe3..8f01bee17715 100644 --- a/fs/locks.c +++ b/fs/locks.c @@ -2096,7 +2096,7 @@ SYSCALL_DEFINE2(flock, unsigned int, fd, unsigned int, cmd) * throw a warning to let people know that they don't actually work. */ if (cmd & LOCK_MAND) { - pr_warn_once("Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.\n"); + pr_warn_once("%s(%d): Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.\n", current->comm, current->pid); return 0; } |