From: Dan Carpenter <error27@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Julia Lawall <julia.lawall@inria.fr>,
Luis Chamberlain <mcgrof@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Hongchen Zhang <zhanghongchen@loongson.cn>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"Christian Brauner (Microsoft)" <brauner@kernel.org>,
David Howells <dhowells@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
maobibo <maobibo@loongson.cn>,
Matthew Wilcox <willy@infradead.org>,
Sedat Dilek <sedat.dilek@gmail.com>
Subject: xen: sleeping in atomic warnings
Date: Tue, 7 Feb 2023 16:37:38 +0300 [thread overview]
Message-ID: <Y+JUIl64UDmdkboh@kadam> (raw)
In-Reply-To: <Y+EupX1jX1c5BAHv@kadam>
These are static checker warnings from Smatch. The line numbers are
based on next-20230207. To reproduce these warnings then you need to
have the latest Smatch from git and you need to rebuild the cross
function probably four times. I have reviewed most of these and they
all seem valid to me. I remember I reported some a while back but never
heard back. https://lore.kernel.org/all/20210802144037.GA29540@kili/
regards,
dan carpenter
arch/x86/xen/p2m.c:189 alloc_p2m_page() warn: sleeping in atomic context
xen_create_contiguous_region() <- disables preempt
xen_destroy_contiguous_region() <- disables preempt
-> xen_remap_exchanged_ptes()
-> set_phys_to_machine()
-> xen_alloc_p2m_entry()
-> alloc_p2m_pmd()
xen_alloc_p2m_entry() <duplicate>
-> alloc_p2m_page()
drivers/xen/events/events_base.c:1213 bind_evtchn_to_irq_chip() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> bind_evtchn_to_irqhandler()
-> bind_evtchn_to_irqhandler_chip()
-> bind_evtchn_to_irq_chip()
drivers/net/ethernet/qlogic/netxen/netxen_nic_hw.c:303 netxen_pcie_sem_lock() warn: sleeping in atomic context
netxen_nic_hw_write_wx_2M() <- disables preempt
netxen_nic_hw_read_wx_2M() <- disables preempt
-> netxen_pcie_sem_lock()
drivers/xen/xen-pciback/pci_stub.c:110 pcistub_device_release() warn: sleeping in atomic context
pcistub_get_pci_dev_by_slot() <- disables preempt
pcistub_get_pci_dev() <- disables preempt
-> pcistub_device_get_pci_dev()
-> pcistub_device_put()
-> pcistub_device_release()
drivers/xen/xen-scsiback.c:1016 __scsiback_del_translation_entry() warn: sleeping in atomic context
scsiback_del_translation_entry() <- disables preempt
scsiback_release_translation_entry() <- disables preempt
-> __scsiback_del_translation_entry()
drivers/xen/xen-scsiback.c:276 scsiback_free_translation_entry() warn: sleeping in atomic context
scsiback_del_translation_entry() <- disables preempt
scsiback_release_translation_entry() <- disables preempt
-> __scsiback_del_translation_entry()
-> scsiback_free_translation_entry()
drivers/xen/events/events_base.c:1427 unbind_from_irq() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> bind_evtchn_to_irqhandler()
-> bind_evtchn_to_irqhandler_chip()
-> unbind_from_irq()
drivers/xen/xenbus/xenbus_client.c:473 xenbus_alloc_evtchn() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> xenbus_alloc_evtchn()
drivers/xen/xenbus/xenbus_client.c:321 xenbus_dev_error() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> xenbus_free_evtchn()
-> xenbus_dev_error()
drivers/xen/xenbus/xenbus_client.c:342 xenbus_dev_fatal() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> xenbus_alloc_evtchn()
-> xenbus_dev_fatal()
drivers/xen/xenbus/xenbus_client.c:494 xenbus_free_evtchn() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> xenbus_free_evtchn()
drivers/xen/xenbus/xenbus_client.c:290 xenbus_va_dev_error() warn: sleeping in atomic context
pvcalls_front_connect() <- disables preempt
pvcalls_front_accept() <- disables preempt
-> create_active()
-> xenbus_free_evtchn()
-> xenbus_dev_error()
create_active() <duplicate>
-> xenbus_alloc_evtchn()
-> xenbus_dev_fatal()
-> xenbus_va_dev_error()
next prev parent reply other threads:[~2023-02-07 13:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 6:04 [PATCH v4] pipe: use __pipe_{lock,unlock} instead of spinlock Hongchen Zhang
2023-01-29 7:33 ` Linus Torvalds
2023-02-03 2:24 ` Hongchen Zhang
2023-02-06 15:58 ` Luis Chamberlain
2023-02-06 16:07 ` Linus Torvalds
2023-02-06 16:13 ` Julia Lawall
2023-02-06 16:45 ` Dan Carpenter
2023-02-06 17:54 ` Luis Chamberlain
2023-02-07 7:02 ` Dan Carpenter
2023-02-06 18:25 ` Linus Torvalds
2023-02-07 13:37 ` Dan Carpenter [this message]
2023-02-07 14:03 ` xen: sleeping in atomic warnings Juergen Gross
2023-02-07 14:06 ` block: " Dan Carpenter
2023-02-07 16:15 ` Linus Torvalds
2023-02-07 17:53 ` Eric Biggers
2023-02-07 18:24 ` Linus Torvalds
2023-02-07 18:36 ` Eric Biggers
2023-02-07 18:57 ` Linus Torvalds
2023-02-07 19:09 ` Linus Torvalds
2023-02-07 19:35 ` Eric Biggers
2023-02-07 19:49 ` Linus Torvalds
2023-02-08 6:53 ` Eric Biggers
2023-02-07 18:31 ` Jens Axboe
2023-02-08 3:15 ` Yu Kuai
2023-02-03 1:42 ` [PATCH v4] pipe: use __pipe_{lock,unlock} instead of spinlock Hongchen Zhang
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=Y+JUIl64UDmdkboh@kadam \
--to=error27@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=fmdefrancesco@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maobibo@loongson.cn \
--cc=mcgrof@kernel.org \
--cc=mchehab@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xen-devel@lists.xenproject.org \
--cc=zhanghongchen@loongson.cn \
/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).