From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: Andres Freund <andres@anarazel.de>
Cc: Dave Chinner <david@fromorbit.com>,
David Sterba <dsterba@suse.com>,
linux-fsdevel@vger.kernel.org, jack@suse.com, hch@infradead.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: Odd locking pattern introduced as part of "nowait aio support"
Date: Wed, 11 Sep 2019 05:55:16 -0500 [thread overview]
Message-ID: <20190911105516.l2iqes7dngj6w27o@fiona> (raw)
In-Reply-To: <20190911093926.pfkkx25mffzeuo32@alap3.anarazel.de>
On 2:39 11/09, Andres Freund wrote:
>
> Ok. Goldwyn, do you want to write a patch, or do you want me to write
> one up?
I'll post one shortly. Thanks for bringing this up.
--
Goldwyn
next prev parent reply other threads:[~2019-09-11 10:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190910223327.mnegfoggopwqqy33@alap3.anarazel.de>
[not found] ` <20190911040420.GB27547@dread.disaster.area>
2019-09-11 9:39 ` Odd locking pattern introduced as part of "nowait aio support" Andres Freund
2019-09-11 10:19 ` Christoph Hellwig
2019-09-11 10:31 ` Ritesh Harjani
2019-09-11 10:55 ` Goldwyn Rodrigues [this message]
2019-09-11 16:45 ` Fix inode sem regression for nowait Goldwyn Rodrigues
2019-09-11 16:45 ` [PATCH 1/3] btrfs: fix inode rwsem regression Goldwyn Rodrigues
2019-09-11 17:21 ` David Sterba
2019-09-11 16:45 ` [PATCH 2/3] ext4: " Goldwyn Rodrigues
2019-09-12 8:52 ` Ritesh Harjani
2019-09-12 9:26 ` Matthew Bobrowski
2019-09-23 10:10 ` Jan Kara
2019-09-23 13:18 ` Theodore Y. Ts'o
2019-09-11 16:45 ` [PATCH 3/3] f2fs: " Goldwyn Rodrigues
2019-09-12 6:17 ` Chao Yu
2019-09-13 19:46 ` Jaegeuk Kim
2019-09-16 1:16 ` Chao Yu
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=20190911105516.l2iqes7dngj6w27o@fiona \
--to=rgoldwyn@suse.de \
--cc=andres@anarazel.de \
--cc=david@fromorbit.com \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=jack@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).