From: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [WEXT 3/12]: Extract standard call iw_point handling into seperate function.
Date: Fri, 21 Dec 2007 23:22:52 -0800 [thread overview]
Message-ID: <1198308172.4895.11.camel@localhost> (raw)
In-Reply-To: <20071221.205407.165162566.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Fri, 2007-12-21 at 20:54 -0800, David Miller wrote:
> [WEXT]: Extract standard call iw_point handling into seperate function.
This potentially does copy_from_user twice,
first to the stack, second to a kmalloc'ed area.
Perhaps it's better to kmalloc first and copy once?
next prev parent reply other threads:[~2007-12-22 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 4:54 [WEXT 3/12]: Extract standard call iw_point handling into seperate function David Miller
[not found] ` <20071221.205407.165162566.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-12-22 7:22 ` Joe Perches [this message]
2007-12-25 5:18 ` David Miller
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=1198308172.4895.11.camel@localhost \
--to=joe-6d6dil74uinbdgjk7y7tuq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).