From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] ath6kl: add blocking debugfs file for retrieving firmware logs
Date: Mon, 6 Feb 2012 14:36:56 +0530 [thread overview]
Message-ID: <20120206090654.GA3260@chvasanth-lnx> (raw)
In-Reply-To: <20120206062340.20231.55630.stgit@localhost6.localdomain6>
On Mon, Feb 06, 2012 at 08:23:40AM +0200, Kalle Valo wrote:
> When debugging firmware issues it's not always enough to get
> the latest firmware logs, sometimes we need to get logs from a longer
> period. To make this possible, add a debugfs file named fwlog_block. When
> reading from this file ath6kl will send firmware logs whenever available
> and otherwise it will block and wait for new logs.
>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
> ---
> +static ssize_t ath6kl_fwlog_block_read(struct file *file,
> + char __user *user_buf,
> + size_t count,
> + loff_t *ppos)
> +{
> + struct ath6kl *ar = file->private_data;
> + struct sk_buff *skb;
> + ssize_t ret_cnt;
> + size_t len = 0, not_copied;
> + char *buf;
> + int ret;
> +
> + buf = vmalloc(count);
> + if (!buf)
> + return -ENOMEM;
> +
> + spin_lock(&ar->debug.fwlog_queue.lock);
> +
> + if (skb_queue_len(&ar->debug.fwlog_queue) == 0) {
> + /* we must init under queue lock */
> + init_completion(&ar->debug.fwlog_completion);
> +
> + spin_unlock(&ar->debug.fwlog_queue.lock);
> +
> + ret = wait_for_completion_interruptible(
> + &ar->debug.fwlog_completion);
> + if (ret == -ERESTARTSYS)
> + return ret;
> +
> + spin_lock(&ar->debug.fwlog_queue.lock);
> + }
> +
> + while ((skb = __skb_dequeue(&ar->debug.fwlog_queue))) {
> + if (skb->len > count - len) {
> + /* not enough space, put skb back and leave */
> + __skb_queue_head(&ar->debug.fwlog_queue, skb);
> + break;
> + }
> +
> +
> + memcpy(buf + len, skb->data, skb->len);
> + len += skb->len;
> +
> + kfree_skb(skb);
> + }
> +
> + spin_unlock(&ar->debug.fwlog_queue.lock);
> +
> + /* FIXME: what to do if len == 0? */
> +
> + not_copied = copy_to_user(user_buf, buf, len);
> + if (not_copied != 0) {
> + ret_cnt = -EFAULT;
> + goto out;
> + }
> +
> + *ppos = *ppos + len;
Why not to use simple_read_from_buffer()?, looks like it can also
takes care of len == 0 case in the following check.
if (pos >= available || !count)
return 0;
when available (len) is 0, pos = available with
ath6kl_fwlog_block_read().
Vasanth
next prev parent reply other threads:[~2012-02-06 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 6:23 [PATCH 1/2] ath6kl: store firmware logs in skbuffs Kalle Valo
2012-02-06 6:23 ` [PATCH 2/2] ath6kl: add blocking debugfs file for retrieving firmware logs Kalle Valo
2012-02-06 9:06 ` Vasanthakumar Thiagarajan [this message]
2012-02-06 12:37 ` Kalle Valo
2012-02-06 15:05 ` Vasanthakumar Thiagarajan
2012-02-06 17:47 ` Kalle Valo
2012-02-07 9:59 ` Vasanthakumar Thiagarajan
2012-02-08 9:30 ` [PATCH 1/2] ath6kl: store firmware logs in skbuffs Kalle Valo
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=20120206090654.GA3260@chvasanth-lnx \
--to=vthiagar@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).