From: Petr Mladek <pmladek@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: boris.ostrovsky@oracle.com, jgross@suse.com,
xen-devel@lists.xenproject.org, Luca Miccio <lucmiccio@gmail.com>,
Stefano Stabellini <stefano.stabellini@xilinx.com>,
live-patching@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH LINUX v5 2/2] xen: add support for initializing xenstore later as HVM domain
Date: Wed, 19 Jul 2023 17:47:37 +0200 [thread overview]
Message-ID: <ZLgFmS4TQwGWA7o0@alley> (raw)
In-Reply-To: <20220513211938.719341-2-sstabellini@kernel.org>
On Fri 2022-05-13 14:19:38, Stefano Stabellini wrote:
> From: Luca Miccio <lucmiccio@gmail.com>
>
> When running as dom0less guest (HVM domain on ARM) the xenstore event
> channel is available at domain creation but the shared xenstore
> interface page only becomes available later on.
>
> In that case, wait for a notification on the xenstore event channel,
> then complete the xenstore initialization later, when the shared page
> is actually available.
>
> The xenstore page has few extra field. Add them to the shared struct.
> One of the field is "connection", when the connection is ready, it is
> zero. If the connection is not-zero, wait for a notification.
I see the following warning from free_irq() in 6.5-rc2 when running
livepatching selftests. It does not happen after reverting this patch.
[ 352.168453] livepatch: signaling remaining tasks
[ 352.173228] ------------[ cut here ]------------
[ 352.175563] Trying to free already-free IRQ 0
[ 352.177355] WARNING: CPU: 1 PID: 88 at kernel/irq/manage.c:1893 free_irq+0xbf/0x350
[ 352.179942] Modules linked in: test_klp_livepatch(EK)
[ 352.181621] CPU: 1 PID: 88 Comm: xenbus_probe Kdump: loaded Tainted: G E K 6.5.0-rc2-default+ #535
[ 352.184754] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014
[ 352.188214] RIP: 0010:free_irq+0xbf/0x350
[ 352.192211] Code: 7a 08 75 0e e9 36 02 00 00 4c 3b 7b 08 74 5a 48 89 da 48 8b 5a 18 48 85 db 75 ee 44 89 f6 48 c7 c7 58 b0 8b 86 e8 21 0a f5 ff <0f> 0b 48 8b 34 24 4c 89 ef e8 53 bb e3 00
48 8b 45 40 48 8b 40 78
[ 352.200079] RSP: 0018:ffffaf0440b4be80 EFLAGS: 00010086
[ 352.201465] RAX: 0000000000000000 RBX: ffff99f105116c80 RCX: 0000000000000003
[ 352.203324] RDX: 0000000080000003 RSI: ffffffff8691d4bc RDI: 00000000ffffffff
[ 352.204989] RBP: ffff99f100052000 R08: 0000000000000000 R09: c0000000ffff7fff
[ 352.206253] R10: ffffaf0440b4bd18 R11: ffffaf0440b4bd10 R12: ffff99f1000521e8
[ 352.207451] R13: ffff99f1000520a8 R14: 0000000000000000 R15: ffffffff86f42360
[ 352.208787] FS: 0000000000000000(0000) GS:ffff99f15a400000(0000) knlGS:0000000000000000
[ 352.210061] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 352.210815] CR2: 00007f8415d56000 CR3: 0000000105e36003 CR4: 0000000000370ee0
[ 352.211867] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 352.212912] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 352.213951] Call Trace:
[ 352.214390] <TASK>
[ 352.214717] ? __warn+0x81/0x170
[ 352.215436] ? free_irq+0xbf/0x350
[ 352.215906] ? report_bug+0x10b/0x200
[ 352.216408] ? prb_read_valid+0x17/0x20
[ 352.216926] ? handle_bug+0x44/0x80
[ 352.217409] ? exc_invalid_op+0x13/0x60
[ 352.217932] ? asm_exc_invalid_op+0x16/0x20
[ 352.218497] ? free_irq+0xbf/0x350
[ 352.218979] ? __pfx_xenbus_probe_thread+0x10/0x10
[ 352.219600] xenbus_probe+0x7a/0x80
[ 352.221030] xenbus_probe_thread+0x76/0xc0
[ 352.221416] ? __pfx_autoremove_wake_function+0x10/0x10
[ 352.221882] kthread+0xfd/0x130
[ 352.222191] ? __pfx_kthread+0x10/0x10
[ 352.222544] ret_from_fork+0x2d/0x50
[ 352.222893] ? __pfx_kthread+0x10/0x10
[ 352.223260] ret_from_fork_asm+0x1b/0x30
[ 352.223629] RIP: 0000:0x0
[ 352.223931] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[ 352.224488] RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
[ 352.225044] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 352.225571] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 352.226106] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[ 352.226632] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 352.227171] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 352.227710] </TASK>
[ 352.227917] irq event stamp: 22
[ 352.228209] hardirqs last enabled at (21): [<ffffffff854240be>] ___slab_alloc+0x68e/0xc80
[ 352.228914] hardirqs last disabled at (22): [<ffffffff85fe98fd>] _raw_spin_lock_irqsave+0x8d/0x90
[ 352.229546] softirqs last enabled at (0): [<ffffffff850fc0ee>] copy_process+0xaae/0x1fd0
[ 352.230079] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 352.230503] ---[ end trace 0000000000000000 ]---
, where the message "livepatch: signaling remaining tasks" means that
it might send fake signals to non-kthread tasks.
The aim is to force userspace tasks to enter and leave kernel space
so that they might start using the new patched code. It is done
this way:
/*
* Sends a fake signal to all non-kthread tasks with TIF_PATCH_PENDING set.
* Kthreads with TIF_PATCH_PENDING set are woken up.
*/
static void klp_send_signals(void)
{
[...]
/*
* Send fake signal to all non-kthread tasks which are
* still not migrated.
*/
set_notify_signal(task);
[...]
The warning is most likely printed in this condition:
const void *free_irq(unsigned int irq, void *dev_id)
{
struct irq_desc *desc = irq_to_desc(irq);
struct irqaction *action;
const char *devname;
if (!desc || WARN_ON(irq_settings_is_per_cpu_devid(desc)))
return NULL;
See below.
> --- a/drivers/xen/xenbus/xenbus_probe.c
> +++ b/drivers/xen/xenbus/xenbus_probe.c
> @@ -750,6 +751,20 @@ static void xenbus_probe(void)
> {
> xenstored_ready = 1;
>
> + if (!xen_store_interface) {
> + xen_store_interface = xen_remap(xen_store_gfn << XEN_PAGE_SHIFT,
> + XEN_PAGE_SIZE);
> + /*
> + * Now it is safe to free the IRQ used for xenstore late
> + * initialization. No need to unbind: it is about to be
> + * bound again from xb_init_comms. Note that calling
> + * unbind_from_irqhandler now would result in xen_evtchn_close()
> + * being called and the event channel not being enabled again
> + * afterwards, resulting in missed event notifications.
> + */
> + free_irq(xs_init_irq, &xb_waitq);
Is it possbile that this free_irq(), the fake signal, and the warning
are somehow related, please?
> + }
> +
> /*
> * In the HVM case, xenbus_init() deferred its call to
> * xs_init() in case callbacks were not operational yet.
Best Regards,
Petr
next parent reply other threads:[~2023-07-19 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.22.394.2205131417320.3842@ubuntu-linux-20-04-desktop>
[not found] ` <20220513211938.719341-2-sstabellini@kernel.org>
2023-07-19 15:47 ` Petr Mladek [this message]
2023-07-20 1:46 ` [PATCH LINUX v5 2/2] xen: add support for initializing xenstore later as HVM domain Stefano Stabellini
2023-07-20 10:18 ` Petr Mladek
2023-07-20 23:31 ` Stefano Stabellini
2023-07-21 12:48 ` Petr Mladek
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=ZLgFmS4TQwGWA7o0@alley \
--to=pmladek@suse.com \
--cc=axboe@kernel.dk \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=live-patching@vger.kernel.org \
--cc=lucmiccio@gmail.com \
--cc=peterz@infradead.org \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.com \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).