From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 1029] New: LTP ustat tests break in 2.6.0-test2-mm1
Date: Fri, 01 Aug 2003 13:18:51 -0700 [thread overview]
Message-ID: <405500000.1059769131@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=1029
Summary: LTP ustat tests break in 2.6.0-test2-mm1
Kernel Version: 2.6.0-test2-mm1 and -mm2
Status: NEW
Severity: normal
Owner: akpm@digeo.com
Submitter: plars@austin.ibm.com
Distribution: Debian Woody
Hardware Environment: 4-way PIII 700, 4GB ram
Software Environment:
LTP-20030710
Gnu C 3.2.3
Gnu make 3.80
util-linux 2.11z
mount 2.11z
module-init-tools 2.4.21
e2fsprogs 1.34-WIP
PPP 2.4.1
nfs-utils 1.0.3
Linux C Library 2.3.1
Dynamic linker (ldd) 2.3.1
Procps 3.1.9
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.0
Problem Description: As of 2.6.0-test2-mm1, the ustat01 and ustat02 tests from
LTP return FAIL, but they do not fail in 2.6.0-test2 unpatched. I'm guessing
this is related to the 64bit dev_t patches? Is this something that glibc will
have to fix or is it ok to work around it in sys_ustat?
Steps to reproduce:
run ustat01 or ustat02 from LTP
reply other threads:[~2003-08-01 20:15 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=405500000.1059769131@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).