From: Jens Axboe <axboe@suse.de>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: Andrew Morton <akpm@osdl.org>,
michael.kerrisk@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: splice/tee bugs?
Date: Fri, 7 Jul 2006 14:28:50 +0200 [thread overview]
Message-ID: <20060707122850.GU4188@suse.de> (raw)
In-Reply-To: <20060707120333.GR4188@suse.de>
On Fri, Jul 07 2006, Jens Axboe wrote:
> On Fri, Jul 07 2006, Michael Kerrisk wrote:
> > > > c) Occasionally the command line just hangs, producing no output.
> > > > In this case I can't kill it with ^C or ^\. This is a
> > > > hard-to-reproduce behaviour on my (x86) system, but I have
> > > > seen it several times by now.
> > >
> > > aka local DoS. Please capture sysrq-T output next time.
> >
> > I don't have sysrq configured in the kernel that I'm testing at
> > the moment (I'll build again with sysrq), but have just got
> > the error again. For what it's worth, "ps l" says:
> >
> > F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
> > 0 1000 7099 630 16 0 0 0 - D+ pts/30 0:00 [ktee]
>
> Try ps -eo cmd,wchan, it should give you a little more at least. But
> sysrq-t is the best, of course.
>
> I'll see about reproducing locally.
With your modified ktee, I can reproduce it here. Here's the ktee and wc
output:
ktee2 D 00000002 0 10027 3182 10028 (L-TLB)
f5cd7da0 00000002 f5cd7d8c 00000002 f5cd7d48 c0148c1e f5cd7d58
c18a5914
c03edc80 c19a9f50 00000007 00000000 c1ff1ab0 b5d39d0a 0000003a
067a9ddd
c1ff1bc0 c19aa720 00000000 00000000 06d4480b 00000000 c0474880
c0474880
Call Trace:
[<c0389114>] __mutex_lock_slowpath+0x95/0x236
[<c03892d1>] mutex_lock+0x1c/0x1f
[<c016cff7>] pipe_read_fasync+0x24/0x57
[<c016d2d4>] pipe_read_release+0x12/0x23
[<c01623c7>] __fput+0x53/0x141
[<c016250e>] fput+0x19/0x1c
[<c015fc84>] filp_close+0x41/0x67
[<c0121c1a>] put_files_struct+0xa6/0xb8
[<c0122d06>] do_exit+0x124/0x8dd
[<c01045a7>] do_trap+0x0/0x9e
[<c01179d9>] do_page_fault+0x274/0x586
[<c0103b6d>] error_code+0x39/0x40
[<c0103039>] sysenter_past_esp+0x56/0x79
wc D C1DB7F74 0 10028 3182 10027 (NOTLB)
c1db7ec8 00000002 c1db7eb4 c1db7f74 00000246 00000101 00000001
00000000
00000003 c1db7f68 00000007 00000001 f6351ab0 af26d8c3 0000003a
0011c727
f6351bc0 c19b2720 00000002 00000044 001ce734 00000000 c0474880
c0474880
Call Trace:
[<c0389114>] __mutex_lock_slowpath+0x95/0x236
[<c03892d1>] mutex_lock+0x1c/0x1f
[<c016d910>] pipe_readv+0x54/0x3a9
[<c016dc84>] pipe_read+0x1f/0x21
[<c0161bbf>] vfs_read+0x85/0xf6
[<c0162048>] sys_read+0x3d/0x64
[<c0103039>] sysenter_past_esp+0x56/0x79
I'll dig around.
--
Jens Axboe
next prev parent reply other threads:[~2006-07-07 12:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 7:07 splice/tee bugs? Michael Kerrisk
2006-07-07 11:07 ` Andrew Morton
2006-07-07 11:42 ` Michael Kerrisk
2006-07-07 12:03 ` Jens Axboe
2006-07-07 12:28 ` Jens Axboe [this message]
2006-07-07 12:31 ` Michael Kerrisk
2006-07-07 12:41 ` Jens Axboe
2006-07-07 13:12 ` Jens Axboe
2006-07-07 13:14 ` Jens Axboe
2006-07-07 13:21 ` Arjan van de Ven
2006-07-07 13:26 ` Jens Axboe
2006-07-07 13:54 ` Paulo Marques
2006-07-07 14:02 ` Jens Axboe
2006-07-07 14:05 ` Michael Kerrisk
2006-07-07 14:08 ` Jens Axboe
2006-07-07 16:13 ` Luiz Fernando N. Capitulino
2006-07-07 21:43 ` Luiz Fernando N. Capitulino
2006-07-08 6:41 ` Jens Axboe
2006-07-08 21:09 ` Luiz Fernando N. Capitulino
2006-07-09 10:36 ` Jens Axboe
2006-07-09 11:16 ` Jens Axboe
2006-07-09 16:47 ` Luiz Fernando N. Capitulino
2006-07-09 17:57 ` Jens Axboe
2006-07-10 6:25 ` Michael Kerrisk
2006-07-10 6:43 ` Jens Axboe
2006-07-10 8:09 ` Michael Kerrisk
2006-07-10 8:24 ` Jens Axboe
2006-07-10 8:40 ` Michael Kerrisk
2006-07-10 8:46 ` Jens Axboe
2006-07-10 8:50 ` Michael Kerrisk
2006-07-10 9:06 ` Jens Axboe
2006-07-10 9:08 ` Michael Kerrisk
2006-07-10 8:50 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2006-07-08 5:33 Chuck Ebbert
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=20060707122850.GU4188@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-manpages@gmx.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 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.