From: Andrew Morton <akpm@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [patch 1/13] signal/timer/event fds v8 - anonymous inode source ...
Date: Fri, 30 Mar 2007 16:08:50 -0700 [thread overview]
Message-ID: <20070330160850.d7988a87.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703301532500.3721@alien.or.mcafeemobile.com>
On Fri, 30 Mar 2007 15:44:15 -0700 (PDT)
Davide Libenzi <davidel@xmailserver.org> wrote:
> On Fri, 30 Mar 2007, Andrew Morton wrote:
>
> > > +#include <asm/uaccess.h>
> > > +
> > > +
> > > +
> >
> > Too many blank lines
>
> It'd be interesting to know how much is enough. You use one, ppl says it
> is too dense. You use more, ppl says it's too much.
> There's the one-line rule for inter-function spacing, but what's the
> include-functions ones? Or the functions-data ones?
>
less ;)
>
> > > +static int __init aino_init(void)
> > > +{
> > > + int error;
> > > +
> > > + error = register_filesystem(&aino_fs_type);
> > > + if (error)
> > > + goto err_exit;
> > > + aino_mnt = kern_mount(&aino_fs_type);
> > > + if (IS_ERR(aino_mnt)) {
> > > + error = PTR_ERR(aino_mnt);
> > > + goto err_unregister_filesystem;
> > > + }
> > > + aino_inode = aino_mkinode();
> > > + if (IS_ERR(aino_inode)) {
> > > + error = PTR_ERR(aino_inode);
> > > + goto err_mntput;
> > > + }
> > > +
> > > + return 0;
> > > +
> > > +err_mntput:
> > > + mntput(aino_mnt);
> > > +err_unregister_filesystem:
> > > + unregister_filesystem(&aino_fs_type);
> > > +err_exit:
> > > + printk(KERN_ERR "aino_init() failed (%d)\n", error);
> >
> > I suspect this is panic time?
>
> Ok, it was panincing, and someone made me change it. Would you please
> agree?
> The system can survive w/out, but it'll be a broken system WRT userspace.
I'd say panic. There's no much point in limping along with an
incorrectly-working kernel, only to have some small number of apps fail
mysteriously later on.
> >
> > Can we make this optional if CONFIG_EMBEDDED? You plan on converting epoll
> > to use this facility, but with CONFIG_EPOLL=n, this is all dead code?
>
> Hmmm, the whole point is that all this stuff works with or without epoll.
> And epoll need no changes to support this.
I'm suggesting that all known clients of anon_inode be made optional.
Hence anon_iode can become optional too.
It's a desirable objective, at least. The default, really.
next prev parent reply other threads:[~2007-03-30 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 18:37 [patch 1/13] signal/timer/event fds v8 - anonymous inode source Davide Libenzi
2007-03-30 19:39 ` Andrew Morton
2007-03-30 22:44 ` Davide Libenzi
2007-03-30 23:02 ` Randy Dunlap
2007-03-30 23:08 ` Andrew Morton [this message]
2007-03-31 1:29 ` Davide Libenzi
2007-03-31 2:24 ` Linus Torvalds
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=20070330160850.d7988a87.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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