mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: [LTP] VFS: brelse: started after 2.4.10-ac7
Date: Tue, 9 Oct 2001 09:47:07 -0400	[thread overview]
Message-ID: <20011009094707.B4951@earthlink.net> (raw)


About 2 minutes into "runalltests.sh" on ltp, ac kernels after 2.4.10-ac7
give a message like:

Oct  9 01:55:09 rushmore kernel: VFS: brelse: Trying to free free buffer
Oct  9 01:55:09 rushmore kernel: VFS: brelse: Trying to free free buffer

Repeatability:   Good

Seen on:

2.4.10-ac8
2.4.10-ac10
2.4.10-ac10+eatcache

Not seen on:

2.4.10-ac4
2.4.10-ac7
2.4.11-pre2
2.4.11-pre6

Has occurred on every case with ac8 and ac10, and no test before.  

Doesn't happen on Linus kernels.

Does not occur on my laptop, which is ext2 only.

Did not occur on Athlon when /tmp was mounted as ext2.  
(LTP tests write a lot of files to /tmp).


I haven't tracked down which test generates the message yet, but it is
before the "personality" tests.


Configuration
-------------

Linux rushmore 2.4.10-ac10a #2 Tue Oct 9 00:42:57 EDT 2001 i686 unknown

Gnu C                  2.95.3
Gnu make               3.79.1
binutils               2.11.2
util-linux             2.11l
mount                  2.11l
modutils               2.4.10
e2fsprogs              1.25
reiserfsprogs          3.x.0j
PPP                    2.4.1
Linux C Library        2.2.4
Dynamic linker (ldd)   2.2.4
Procps                 2.0.7
Net-tools              1.60
Kbd                    1.06
Sh-utils               2.0
Modules Loaded         cmpci ppp_deflate bsd_comp ppp_async ipt_state ipt_limit ipt_MASQUERADE iptable_nat ip_conntrack iptable_filter ip_tables



-- 
Randy Hron


             reply	other threads:[~2001-10-09 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 13:47 rwhron [this message]
2001-10-09 13:50 ` Nikita Danilov
2001-10-09 13:55 ` Chris Mason
2001-10-09 14:14 ` Alan Cox

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=20011009094707.B4951@earthlink.net \
    --to=rwhron@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    /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®