[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80afde93-b9cf-f6c4-da40-3385d7f6741b@linux.ibm.com>
Date: Fri, 13 May 2022 09:45:39 +0200
From: Steffen Eiden <seiden@...ux.ibm.com>
To: Claudio Imbrenda <imbrenda@...ux.ibm.com>
Cc: Greg KH <greg@...ah.com>, Heiko Carstens <hca@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Shuah Khan <shuah@...nel.org>,
Christian Borntraeger <borntraeger@...ux.ibm.com>,
Janosch Frank <frankja@...ux.ibm.com>,
David Hildenbrand <david@...hat.com>,
Nico Boehr <nrb@...ux.ibm.com>, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH v4 1/2] drivers/s390/char: Add Ultravisor io device
On 5/12/22 16:33, Claudio Imbrenda wrote:
[snip]
>> +/*
>> + * IOCTL entry point for the Ultravisor device.
>> + */
>> +static long uvio_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
>> +{
>> + void __user *argp = (void __user *)arg;
>> + struct uvio_ioctl_cb *uv_ioctl;
>> + long ret;
>> +
>> + ret = -ENOMEM;
>> + uv_ioctl = vzalloc(sizeof(*uv_ioctl));
> struct uvio_ioctl_cb is rather small, couldn't you just allocate it on
> the stack?
>
IIRC it was on stack in some previous version. We then had a discussion
earlier about this triggered by the inverse comment and decided to not
use the stack.
[snip]
Powered by blists - more mailing lists