From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Anton Salikhmetov <salikhmetov@gmail.com>
Cc: linux-mm@kvack.org, jakob@unthought.net,
linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu,
riel@redhat.com, ksm@42.dk, staubach@redhat.com,
jesper.juhl@gmail.com
Subject: Re: [PATCH 2/2][RFC][BUG] msync: updating ctime and mtime at syncing
Date: Sat, 12 Jan 2008 14:09:01 +0100 [thread overview]
Message-ID: <1200143342.7999.25.camel@lappy> (raw)
In-Reply-To: <4df4ef0c0801120438n4a3c1cfpd3563531929a1a91@mail.gmail.com>
On Sat, 2008-01-12 at 15:38 +0300, Anton Salikhmetov wrote:
> 2008/1/12, Peter Zijlstra <a.p.zijlstra@chello.nl>:
> >
> > On Sat, 2008-01-12 at 10:36 +0100, Peter Zijlstra wrote:
> > > On Fri, 2008-01-11 at 03:44 +0300, Anton Salikhmetov wrote:
> > >
> > > > +/*
> > > > + * Update the ctime and mtime stamps after checking if they are to be updated.
> > > > + */
> > > > +void mapped_file_update_time(struct file *file)
> > > > +{
> > > > + if (test_and_clear_bit(AS_MCTIME, &file->f_mapping->flags)) {
> > > > + get_file(file);
> > > > + file_update_time(file);
> > > > + fput(file);
> > > > + }
> > > > +}
> > > > +
> > >
> > > I don't think you need the get/put file stuff here, because
> >
> > BTW, the reason for me noticing this is that if it would be needed there
> > is a race condition right there, who is to say that the file pointer
> > you're deref'ing in your test condition isn't a dead one already.
>
> So, in your opinion, is it at all needed here to play with the file reference
> counter? May I drop the get_file() and fput() calls from the
> sys_msync() function?
No, the ones in sys_msync() around calling do_fsync() are most
definately needed because we release mmap_sem there.
What I'm saying is that you can remove the get_file()/fput() calls from
your new mapped_file_update_time() function.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Anton Salikhmetov <salikhmetov@gmail.com>
Cc: linux-mm@kvack.org, jakob@unthought.net,
linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu,
riel@redhat.com, ksm@42.dk, staubach@redhat.com,
jesper.juhl@gmail.com
Subject: Re: [PATCH 2/2][RFC][BUG] msync: updating ctime and mtime at syncing
Date: Sat, 12 Jan 2008 14:09:01 +0100 [thread overview]
Message-ID: <1200143342.7999.25.camel@lappy> (raw)
In-Reply-To: <4df4ef0c0801120438n4a3c1cfpd3563531929a1a91@mail.gmail.com>
On Sat, 2008-01-12 at 15:38 +0300, Anton Salikhmetov wrote:
> 2008/1/12, Peter Zijlstra <a.p.zijlstra@chello.nl>:
> >
> > On Sat, 2008-01-12 at 10:36 +0100, Peter Zijlstra wrote:
> > > On Fri, 2008-01-11 at 03:44 +0300, Anton Salikhmetov wrote:
> > >
> > > > +/*
> > > > + * Update the ctime and mtime stamps after checking if they are to be updated.
> > > > + */
> > > > +void mapped_file_update_time(struct file *file)
> > > > +{
> > > > + if (test_and_clear_bit(AS_MCTIME, &file->f_mapping->flags)) {
> > > > + get_file(file);
> > > > + file_update_time(file);
> > > > + fput(file);
> > > > + }
> > > > +}
> > > > +
> > >
> > > I don't think you need the get/put file stuff here, because
> >
> > BTW, the reason for me noticing this is that if it would be needed there
> > is a race condition right there, who is to say that the file pointer
> > you're deref'ing in your test condition isn't a dead one already.
>
> So, in your opinion, is it at all needed here to play with the file reference
> counter? May I drop the get_file() and fput() calls from the
> sys_msync() function?
No, the ones in sys_msync() around calling do_fsync() are most
definately needed because we release mmap_sem there.
What I'm saying is that you can remove the get_file()/fput() calls from
your new mapped_file_update_time() function.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-12 13:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1200006638.19293.42.camel@codedot>
2008-01-11 0:38 ` [PATCH 1/2][RFC][BUG] msync: massive code cleanup of sys_msync() Anton Salikhmetov
2008-01-11 0:38 ` Anton Salikhmetov, Anton Salikhmetov
2008-01-11 15:55 ` Rik van Riel
2008-01-11 15:55 ` Rik van Riel
2008-01-11 0:38 ` [PATCH 2/2][RFC][BUG] msync: updating ctime and mtime at syncing Anton Salikhmetov
2008-01-11 16:03 ` Rik van Riel
2008-01-11 0:44 ` Anton Salikhmetov
2008-01-11 0:44 ` Anton Salikhmetov, Anton Salikhmetov
2008-01-11 18:55 ` Peter Staubach
2008-01-11 18:55 ` Peter Staubach
2008-01-11 19:29 ` Anton Salikhmetov
2008-01-11 19:29 ` Anton Salikhmetov
2008-01-11 18:59 ` Peter Staubach
2008-01-11 21:40 ` Anton Salikhmetov
2008-01-11 21:40 ` Anton Salikhmetov
2008-01-11 21:59 ` Peter Staubach
2008-01-11 21:59 ` Peter Staubach
2008-01-11 22:15 ` Anton Salikhmetov
2008-01-11 22:15 ` Anton Salikhmetov
2008-01-12 2:24 ` Anton Salikhmetov
2008-01-12 2:24 ` Anton Salikhmetov
2008-01-12 9:36 ` Peter Zijlstra
2008-01-12 9:36 ` Peter Zijlstra
2008-01-12 9:40 ` Peter Zijlstra
2008-01-12 9:40 ` Peter Zijlstra
2008-01-12 12:38 ` Anton Salikhmetov
2008-01-12 12:38 ` Anton Salikhmetov
2008-01-12 13:09 ` Peter Zijlstra [this message]
2008-01-12 13:09 ` Peter Zijlstra
2008-01-12 13:51 ` Anton Salikhmetov
2008-01-12 13:51 ` Anton Salikhmetov
2008-01-12 12:17 ` Anton Salikhmetov
2008-01-12 12:17 ` Anton Salikhmetov
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=1200143342.7999.25.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jakob@unthought.net \
--cc=jesper.juhl@gmail.com \
--cc=ksm@42.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=salikhmetov@gmail.com \
--cc=staubach@redhat.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.