From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: kernel test robot <lkp@intel.com>, "Jan, Kara," <jack@suse.cz>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ming Lei <ming.lei@redhat.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: kernel/trace/blktrace.c:347:12: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Wed, 3 Jun 2020 20:30:31 -0600 [thread overview]
Message-ID: <1327a77d-3c9e-31d3-0b14-454803068402@kernel.dk> (raw)
In-Reply-To: <BYAPR04MB496578B5C8F42E1639F56D8A86880@BYAPR04MB4965.namprd04.prod.outlook.com>
On 6/3/20 4:34 PM, Chaitanya Kulkarni wrote:
> Jens,
>
> On 6/3/20 4:32 AM, kernel test robot wrote:
>> tree:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: d6f9469a03d832dcd17041ed67774ffb5f3e73b3
>> commit: c780e86dd48ef6467a1146cf7d0fe1e05a635039 blktrace: Protect q->blk_trace with RCU
>> date: 3 months ago
>> config: arc-randconfig-s031-20200603 (attached as .config)
>> compiler: arc-elf-gcc (GCC) 9.3.0
>> reproduce:
>> # apt-get install sparse
>> # sparse version: v0.6.1-244-g0ee050a8-dirty
>> git checkout c780e86dd48ef6467a1146cf7d0fe1e05a635039
>> # save the attached .config to linux build tree
>> make W=1 C=1 ARCH=arc CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot<lkp@intel.com>
>
> I think Jan has sent the patch to fix the rcu and I've sent out the
> series to fix the rest of the issues.
>
> Can you please let me know how can we proceed with the series so that
> we can stop these emails ?
Which patch from Jan? I saw one, and it had issues. Then there's a second
one, which is ordered behind a series that's not in my tree and wasn't
queued for 5.8. And finally, there's your series, which seemed to be a
subset of Jan's patch for patch 1.
So it's really not very clear. Maybe if folks got together and actually
put together a series to fix this it would be easier to get this done.
--
Jens Axboe
next prev parent reply other threads:[~2020-06-04 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 11:32 kernel test robot
2020-06-03 22:34 ` Chaitanya Kulkarni
2020-06-04 2:30 ` Jens Axboe [this message]
2020-06-04 7:17 ` Chaitanya Kulkarni
-- strict thread matches above, loose matches on Subject: below --
2020-05-28 7:48 kbuild test robot
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=1327a77d-3c9e-31d3-0b14-454803068402@kernel.dk \
--to=axboe@kernel.dk \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=bvanassche@acm.org \
--cc=jack@suse.cz \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
/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®