From: Raj <raju@mailandnews.com>
To: Tore Anderson <tore@linpro.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] scheduling while atomic when lseek()ing in /proc/net/tcp
Date: Fri, 28 Nov 2003 11:49:34 +0530 [thread overview]
Message-ID: <3FC6E8F6.80008@mailandnews.com> (raw)
In-Reply-To: <1069974335.14367.17.camel@echo.linpro.no>
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]
Tore Anderson wrote:
> Hi,
>
> The following code instantly freezes my all of my machines running
> any of the beavers:
>
>
The following patch fixed this, but i am _not_not_not sure whether this
is the right way to do.
Any ideas folks ?
/Raj
[-- Attachment #2: lseek_crash.patch --]
[-- Type: text/plain, Size: 294 bytes --]
--- seq_file.c.org 2003-11-28 11:12:28.000000000 +0530
+++ seq_file.c 2003-11-28 11:44:44.968883784 +0530
@@ -213,6 +213,9 @@
switch (origin) {
case 1:
offset += file->f_pos;
+ if(offset >= 0)
+ retval = file->f_pos = offset;
+ break;
case 0:
if (offset < 0)
break;
next prev parent reply other threads:[~2003-11-28 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 23:05 [BUG] scheduling while atomic when lseek()ing in /proc/net/tcp Tore Anderson
2003-11-28 6:19 ` Raj [this message]
2003-11-28 17:12 ` OGAWA Hirofumi
2003-11-30 4:42 ` David S. Miller
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=3FC6E8F6.80008@mailandnews.com \
--to=raju@mailandnews.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tore@linpro.no \
/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;
as well as URLs for NNTP newsgroup(s).