signal: do not print message when dealing with SIG_PIPE

Liu Hua · Liu Hua · commit 86277395cf66 · 2021-01-12T12:34:53.000+08:00
If we print message when SIG_PIPE occuers in signal handler.
There is a loop {print-&gt;SIG_PIPE-&gt;print-&gt;SIG_PIPE...}, which consume
a lot of cpu time. So do not print message in this situaiton.

Signed-off-by: Liu Hua &lt;weldonliu@tencent.com&gt;
diff --git a/cmd/containerd/command/main_unix.go b/cmd/containerd/command/main_unix.go
@@ -45,12 +45,17 @@ func handleSignals(ctx context.Context, signals chan os.Signal, serverC chan *se
 			case s := <-serverC:
 				server = s
 			case s := <-signals:
+
+				// Do not print message when deailing with SIGPIPE, which may cause
+				// nested signals and consume lots of cpu bandwidth.
+				if s == unix.SIGPIPE {
+					continue
+				}
+
 				log.G(ctx).WithField("signal", s).Debug("received signal")
 				switch s {
 				case unix.SIGUSR1:
 					dumpStacks(true)
-				case unix.SIGPIPE:
-					continue
 				default:
 					if err := notifyStopping(ctx); err != nil {
 						log.G(ctx).WithError(err).Error("notify stopping failed")
