From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: zanussi@comcast.net, jens.axboe@oracle.com, linux-kernel@vger.kernel.org
Subject: [PROBLEM] hard-lock with kmemtrace, relayfs, and splice
Date: Fri, 10 Oct 2008 12:42:03 +0300 [thread overview]
Message-ID: <1223631723.8959.46.camel@penberg-laptop> (raw)
In-Reply-To: <1223629803.8959.40.camel@penberg-laptop>
(I'm cc'ing Tom, Jens, and LKML.)
On Fri, 2008-10-10 at 12:10 +0300, Pekka Enberg wrote:
> > I'm seeing a hard lock on my machine when I run kmemtraced with the
> > following patch applied:
> >
> > http://git.kernel.org/?p=linux/kernel/git/penberg/slab-2.6.git;a=commitdiff;h=17ca1d5506b1db433f0b7167a627bfd55d319dd3
> >
> > I can enable/disable kmemtrace via the debugfs files fine and can also
> > read the relay files with cat.
> >
> > Any idea where this is coming from?
>
> OK, it's the first splice() call in reader_thread() that causes the
> hang. Hmm.
To recap, with a CONFIG_KMEMTRACE enabled kernel from the
"topic/kmemtrace" branch of:
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6.git topic/kmemtrace
running the "kmemtraced" program from
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/kmemtrace-user.git
results to a hard lock on my machine. I am unable to find anything
obviously wrong with it and as I can read/write the relay files just
fine, I'm beginning to think it's problem in relayfs splice
implementation.
Tom, thoughts?
Pekka
next prev parent reply other threads:[~2008-10-10 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 21:29 [ANNOUNCE] kmemtrace-user repo update Eduard - Gabriel Munteanu
[not found] ` <1223386477.28348.42.camel@penberg-laptop>
[not found] ` <1223623191.8959.26.camel@penberg-laptop>
[not found] ` <1223628687.8959.37.camel@penberg-laptop>
[not found] ` <1223629803.8959.40.camel@penberg-laptop>
2008-10-10 9:42 ` Pekka Enberg [this message]
2008-10-10 11:51 ` [PROBLEM] hard-lock with kmemtrace, relayfs, and splice Eduard - Gabriel Munteanu
2008-10-11 4:58 ` Tom Zanussi
2008-10-11 18:17 ` Eduard - Gabriel Munteanu
2008-10-13 6:57 ` Pekka Enberg
2008-10-14 4:03 ` Tom Zanussi
2008-10-14 5:13 ` Pekka Enberg
2008-10-14 5:46 ` Tom Zanussi
2008-10-14 6:58 ` Pekka Enberg
2008-10-14 7:30 ` Eduard - Gabriel Munteanu
2008-10-14 7:05 ` Pekka Enberg
2008-10-24 4:44 ` Peter Teoh
2008-10-24 14:15 ` Pekka Enberg
2008-10-25 0:56 ` Peter Teoh
2008-10-25 14:04 ` Eduard - Gabriel Munteanu
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=1223631723.8959.46.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=eduard.munteanu@linux360.ro \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@comcast.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