From: Pavel Machek <pavel@suse.cz>
To: Andi Kleen <ak@suse.de>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ioctl cleanups: move SG_IO translation where it belongs
Date: Tue, 6 May 2003 23:38:53 +0200 [thread overview]
Message-ID: <20030506213853.GA5615@elf.ucw.cz> (raw)
In-Reply-To: <1052252472.23104.11.camel@averell>
Hi!
> > This enables sharing of 200 lines of SG_IO support by all 64-bit
> > architectures. If it looks okay, more such patches will follow.
>
>
> I currently have some patches for this function pending. When an
> unchanged data buffer is passed it is ok to just verify_area it, no need
> to kmalloc and copy. This simplifies this handler vastly.
>
> Here is the part from the 2.4 patch; haven't tried it with 2.5 yet,
> but should apply there too.
>
> Also adds some boundary checking.
I'll merge it. Can you mail me whole 2.4 patch [I had it but deleted
it, sorry]. I'll attempt to port it to 2.5 and return it back to
you...
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-05-06 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 20:03 ioctl cleanups: move SG_IO translation where it belongs Pavel Machek
2003-05-06 20:21 ` Andi Kleen
2003-05-06 21:38 ` Pavel Machek [this message]
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=20030506213853.GA5615@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--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