From: Brent Casavant <bcasavan@sgi.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, Christoph Rohland <cr@sap.com>,
Robin Holt <holt@sgi.com>, "Adam J. Richter" <adam@yggdrasil.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] shmem: restore superblock info
Date: Mon, 6 Jun 2005 15:36:39 -0500 (CDT) [thread overview]
Message-ID: <20050606153515.H19925@chenjesu.americas.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506062122500.5122@goblin.wat.veritas.com>
On Mon, 6 Jun 2005, Hugh Dickins wrote:
> On Mon, 6 Jun 2005, Brent Casavant wrote:
> > On Mon, 6 Jun 2005, Hugh Dickins wrote:
> >
> > > @@ -1607,15 +1582,17 @@ static int shmem_statfs(struct super_blo
> > > - if (sbinfo) {
> > > - spin_lock(&sbinfo->stat_lock);
> > > + spin_lock(&sbinfo->stat_lock);
> ...
> >
> > This is the only change I'm at all concerned about.
>
> Thanks for noticing, I hadn't really considered that.
>
> > I'm not sure how frequent statfs operations occur in practice (I suspect
> > infrequently),
>
> Infrequently, yes. I think infrequently to the point of never in
> the case that concerns you: correct if I'm wrong, someone, but I think
> there's actually no handle by which user can statfs shm's internal mount.
Ah, that's an even better point, which I had failed to consider. Consider
my concerns duly nullified. :)
Thanks for CC'ing me on the change.
Brent
--
Brent Casavant If you had nothing to fear,
bcasavan@sgi.com how then could you be brave?
Silicon Graphics, Inc. -- Queen Dama, Source Wars
prev parent reply other threads:[~2005-06-06 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 19:46 Hugh Dickins
2005-06-06 20:18 ` Brent Casavant
2005-06-06 20:30 ` Hugh Dickins
2005-06-06 20:36 ` Brent Casavant [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=20050606153515.H19925@chenjesu.americas.sgi.com \
--to=bcasavan@sgi.com \
--cc=adam@yggdrasil.com \
--cc=akpm@osdl.org \
--cc=cr@sap.com \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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®