From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net
Cc: linux-kernel@vger.kernel.org, linux-um@lists.infradead.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH] um: Add winch to winch_handlers before registering winch IRQ
Date: Thu, 07 Mar 2024 13:43:40 +0100 [thread overview]
Message-ID: <2d70513e9f84e650ef1ede5a8ae5960a9de782bc.camel@huaweicloud.com> (raw)
In-Reply-To: <20240307104926.3531358-1-roberto.sassu@huaweicloud.com>
On Thu, 2024-03-07 at 11:49 +0100, Roberto Sassu wrote:
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> Registering a winch IRQ is racy, an interrupt may occur before the winch is
> added to the winch_handlers list.
>
> If that happens, register_winch_irq() adds to that list a winch that is
> scheduled to be (or has already been) freed, causing a panic later in
> winch_cleanup().
>
> Avoid the race by adding the winch to the winch_handlers list before
> registering the IRQ, and rolling back if um_request_irq() fails.
>
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
Fixes: 42a359e31a0e ("uml: SIGIO support cleanup")
I see that before that commit there was the same ordering (list_add()
before um_request_irq()).
Failure from um_request_irq() should not result in executing
winch_interrupt() which could call list_del() itself. Then, it should
be fine to delete the winch in the error path.
Roberto
> ---
> arch/um/drivers/line.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/um/drivers/line.c b/arch/um/drivers/line.c
> index ffc5cb92fa36..d82bc3fdb86e 100644
> --- a/arch/um/drivers/line.c
> +++ b/arch/um/drivers/line.c
> @@ -676,24 +676,26 @@ void register_winch_irq(int fd, int tty_fd, int pid, struct tty_port *port,
> goto cleanup;
> }
>
> - *winch = ((struct winch) { .list = LIST_HEAD_INIT(winch->list),
> - .fd = fd,
> + *winch = ((struct winch) { .fd = fd,
> .tty_fd = tty_fd,
> .pid = pid,
> .port = port,
> .stack = stack });
>
> + spin_lock(&winch_handler_lock);
> + list_add(&winch->list, &winch_handlers);
> + spin_unlock(&winch_handler_lock);
> +
> if (um_request_irq(WINCH_IRQ, fd, IRQ_READ, winch_interrupt,
> IRQF_SHARED, "winch", winch) < 0) {
> printk(KERN_ERR "register_winch_irq - failed to register "
> "IRQ\n");
> + spin_lock(&winch_handler_lock);
> + list_del(&winch->list);
> + spin_unlock(&winch_handler_lock);
> goto out_free;
> }
>
> - spin_lock(&winch_handler_lock);
> - list_add(&winch->list, &winch_handlers);
> - spin_unlock(&winch_handler_lock);
> -
> return;
>
> out_free:
next prev parent reply other threads:[~2024-03-07 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 10:49 Roberto Sassu
2024-03-07 12:43 ` Roberto Sassu [this message]
2024-03-28 8:11 ` Roberto Sassu
2024-03-28 8:25 ` Johannes Berg
2024-04-23 7:22 ` Roberto Sassu
2024-04-23 8:11 ` Richard Weinberger
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=2d70513e9f84e650ef1ede5a8ae5960a9de782bc.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=roberto.sassu@huawei.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®