From: Martin Zwickel <martin.zwickel@technotrend.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.0-t3: vfs/ext3 do_lookup bug?!
Date: Wed, 20 Aug 2003 17:14:31 +0200 [thread overview]
Message-ID: <20030820171431.0211930e.martin.zwickel@technotrend.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]
Hi there!
Today I wanted to check out some src-files from cvs.
But my fault was, that I ran cvs twice at the same time.
so two "cvs upd -d -A" are now in 'D' state.
I think they got stuck because both tried to access the same file.
#ps lax
4 0 11833 11832 15 0 4136 2664 down D pts/18 0:07 cvs upd -d -A
4 0 11933 11932 22 0 2672 1180 down D pts/19 0:00 cvs upd -d -A
#sysrq-t + dmesg:
cvs D 00000196 294197680 11833 11832 (NOTLB)
dc84de5c 00000082 d2314a0c 00000196 d23148fc dc84de58 cafba080 cccee770
00000282 cafba080 cccee778 c0107f8e 00000001 cafba080 c0119687 d49d3e94
cccee778 dc84de7c 00000000 d919a9f0 00000000 cccee770 cccee708 d919a980
Call Trace:
[<c0107f8e>] __down+0x7c/0xc7
[<c0119687>] default_wake_function+0x0/0x2e
[<c0108118>] __down_failed+0x8/0xc
[<c0159df3>] .text.lock.namei+0x5/0x16a
[<c0156c98>] do_lookup+0x96/0xa1
[<c0157077>] link_path_walk+0x3d4/0x762
[<c0157c57>] open_namei+0x8e/0x3f3
[<c014a265>] filp_open+0x43/0x69
[<c014a64c>] sys_open+0x5b/0x8b
[<c0109063>] syscall_call+0x7/0xb
cvs D C8E86424 297794096 11933 11932 (NOTLB)
d49d3e80 00000086 c03a561b c8e86424 00000001 d092d408 c2dd2080 cccee770
00000286 c2dd2080 cccee778 c0107f8e 00000001 c2dd2080 c0119687 cccee778
dc84de70 d49d3f38 dffe46c0 d49d3ee4 00000000 cccee770 cccee708 d919a980
Call Trace:
[<c0107f8e>] __down+0x7c/0xc7
[<c0119687>] default_wake_function+0x0/0x2e
[<c0108118>] __down_failed+0x8/0xc
[<c0159df3>] .text.lock.namei+0x5/0x16a
[<c0156c98>] do_lookup+0x96/0xa1
[<c0157077>] link_path_walk+0x3d4/0x762
[<c015783c>] __user_walk+0x49/0x5e
[<c0149be1>] sys_access+0x93/0x150
[<c015393d>] sys_stat64+0x37/0x39
[<c0109063>] syscall_call+0x7/0xb
So is it a kernel bug? the down in do_lookup shouldn't lock the process
forever...
Regards,
Martin
--
MyExcuse:
The salesman drove over the CPU board.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-08-20 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 15:14 Martin Zwickel [this message]
2003-08-20 18:36 ` Andrew Morton
2003-08-20 19:06 ` Linus Torvalds
2003-08-21 6:33 ` Martin Zwickel
2003-08-21 6:41 ` Andrew Morton
2003-08-21 7:25 ` Martin Zwickel
2003-08-21 7:40 ` Andrew Morton
2003-08-21 8:32 ` Martin Zwickel
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=20030820171431.0211930e.martin.zwickel@technotrend.de \
--to=martin.zwickel@technotrend.de \
--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
all inboxes | Powered by JetHome®