From: Taral <taral@taral.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: [BK PATCH] __verify_write brokenness
Date: Fri, 9 May 2003 21:45:44 -0500 [thread overview]
Message-ID: <20030510024544.GA1561@taral.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]
Looks like the recent access_ok fixes broke building of i386.
__verify_write is still referenced in a couple places.
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
===================================================================
ChangeSet@1.1096, 2003-05-09 21:37:04-05:00, taral@dragon.taral.net
Remove remaining references to __verify_write
arch/i386/kernel/i386_ksyms.c | 3 ---
include/asm-i386/uaccess.h | 2 --
2 files changed, 5 deletions(-)
diff -Nru a/arch/i386/kernel/i386_ksyms.c b/arch/i386/kernel/i386_ksyms.c
--- a/arch/i386/kernel/i386_ksyms.c Fri May 9 21:44:01 2003
+++ b/arch/i386/kernel/i386_ksyms.c Fri May 9 21:44:01 2003
@@ -73,9 +73,6 @@
#ifdef CONFIG_X86_NUMAQ
EXPORT_SYMBOL(xquad_portio);
#endif
-#ifndef CONFIG_X86_WP_WORKS_OK
-EXPORT_SYMBOL(__verify_write);
-#endif
EXPORT_SYMBOL(dump_thread);
EXPORT_SYMBOL(dump_fpu);
EXPORT_SYMBOL(dump_extended_fpu);
diff -Nru a/include/asm-i386/uaccess.h b/include/asm-i386/uaccess.h
--- a/include/asm-i386/uaccess.h Fri May 9 21:44:01 2003
+++ b/include/asm-i386/uaccess.h Fri May 9 21:44:01 2003
@@ -42,8 +42,6 @@
} ____cacheline_aligned_in_smp movsl_mask;
#endif
-int __verify_write(const void *, unsigned long);
-
#define __addr_ok(addr) ((unsigned long)(addr) < (current_thread_info()->addr_limit.seg))
/*
===================================================================
This BitKeeper patch contains the following changesets:
+
## Wrapped with gzip_uu ##
M'XL( '%GO#X \55VV[30!!]SG[%2GU$MF?VXIL45&@12" 1!?4)H6B[7B=6
M8KO:=5HJ^>.[-="$BL10BK#]L-ZQS\R<,\<^H1?.V'S2*:LVY(2^:UV73PJK
MEFT3#IMA8SH?F+>M#T1;9R-G=;2IFNW7@(62^-A,=7I%KXUU^01#_K#3W5Z9
M?#)_\_;BPZLY(=,I/5NI9FD^F8Y.IZ1K[;7:%.Y4=:O-?3JK&E>;3H6ZK?N'
M1WL&P/PI,>$@XQYC$$FOL4!4 DT!3*2QV*%=F6:YK8[">1S(&#(!<0^(".2<
M8HB0Q11X!#*"C#+,>9*#"$#F '3@XO0Q,?0%HP&0U_1Y>SDCFLY-W5X;:DVM
MJJ9JEGY5&FL:;9S/1A<+SW=5WBYN;-49\I[*&,AL1S )_O @!!20ER.=5(W>
M; L3*5<'%4_C:*NTK\B%J_W6,B%ZR05"+T4A$HZRT&5<RHP?X'$$UW.%'ITC
M9CT(1#9:I[)Z%0U :V,;LQG6B[6[K5VH]TH5P+"721JG?9J4I;Y,%5=2\DMV
ML-11Z/UJN;\5P^@??6W<#L_0$%'KJ_JTJ):FO8?\_"/AE]]I2: $CH"BYS+A
M<C",9#_;!7/,1NP"-.#_UB[?3?)+CWQ3XR,-[,UP^:F?'1?F"38Z3V+*!\D/
M#_6XWG]KM,-BCUH-4H^=2M%#&K-T4)K)IRC-_I_2PT?BD="'&W^*RD)2MOOY
6Z971:[>MIX JP4PK<@=<#^Z-6@<
--
Taral <taral@taral.net>
This message is digitally signed. Please PGP encrypt mail to me.
"Most parents have better things to do with their time than take care of
their children." -- Me
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-05-10 2:33 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=20030510024544.GA1561@taral.net \
--to=taral@taral.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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