From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: fix ref of discard command
Date: Wed, 14 Jun 2017 07:26:48 -0700 [thread overview]
Message-ID: <20170614142648.GA74571@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <54b5aaad-1674-8d76-c489-d5eee6ef7f26@huawei.com>
On 06/12, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2017/6/12 11:04, Jaegeuk Kim wrote:
> > This patch resolves kernel panic for xfstests/081, caused by recent f2fs_bug_on
> >
> > f2fs: add f2fs_bug_on in __remove_discard_cmd
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> > fs/f2fs/segment.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> > index 86a0c1095939..a6d77388a806 100644
> > --- a/fs/f2fs/segment.c
> > +++ b/fs/f2fs/segment.c
> > @@ -1025,6 +1025,8 @@ static void __wait_discard_cmd(struct f2fs_sb_info *sbi, bool wait_cond)
> > list_for_each_entry_safe(dc, tmp, wait_list, list) {
> > if (!wait_cond || (dc->state == D_DONE && !dc->ref)) {
> > wait_for_completion_io(&dc->wait);
> > + if (dc->state == D_DONE && dc->ref)
> > + dc->ref--;
>
> Should set dc->ref to 0 to avoid panic once we add other referrers?
Sorry, could you please explain this in more detail?
Thanks,
>
> Thanks,
>
> > __remove_discard_cmd(sbi, dc);
> > } else {
> > dc->ref++;
> >
next prev parent reply other threads:[~2017-06-14 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 3:04 Jaegeuk Kim
2017-06-12 11:17 ` Chao Yu
2017-06-14 14:26 ` Jaegeuk Kim [this message]
2017-06-14 14:58 ` [f2fs-dev] " Chao Yu
2017-06-14 15:20 ` Jaegeuk Kim
2017-06-14 15:40 ` Chao Yu
2017-06-23 8:16 ` Chao Yu
2017-06-24 16:26 ` Jaegeuk Kim
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=20170614142648.GA74571@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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
all inboxes | Powered by JetHome®