[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <355954d9.5264.176fbee1ed6.Coremail.wangyingjie55@126.com>
Date: Wed, 13 Jan 2021 21:27:35 +0800 (CST)
From: "Yingjie Wang" <wangyingjie55@....com>
To: "Jakub Kicinski" <kuba@...nel.org>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re:Re: [PATCH v2] af/rvu_cgx: Fix missing check bugs in rvu_cgx.c
Thanks for your reply. I commit this change on linux-next/stable branch, and I use "git log --pretty=fixes" command to get the Fixes tag. I want to know if I need to make a change on any other branch and commit it?
At 2021-01-13 10:13:28, "Jakub Kicinski" <kuba@...nel.org> wrote:
>On Mon, 11 Jan 2021 18:09:49 -0800 wangyingjie55@....com wrote:
>> From: Yingjie Wang <wangyingjie55@....com>
>>
>> In rvu_mbox_handler_cgx_mac_addr_get()
>> and rvu_mbox_handler_cgx_mac_addr_set(),
>> the msg is expected only from PFs that are mapped to CGX LMACs.
>> It should be checked before mapping,
>> so we add the is_cgx_config_permitted() in the functions.
>>
>> Fixes: 289e20bc1ab5 ("af/rvu_cgx: Fix missing check bugs in rvu_cgx.c")
>> Signed-off-by: Yingjie Wang <wangyingjie55@....com>
>
>
>Fixes tag: Fixes: 289e20bc1ab5 ("af/rvu_cgx: Fix missing check bugs in rvu_cgx.c")
>Has these problem(s):
> - Target SHA1 does not exist
>
>Where is that commit from? You're not referring to this commit itself
>in your tree? The subject is suspiciously similar :S
Powered by blists - more mailing lists