public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Chris Wright <chrisw@osdl.org>,
	linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: Re: [PATCH] add securityfs for all LSMs to use
Date: Wed, 6 Jul 2005 13:19:17 -0700	[thread overview]
Message-ID: <20050706201917.GB18969@kroah.com> (raw)
In-Reply-To: <200507062213.05337.ioe-lkml@rameria.de>

On Wed, Jul 06, 2005 at 10:12:59PM +0200, Ingo Oeser wrote:
> Hi Greg,
> 
> On Wednesday 06 July 2005 10:17, Greg KH wrote:
> > + * TODO:
> > + *   I think I can get rid of these default_file_ops, but not quite sure...
> > + */
> > +static ssize_t default_read_file(struct file *file, char __user *buf,
> > +				 size_t count, loff_t *ppos)
> > +{
> > +	return 0;
> > +}
> > +
> > +static ssize_t default_write_file(struct file *file, const char __user *buf,
> > +				   size_t count, loff_t *ppos)
> > +{
> > +	return count;
> > +}
> 
> Yes, you can get rid of both, if you move read_null and write_null from 
> drivers/char/mem.c to fs/libfs.c and export them.

That's not really necessary.

> But for what do you need a successful dummy read/write?

I don't.  I need a file_ops structure to give to my newly created dentry
before I assign the one passed in by the caller to it.  That's all.  I
could probably just pass it up the function stack to do it properly,
haven't really looked into it...

thanks,

greg k-h

  reply	other threads:[~2005-07-06 20:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06  8:17 [PATCH] add securityfs for all LSMs to use Greg KH
2005-07-06 20:12 ` Ingo Oeser
2005-07-06 20:19   ` Greg KH [this message]
2005-07-07  4:59 ` Mike Waychison
2005-07-07 21:31   ` Greg KH
2005-07-07 21:37 ` Greg KH

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=20050706201917.GB18969@kroah.com \
    --to=greg@kroah.com \
    --cc=chrisw@osdl.org \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.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