From: Matthieu Delahaye <delahaym@esiee.fr>
To: Matthew Wilcox <matthew@wil.cx>,
parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] glibc 2.2.3 make check status
Date: Sat, 05 May 2001 17:12:39 +0200 [thread overview]
Message-ID: <3AF41867.FEA3F5B6@esiee.fr> (raw)
In-Reply-To: 20010505033457.Q32445@parcelfarce.linux.theplanet.co.uk
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Hi willy
Matthew Wilcox wrote:
>
> I'm not sure people actually ran make check against glibc 2.2.1, so I don't
> know how this compares. Maybe 2.2.3 just has more tests than 2.2.1 did...
>
> I'd love some help on this. Really. check the merge_GLIBC_CVS_20010424
> branch out of CVS, configure it, make, then make check, and you'll start
> hitting failures. I've indicated the ones I've investigated.
> * posix/testchmod fails. This is due to a kernel bug in strncpy_from_user.
> Bug #118
The patch given above is supposed to correct this bug. It deals with the
fact that r24 counter is not "up to date" when the loop is stoped due to
a 0 byte's copy.
I didn't find your merge_GLIBC_CVS_20010424 file. If you could point me
where
it is, I could perhaps try to help you as you request. More over, as you
might infer
I wasn't able to check the patch with the make check of the merge. The
only thing I know
is that my kernel still work with this patch , which is not a proof.
Regards,
Matthieu
--
Matthieu Delahaye
ESIEE Team
http://mkhppa1.esiee.fr/
[-- Attachment #2: strncopy_from_user.diff --]
[-- Type: text/plain, Size: 894 bytes --]
diff -Nru linux.old/arch/parisc/lib/lusercopy.S linux.new/arch/parisc/lib/lusercopy.S
--- linux.old/arch/parisc/lib/lusercopy.S Sat May 5 16:43:40 2001
+++ linux.new/arch/parisc/lib/lusercopy.S Sat May 5 16:44:00 2001
@@ -144,7 +144,7 @@
*
* Returns -EFAULT if exception before terminator,
* N if the entire buffer filled,
- * otherwise strlen + 1 (i.e. includes zero byte)
+ * otherwise strlen (i.e. excludes zero byte)
*/
.export lstrncpy_from_user,code
@@ -153,7 +153,7 @@
.callinfo NO_CALLS
.entry
comib,= 0,%r24,$lsfu_done
- copy %r26,%r23
+ copy %r24,%r23
get_sr
1: ldbs,ma 1(%sr1,%r25),%r1
$lsfu_loop:
@@ -162,7 +162,7 @@
addib,<>,n -1,%r24,$lsfu_loop
2: ldbs,ma 1(%sr1,%r25),%r1
$lsfu_done:
- sub %r26,%r23,%r28
+ sub %r23,%r24,%r28
$lsfu_exit:
bv %r0(%r2)
nop
next prev parent reply other threads:[~2001-05-05 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 2:34 [parisc-linux] glibc 2.2.3 make check status Matthew Wilcox
2001-05-05 15:12 ` Matthieu Delahaye [this message]
2001-05-05 21:16 ` Matthew Wilcox
2001-05-05 22:45 ` Matthew Wilcox
2001-05-08 13:48 ` Paul Bame
2001-05-08 16:53 ` Matthew Wilcox
2001-05-08 19:52 ` Matthew Wilcox
2001-05-20 3:15 ` Matthew Wilcox
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=3AF41867.FEA3F5B6@esiee.fr \
--to=delahaym@esiee.fr \
--cc=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.