mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
	Chris Zankel <zankel@tensilica.com>
Subject: [PATCH 0/3] remove verify_area()
Date: Mon, 29 Aug 2005 23:23:59 +0200	[thread overview]
Message-ID: <200508292324.01342.jesper.juhl@gmail.com> (raw)

Andrew, 
	it's time to kill off verify_area().

	verify_area() has been deprecated for quite a while now and is 
documented in Documentation/feature-removal-schedule.txt as going away in 
July 2005.
It is completely replaced by access_ok() and there are no in-kernel users
left [1]. It's time for verify_area() to die.

	The following 3 patches remove verify_area() itself as well as 
remove or modify some documentation related to it.


 1 - remove verify_area() from various uaccess.h headers
 2 - remove or edit references to verify_area in Documentation/
 3 - remove fs/umsdos/notes as it only contain a verify_area related note

 note: I only have access to i386 hardware, so that's all I've been able to
       test on, but since there are no users of this left and the patch just
       remove the unused function, there should really not be any trouble.


[1] The Xtensa architecture was merged post the big verify_area() to 
    access_ok() cleanup I did some months back and is still using 
    verify_area(). I've submitted sepperate cleanup patches to get rid of 
    it from Xtensa to Chris Zankel and they should flow your way eventually.
    These 3 patches therefore leave Xtensa alone.


-- 
 Jesper Juhl


                 reply	other threads:[~2005-08-29 21:23 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=200508292324.01342.jesper.juhl@gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zankel@tensilica.com \
    /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®