From: Jaegeuk Kim <jaegeuk@kernel.org>
To: nick <xerofoify@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs crypto: add rwsem to avoid data races
Date: Tue, 19 May 2015 17:38:59 -0700 [thread overview]
Message-ID: <20150520003859.GA55280@jaegeuk-mac02.mot.com> (raw)
In-Reply-To: <555B4A32.3000302@gmail.com>
On Tue, May 19, 2015 at 10:35:30AM -0400, nick wrote:
>
>
> On 2015-05-19 10:29 AM, Theodore Ts'o wrote:
> > On Mon, May 18, 2015 at 10:36:41PM -0700, Jaegeuk Kim wrote:
> >> Previoulsy, fi->i_crypt_info was not covered by any lock, resulting in
> >> memory leak.
> >>
> >> This patch adds a rwsem to avoid leaking objects on i_crypt_info.
> >>
> >> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> >
> > I'm not sure we need an rwsem to fix this issue. In terms of
> > serializing the creation and deletion of the structure, it should be
> > possible to use an cmpxchg() on the pointer itself. (e.g., if we lose
> > the race on the creation side, we just release our structure and use
> > the one that the winner allocated).
> >
> > If we do end up needing to serialize access to the tfm in the
> > i_crypt_info object for datapath reads/writes, then we might need a
> > mutex, but I think that should be it, no?
> >
> > - Ted
> >
> I have to agree with Ted here, as mutual exclusion locking is ideal
> for the scenario here of a reader vs writer exclusion. My only concern
What I'm saying is writer vs writer actually.
> is that can there be many readers to one writer here as if so reader/writer
> spin locks may be better.
I could write another patch using a rwlock by removing needless down_write for
f2fs_free_encryption_info.
Thanks,
> Nick
next prev parent reply other threads:[~2015-05-20 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 5:36 [PATCH] f2fs crypto: add rwsem to avoid data races Jaegeuk Kim
2015-05-19 14:29 ` Theodore Ts'o
2015-05-19 17:42 ` Jaegeuk Kim
[not found] ` <555B4A32.3000302@gmail.com>
2015-05-20 0:38 ` Jaegeuk Kim [this message]
2015-05-20 4:35 ` [f2fs-dev] " Theodore Ts'o
2015-05-20 4:55 ` Jaegeuk Kim
2015-05-20 12:38 ` Theodore Ts'o
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=20150520003859.GA55280@jaegeuk-mac02.mot.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xerofoify@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).