From: David Vrabel <david.vrabel@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, SeeChen Ng <seechen81@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH net-next v4] xen-netback: Adding debugfs "io_ring_qX" files
Date: Mon, 11 Aug 2014 11:50:56 +0100 [thread overview]
Message-ID: <53E8A010.1080208@citrix.com> (raw)
In-Reply-To: <20140811103802.GA3249@zion.uk.xensource.com>
On 11/08/14 11:38, Wei Liu wrote:
> On Sun, Aug 10, 2014 at 10:57:51PM +0800, SeeChen Ng wrote:
>> Hi, I'm a noob to linux kernel, I tried to figure out the usage of the function
>> "simple_write_to_buffer", and I got confused about the code here.
>>
>>> +static ssize_t
>>> +xenvif_write_io_ring(struct file *filp, const char __user *buf, size_t count,
>>> + loff_t *ppos)
>>> +{
>>> + struct xenvif_queue *queue =
>>> + ((struct seq_file *)filp->private_data)->private;
>>> + int len;
>>> + char write[sizeof(XENVIF_KICK_STR)];
>>> +
>>> + /* don't allow partial writes and check the length */
>>> + if (*ppos != 0)
>>> + return 0;
>>> + if (count < sizeof(XENVIF_KICK_STR) - 1)
>>> + return -ENOSPC;
>> The statement here is trying to verify the value of "count" is smaller
>> than the size of array "write", make sure that the array got
>> enough space for the write operation, right?
>>
>
> Yes I think so.
Is anyone reading the comment?
/* don't allow partial writes and check the length */
The sense of the check is correct.
David
next prev parent reply other threads:[~2014-08-11 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 14:57 [PATCH net-next v4] xen-netback: Adding debugfs "io_ring_qX" files SeeChen Ng
2014-08-11 10:38 ` Wei Liu
2014-08-11 10:50 ` David Vrabel [this message]
2014-08-11 10:56 ` Wei Liu
2014-08-11 12:17 ` Zoltan Kiss
2014-08-11 12:31 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2014-07-08 18:49 Zoltan Kiss
2014-07-08 18:59 ` Konrad Rzeszutek Wilk
2014-07-09 3:49 ` David Miller
2014-07-09 3:49 ` David Miller
2014-07-08 18:49 Zoltan Kiss
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=53E8A010.1080208@citrix.com \
--to=david.vrabel@citrix.com \
--cc=seechen81@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.