Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210829181824.534447-1-colin.king@canonical.com>
In-Reply-To: <20210829181824.534447-1-colin.king@canonical.com>
From:   Ilya Dryomov <idryomov@gmail.com>
Date:   Mon, 30 Aug 2021 12:14:20 +0200
Message-ID: <CAOi1vP8e4xXUwGe5G260rOM8xgQVi6zcLTs_6bq-ND23G6e1YQ@mail.gmail.com>
Subject: Re: [PATCH][next] ceph: Fix dereference of null pointer cf
To:     Colin King <colin.king@canonical.com>
Cc:     Jeff Layton <jlayton@kernel.org>, Xiubo Li <xiubli@redhat.com>,
        Ceph Development <ceph-devel@vger.kernel.org>,
        kernel-janitors@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sun, Aug 29, 2021 at 8:18 PM Colin King <colin.king@canonical.com> wrote:
>
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently in the case where kmem_cache_alloc fails the null pointer
> cf is dereferenced when assigning cf->is_capsnap = false. Fix this
> by adding a null pointer check and return path.
>
> Addresses-Coverity: ("Dereference null return")
> Fixes: b2f9fa1f3bd8 ("ceph: correctly handle releasing an embedded cap flush")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  fs/ceph/caps.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c
> index 39db97f149b9..eceb3ceaac48 100644
> --- a/fs/ceph/caps.c
> +++ b/fs/ceph/caps.c
> @@ -1746,6 +1746,8 @@ struct ceph_cap_flush *ceph_alloc_cap_flush(void)
>         struct ceph_cap_flush *cf;
>
>         cf = kmem_cache_alloc(ceph_cap_flush_cachep, GFP_KERNEL);
> +       if (!cf)
> +               return NULL;
>         cf->is_capsnap = false;
>         return cf;
>  }
> --
> 2.32.0
>

Hi Colin,

I guess we were too focused on the details of b2f9fa1f3bd8 to spot the
obvious...  It sat in next for a few days but apparently not enough to
be included in the Coverity run.  What is the frequency of these runs?

Applied and added an explicit stable tag since b2f9fa1f3bd8 is already
on its way to stable kernels.

Thanks,

                Ilya