On Thu, Feb 04, 2021 at 11:22:42PM +0100, Norbert Slusarek wrote:
We request Fixes: tag for patches targeting net tree.
You could also mention the vsock_connect_timeout()
issue was found by a reviewer and give some credits ;)
You're right, Eric Dumazet spotted the locking problem in
vsock_cancel_timeout().
I am not too familiar how I should format my response to include it to the final
patch message, in case I should specifically format it, just let me know.
For now:
From Documentation/process/submitting-patches.rst:
"please use the 'Fixes:' tag with the first 12 characters of the SHA-1
ID, and the one line summary."
Fixes: 380feae0def7e6a115124a3219c3ec9b654dca32 (vsock: cancel packets when
failing to connect)
So this should be :
Fixes: 380feae0def7 ("vsock: cancel packets when failing to connect")
This maybe could apply for the locking issue, but for the NULL pointer
issue is better to refer to the commit that handled vsk->transport
pointer dynamically, that is this one:
Fixes: c0cfa2d8a788 ("vsock: add multi-transports support")
As I suggested, I think is better to split this patch in two patches
since we are fixing two issues. This should also simplify to attach the
proper 'Fixes' tag.
But if you want to send a single patch, I thing the right 'Fixes:' tag
should be the c0cfa2d8a788, since before this commit, both issues are
not really exploitable.
Reported-by: Norbert Slusarek <nslusa...@gmx.net>
Reported-by: Eric Dumazet <eric.duma...@gmail.com>
Splitting also allows to put the reporter in the right issue he
reported.
Thanks,
Stefano
