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