* Block driver design issue
@ 2001-02-12 17:16 LA Walsh
2001-02-12 17:30 ` Manfred Spraul
0 siblings, 1 reply; 2+ messages in thread
From: LA Walsh @ 2001-02-12 17:16 UTC (permalink / raw)
To: linux-kernel
I have a block driver I inherited that I working on that has a problem and
was wondering for cleaner solutions.
The driver can accept written characters from either userspace programs or from
the kernel. From userspace it uses sys_write. That in turn calls block_write.
There's almost 100 lines of duplicated code in a copy of the block_write
code in the driver "block_writek" as well as duplicate code in audit_write vs. audit_writek.
The only difference being down in block_write at the "copy_from_user(p,buf,chars); "
which becomes a "memcpy(p,buf,chars)" in the "block_writek" version.
I find this duplication of code to be inefficient. Is there a way to dummy up the
the 'buf' address so that the "copy_from_user" will copy the buffer from kernel space?
My assumption is that it wouldn't "just work" (which may also be an invalid assumption).
Suggestions? Abuse?
Thanks!
-linda
--
L A Walsh | Trust Technology, Core Linux, SGI
law@sgi.com | Voice: (650) 933-5338
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-02-12 17:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-02-12 17:16 Block driver design issue LA Walsh
2001-02-12 17:30 ` Manfred Spraul
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox