From: Peter Hurley <peter@hurleysoftware.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kernel-janitors@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: tty: Change tty lock order to master->slave
Date: Tue, 11 Nov 2014 17:19:41 +0000 [thread overview]
Message-ID: <5462452D.8020306@hurleysoftware.com> (raw)
In-Reply-To: <20141111125011.GA12942@mwanda>
On 11/11/2014 07:50 AM, Dan Carpenter wrote:
> Hello Peter Hurley,
>
> The patch 2aff5e2bc62d: "tty: Change tty lock order to master->slave"
> from Nov 5, 2014, leads to the following static checker warning:
>
> drivers/tty/tty_mutex.c:50 tty_lock_slave()
> warn: add some parenthesis here?
>
> drivers/tty/tty_mutex.c
> 47 void __lockfunc tty_lock_slave(struct tty_struct *tty)
> 48 {
> 49 if (tty && tty != tty->link) {
> 50 WARN_ON(!mutex_is_locked(&tty->link->legacy_mutex) ||
> 51 !tty->driver->type = TTY_DRIVER_TYPE_PTY ||
> 52 !tty->driver->type = PTY_TYPE_SLAVE);
>
> ! has high precedence than = so those tests are never true. != doesn't
> make sense either. Probably the negate operatons are just copy-and-paste
> errors?
Thanks for catching this, Dan.
Unfortunately, this is not a copy-and-paste error; apparently, emacs cannot
code-what-I-mean rather than code-what-I-type.
The warning is not necessary now; when I respun this series with fixed lock
subclasses I should have ripped this out. I will send a patch forthwith.
Regards,
Peter Hurley
> 53 tty_lock(tty);
> 54 }
> 55 }
>
> regards,
> dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Hurley <peter@hurleysoftware.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kernel-janitors@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: tty: Change tty lock order to master->slave
Date: Tue, 11 Nov 2014 12:19:41 -0500 [thread overview]
Message-ID: <5462452D.8020306@hurleysoftware.com> (raw)
In-Reply-To: <20141111125011.GA12942@mwanda>
On 11/11/2014 07:50 AM, Dan Carpenter wrote:
> Hello Peter Hurley,
>
> The patch 2aff5e2bc62d: "tty: Change tty lock order to master->slave"
> from Nov 5, 2014, leads to the following static checker warning:
>
> drivers/tty/tty_mutex.c:50 tty_lock_slave()
> warn: add some parenthesis here?
>
> drivers/tty/tty_mutex.c
> 47 void __lockfunc tty_lock_slave(struct tty_struct *tty)
> 48 {
> 49 if (tty && tty != tty->link) {
> 50 WARN_ON(!mutex_is_locked(&tty->link->legacy_mutex) ||
> 51 !tty->driver->type == TTY_DRIVER_TYPE_PTY ||
> 52 !tty->driver->type == PTY_TYPE_SLAVE);
>
> ! has high precedence than == so those tests are never true. != doesn't
> make sense either. Probably the negate operatons are just copy-and-paste
> errors?
Thanks for catching this, Dan.
Unfortunately, this is not a copy-and-paste error; apparently, emacs cannot
code-what-I-mean rather than code-what-I-type.
The warning is not necessary now; when I respun this series with fixed lock
subclasses I should have ripped this out. I will send a patch forthwith.
Regards,
Peter Hurley
> 53 tty_lock(tty);
> 54 }
> 55 }
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2014-11-11 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 12:50 tty: Change tty lock order to master->slave Dan Carpenter
2014-11-11 17:19 ` Peter Hurley [this message]
2014-11-11 17:19 ` Peter Hurley
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=5462452D.8020306@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-next@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.