Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 26 May 2020 12:16:04 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" 
        <longpeng2@huawei.com>
Cc:     Markus Elfring <Markus.Elfring@web.de>,
        linux-crypto@vger.kernel.org,
        virtualization@lists.linux-foundation.org,
        Gonglei <arei.gonglei@huawei.com>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        Corentin Labbe <clabbe@baylibre.com>,
        "Michael S. Tsirkin" <mst@redhat.com>,
        Jason Wang <jasowang@redhat.com>,
        "David S. Miller" <davem@davemloft.net>,
        linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [v2 2/2] crypto: virtio: Fix use-after-free in
 virtio_crypto_skcipher_finalize_req()
Message-ID: <20200526101604.GB2759907@kroah.com>
References: <20200526031956.1897-1-longpeng2@huawei.com>
 <20200526031956.1897-3-longpeng2@huawei.com>
 <0248e0f6-7648-f08d-afa2-170ad2e724b7@web.de>
 <03d3387f-c886-4fb9-e6f2-9ff8dc6bb80a@huawei.com>
 <8aab4c6b-7d41-7767-4945-e8af1dec902b@web.de>
 <321c79df-6397-bbf1-0047-b0b10e5af353@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <321c79df-6397-bbf1-0047-b0b10e5af353@huawei.com>
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

On Tue, May 26, 2020 at 05:24:03PM +0800, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote:
> 
> 
> On 2020/5/26 17:01, Markus Elfring wrote:
> >>>> … Thus release specific resources before
> >>>
> >>> Is there a need to improve also this information another bit?
> >>>
> >> You mean the last two paragraph is redundant ?
> > 
> > No.
> > 
> > I became curious if you would like to choose a more helpful information
> > according to the wording “specific resources”.
> > 
> > Regards,
> > Markus
> > 
> Hi Markus,
> 
> I respect your work, but please let us to focus on the code itself. I think
> experts in this area know what these patches want to solve after look at the code.
> 
> I hope experts in the thread could review the code when you free, thanks :)

Please note that you are responding to someone who is known to be a pain
in patch reviews and has been blocked by many kernel
developers/maintainers because they just waste people's time.

I suggest you all do the same here, and just ignore them, like I do :)

thanks,

greg k-h