All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Slusarek <nslusarek@gmx.net>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	alex.popov@linux.com, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net/vmw_vsock: fix NULL pointer deref and improve locking
Date: Fri, 5 Feb 2021 10:05:07 +0100	[thread overview]
Message-ID: <trinity-bdbd75a0-df3a-4b34-a8ca-b812c83eb6ad-1612515906996@3c-app-gmx-bs43> (raw)
In-Reply-To: <20210205082038.ziaouef3v6hhmjow@steredhat>

> 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.

> Splitting also allows to put the reporter in the right issue he
> reported.

I agree it makes sense to split it. I will send separate patches in a few hours.

Norbert

      reply	other threads:[~2021-02-05  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 21:28 [PATCH] net/vmw_vsock: fix NULL pointer deref and improve locking Norbert Slusarek
2021-02-04 21:37 ` Eric Dumazet
2021-02-04 22:22   ` Norbert Slusarek
2021-02-05  8:20     ` Stefano Garzarella
2021-02-05  9:05       ` Norbert Slusarek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-bdbd75a0-df3a-4b34-a8ca-b812c83eb6ad-1612515906996@3c-app-gmx-bs43 \
    --to=nslusarek@gmx.net \
    --cc=alex.popov@linux.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.