From: Dan Carpenter <dan.carpenter@oracle.com>
To: dsterba@suse.cz, Chris Mason <clm@fb.com>,
Jeff Mahoney <jeffm@suse.com>, Josef Bacik <josef@toxicpanda.com>,
kernel-janitors@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Silence a static checker locking warning
Date: Mon, 11 Feb 2019 18:42:36 +0000 [thread overview]
Message-ID: <20190211183231.GA5436@kadam> (raw)
In-Reply-To: <20190211163612.GW2900@suse.cz>
On Mon, Feb 11, 2019 at 05:36:13PM +0100, David Sterba wrote:
> > I have re-written the code though to make it cleaner and
> > to silence the static checkers.
>
> Maybe there's something new the static checker needs to learn.
Gar. Yes. You're right. I hadn't thought about that read locks could
nest.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: dsterba@suse.cz, Chris Mason <clm@fb.com>,
Jeff Mahoney <jeffm@suse.com>, Josef Bacik <josef@toxicpanda.com>,
kernel-janitors@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Silence a static checker locking warning
Date: Mon, 11 Feb 2019 21:42:36 +0300 [thread overview]
Message-ID: <20190211183231.GA5436@kadam> (raw)
In-Reply-To: <20190211163612.GW2900@suse.cz>
On Mon, Feb 11, 2019 at 05:36:13PM +0100, David Sterba wrote:
> > I have re-written the code though to make it cleaner and
> > to silence the static checkers.
>
> Maybe there's something new the static checker needs to learn.
Gar. Yes. You're right. I hadn't thought about that read locks could
nest.
regards,
dan carpenter
next prev parent reply other threads:[~2019-02-11 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 9:02 [PATCH] btrfs: Silence a static checker locking warning Dan Carpenter
2019-02-09 9:02 ` Dan Carpenter
2019-02-11 16:36 ` David Sterba
2019-02-11 16:36 ` David Sterba
2019-02-11 17:07 ` David Sterba
2019-02-11 17:07 ` David Sterba
2019-02-11 18:42 ` Dan Carpenter [this message]
2019-02-11 18:42 ` Dan Carpenter
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=20190211183231.GA5436@kadam \
--to=dan.carpenter@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jeffm@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-btrfs@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 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.