[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2370587.1744379306@warthog.procyon.org.uk>
Date: Fri, 11 Apr 2025 14:48:26 +0100
From: David Howells <dhowells@...hat.com>
To: Viacheslav Dubeyko <Slava.Dubeyko@....com>
Cc: dhowells@...hat.com, Alex Markuze <amarkuze@...hat.com>,
"slava@...eyko.com" <slava@...eyko.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"idryomov@...il.com" <idryomov@...il.com>,
"jlayton@...nel.org" <jlayton@...nel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"ceph-devel@...r.kernel.org" <ceph-devel@...r.kernel.org>,
"dongsheng.yang@...ystack.cn" <dongsheng.yang@...ystack.cn>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 06/35] rbd: Use ceph_databuf for rbd_obj_read_sync()
Viacheslav Dubeyko <Slava.Dubeyko@....com> wrote:
> > + dbuf = ceph_databuf_req_alloc(1, sizeof(*ondisk), GFP_KERNEL);
>
> I am slightly worried about such using of ondisk variable. We have garbage as a
> value of ondisk pointer on this step yet. And pointer dereferencing could look
> confusing here. Also, potentially, compiler and static analysis tools could
> complain. I don't see a problem here but anyway I am feeling worried. :)
It's a sizeof() construction. We do this all the time:
struct fred *p;
p = kmalloc(sizeof(*p), GFP_KERNEL);
David
Powered by blists - more mailing lists