From: Davide Libenzi <davidel@xmailserver.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [patch 1/13] signal/timer/event fds v7 - anonymous inode source ...
Date: Mon, 19 Mar 2007 18:38:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703191836230.3733@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <1174352866.13341.758.camel@localhost.localdomain>
On Tue, 20 Mar 2007, Thomas Gleixner wrote:
> > + error = -ENFILE;
> > + file = get_empty_filp();
> > + if (!file)
> > + goto eexit_1;
>
> make this "return -ENFILE;" please
Done
> > + inode = aino_getinode();
> > + if (IS_ERR(inode)) {
> > + error = PTR_ERR(inode);
> > + goto eexit_2;
>
> Can you please use a bit more descriptive labels ?
>
> e.g:
> goto out_filp;
Done
> > +static int ainofs_delete_dentry(struct dentry *dentry)
> > +{
> > + /*
> > + * We faked vfs to believe the dentry was hashed when we created it.
> > + * Now we restore the flag so that dput() will work correctly.
> > + */
> > + dentry->d_flags |= DCACHE_UNHASHED;
> > + return 1;
> > +}
>
> Please put either "struct ainofs_dentry_operations ..." below the next
> function or move ainofs_delete_dentry() above "struct
> ainofs_dentry_operations ..."
>
> It's annoying to lookup the protoypes and implemenation back and forth.
I prefer to have all data declarations at the beginning. but if you can
manage to have that requirement in the Coding Style, I'll change it ;)
> > +static struct inode *aino_getinode(void)
> > +{
> > + return igrab(aino_inode);
> > +}
>
> Please use "igrab(aino_inode);" directly in this one single place above.
> That saves us a prototype and an useless static function with no value.
Done
> > +/*
> > + * A single inode exist for all aino files. On the contrary of pipes,
> > + * aino inodes has no per-instance data associated, so we can avoid
> > + * the allocation of multiple of them.
> > + */
> > +static struct inode *aino_mkinode(void)
> > +{
> > + int error = -ENOMEM;
> > + struct inode *inode = new_inode(aino_mnt->mnt_sb);
> > +
> > + if (!inode)
> > + goto eexit_1;
>
> return ERR_PTR(-ENOMEM);
Done
> > + aino_mnt = kern_mount(&aino_fs_type);
> > + if (IS_ERR(aino_mnt))
> > + goto epanic;
> > +
> > + aino_inode = aino_mkinode();
> > + if (IS_ERR(aino_inode))
> > + goto epanic;
> > +
> > + return 0;
> > +
> > +epanic:
> > + panic("aino_init() failed\n");
>
> Panic ? It's not life critical - is it ?
>
> A printk(KERN_ERR...) and a return -Exx would be sufficient.
Done.
- Davide
prev parent reply other threads:[~2007-03-20 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 23:47 Davide Libenzi
2007-03-20 1:07 ` Thomas Gleixner
2007-03-20 1:38 ` Davide Libenzi [this message]
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=Pine.LNX.4.64.0703191836230.3733@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.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
all inboxes | Powered by JetHome®