Alexander Viro wrote: > * verify_area() cleans the value, but you'll be better off > considering these as dangerous - it only checks that range is OK and if > pointer arithmetics moves you out of that range or you access piece longer > than range in question... Note that verify_area's argument cannot be safely dereferenced if a parallel thread is able to change the user-space mapping. This is usually possible. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- [CHECKER] 9 potential copy_*_user bugs in 2.4.1 Dawson Engler
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4.1 Alexander Viro
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4... Dawson Engler
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4... Jamie Lokier
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4.1 Greg KH
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4.1 David S. Miller
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4.1 David Woodhouse
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4... Russell King
- Locking question (was: [CHECKER] 9 potential copy_*_u... Nigel Gamble
- Re: [CHECKER] 9 potential copy_*_user bugs in 2.4.1 Rusty Russell