From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB0F4C3A5A0 for ; Mon, 20 Apr 2020 08:51:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9965120A8B for ; Mon, 20 Apr 2020 08:51:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="nqmQlQgL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725971AbgDTIvO (ORCPT ); Mon, 20 Apr 2020 04:51:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53574 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725896AbgDTIvO (ORCPT ); Mon, 20 Apr 2020 04:51:14 -0400 Received: from mail-ej1-x641.google.com (mail-ej1-x641.google.com [IPv6:2a00:1450:4864:20::641]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0C3DC061A0C for ; Mon, 20 Apr 2020 01:51:12 -0700 (PDT) Received: by mail-ej1-x641.google.com with SMTP id gr25so7239823ejb.10 for ; Mon, 20 Apr 2020 01:51:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=r9N7Yr5/J8/DUekrT7B7XxT9NC2Wr8uGEwUoP3kgmRw=; b=nqmQlQgLNZ/dqEDdLsbDgNM9iS+Si14e6dZxkD3ckLfD6b08e53BWbaCg8DRsK36jW rtjENZ2QyAWOqeP221sVedpMLGe+pA0h8nbUbFdBEuGPaTaxH/rVdNo86MvFcky8SuSS dOqurmxIujk4356JLiz9jr779SbzVzuo6Pr5w2092RezhrcmIbHupJfN43UEadRV9HB3 HxbyDCBrVeADBr8O8TP6og9Cjv8FdyoHA6W+p1F4N/LjhhECRq9upjhFPNcYjBioswtg mXgQ5SfLekiLCdiBnCqob2xeGAPcW2bvLyaTgusQK0Pgsi6k8JtJc3Mts/9vbCtPlnfy nALQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=r9N7Yr5/J8/DUekrT7B7XxT9NC2Wr8uGEwUoP3kgmRw=; b=Bzchvu0MT9SPWecCFCQSmx9B7m6JUHDNYYxSECWsk2OBSpJRyfhB7xICTtBaQatdYW egazsmG+5j1UfAbBUHBkMMs7hruJ4tz6+/Zwocqog/OLkQKToPTd+OKqUQeUCcDVusfP Aeq0Vv9USeBnUPFVpix3vjYT/vWPYxZMDNQYHvFGNrG7Vh6Saqv1SJuq8CqTBJw9gwx+ JWh5zb4TJn1qT20nxCa8IrEXyhICnNxx0MySLkP96zP7AcpX1pQSiFvDnJ/e3wyAVwpP 9LpK/5okPCJ562Mzqn/QfJ85QsxL7zcVSssM/PD8m6HnDzsHDmtsGr2A8W/d3l8g/+gW xMLw== X-Gm-Message-State: AGi0PuZeUCXZxx/wyCADw4DpHelf27mBaeymnqkoCDJpsUODnlZAD+tM mCCn8NRPP0nJUa5NaSSQco0tCacZYSkATMtyKiryTQ== X-Google-Smtp-Source: APiQypKzSOGXujxPHPNnLk4x3aIZUCW9zLCys4Q7+f9rwJgclUmg33+Pdao40XsnaLQhsJsg/nBW0daa40n2m/s6KWw= X-Received: by 2002:a17:906:4903:: with SMTP id b3mr9281144ejq.80.1587372671658; Mon, 20 Apr 2020 01:51:11 -0700 (PDT) MIME-Version: 1.0 References: <20200419064825.GA32002@Debian-50-lenny-64-minimal> <0f760556-f587-fbb0-581c-d0f5a38ad23e@gmail.com> <20200420084932.xvz32vuv7uqudyih@jwilk.net> In-Reply-To: <20200420084932.xvz32vuv7uqudyih@jwilk.net> Reply-To: mtk.manpages@gmail.com From: "Michael Kerrisk (man-pages)" Date: Mon, 20 Apr 2020 10:51:00 +0200 Message-ID: Subject: Re: Errors in man pages, here: signal(7): Sentence to long To: Jakub Wilk Cc: Helge Kreutzmann , linux-man Content-Type: text/plain; charset="UTF-8" Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org On Mon, 20 Apr 2020 at 10:49, Jakub Wilk wrote: > > * Michael Kerrisk (man-pages) , 2020-04-20, 10:33: > >>"A signal may be generated (and thus pending) for a process as a whole (e." > >>"g., when sent using B(2)) or for a specific thread (e.g., certain " > >>"signals, such as B and B, generated as a consequence of " > >>"executing a specific machine-language instruction are thread directed, as " > >>"are signals targeted at a specific thread using B(3)). A " > >>"process-directed signal may be delivered to any one of the threads that does " > >>"not currently have the signal blocked. If more than one of the threads has " > >>"the signal unblocked, then the kernel chooses an arbitrary thread to which " > >>"to deliver the signal." > > > >I can't find the text referred to. I think you may be working > >with an older version of the page. Can you please check. > > In 3b9d44099f234e8e, the long sentence was replaced with this paragraph: > > "A signal may be process-directed or thread-directed. A process-directed > signal is one that is targeted at (and thus pending for) the process as > a whole. A signal may be process-directed because it was generated by > the kernel for reasons other than a hardware exception, or because it > was sent using kill(2) or sigqueue(3). A thread-directed signals is one > that is targeted at a specific thread. A signal may be thread-directed > because it was generated as a consequence of executing a specific > machine-language instruction that triggered a hardware exception (e.g., > SIGSEGV for an invalid memory access, or SIGFPE for a math error), or > because it was it was targeted at a specific thread using interfaces > such as tgkill(2) or pthread_kill(3). Thanks, Jakub. -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/