linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>, Russell King <rmk@arm.linux.org.uk>,
	linux-serial@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 4/4] serial: doc: .break_ctl() may sleep
Date: Fri, 15 Apr 2016 16:07:39 -0700	[thread overview]
Message-ID: <5711743B.3030207@hurleysoftware.com> (raw)
In-Reply-To: <20160415164150.1666b58c@lwn.net>

On 04/15/2016 03:41 PM, Jonathan Corbet wrote:
> On Fri, 15 Apr 2016 15:31:30 -0700
> Peter Hurley <peter@hurleysoftware.com> wrote:
> 
>> The only caller of the uart driver's break_ctl() method is
>> uart_break_ctl(), which is serial core's proxy tty driver break_ctl()
>> method. uart_break_ctl() claims the struct tty_port::mutex to prevent
>> concurrent tiocmset().
>>
>> Thus, the uart driver's break_ctl() method won't be called in atomic
>> context.
> 
> I'm missing something here.

Yes.

The analysis above is required to show that the API contract asserted by
the proposed change to the documentation is currently true in the code,
which is what I care about.

I don't mind if that's not in the changelog, though.

> I can fully believe that uart_break_ctl()
> won't call break_ctl() in atomic context, but the fact that it holds a
> mutex in no way guarantees that.  If uart_break_ctl() makes that promise
> we should just say so.
> 
> Sorry to be obnoxious, but I'd rather not put confusing stuff into the
> changelog if possible.

Sure, that's fine.

Regards,
Peter Hurley

  reply	other threads:[~2016-04-15 23:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  9:08 [PATCH 0/4] serial: doc: Low Level Serial API Documentation Improvements (take two) Geert Uytterhoeven
2016-04-14  9:08 ` [PATCH 1/4] serial: doc: Re-add paragraph documenting uart_console_write() Geert Uytterhoeven
2016-04-14  9:08 ` [PATCH 2/4] serial: doc: .(un)throttle() depends on hardware assisted flow control Geert Uytterhoeven
2016-04-14  9:08 ` [PATCH 3/4] serial: doc: .(un)throttle() are serialized by the tty layer Geert Uytterhoeven
2016-04-14  9:08 ` [PATCH 4/4] serial: doc: .break_ctl() may sleep Geert Uytterhoeven
2016-04-15 22:01   ` Jonathan Corbet
2016-04-15 22:31     ` Peter Hurley
2016-04-15 22:41       ` Jonathan Corbet
2016-04-15 23:07         ` Peter Hurley [this message]
2016-04-16 16:47           ` Jonathan Corbet
2016-04-18  8:24             ` Geert Uytterhoeven

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=5711743B.3030207@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=corbet@lwn.net \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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).