All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: jhansen@vmware.com, netdev@vger.kernel.org, kuba@kernel.org,
	decui@microsoft.com, linux-kernel@vger.kernel.org,
	stefanha@redhat.com
Subject: Re: [PATCH net 0/2] vsock: fix null pointer dereference and cleanup in vsock_poll()
Date: Wed, 12 Aug 2020 09:17:42 +0200	[thread overview]
Message-ID: <20200812071742.4zoxlvu44ivunsjd@steredhat> (raw)
In-Reply-To: <20200811.102418.1200203139092745562.davem@davemloft.net>

On Tue, Aug 11, 2020 at 10:24:18AM -0700, David Miller wrote:
> From: Stefano Garzarella <sgarzare@redhat.com>
> Date: Tue, 11 Aug 2020 11:55:02 +0200
> 
> > The first patch fixes a potential null pointer dereference in vsock_poll()
> > reported by syzbot.
> > The second patch is a simple cleanup in the same block code. I put this later,
> > to make it easier to backport the first patch in the stable branches.
> 
> Please do not mix cleanups and bug fixes into the same patch series.

I did it because I was going through the same part of the code,
but I won't do it again!

> 
> net-next is closed, so you should not be submitting non-bugfixes at
> this time.
> 

I'll resend only the first patch, sorry for the noise.

Thanks,
Stefano


      reply	other threads:[~2020-08-12  7:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  9:55 [PATCH net 0/2] vsock: fix null pointer dereference and cleanup in vsock_poll() Stefano Garzarella
2020-08-11  9:55 ` [PATCH net 1/2] vsock: fix potential null pointer dereference " Stefano Garzarella
2020-08-11  9:55 ` [PATCH net 2/2] vsock: small cleanup " Stefano Garzarella
2020-08-11 17:24 ` [PATCH net 0/2] vsock: fix null pointer dereference and " David Miller
2020-08-12  7:17   ` Stefano Garzarella [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=20200812071742.4zoxlvu44ivunsjd@steredhat \
    --to=sgarzare@redhat.com \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=jhansen@vmware.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stefanha@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.