public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Eryu Guan <eguan@redhat.com>,
	linux-xfs@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [BUG] xfs/104 triggered NULL pointer dereference in iomap  based dio
Date: Thu, 14 Sep 2017 12:25:57 +0530	[thread overview]
Message-ID: <1565818.oNrvGvf46j@localhost.localdomain> (raw)
In-Reply-To: <20170913165546.GA18388@lst.de>

On Wednesday, September 13, 2017 10:25:46 PM IST Christoph Hellwig wrote:
> Does it work fine if you call sb_init_dio_done_wq unconditionally?
> 
> 

Yes, The issue isn't recreated when sb_init_dio_done_wq() is 
invoked unconditionally.

-- 
chandan


      reply	other threads:[~2017-09-14  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 10:58 [BUG] xfs/104 triggered NULL pointer dereference in iomap based dio Eryu Guan
2017-09-13 16:36 ` Chandan Rajendra
2017-09-13 16:55   ` Christoph Hellwig
2017-09-14  6:55     ` Chandan Rajendra [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=1565818.oNrvGvf46j@localhost.localdomain \
    --to=chandan@linux.vnet.ibm.com \
    --cc=eguan@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-xfs@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