From: Omar Sandoval <osandov@osandov.com>
To: dsterba@suse.cz, Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com,
Josef Bacik <jbacik@fb.com>
Subject: Re: [PATCH 1/2] btrfs: kill btrfs_write_inode
Date: Fri, 20 Jul 2018 11:30:17 -0700 [thread overview]
Message-ID: <20180720183017.GE29351@vader> (raw)
In-Reply-To: <20180720114801.GA26141@twin.jikos.cz>
On Fri, Jul 20, 2018 at 01:48:01PM +0200, David Sterba wrote:
> On Thu, May 31, 2018 at 11:49:28AM +0200, David Sterba wrote:
> > On Tue, May 29, 2018 at 12:17:42PM -0700, Omar Sandoval wrote:
> > > On Mon, May 28, 2018 at 06:57:59PM +0200, David Sterba wrote:
> > > > On Tue, May 22, 2018 at 01:47:22PM -0400, Josef Bacik wrote:
> > > > > From: Josef Bacik <jbacik@fb.com>
> > > > >
> > > > > We don't actually need this. It used to be in place for O_SYNC writes,
> > > > > but we've used the normal fsync() path for that for years now. The
> > > > > other case we hit this is through sync(), which will commit the
> > > > > transaction anyway. All this does is make us commit the transaction a
> > > > > bunch for no reason, and it could deadlock with delayed iput's.
> > > >
> > > > In what way does it deadlock with delayed iput?
> > >
> > > Here's an example stack trace:
> >
> > Aha, so that's an actual bugfix. The changelog should have been stated
> > the other way around: there's a deadlock scenario and can be fixed by
> > removing the whole function because there's another mechanism to achieve
> > the same O_SYNC behaviour. Please update and resend.
>
> Ping, update and resend if you want this patch to go to 4.19. Thanks.
Josef just left for vacation, but I can resend this with a better
description.
prev parent reply other threads:[~2018-07-20 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 17:47 [PATCH 1/2] btrfs: kill btrfs_write_inode Josef Bacik
2018-05-22 17:47 ` [PATCH 2/2] btrfs: always wait on ordered extents at fsync time Josef Bacik
2018-05-23 12:24 ` David Sterba
2018-05-23 15:38 ` Josef Bacik
2018-05-23 15:41 ` Nikolay Borisov
2018-05-23 15:53 ` Filipe Manana
2018-05-22 17:54 ` [PATCH 1/2] btrfs: kill btrfs_write_inode Omar Sandoval
2018-05-28 16:57 ` David Sterba
2018-05-29 19:17 ` Omar Sandoval
2018-05-31 9:49 ` David Sterba
2018-07-20 11:48 ` David Sterba
2018-07-20 18:30 ` Omar Sandoval [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=20180720183017.GE29351@vader \
--to=osandov@osandov.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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).