From: Amit Shah <amit.shah@redhat.com>
To: Julia Lawall <julia@diku.dk>
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 1/4] drivers/char: Eliminate use after free
Date: Mon, 17 May 2010 14:31:40 +0530 [thread overview]
Message-ID: <20100517072337.GC3313@amit-laptop.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005151145340.15566@ask.diku.dk>
On (Sat) May 15 2010 [11:45:53], Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> In each case, the first argument to send_control_msg or __send_control_msg,
> respectively, has either not been successfully allocated or has been freed
> at the point of the call. In the first case, the first argument, port, is
> only used to access the portdev and id fields, in order to call
> __send_control_msg. Thus it seems possible instead to call
> __send_control_msg directly. In the second case, the call to
> __send_control_msg is moved up to a place where it seems like the first
> argument, portdev, has been initialized sufficiently to make the call to
> __send_control_msg meaningful.
>
> This has only been compile tested.
>
> A simplified version of the semantic match that finds this problem is as
> follows: (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @free@
> expression E;
> position p;
> @@
> kfree@p(E)
>
> @@
> expression free.E, subE<=free.E, E1;
> position free.p;
> @@
>
> kfree@p(E)
> ...
> (
> subE = E1
> |
> * E
> )
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
Acked-by: Amit Shah <amit.shah@redhat.com>
Thanks, Julia.
Rusty, please pick this patch. Thanks.
>
> ---
> drivers/char/virtio_console.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
> index 458d907..8c99bf1 100644
> --- a/drivers/char/virtio_console.c
> +++ b/drivers/char/virtio_console.c
> @@ -1090,7 +1090,7 @@ free_port:
> kfree(port);
> fail:
> /* The host might want to notify management sw about port add failure */
> - send_control_msg(port, VIRTIO_CONSOLE_PORT_READY, 0);
> + __send_control_msg(portdev, id, VIRTIO_CONSOLE_PORT_READY, 0);
> return err;
> }
>
> @@ -1559,6 +1559,9 @@ static int __devinit virtcons_probe(struct virtio_device *vdev)
> return 0;
>
> free_vqs:
> + /* The host might want to notify mgmt sw about device add failure */
> + __send_control_msg(portdev, VIRTIO_CONSOLE_BAD_ID,
> + VIRTIO_CONSOLE_DEVICE_READY, 0);
> vdev->config->del_vqs(vdev);
> kfree(portdev->in_vqs);
> kfree(portdev->out_vqs);
> @@ -1567,9 +1570,6 @@ free_chrdev:
> free:
> kfree(portdev);
> fail:
> - /* The host might want to notify mgmt sw about device add failure */
> - __send_control_msg(portdev, VIRTIO_CONSOLE_BAD_ID,
> - VIRTIO_CONSOLE_DEVICE_READY, 0);
> return err;
> }
>
Amit
next prev parent reply other threads:[~2010-05-17 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 9:45 Julia Lawall
2010-05-17 9:01 ` Amit Shah [this message]
2010-05-18 0:39 ` Rusty Russell
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=20100517072337.GC3313@amit-laptop.redhat.com \
--to=amit.shah@redhat.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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
Powered by JetHome