From: Arjan van de Ven <arjan@infradead.org>
To: selvakumar nagendran <kernelselva@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug_reply : Out of range ptr error in module indicates bug in slab.c
Date: Thu, 30 Dec 2004 13:18:10 +0100 [thread overview]
Message-ID: <1104409090.4170.12.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20041230121310.41867.qmail@web60605.mail.yahoo.com>
On Thu, 2004-12-30 at 04:13 -0800, selvakumar nagendran wrote:
>
> Thanks for ur help. The user will be changing
> this using system calls like dup,dup2 etc. If I keep
> track of all these modifications by intercepting all
> those syscalls and use inode number for identifying
> the structure uniquely, will it break?
it sure is not a reliable method. The user can change the fd's YOU log.
So your logging is inaccurate. That may or may not be a problem, it
depends on what the application of this is.
next prev parent reply other threads:[~2004-12-30 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 10:54 Bug " selvakumar nagendran
2004-12-30 11:18 ` Arjan van de Ven
2004-12-30 12:13 ` Bug_reply " selvakumar nagendran
2004-12-30 12:18 ` Arjan van de Ven [this message]
2004-12-31 6:51 ` Interception for a resource based scheduler selvakumar nagendran
2004-12-31 7:48 ` Arjan van de Ven
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=1104409090.4170.12.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=kernelselva@yahoo.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
all inboxes | Powered by JetHome®