All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish Samant <ashish.samant@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org,
	fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [PATCH] fuse: Dont set_page_dirty_lock() for ITER_BVEC pages for async_dio
Date: Wed, 12 Jul 2017 19:29:01 -0700	[thread overview]
Message-ID: <5966DAED.7020306@oracle.com> (raw)
In-Reply-To: <CAJfpegsBRdq5omoXu2_dO-ncPyL-efKofpzYapUtK203LPFvGw@mail.gmail.com>



On 07/12/2017 05:21 AM, Miklos Szeredi wrote:
> On Mon, Jul 10, 2017 at 11:36 PM, Ashish Samant
> <ashish.samant@oracle.com> wrote:
>> Hi,
>>
>> Any update here? This attempts to fix a real deadlock which happens as soon
>> as a loop device is created in a fuse mount point with the async_dio mount
>> option enabled.
> The patch header should contain the explanation of this deadlock.
>
> Can you please resend the patch with a more detailed description?

Sent V2 with detailed commit message.

Thanks,
Ashish
>
> Thanks,
> Miklos

      reply	other threads:[~2017-07-13  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  0:33 [PATCH] fuse: Dont set_page_dirty_lock() for ITER_BVEC pages for async_dio Ashish Samant
2017-07-10 21:36 ` Ashish Samant
2017-07-12 12:21   ` Miklos Szeredi
2017-07-13  2:29     ` Ashish Samant [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=5966DAED.7020306@oracle.com \
    --to=ashish.samant@oracle.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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.