public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Himanshu Chauhan <himanshu@symmetricore.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Kernel Newbies <kernelnewbies@nl.linux.org>, Greg Kroah <greg@kroah.com>
Subject: sysfs_ops show vector: size of buffer not required?
Date: Sun, 24 Jan 2010 13:11:18 +0530	[thread overview]
Message-ID: <20100124074118.GA4201@himanshu-laptop> (raw)

Hi All,

The sysfs_ops's show vector doesn't have a size of the
buffer given to the vector, while store on the other hand
has. What is the rationale behind it?

I see most of the implementations doing strcpy in the
show vectors. Ill behaved driver might overwrite the
given buffer when size is not known. Should this be addressed
by providing the buffer size along with the buffer pointer?

Thanks

Best Regards
Himanshu

             reply	other threads:[~2010-01-24  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24  7:41 Himanshu Chauhan [this message]
2010-01-26  4:36 ` sysfs_ops show vector: size of buffer not required? Greg KH
2010-01-26  6:31   ` Himanshu Chauhan
2010-01-26 15:29     ` Greg KH
2010-01-26 17:10       ` Himanshu Chauhan

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=20100124074118.GA4201@himanshu-laptop \
    --to=himanshu@symmetricore.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@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