archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <>
To: "Michael Kerrisk (man-pages)" <>,
	Andy Whitcroft <>, Joe Perches <>
Cc:, Andy Lutomirski <>
Subject: [PATCH v3] New instances of ENOSYS are errors
Date: Fri, 22 Aug 2014 11:05:25 -0700	[thread overview]
Message-ID: <> (raw)

ENOSYS means that a nonexistent system call was called.  We have a
bad habit of using it for things like invalid operations on
otherwise valid syscalls.  We should avoid this in new code.

Signed-off-by: Andy Lutomirski <>

Pervasive incorrect usage of ENOSYS came up at the kernel summit ABI
review discussion.  Let's see if checkpatch can help.

I'll submit a separate patch for include/uapi/asm-generic/errno.h.

Changes from v2:
 - Reduce severity to WARN.
 - Remove unnecessary clarification.
 - Rebase onto Linus' tree instead of v3.16.

Changes from v1:
 - Moved later so that it won't warn on context lines.
 - Use $herecur.
 - Improve regex pattern.

 scripts/ | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/scripts/ b/scripts/
index 31a731e..448d075 100755
--- a/scripts/
+++ b/scripts/
@@ -3214,6 +3214,14 @@ sub process {
 			     "Prefer dev_$level(... to dev_printk(KERN_$orig, ...\n" . $herecurr);
+# ENOSYS means "bad syscall nr" and nothing else.  This will have a small
+# number of false positives, but assembly files are not checked, so at
+# least the arch entry code will not trigger this warning.
+		if ($line =~ /\bENOSYS\b/) {
+			     "ENOSYS means 'invalid syscall nr' and nothing else\n" . $herecurr);
+		}
 # function brace can't be on same line, except for #defines of do while,
 # or if closed on same line
 		if (($line=~/$Type\s*$Ident\(.*\).*\s*{/) and

             reply	other threads:[~2014-08-22 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 18:05 Andy Lutomirski [this message]
2014-08-22 18:14 ` [PATCH v3] New instances of ENOSYS are errors Joe Perches
2015-04-10 22:30   ` Andy Lutomirski
2015-04-10 22:44     ` Joe Perches
2015-04-10 22:56       ` Andy Lutomirski

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:

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

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).