public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Cc: alex.dewar90@gmail.com, arnd@arndb.de,
	linux-kernel@vger.kernel.org,
	syzbot+15ec7391f3d6a1a7cc7d@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] drivers/misc/vmw_vmci: restrict too big queue size in
Date: Tue, 9 Feb 2021 10:49:07 +0100	[thread overview]
Message-ID: <YCJak9a2WWRgiQWE@kroah.com> (raw)
In-Reply-To: <20210209093101.2097627-1-snovitoll@gmail.com>

On Tue, Feb 09, 2021 at 03:31:01PM +0600, Sabyrzhan Tasbolatov wrote:
> syzbot found WARNING in qp_broker_alloc[1] in qp_host_alloc_queue()
> when num_pages is 0x100001, giving queue_size + queue_page_size
> bigger than KMALLOC_MAX_SIZE for kzalloc(), resulting order >= MAX_ORDER
> condition.
> 
> queue_size + queue_page_size=0x8000d8, where KMALLOC_MAX_SIZE=0x400000.
> 
> Reported-by: syzbot+15ec7391f3d6a1a7cc7d@syzkaller.appspotmail.com
> Signed-off-by: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
> ---
> >As this is controllable by userspace, you just provided a way to flood
> >the kernel logs.
> >
> >Please make this a dev_dbg() call instead, if you really want to see it.
> >Otherwise just return NULL, no need to report anything, right?
> 
> Thanks, removed pr_warn().
> 
> v2: Removed pr_warn() to avoid flood from user-space
> ---
>  drivers/misc/vmw_vmci/vmci_queue_pair.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/misc/vmw_vmci/vmci_queue_pair.c b/drivers/misc/vmw_vmci/vmci_queue_pair.c
> index f6af406fda80..ea16df73cde0 100644
> --- a/drivers/misc/vmw_vmci/vmci_queue_pair.c
> +++ b/drivers/misc/vmw_vmci/vmci_queue_pair.c
> @@ -538,9 +538,7 @@ static struct vmci_queue *qp_host_alloc_queue(u64 size)
>  	queue_page_size = num_pages * sizeof(*queue->kernel_if->u.h.page);
>  
>  	if (queue_size + queue_page_size > KMALLOC_MAX_SIZE) {
> -		pr_warn("too big queue to allocate\n");
>  		return NULL;
> -	}
>  

This patch doesn't apply to the tree, you can't send me a patch that is
relative to your previous one, that doesn't work at all.

And also, test-build your patches always first, to not do so is a bit
rude to maintainers...

thanks,

greg k-h

      parent reply	other threads:[~2021-02-09  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  5:34 [PATCH] drivers/misc/vmw_vmci: restrict too big queue size in qp_host_alloc_queue Sabyrzhan Tasbolatov
2021-02-09  8:38 ` Greg KH
2021-02-09  9:31   ` [PATCH v2] drivers/misc/vmw_vmci: restrict too big queue size in Sabyrzhan Tasbolatov
2021-02-09  9:32     ` Alex Dewar
2021-02-09  9:45       ` [PATCH v3] " Sabyrzhan Tasbolatov
2021-02-09  9:54         ` Greg KH
2021-02-09 10:26           ` [PATCH v4] drivers/misc/vmw_vmci: restrict too big queue size in qp_host_alloc_queue Sabyrzhan Tasbolatov
2021-02-09  9:49     ` Greg KH [this message]

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=YCJak9a2WWRgiQWE@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alex.dewar90@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snovitoll@gmail.com \
    --cc=syzbot+15ec7391f3d6a1a7cc7d@syzkaller.appspotmail.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