From: Prasanna S Panchamukhi <prasanna@in.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Christoph Hellwig <hch@lst.de>,
akpm@osdl.org, linux-fsdevel@vger.kernel.org, suparna@in.ibm.com,
maneesh@in.ibm.com, jkenisto@us.ibm.com
Subject: Re: [PATCH] mark address_space_operations const
Date: Tue, 9 May 2006 12:54:57 +0530 [thread overview]
Message-ID: <20060509072457.GA12379@in.ibm.com> (raw)
In-Reply-To: <20060509055636.GA25575@kroah.com>
On Mon, May 08, 2006 at 10:56:36PM -0700, Greg KH wrote:
> On Tue, May 09, 2006 at 11:00:39AM +0530, Prasanna S Panchamukhi wrote:
> > On Wed, May 03, 2006 at 03:18:36PM +0200, Christoph Hellwig wrote:
> > > Same as with already do with the file operations:
> > > keep them in .rodata and prevents people from doing runtime patching.
> >
> > I understand that making file operations .rodata was
> > to prevent binary driver authors overriding individual
> > file_operations members at runtime.
> >
> > This patch prevents even GPL code from overriding address_space
> > operations. There might be in kernel users who want to override
> > address_space operations.
>
> Are there any existing in-kernel users who wish to override these
> operations?
>
Current prototype of user-space probes uses this feature.
http://lkml.org/lkml/2006/5/9/32
Thanks
Prasanna
--
Prasanna S Panchamukhi
Linux Technology Center
India Software Labs, IBM Bangalore
Email: prasanna@in.ibm.com
Ph: 91-80-41776329
next prev parent reply other threads:[~2006-05-09 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 13:18 [PATCH] mark address_space_operations const Christoph Hellwig
2006-05-09 5:30 ` Prasanna S Panchamukhi
2006-05-09 5:56 ` Greg KH
2006-05-09 7:24 ` Prasanna S Panchamukhi [this message]
2006-05-09 9:13 ` Christoph Hellwig
2006-05-12 11:20 ` Andrew Morton
2006-05-12 18:35 ` [PATCH] CIFS: Do not overwrite aops elements Dave Kleikamp
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=20060509072457.GA12379@in.ibm.com \
--to=prasanna@in.ibm.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=jkenisto@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=suparna@in.ibm.com \
/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).