From: Geliang Tang <geliangtang@163.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
Julia Lawall <julia.lawall@lip6.fr>
Cc: Geliang Tang <geliangtang@163.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kdave:misc-cleanups-4.5 9/9] fs/btrfs/backref.c:565:1-20: iterator with update on line 577
Date: Tue, 12 Jan 2016 23:23:15 +0800 [thread overview]
Message-ID: <cover.1452611741.git.geliangtang@163.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1601120706340.2042@localhost6.localdomain6>
On Tue, Jan 12, 2016 at 07:07:24AM +0100, Julia Lawall wrote:
> I really have no idea if this is safe or not.
>
> julia
>
> On Tue, 12 Jan 2016, kbuild test robot wrote:
>
> > CC: kbuild-all@01.org
> > TO: Geliang Tang <geliangtang@163.com>
> > CC: David Sterba <dsterba@suse.com>
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux misc-cleanups-4.5
> > head: a7ca42256d9fad572fb7f2c471514d7d3572b1db
> > commit: a7ca42256d9fad572fb7f2c471514d7d3572b1db [9/9] btrfs: use list_for_each_entry* in backref.c
> > :::::: branch date: 5 days ago
> > :::::: commit date: 5 days ago
> >
> > >> fs/btrfs/backref.c:565:1-20: iterator with update on line 577
Sorry for the trouble caused. It's probably unsafe. I updated my patch
to fix this problem.
- Geliang
Geliang Tang (1):
btrfs: use list_for_each_entry* in backref.c
fs/btrfs/backref.c | 25 +++++++------------------
1 file changed, 7 insertions(+), 18 deletions(-)
--
2.5.0
next parent reply other threads:[~2016-01-12 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1601120706340.2042@localhost6.localdomain6>
2016-01-12 15:23 ` Geliang Tang [this message]
2016-01-12 15:23 ` [PATCH v3] btrfs: use list_for_each_entry* in backref.c Geliang Tang
2016-01-12 18:13 ` David Sterba
2016-01-13 14:08 ` [PATCH] btrfs: fix iterator with update error " Geliang Tang
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=cover.1452611741.git.geliangtang@163.com \
--to=geliangtang@163.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).