From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: DanCarpenter <dan.carpenter@oracle.com>,
linux-nilfs <linux-nilfs@vger.kernel.org>,
"Linux FS Devel" <linux-fsdevel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, akpm@linux-foundation.org,
"Jérôme Poulin" <jeromepoulin@gmail.com>
Subject: Re: [PATCH v2] nilfs2: remove double bio_put() in nilfs_end_bio_write() for BIO_EOPNOTSUPP error
Date: Wed, 31 Jul 2013 14:36:47 +0400 [thread overview]
Message-ID: <1375267007.2364.7.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130727.120232.356926182.konishi.ryusuke@lab.ntt.co.jp>
Hi Ryusuke,
On Sat, 2013-07-27 at 12:02 +0900, Ryusuke Konishi wrote:
[snip]
>
> This decrement looks wrong.
>
> Otherwise, your change of nilfs_segbuf_submit_bio() is just a
> equivalent transformation and doesn't fix problem, that is, a mismatch
> of the number of calls between complete() and wait_for_completion().
>
> In your patch, nilfs_end_bio_write() function calls the complete()
> routine as before even if it received an EOPNOTSUPP error.
>
> In that case, segbuf->sb_nbio must be incremented to call
> wait_for_completion() the right number of times.
>
> Note that wait_for_completion() is called based on the count of
> segbuf->sb_nbio even if nilfs_segbuf_submit_bio() returns an error.
> This is performed through the following path:
>
> nilfs_segbuf_submit_bio
> nilfs_segbuf_submit_bh
> nilfs_segbuf_write
> nilfs_write_logs
> nilfs_segctor_write
> nilfs_segctor_do_construct
> nilfs_segctor_abort_construction
> nilfs_wait_on_logs
> nilfs_segbuf_wait
> wait_for_completion
> (repeated for the number of times of segbuf->sb_nbio)
>
>
> If you think this is a separate problem, then it should be fixed in
> another patch and nilfs_segbuf_submit_bio() should not be touched in
> this patch.
>
Sorry for delay with working on this patch. Now I am investigating
the issue (Kernel Bug: unable to handle kernel paging request) that it
was reported by Jérôme Poulin <jeromepoulin@gmail.com>. I suspect that
the reported issue is related to this patch. So, I feel a necessity to
investigate the issue more deeply before continuation to work on this
patch.
With the best regards,
Vyacheslav Dubeyko.
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-31 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 13:59 [PATCH v2] nilfs2: remove double bio_put() in nilfs_end_bio_write() for BIO_EOPNOTSUPP error Vyacheslav Dubeyko
2013-07-27 3:02 ` Ryusuke Konishi
2013-07-31 10:36 ` Vyacheslav Dubeyko [this message]
[not found] ` <20130727.120232.356926182.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-08-12 13:16 ` Vyacheslav Dubeyko
2013-08-12 14:57 ` Ryusuke Konishi
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=1375267007.2364.7.camel@slavad-ubuntu \
--to=slava@dubeyko.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=jeromepoulin@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nilfs@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).