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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 649F4C433EF for ; Tue, 24 May 2022 01:13:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231460AbiEXBNq (ORCPT ); Mon, 23 May 2022 21:13:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229470AbiEXBNq (ORCPT ); Mon, 23 May 2022 21:13:46 -0400 Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 52118939C7; Mon, 23 May 2022 18:13:44 -0700 (PDT) Received: from kwepemi100019.china.huawei.com (unknown [172.30.72.56]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4L6bmz63z7zDqMC; Tue, 24 May 2022 09:13:39 +0800 (CST) Received: from kwepemm600009.china.huawei.com (7.193.23.164) by kwepemi100019.china.huawei.com (7.221.188.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 24 May 2022 09:13:42 +0800 Received: from [10.174.176.73] (10.174.176.73) by kwepemm600009.china.huawei.com (7.193.23.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 24 May 2022 09:13:41 +0800 Subject: Re: [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion To: Jan Kara CC: , , , , , , Jens Axboe 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> <25f6703e-9e10-75d9-a893-6df1e6b75254@kernel.dk> <20220523152516.7sr247i3bzwhr44w@quack3.lan> From: Yu Kuai Message-ID: <13ad158e-7859-ca61-209e-7d1fe99d0bdb@huawei.com> Date: Tue, 24 May 2022 09:13:40 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20220523152516.7sr247i3bzwhr44w@quack3.lan> Content-Type: text/plain; charset="gbk"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.176.73] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To kwepemm600009.china.huawei.com (7.193.23.164) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org ÔÚ 2022/05/23 23:25, Jan Kara дµÀ: > On Mon 23-05-22 06:36:58, Jens Axboe wrote: >> 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? > > Hum, for me all emails from Huawei I've received even today fail the DKIM > check. After some more digging there is interesting inconsistency in DMARC > configuration for huawei.com domain. There is DMARC record for huawei.com > like: > > huawei.com. 600 IN TXT "v=DMARC1;p=none;rua=mailto:dmarc@edm.huawei.com" > > which means no DKIM is required but _dmarc.huawei.com has: > > _dmarc.huawei.com. 600 IN TXT "v=DMARC1;p=quarantine;ruf=mailto:dmarc@huawei.com;rua=mailto:dmarc@huawei.com" > > which says that DKIM is required. I guess this inconsistency may be the > reason why there are problems with DKIM validation for senders from > huawei.com. Yu Kuai, can you perhaps take this to your IT support to fix > this? Either make sure huawei.com emails get properly signed with DKIM or > remove the 'quarantine' record from _dmarc.huawei.com. Thanks! Of course, I'll try to contact our IT support. Thanks, Kuai > > Honza > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yu Kuai Subject: Re: [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion Date: Tue, 24 May 2022 09:13:40 +0800 Message-ID: <13ad158e-7859-ca61-209e-7d1fe99d0bdb@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> <25f6703e-9e10-75d9-a893-6df1e6b75254@kernel.dk> <20220523152516.7sr247i3bzwhr44w@quack3.lan> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20220523152516.7sr247i3bzwhr44w@quack3.lan> List-ID: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: Jan Kara 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, Jens Axboe =D4=DA 2022/05/23 23:25, Jan Kara =D0=B4=B5=C0: > On Mon 23-05-22 06:36:58, Jens Axboe wrote: >> 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 p= ass >>> (likely matching SPF records for originating mail server save the email >>> from going to spam) but messages going through mailing lists are flagge= d 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 issu= e). >>> 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? >=20 > Hum, for me all emails from Huawei I've received even today fail the DKIM > check. After some more digging there is interesting inconsistency in DMARC > configuration for huawei.com domain. There is DMARC record for huawei.com > like: >=20 > huawei.com. 600 IN TXT "v=3DDMARC1;p=3Dnone;rua=3Dmailto:dmarc@edm.huawe= i.com" >=20 > which means no DKIM is required but _dmarc.huawei.com has: >=20 > _dmarc.huawei.com. 600 IN TXT "v=3DDMARC1;p=3Dquarantine;ruf=3Dmailto:dma= rc@huawei.com;rua=3Dmailto:dmarc@huawei.com" >=20 > which says that DKIM is required. I guess this inconsistency may be the > reason why there are problems with DKIM validation for senders from > huawei.com. Yu Kuai, can you perhaps take this to your IT support to fix > this? Either make sure huawei.com emails get properly signed with DKIM or > remove the 'quarantine' record from _dmarc.huawei.com. Thanks! Of course, I'll try to contact our IT support. Thanks, Kuai >=20 > Honza >=20