From: Oleg Drokin <green@namesys.com>
To: wolfgang.glas@ev-i.at
Cc: reiserfs-list@namesys.com
Subject: Re: kernel loop with lseek + LFS on reiser partition.
Date: Mon, 22 Apr 2002 13:35:46 +0400 [thread overview]
Message-ID: <20020422133546.A9019@namesys.com> (raw)
In-Reply-To: <OF3FAEC010.18270BFB-ONC1256BA3.002DB214@ev-i.at>
Hello!
On Mon, Apr 22, 2002 at 10:28:05AM +0200, wolfgang.glas@ev-i.at wrote:
> Running the program under SuSE7.3 with the folowing two kernels lets the
> process starve in an infineite loop inside the kernel (99% kernel CPU):
Ok, now having done more research, I must say it is not infinite loop
in fact:
green@angband:~/work/bugs> gcc -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -o t testprg.c
testprg.c: In function `main':
testprg.c:47: warning: use of `l' length character with `f' type character
testprg.c:54: warning: control reaches end of non-void function
green@angband:~/work/bugs> time ./t
real 6m20.958s
user 0m0.000s
sys 6m22.430s
I think this is because of expanding-truncate patch.
So, the real bug is this process cannot get interrupted until finished
which opens a window for resource-eating.
> No go with kill, kill -9...... Only reboot helps.
How long have you tried to wait?
Bye,
Oleg
next prev parent reply other threads:[~2002-04-22 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 8:28 kernel loop with lseek + LFS on reiser partition wolfgang.glas
2002-04-22 8:32 ` Oleg Drokin
2002-04-22 9:35 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 9:49 wolfgang.glas
2002-04-22 10:02 ` Oleg Drokin
2002-04-22 11:30 wolfgang.glas
2002-04-22 12:10 ` Oleg Drokin
[not found] <200204221910.16392.Dieter.Nuetzel@hamburg.de>
2002-04-23 4:58 ` Oleg Drokin
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=20020422133546.A9019@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=wolfgang.glas@ev-i.at \
/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.