Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Dominique Martinet <asmadeus@codewreck.org>
To:     v9fs-developer@lists.sourceforge.net,
        Eric Van Hensbergen <ericvh@gmail.com>,
        Latchesar Ionkov <lucho@ionkov.net>
Cc:     linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
        Dominique Martinet <dominique.martinet@cea.fr>
Subject: [PATCH 0/4] 9p coverity fixes
Date:   Fri,  7 Sep 2018 18:50:53 +0200
Message-Id: <1536339057-21974-1-git-send-email-asmadeus@codewreck.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Dominique Martinet <dominique.martinet@cea.fr>

Since we already had one coverity fix for 9p, I figured I could request
an account and look at stuff that actually could matter.

The leak of glock.client_id wasn't found by coverity but when I was
looking at a false positive there, of the rest the rdma one is useless
but the other two are pretty important -- I will probably mark the three
useful ones to backport to stable kernels.

As usual, comments more than welcome, but I'll probably push them to
linux-next along with the other patches that need test after testing the
whole batch together next week.


Dominique Martinet (4):
  9p: acl: fix uninitialized iattr access
  9p/rdma: remove useless check in cm_event_handler
  9p: p9dirent_read: check network-provided name length
  9p locks: fix glock.client_id leak in do_lock

 fs/9p/acl.c         |  2 +-
 fs/9p/vfs_file.c    | 16 ++++++++++++++--
 net/9p/protocol.c   | 12 +++++++++---
 net/9p/trans_rdma.c |  3 +--
 4 files changed, 25 insertions(+), 8 deletions(-)

-- 
2.17.1