[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y4Q1dOgAY3fWuZBn@kadam>
Date: Mon, 28 Nov 2022 07:13:40 +0300
From: Dan Carpenter <error27@...il.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>,
harshit.m.mogalapalli@...il.com, Jason Wang <jasowang@...hat.com>,
Xie Yongji <xieyongji@...edance.com>,
Gautam Dawar <gautam.dawar@...inx.com>,
Maxime Coquelin <maxime.coquelin@...hat.com>,
Guanjun <guanjun@...ux.alibaba.com>,
Parav Pandit <parav@...dia.com>, Eli Cohen <elic@...dia.com>,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vduse: Fix a possible warning in vduse_create_dev()
Btw, after you add the check to vduse_validate_config() you can test
that it silences the Smatch warning by doing:
kchecker --info drivers/vdpa/vdpa_user/vduse_dev.c | tee out
~/smatch/smatch_data/db/reload_partial.sh out
kchecker drivers/vdpa/vdpa_user/vduse_dev.c
You might need to do a second --info and reload for the changes to
propagate.
regards,
dan carpenter
Powered by blists - more mailing lists