From: Andries.Brouwer@cwi.nl
To: aebr@win.tue.nl, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: sparse
Date: Tue, 9 Sep 2003 03:58:21 +0200 (MEST) [thread overview]
Message-ID: <UTC200309090158.h891wLf25425.aeb@smtp.cwi.nl> (raw)
> the rest are mostly due to the address space checks. Some of them are
> likely trivial to fix, but the most interesting ones (in the networking
> code) are because the networking code re-uses the same data structures
> for both kernel and user addresses.
By separate mail I sent you half a dozen or perhaps a dozen sparse
fixes, all of the trivial kind. Hope you don't mind.
I did more, but the nfs / aio / sendfile stuff involves somewhat
larger surgery - will send some other time.
> it's not seriously usable yet
I like it, or, rather, the result of having __user annotation
for pointers to user space.
Andries
reply other threads:[~2003-09-09 1:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=UTC200309090158.h891wLf25425.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®