From: Christoph Hellwig <hch@lst.de>
To: Steven French <sfrench@us.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: remove useless cargo-cult checks
Date: Wed, 7 Mar 2007 23:17:46 +0100 [thread overview]
Message-ID: <20070307221746.GA3620@lst.de> (raw)
In-Reply-To: <OF8579A98D.13CFCC0A-ON87257297.006728AA-86257297.006794F0@us.ibm.com>
On Wed, Mar 07, 2007 at 12:51:04PM -0600, Steven French wrote:
> > file->f_path.dentry or file->f_path.dentry.d_inode can't be NULL
>
> OK - I don't really mind removing these checks - and I agree that I there
> is not an obvious way that they can be null, yet we had a case in which
> file->f_dentry was reported as NULL a few years back in a bug report that
> we could not reproduce.
There's a good reason you couldn't reproduce it, because it most likely
must have been a really bad hack in the submitters kernel. Setting
up file->f_dentry is one of the first thing we do after allocating the
file struct.
>
> The change to f_path.dentry did hit all filesystems (not sure who did it
> last year) and that patch did hit lkml - so this is not something new that
> just slipped in.
I know - that patch just made the enormous amount of useless checks
vissible.
> Is there an easy way to mirror particular patches going into the
> cifs-2.6.git tree (which is pulled into mm) to lkml?
Maybe some git expert can comment on that.
> The cifs patches go in mm for at least a week before they go into kernel
> but some of them I would like to post again to lkml.
polling -mm is a little hard as it's an enormous blob, so posting to
lkml or -fsdevel would definitively be quite helpfull.
next prev parent reply other threads:[~2007-03-07 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 15:29 [PATCH] cifs: remove useless cargo-cult checks Christoph Hellwig
[not found] ` <OF8579A98D.13CFCC0A-ON87257297.006728AA-86257297.006794F0@us.ibm.com>
2007-03-07 22:17 ` Christoph Hellwig [this message]
2007-03-07 22:27 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 0:49 Steve French
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=20070307221746.GA3620@lst.de \
--to=hch@lst.de \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.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