From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, tibor.tajti@gmail.com
Subject: Re: [GIT PULL] UDF tree fixes
Date: Mon, 1 Dec 2008 18:06:34 +0100 [thread overview]
Message-ID: <20081201170614.GA20279@duck.suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.0812010822060.3256@nehalem.linux-foundation.org>
On Mon 01-12-08 08:33:36, Linus Torvalds wrote:
>
>
> On Mon, 1 Dec 2008, Jan Kara wrote:
> >
> > Yes, I would like to do it as well. But as I write in the changelog,
> > currently there's no good callback for that (I've mailed about it at
> > linux-fsdevel and noone had a better idea either). So for now I've just
> > used this kludge to silence the Oops.
>
> No, I meant just a simple "just call clear_inode() from
> udf_clear_inode()". But on a slightly closer look I notice that won't
> work, since it will just cause recursion (well, you could just clear the
> s_op field to avoid it, but that would be uglier than your fix).
>
> I wonder if we should perhaps just move the invalidate_inode_buffers()
> call later in clear_inode(). That's a scary change, though.
>
> I just think your patch is pretty ugly. I'm sure it works, but I also
> suspect it indicates some kind of more fundamental problem. I also wonder
> why udf needs it but nobody else does (others do preallocation too)
UDF needs this because it does preallocation on directories (and I don't
know about other in-kernel fs which would do this). For regular files,
preallocation is dropped on the last close() but for directories I don't
know about such a good place so we do it in udf_clear_inode().
There used to be put_inode() callback which could be used for this but
Christoph Hellwig killed it in April.
Honza
prev parent reply other threads:[~2008-12-01 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 17:23 Jan Kara
2008-11-30 20:58 ` Linus Torvalds
2008-12-01 12:01 ` Jan Kara
2008-12-01 16:33 ` Linus Torvalds
2008-12-01 17:06 ` Jan Kara [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=20081201170614.GA20279@duck.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tibor.tajti@gmail.com \
--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®