Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 6 Jan 2021 08:44:30 -0800
From:   Jakub Kicinski <kuba@kernel.org>
To:     dinghao.liu@zju.edu.cn
Cc:     "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
        "Florian Fainelli" <f.fainelli@gmail.com>,
        "Andrew Lunn" <andrew@lunn.ch>, kjlu@umn.edu,
        "David S. Miller" <davem@davemloft.net>,
        "Jesse Brandeburg" <jesse.brandeburg@intel.com>,
        "Arnd Bergmann" <arnd@arndb.de>, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: Fix memleak in ethoc_probe
Message-ID: <20210106084430.291a90cc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
In-Reply-To: <328f073a.222d7.176d7572f29.Coremail.dinghao.liu@zju.edu.cn>
References: <20201223153304.GD3198262@lunn.ch>
        <20201223123218.1cf7d9cb@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
        <20201223210044.GA3253993@lunn.ch>
        <20201223131149.15fff8d2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
        <680850a9-8ab0-4672-498e-6dc740720da3@gmail.com>
        <20201223174146.37e62326@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
        <20201224180631.l4zieher54ncqvwl@chatter.i7.local>
        <fc7be127-648c-6b09-6f00-3542e0388197@gmail.com>
        <20201228202302.afkxtco27j4ahh6d@chatter.i7.local>
        <08e2b663-c144-d1bb-3f90-5e4ef240d14b@gmail.com>
        <20201228211417.m5gdnqexjzgt4ix6@chatter.i7.local>
        <20201230133618.7c242856@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
        <328f073a.222d7.176d7572f29.Coremail.dinghao.liu@zju.edu.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Wed, 6 Jan 2021 18:56:23 +0800 (GMT+08:00) dinghao.liu@zju.edu.cn
wrote:
> > I used this one for a test:
> > 
> > https://patchwork.kernel.org/project/netdevbpf/patch/1609312994-121032-1-git-send-email-abaci-bugfix@linux.alibaba.com/
> > 
> > I'm not getting the Fixes tag when I download the mbox.  
> 
> It seems that automatically generating Fixes tags is a hard work.
> Both patches and bugs could be complex. Sometimes even human cannot
> determine which commit introduced a target bug.
> 
> Is this an already implemented functionality?

I'm not sure I understand. Indeed finding the right commit to use in 
a Fixes tag is not always easy, and definitely not easy to automate.
Human validation is always required.

If we could easily automate finding the commit which introduced a
problem we wouldn't need to add the explicit tag, backporters could
just run such script locally.. That's why it's best if the author 
does the digging and provides the right tag.

The conversation with Konstantin and Florian was about automatically
picking up Fixes tags from the mailing list by the patchwork software,
when such tags are posted in reply to the original posting, just like
review tags. But the tags are still generated by humans.