Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp1885762ioo; Mon, 23 May 2022 05:37:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyJJpkNjAPeBWslzRP5DjsEWYZCRmh13EP9npyzG71AaUMAi5x5ii+EkcvAKlo2yYRuEUNT X-Received: by 2002:a17:90a:64c5:b0:1df:d3d6:8921 with SMTP id i5-20020a17090a64c500b001dfd3d68921mr24840358pjm.87.1653309437966; Mon, 23 May 2022 05:37:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653309437; cv=none; d=google.com; s=arc-20160816; b=bmG9q7hpxKhGR+CuWmUHPtYcOp8dOcYl4kCaLSX+j7oZ7sBa/t05nG8KVPUrP704KZ 7aNHV48Qqwv3RidMmpx5uMgdrNxVzG9CIHkMcZJuvwFLrBOwjYigFxh+nixAF53vog/0 iKufwgz0gLem6OBpkUszoXkfWpmJ1IcP0VJVlCzh8/AIQOEG3pSk+ulumv0MSxBEwHa6 Of8XcG1EQOBRb1+5oTTPNuPeyO63ULO5zfconrNp0YYF3BNEDiJ6gFxN+IFgznEmDVIy ys/rHJruNCG6uykcXIuCrSZ3Nkqa9u4RxBF5UwYorm7H+iHx0dMDGt00rk8kGnMB5i1j tdCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=L18DlrO1XtDATl5hYjR3u+d9RECswhbrU+Pb38Js3ks=; b=yyGF7b0OjQuNKzLavyH3nAYrLZBjoDJ+teUb26i6lPYq0U3Aqx0Ao7Hi5YQqQLJx5g rGQzHAqdKtR+NhDxUIapq9SMDDIl+0a9fT1f5q2c9BltdRUhZbEUgL4dZSQbDQRFgOXL qfuegsZMQE5TBROH5odsruvwd9lWuhgTUMkCuC+0lCx3x1ECfX7t1nLLKQVACnUmQo/W WksSNqbqmPR2rEf+UlWgDsFJIzLfZb0hr+jtjTZnOUUoyV6W8DUkJVD+KUTuLgPUEcev lGu7pBAI2FpV26nTL42/I1D9kwrbxnNS7Li46w2fdWS5GCfgjQrGR4yasKBNpT+Xauwb NJ/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20210112.gappssmtp.com header.s=20210112 header.b=JPrsnrHf; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id j9-20020a17090a31c900b001dc4e0e712asi12004174pjf.125.2022.05.23.05.37.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 May 2022 05:37:17 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel-dk.20210112.gappssmtp.com header.s=20210112 header.b=JPrsnrHf; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B59054504A; Mon, 23 May 2022 05:37:15 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235577AbiEWMhG (ORCPT + 99 others); Mon, 23 May 2022 08:37:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50680 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235584AbiEWMhE (ORCPT ); Mon, 23 May 2022 08:37:04 -0400 Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AF4FC4D240 for ; Mon, 23 May 2022 05:37:00 -0700 (PDT) Received: by mail-pf1-x42f.google.com with SMTP id h13so7294455pfq.5 for ; Mon, 23 May 2022 05:37:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=L18DlrO1XtDATl5hYjR3u+d9RECswhbrU+Pb38Js3ks=; b=JPrsnrHfNbDWW8uJ6kKFgzO5szuJhqQJLtNpQJjh4Q321Oq3Dg2PJSwb344Snwl0aT 6XvysX8RCg64WjCOz9hKQCekBRzdVnbvnWZBx2vl3DXsfMe6252Nh/8UA0xydXuCjfqP hqi4H3Vo0ZxSzk6qfBC+lAtshlsEebYPectaMGWkwKMpy2wxiHUF+F3GGuw9mtS5n/5C Om9NqySHY1pJx59ONDkraeOaSRduGCCNMnv/46+11kwCRSfHgKx7ht5oIBpJIa49jrqG bIPVZrHUwUVxzhPBrU+ujxfWluAP7f+yhsnBPpTNa2rq8GcRlJCw9MZ0qGRfGJ2nmu9C faUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=L18DlrO1XtDATl5hYjR3u+d9RECswhbrU+Pb38Js3ks=; b=wuT9/+ZS8s0FNEQYG2c+u40G2EjPQR8uEzL25RxIn3Me4+2tR6Fh6vm1rJQdzGhr7E 7raJakecgIt/n8Dw7bBS8lxe87uHATC83G6FYxRh5+XcEakSa0D/S2lAS5o52F6AjFN9 7k475Ln1nEOr2m0Rzp2IfM8X7OgazYONX9kWIgUallEPmy47Wv9ylaYJn3tkE0gtcSK2 NzpjekdK1u/jgC6ogQtOJ63/WpF8BgQp8FJNTITX8lGqe1uO0grWQgGP8QKjpxUV413+ pBRYfz2Q3/2ut0RG0G7HxEe1UEM9y4klEHf3kKObBFOKEoLa3OYIwXGrF2Cu/c0eezrq iXmA== X-Gm-Message-State: AOAM532MmpSrfff1yRU56hhzKBYuOpuvgxBHM7c0dETbo7ZHPcrz71U7 67AVyOZH2sTbfYQ9PpUr7cizUg== X-Received: by 2002:a63:2209:0:b0:3ab:113b:9a2b with SMTP id i9-20020a632209000000b003ab113b9a2bmr20357561pgi.235.1653309420117; Mon, 23 May 2022 05:37:00 -0700 (PDT) Received: from [192.168.1.100] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id i7-20020a1709026ac700b0015e8d4eb25asm5000680plt.164.2022.05.23.05.36.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 May 2022 05:36:59 -0700 (PDT) Message-ID: <25f6703e-9e10-75d9-a893-6df1e6b75254@kernel.dk> Date: Mon, 23 May 2022 06:36:58 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion Content-Language: en-US To: Jan Kara , "yukuai (C)" Cc: paolo.valente@linaro.org, tj@kernel.org, linux-block@vger.kernel.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, yi.zhang@huawei.com References: <20220428120837.3737765-1-yukuai3@huawei.com> <61b67d5e-829c-8130-7bda-81615d654829@huawei.com> <81411289-e13c-20f5-df63-c059babca57a@huawei.com> <55919e29-1f22-e8aa-f3d2-08c57d9e1c22@huawei.com> <20220523085902.wmxoebyq3crerecr@quack3.lan> From: Jens Axboe In-Reply-To: <20220523085902.wmxoebyq3crerecr@quack3.lan> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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-kernel@vger.kernel.org On 5/23/22 2:59 AM, Jan Kara wrote: > On Mon 23-05-22 09:10:38, yukuai (C) wrote: >> ? 2022/05/21 20:21, Jens Axboe ??: >>> On 5/21/22 1:22 AM, yukuai (C) wrote: >>>> ? 2022/05/14 17:29, yukuai (C) ??: >>>>> ? 2022/05/05 9:00, yukuai (C) ??: >>>>>> Hi, Paolo >>>>>> >>>>>> Can you take a look at this patchset? It has been quite a long time >>>>>> since we spotted this problem... >>>>>> >>>>> >>>>> friendly ping ... >>>> friendly ping ... >>> >>> I can't speak for Paolo, but I've mentioned before that the majority >>> of your messages end up in my spam. That's still the case, in fact >>> I just marked maybe 10 of them as not spam. >>> >>> You really need to get this issued sorted out, or you will continue >>> to have patches ignore because folks may simply not see them. >>> >> Hi, >> >> Thanks for your notice. >> >> Is it just me or do you see someone else's messages from *huawei.com >> end up in spam? I tried to seek help from our IT support, however, they >> didn't find anything unusual... > > So actually I have noticed that a lot of (valid) email from huawei.com (not > just you) ends up in the spam mailbox. For me direct messages usually pass > (likely matching SPF records for originating mail server save the email > from going to spam) but messages going through mailing lists are flagged as > spam because the emails are missing valid DKIM signature but huawei.com > DMARC config says there should be DKIM signature (even direct messages are > missing DKIM so this does not seem as a mailing list configuration issue). > So this seems as some misconfiguration of the mails on huawei.com side > (likely missing DKIM signing of outgoing email). SPF/DKIM was indeed a problem earlier for yukaui patches, but I don't see that anymore. Maybe it's still an issue for some emails, from them or Huawei in general? -- Jens Axboe