Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp8964422rwr; Thu, 11 May 2023 08:18:06 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7xXnTGBkY2Y1/6ZJwgq1sDq4EkMDhdvPJHbssw1MdeNDQDahI8cJEcem6OaWZ5aVN3z/t5 X-Received: by 2002:a17:90b:ecd:b0:252:a7b3:c24c with SMTP id gz13-20020a17090b0ecd00b00252a7b3c24cmr314959pjb.20.1683818286241; Thu, 11 May 2023 08:18:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683818286; cv=none; d=google.com; s=arc-20160816; b=PKFRqajJPBxJ3hyyLkxhD5YeEIsewrfD8b6jLZ9tZDUgxCM5HKosMaD3aCVDXvVHc3 gtIYJto8ZuIX2MJLrZ/izvhczOarI8YuM3jJ77aI/2z0qf4+WSAXPDl0oKIeLzHwCl8C gJbKJ06btcI1I5GGrNqEEjdtQpekDXcmaVn9Pv6ni2VFLCmeQRVYUY1y0zC0qppCo4au O4iExdWMy3XL5ck19jN+nCooVMtSez42fShcminaKxlFLX62HGSP4B1qLH/3MQmNSe3s QXQFrOVeaiIVd4iIX4b2Y0rnVcv9qkn1r6AEbgl2KZp0xIMeQPV5xC2e6TGjNDO98NQd anOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=UO/D1O1faXkPbB/YMuRgtGeWgLWeF6P7NdI3zyMJJGM=; b=bbuHvXZomhVtqPt7KhFg0MF4nJnaPKvuHld2CSFTHhzQAGB/HMX3ddSMAGztzrjxdN jORJt9k6GUo5WZzMvAvXfvJlFmSXMlYC/dEnqfGNMzE4fN8C+ioz6ce2ediqdKZyaMqp st3yrn8QoMzgHz50guxcWM0jttTXEgpJMs7UMIDIe7WAJDfufDeRSL5ajRin0l5z65oe dMqw9e5Dpr/b6lb5U5ei+gdvPp0Y5euGJ6s270kpJRddLeuLwwaRIEMmCKAuZV1lt6Ud HzoddPHtFKof++7JORDm2mVuedQb058UlkcppdJvKnwRJ40mOiZEq+ur8xkXSCB7aWhA jPJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=XhaSE+lW; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id pf11-20020a17090b1d8b00b0024e0254d807si22641120pjb.143.2023.05.11.08.17.46; Thu, 11 May 2023 08:18:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=XhaSE+lW; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237978AbjEKPLs (ORCPT + 99 others); Thu, 11 May 2023 11:11:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38722 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238220AbjEKPLr (ORCPT ); Thu, 11 May 2023 11:11:47 -0400 Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 96A9010A for ; Thu, 11 May 2023 08:11:45 -0700 (PDT) Received: by mail-il1-x130.google.com with SMTP id e9e14a558f8ab-33164ec77ccso538935ab.0 for ; Thu, 11 May 2023 08:11:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1683817905; x=1686409905; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=UO/D1O1faXkPbB/YMuRgtGeWgLWeF6P7NdI3zyMJJGM=; b=XhaSE+lWv6BPmJa70xMSgNcyarLI2AGHV1jYvcKnNz9PIvlzWF7TJAO6RRSEauBG5C mHocJ9FkazVh/RC8YlLltsRIF6E/HFUMEVqcZC0nz4BzWa1aOPqJmP2MEFVvJvfREnoH 3CQV1APFAyKXLKEYK2ES1XdEvZgjI3XhPWXlZgzxzXgECE+pN/QzkIzKRfw7Di7tNlCb JJz00jTvXfTeUqTQZmylsf/59UL05Z3UqfgdFQJorm2my9o8VBk3CrBRBUNycCpHwnlH yW4lmJHI1iuf9WdKDiAfa5NvEfJ9LC6cQ6CAOwh37aai0IgmqfLLDFXZlhhcYHkPWNhm rHMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683817905; x=1686409905; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=UO/D1O1faXkPbB/YMuRgtGeWgLWeF6P7NdI3zyMJJGM=; b=fqnOzCu/jy974T1uAoUieZHsTAdIwfpp+9i5JWddjTUAqtgnlXuq4hleNzvuAkTQy+ kmcYBwyhuP0v9hL237TCp/TGIPxiPkj4USAdlrFdGI0/kuxjvSkli7rKRFxYcIuBcK+c MvB7ZLDevQQMBUUd3tPVleK3pOT0bWsbOBEzpCQLCQBY6msgQpBc1AXgxtV3Zz0RqCA1 2n/sMxw8GHoXXUQWpR32a3OaryhFuL0JWdvl9L773bkvEcnTv7zYqyxkTbvfd7JFYDVL LZMr4J9G/dOOUeis6rXV3V0YzpX5NHWLeOqrAEo+vmLwoQtvRvvEqodterWlGlOo3Tgq lSOA== X-Gm-Message-State: AC+VfDzph5Ox9oEtUpYWm1LqZmyi47gAUaP2atpRXXPpgX89s3HqZW/5 g0EjFGeeAhwgI2BsMZ74DRe4+JpSb+pToEojiLA/pQ== X-Received: by 2002:a05:6e02:1c4a:b0:335:5940:5ca6 with SMTP id d10-20020a056e021c4a00b0033559405ca6mr276338ilg.13.1683817904890; Thu, 11 May 2023 08:11:44 -0700 (PDT) MIME-Version: 1.0 References: <00000000000050327205f9d993b2@google.com> <41ddc20d-8675-d8bc-18c6-2a26f0d6b104@linaro.org> <20230505040134.GA883142@mit.edu> In-Reply-To: From: Aleksandr Nogikh Date: Thu, 11 May 2023 17:11:33 +0200 Message-ID: Subject: Re: [PATCH] hwrng: virtio - Fix race on data_avail and actual data To: "Theodore Ts'o" Cc: Dmitry Vyukov , Tudor Ambarus , Herbert Xu , syzbot , davem@davemloft.net, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, olivia@selenic.com, syzkaller-bugs@googlegroups.com, Jason Wang , "Michael S. Tsirkin" , Laurent Vivier , Rusty Russell , syzkaller Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi Ted, On Mon, May 8, 2023 at 11:06=E2=80=AFAM Theodore Ts'o wrote= : > > On Mon, May 08, 2023 at 07:33:39AM +0200, Dmitry Vyukov wrote: > > A link like this may work for syzbot instead of the Reported-by tag > > (may work out of the box, but need to double check if we start to use > > this): > > > > Link: https://syzkaller.appspot.com/bug?extid=3D726dc8c62c3536431ceb > > > > Or similarly this may work: > > > > Reported-by: https://syzkaller.appspot.com/bug?extid=3D726dc8c62c353643= 1ceb > > I think the parsing code mostly looks for the hash. > > > > This was proposed, but people said that they need links to lore and > > don't want links to syzkaller dashboard. So this was rejected at the > > time. > > I think the "Reported-by: " line should continue to contain an e-mail, > since that way "git send-email" will automatically include a Cc: to > the mailing list address so that the syzbot page for the report will > contain a link to the page. > > What *would* be useful would be a search box on the top-level > https://syzkaller.appspot.com where you could either enter an e-mail > address like: > > syzbot+726dc8c62c3536431ceb@syzkaller.appspotmail.com > > or the syzbot report title e.g.: > > KCSAN: data-race in random_recv_done / virtio_read (3) > > or just a function name: > > sys_quotactl_fd > > The search box could just push the text to google.com with > "site:syzkaller.appspot.com", which should mostly do the right thing. Thanks for the suggestion! I've filed https://github.com/google/syzkaller/issues/3892 > > Also, it would also be nice if all of the URL links on the > syzkaller.appspot.com used the id form of the URL. That is, to use > > https://syzkaller.appspot.com/bug?extid=3D6c73bd34311ee489dbf5 > > instead of: > > https://syzkaller.appspot.com/bug?id=3D32c54626e170a6b327ca2c8ae4c1aea666= a8c20b > > The extid form of the URL is shorter, and having a consistency so that > the primary URL is the extid would reduce confusion. The web site > will need to continue to support the id form of the URL since there > are quite a few of those URL's in mailing list archives and git commit > descriptions. > > It also would be useful if there was a way to translate from the extid > hash to the id hash, so that it's possible to search for the extid and > id forms of the URL --- since the URL aliasing means that for a > developer trying to do code archeology and web searches, that we need > to search for both URL forms for past syzbot reports. (But if we can > avoid the aliasing confusion moving forward, that would be **really** > nice.) I've just sent a PR [1] so that URLs from bug lists on the web dashboard use the extid=3D instead of the id=3D parameter. Hopefully this will reduce the confusion. [1] https://github.com/google/syzkaller/pull/3891 --=20 Aleksandr > > Cheers, > > - Ted