mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@kernel.org>
To: Eric Van Hensbergen <ericvh@gmail.com>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Dominique Martinet <asmadeus@codewreck.org>
Cc: Simon Horman <simon.horman@corigine.com>,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Fix scan-build warnings
Date: Thu, 20 Jul 2023 21:26:36 +0000	[thread overview]
Message-ID: <168988839634.88307.10673257683695224856.b4-ty@kernel.org> (raw)
In-Reply-To: <20230427-scan-build-v2-0-bb96a6e6a33b@codewreck.org>


On Wed, 03 May 2023 16:49:24 +0900, Dominique Martinet wrote:
> I ran scan-build very crudly on our source files, and there was at least
> one real bug so we might as well run it once in a while, in which case
> we probably ought to also fix the less important things hence this
> series.
> In here the first patch is a real fix and the rest is low priority, the
> last one is arguably not an improvement and can be discussed (happy to
> just move the 0-initializations around to variable declaration which
> would also silence scan-build afaict)
> 
> [...]

Applied, thanks!

[1/5] 9p: fix ignored return value in v9fs_dir_release
      commit: eee4a119e96c2f58cfd1b6d4de42095abc5f8877
[2/5] 9p: virtio: fix unlikely null pointer deref in handle_rerror
      commit: 13ade4ac5c28e8a014fa85278f5a4270b215f906
[3/5] 9p: virtio: make sure 'offs' is initialized in zc_request
      commit: 4a73edab69d3a6623f03817fe950a2d9585f80e4
[4/5] 9p: virtio: skip incrementing unused variable
      commit: f41b402d2572e93bee85669ed05eb5e1f3725704
[5/5] 9p: remove dead stores (variable set again without being read)
      commit: cf7c33d332ab67603f159123b691c61270b14c33

Best regards,
-- 
Eric Van Hensbergen <ericvh@kernel.org>


      parent reply	other threads:[~2023-07-20 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  7:49 Dominique Martinet
2023-05-03  7:49 ` [PATCH v2 1/5] 9p: fix ignored return value in v9fs_dir_release Dominique Martinet
2023-05-03  7:49 ` [PATCH v2 2/5] 9p: virtio: fix unlikely null pointer deref in handle_rerror Dominique Martinet
2023-05-03  7:49 ` [PATCH v2 3/5] 9p: virtio: make sure 'offs' is initialized in zc_request Dominique Martinet
2023-05-03  7:49 ` [PATCH v2 4/5] 9p: virtio: skip incrementing unused variable Dominique Martinet
2023-05-03  7:49 ` [PATCH v2 5/5] 9p: remove dead stores (variable set again without being read) Dominique Martinet
2023-05-03  8:22   ` Christian Schoenebeck
2023-05-03  8:44     ` Dominique Martinet
2023-07-20 21:26 ` Eric Van Hensbergen [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=168988839634.88307.10673257683695224856.b4-ty@kernel.org \
    --to=ericvh@kernel.org \
    --cc=asmadeus@codewreck.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ericvh@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.com \
    --cc=v9fs@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®