From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Pavel Reichl <preichl@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v9 4/4] xfs: replace mrlock_t with rw_semaphores
Date: Wed, 7 Oct 2020 08:25:54 -0700 [thread overview]
Message-ID: <20201007152554.GL49559@magnolia> (raw)
In-Reply-To: <066ebfa6-25a2-aee4-a01c-3803ef716361@sandeen.net>
On Wed, Oct 07, 2020 at 09:17:13AM -0500, Eric Sandeen wrote:
> On 10/6/20 8:21 PM, Darrick J. Wong wrote:
> > On Tue, Oct 06, 2020 at 09:15:41PM +0200, Pavel Reichl wrote:
> >> Remove mrlock_t as it does not provide any extra value over
> >> rw_semaphores. Make i_lock and i_mmaplock native rw_semaphores and
> >> replace mr*() functions with native rwsem calls.
> >>
> >> Release the lock in xfs_btree_split() just before the work-queue
> >> executing xfs_btree_split_worker() is scheduled and make
> >> xfs_btree_split_worker() to acquire the lock as a first thing and
> >> release it just before returning from the function. This it done so the
> >> ownership of the lock is transfered between kernel threads and thus
> >> lockdep won't complain about lock being held by a different kernel
> >> thread.
> >>
> >> Signed-off-by: Pavel Reichl <preichl@redhat.com>
> >> ---
> >> fs/xfs/libxfs/xfs_btree.c | 14 +++++++
> >> fs/xfs/mrlock.h | 78 ---------------------------------------
> >> fs/xfs/xfs_inode.c | 36 ++++++++++--------
> >> fs/xfs/xfs_inode.h | 4 +-
> >> fs/xfs/xfs_iops.c | 4 +-
> >> fs/xfs/xfs_linux.h | 2 +-
> >> fs/xfs/xfs_super.c | 6 +--
> >> 7 files changed, 41 insertions(+), 103 deletions(-)
> >> delete mode 100644 fs/xfs/mrlock.h
> >>
> >> diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
> >> index 2d25bab68764..1d1bb8423688 100644
> >> --- a/fs/xfs/libxfs/xfs_btree.c
> >> +++ b/fs/xfs/libxfs/xfs_btree.c
> >> @@ -2816,6 +2816,7 @@ xfs_btree_split_worker(
> >> unsigned long pflags;
> >> unsigned long new_pflags = PF_MEMALLOC_NOFS;
> >>
> >> + rwsem_acquire(&args->cur->bc_ino.ip->i_lock.dep_map, 0, 0, _RET_IP_);
> > These calls also need a comment explaining just what they're doing.
> >
> >> /*
> >> * we are in a transaction context here, but may also be doing work
> >> * in kswapd context, and hence we may need to inherit that state
> >> @@ -2832,6 +2833,7 @@ xfs_btree_split_worker(
> >> complete(args->done);
> >>
> >> current_restore_flags_nested(&pflags, new_pflags);
> >> + rwsem_release(&args->cur->bc_ino.ip->i_lock.dep_map, _THIS_IP_);
> > Note that as soon as you call complete(), xfs_btree_split can wake up
> > and return, which means that *args could now point to reclaimed stack
> > space. This leads to crashes and memory corruption in generic/562 on
> > a 1k block filesystem (though in principle this can happen anywhere):
>
>
> What's the right way out of this; store *ip when we enter the function
> and use that to get to the map, rather than args i guess?
Er, no, because the worker could also get preempted right after
complete() and take so long to get rescheduled that the the inode have
been reclaimed. Think about it -- the original thread is waiting on the
completion that it passed to the worker through $args, and therefore the
worker cannot touch any of the resources it was accessing through $args
after calling complete()....
--D
> Thanks,
> -Eric
next prev parent reply other threads:[~2020-10-07 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 19:15 [PATCH v9 0/4] xfs: Remove wrappers for some semaphores Pavel Reichl
2020-10-06 19:15 ` [PATCH v9 1/4] xfs: Refactor xfs_isilocked() Pavel Reichl
2020-10-06 19:15 ` [PATCH v9 2/4] xfs: clean up whitespace in xfs_isilocked() calls Pavel Reichl
2020-10-06 19:15 ` [PATCH v9 3/4] xfs: xfs_isilocked() can only check a single lock type Pavel Reichl
2020-10-06 19:15 ` [PATCH v9 4/4] xfs: replace mrlock_t with rw_semaphores Pavel Reichl
2020-10-07 1:21 ` Darrick J. Wong
2020-10-07 14:17 ` Eric Sandeen
2020-10-07 15:25 ` Darrick J. Wong [this message]
2020-10-07 21:15 ` Pavel Reichl
2020-10-07 21:55 ` Darrick J. Wong
2020-10-08 13:55 ` Pavel Reichl
2020-10-08 16:16 ` Darrick J. Wong
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=20201007152554.GL49559@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=preichl@redhat.com \
--cc=sandeen@sandeen.net \
/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).