From: Earl Chew <earl_chew@agilent.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: fs/pipe.c null pointer dereference
Date: Thu, 15 Oct 2009 20:39:58 -0700 [thread overview]
Message-ID: <4AD7EB0E.7000309@agilent.com> (raw)
In-Reply-To: <4AD7E928.9000701@agilent.com>
Earl Chew wrote:
> Is this possible via /proc/pid/fd/* ?
The window for failure is small. It's easiest to reproduce
this problem by stalling pipe_rdwr_open() to open up the
window:
--- pipe.c.orig 2009-10-15 20:33:53.000000000 -0700
+++ pipe.c 2009-10-15 20:17:40.000000000 -0700
@@ -736,2 +736,3 @@
{
+ msleep(100);
mutex_lock(&inode->i_mutex);
With the failure window widened, it's easy to reproduce
the failure with:
--------------------------------------------------------------
#!/bin/sh
while : ; do
{ echo y ; sleep 1 ; } | { while read ; do echo z$REPLY; done ; } &
PID=$!
OUT=$(ps -efl | grep 'sleep 1' | grep -v grep |
{ read PID REST ; echo $PID; } )
OUT="${OUT%% *}"
DELAY=$((RANDOM * 1000 / 32768))
usleep $((DELAY * 1000 + RANDOM % 1000 ))
echo n > /proc/$OUT/fd/1
done
--------------------------------------------------------------
prev parent reply other threads:[~2009-10-16 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 13:39 fs/pipe.c null pointer dereference Earl Chew
2009-10-14 14:53 ` Frans Pop
2009-10-14 22:50 ` Earl Chew
2009-10-15 0:11 ` Frans Pop
2009-10-16 4:27 ` Earl Chew
2009-10-16 7:16 ` Pekka Enberg
2009-10-16 14:51 ` Earl Chew
2009-10-16 3:31 ` Earl Chew
2009-10-16 3:39 ` Earl Chew [this message]
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=4AD7EB0E.7000309@agilent.com \
--to=earl_chew@agilent.com \
--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