From: Xie He <xie.he.0141@gmail.com>
To: Gao Yan <gao.yanB@h3c.com>
Cc: paulus@samba.org, davem@davemloft.net, kuba@kernel.org,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: remove disc_data_lock in ppp line discipline
Date: Thu, 31 Dec 2020 17:37:44 -0800 [thread overview]
Message-ID: <20210101013744.72562-1-xie.he.0141@gmail.com> (raw)
In-Reply-To: <20201228071550.15745-1-gao.yanB@h3c.com>
> In tty layer, it use tty->ldisc_sem to proect tty_ldisc_ops.
> So I think tty->ldisc_sem can also protect tty->disc_data;
It might help by CC'ing TTY people, so that we could get this reviewed by
people who are familiar with TTY code.
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:TTY LAYER)
Jiri Slaby <jirislaby@kernel.org> (supporter:TTY LAYER)
Thanks!
> For examlpe,
> When cpu A is running ppp_synctty_ioctl that hold the tty->ldisc_sem,
> at the same time if cpu B calls ppp_synctty_close, it will wait until
> cpu A release tty->ldisc_sem. So I think it is unnecessary to have the
> disc_data_lock;
>
> cpu A cpu B
> tty_ioctl tty_reopen
> ->hold tty->ldisc_sem ->hold tty->ldisc_sem(write), failed
> ->ld->ops->ioctl ->wait...
> ->release tty->ldisc_sem ->wait...OK,hold tty->ldisc_sem
> ->tty_ldisc_reinit
> ->tty_ldisc_close
> ->ld->ops->close
IMHO an example might not be necessary. Examples are useful to show
incorrectness. But we cannot show correctness by examples because
examples are not exhaustive.
BTW, there're some typos:
"proect" -> "protect"
"examlpe" -> "example"
"that hold ..." -> "that holds ..."
"cpu A release ..." -> "cpu A releases ..."
> * FIXME: this is no longer true. The _close path for the ldisc is
> * now guaranteed to be sane.
> */
> *
> * FIXME: Fixed in tty_io nowadays.
> */
Since you are removing "disc_data_lock", please update (or remove) these
two comments. Thanks!
next prev parent reply other threads:[~2021-01-01 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 7:15 [PATCH] net: remove disc_data_lock in ppp line discipline Gao Yan
2020-12-31 10:00 ` 答复: " Gaoyan
2021-01-01 1:37 ` Xie He [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-15 15:00 Gao Yan
2020-12-17 0:48 ` Jakub Kicinski
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=20210101013744.72562-1-xie.he.0141@gmail.com \
--to=xie.he.0141@gmail.com \
--cc=davem@davemloft.net \
--cc=gao.yanB@h3c.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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).