From: Ralf Baechle <ralf@linux-mips.org>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Andrew Morton <akpm@osdl.org>,
Yoichi Yuasa <yuasa@hh.iij4u.or.jp>,
linux-kernel@vger.kernel.org
Subject: Re: [patch][resend] convert a remaining verify_area to access_ok (was: Re: [PATCH 2.6.11-mm1] mips: more convert verify_area to access_ok) (fwd)
Date: Fri, 18 Mar 2005 22:56:40 +0000 [thread overview]
Message-ID: <20050318225640.GA4817@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0503180109490.2512@dragon.hyggekrogen.localhost>
On Fri, Mar 18, 2005 at 01:17:47AM +0100, Jesper Juhl wrote:
> I hope I did a descent job and that you didn't waste too much time
> duplicating effort...
Didn't look too hard at it since my patch of something like 2,500 lines
should be a superset of yours.
> > The last instance of verify_area() in the MIPS code is now the definition
> > itself.
> >
> The plan is to wait for a few months (or a few kernel releases - whichever
> comes first) and then I'll send Andrew patches to remove it completely.
> There are still a few related nits left, like the FPU_verify_area function
> arch/i386/math-emu/reg_ld_str.c and the rw_verify_area function in
> fs/read_write.c that I want to get out of the way first (think I'll
> probably end up attempting to rename those s/verify_area/access_ok/ and
> see if people scream).
Access_ok was introduced in 2.1.4. Easy for people to write code that's
portable and so verify_area should die a peaceful death.
Ralf
prev parent reply other threads:[~2005-03-20 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 21:35 [patch][resend] convert a remaining verify_area to access_ok (was: Re: [PATCH 2.6.11-mm1] mips: more convert verify_area to access_ok) (fwd) Jesper Juhl
2005-03-16 22:55 ` Andrew Morton
2005-03-16 23:01 ` Jesper Juhl
2005-03-17 13:14 ` Ralf Baechle
2005-03-17 21:44 ` Ralf Baechle
2005-03-17 21:43 ` Ralf Baechle
2005-03-18 0:17 ` Jesper Juhl
2005-03-18 22:56 ` Ralf Baechle [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=20050318225640.GA4817@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@osdl.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=yuasa@hh.iij4u.or.jp \
/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