From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: davem@davemloft.net,
Stephen Hemminger <stephen@networkplumber.org>,
keescook@chromium.org, dhowells@redhat.com, allen.lkml@gmail.com,
johannes.berg@intel.com, arvind.yadav.cs@gmail.com
Cc: netdev@vger.kernel.org, linux-parisc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [BUG] tulip/de4x5: a possible sleep-in-atomic bug in de4x5_interrupt
Date: Wed, 13 Dec 2017 18:13:53 +0800 [thread overview]
Message-ID: <e7489930-b0dd-ff89-a0a6-6fba5a41af5e@gmail.com> (raw)
According to drivers/net/ethernet/dec/tulip/de4x5.c, the driver may
sleep in the interrupt handler.
The function call path is:
de4x5_interrupt (interrupt handler)
synchronize_irq --> may sleep
I do not find a good way to fix it, so I only report.
This possible bug is found by my static analysis tool (DSAC) and checked
by my code review.
Thanks,
Jia-Ju Bai
reply other threads:[~2017-12-13 10:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e7489930-b0dd-ff89-a0a6-6fba5a41af5e@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=allen.lkml@gmail.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=johannes.berg@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).