All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org, lord@sgi.com
Subject: Re: 2.4.20pre5aa1
Date: Thu, 5 Sep 2002 20:02:40 +0100	[thread overview]
Message-ID: <20020905200240.A12253@infradead.org> (raw)
In-Reply-To: <20020905185917.GG1657@dualathlon.random>; from andrea@suse.de on Thu, Sep 05, 2002 at 08:59:17PM +0200

On Thu, Sep 05, 2002 at 08:59:17PM +0200, Andrea Arcangeli wrote:
> > I think we should take the XFS-specific inode lock around vmtruncate.
> > Need to double-check with Steve.
> 
> this is the function I'm looking at and it's called with xfs specific
> inode lock, and I don't see it grabbed either before calling vmtruncate:

should != do

we either need to use your accessors for i_size or take the XFS inode
lock around vmtruncate.

  reply	other threads:[~2002-09-05 18:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 23:35 2.4.20pre5aa1 Andrea Arcangeli
2002-09-04 23:56 ` 2.4.20pre5aa1 Andrew Morton
2002-09-05  0:25   ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 12:44 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 16:53   ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 17:09     ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:41       ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 18:46         ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:59           ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:02             ` Christoph Hellwig [this message]
2002-09-05 19:13               ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:17                 ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 18:48         ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:06           ` 2.4.20pre5aa1 Andrea Arcangeli
2002-09-05 19:15             ` 2.4.20pre5aa1 Christoph Hellwig
2002-09-05 19:26               ` 2.4.20pre5aa1 Christoph Hellwig

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=20020905200240.A12253@infradead.org \
    --to=hch@infradead.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.