17aa40
From bfa090ce83f2b0734c526a4426a20f6f0f943aa0 Mon Sep 17 00:00:00 2001
17aa40
From: Lennart Poettering <lennart@poettering.net>
17aa40
Date: Wed, 10 Apr 2019 19:36:40 +0200
17aa40
Subject: [PATCH] lgtm: complain about accept() [people should use accept4()
17aa40
 instead, due to O_CLOEXEC]
17aa40
17aa40
(cherry picked from commit e2d0fa6feb3797246c8bfda3db45a2f5b62e1b5b)
17aa40
17aa40
Related: #2017033
17aa40
---
17aa40
 .lgtm/cpp-queries/PotentiallyDangerousFunction.ql | 3 +++
17aa40
 1 file changed, 3 insertions(+)
17aa40
17aa40
diff --git a/.lgtm/cpp-queries/PotentiallyDangerousFunction.ql b/.lgtm/cpp-queries/PotentiallyDangerousFunction.ql
17aa40
index 96712cf1c6..865330430d 100644
17aa40
--- a/.lgtm/cpp-queries/PotentiallyDangerousFunction.ql
17aa40
+++ b/.lgtm/cpp-queries/PotentiallyDangerousFunction.ql
17aa40
@@ -41,6 +41,9 @@ predicate potentiallyDangerousFunction(Function f, string message) {
17aa40
   ) or (
17aa40
     f.getQualifiedName() = "strerror" and
17aa40
     message = "Call to strerror() is not thread-safe. Use strerror_r() or printf()'s %m format string instead."
17aa40
+  ) or (
17aa40
+    f.getQualifiedName() = "accept" and
17aa40
+    message = "Call to accept() is not O_CLOEXEC-safe. Use accept4() instead."
17aa40
   )
17aa40
 }
17aa40