From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alexander Viro <viro@math.psu.edu>
Cc: Gergely Tamas <dice@mfa.kfki.hu>, linux-kernel@vger.kernel.org
Subject: Re: OOPS with 2.4.5 [kernel BUG at inode.c:486]
Date: Wed, 30 May 2001 10:10:31 +0200 [thread overview]
Message-ID: <15124.43767.470515.182286@charged.uio.no> (raw)
In-Reply-To: <Pine.GSO.4.21.0105300328230.12645-100000@weyl.math.psu.edu>
In-Reply-To: <shssnhn47tl.fsf@charged.uio.no> <Pine.GSO.4.21.0105300328230.12645-100000@weyl.math.psu.edu>
>>>>> " " == Alexander Viro <viro@math.psu.edu> writes:
> On 30 May 2001, Trond Myklebust wrote:
>> Al: Is there any reason why the cases
>>
>> if (!inode->i_nlink)
>>
>> and the 'magic nfs path' should be treated differently?
>> Personally, I'd rather prefer to merge the 2.
> I don't think that it's a good idea. Why not fry the cache
> explicitly when you invalidate the inode?
Won't there be a race there? Imagine if some other process is busy
writing to that inode, and happens to add a new page after we've
truncated...
Cheers,
Trond
prev parent reply other threads:[~2001-05-30 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 17:03 Gergely Tamas
2001-05-29 17:30 ` Alexander Viro
2001-05-30 7:25 ` Trond Myklebust
2001-05-30 7:30 ` Alexander Viro
2001-05-30 8:10 ` Trond Myklebust [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=15124.43767.470515.182286@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=dice@mfa.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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®