linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	Vincent Cuissard <cuissard@marvell.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH] NFC: nci: uart: Set tty->disc_data only in success path
Date: Wed, 18 Jun 2025 09:44:56 +0200	[thread overview]
Message-ID: <2025061838-frustrate-operative-bd34@gregkh> (raw)
In-Reply-To: <20250618073649.25049-2-krzysztof.kozlowski@linaro.org>

On Wed, Jun 18, 2025 at 09:36:50AM +0200, Krzysztof Kozlowski wrote:
> Setting tty->disc_data before opening the NCI device means we need to
> clean it up on error paths.  This also opens some short window if device
> starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded
> (broken hardware?).  Close the window by exposing tty->disc_data only on
> the success path, when opening of the NCI device and try_module_get()
> succeeds.
> 
> The code differs in error path in one aspect: tty->disc_data won't be
> ever assigned thus NULL-ified.  This however should not be relevant
> difference, because of "tty->disc_data=NULL" in nci_uart_tty_open().
> 
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: Linus Torvalds <torvalds@linuxfoundation.org>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Fixes: 9961127d4bce ("NFC: nci: add generic uart support")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>  net/nfc/nci/uart.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/net/nfc/nci/uart.c b/net/nfc/nci/uart.c
> index ed1508a9e093..aab107727f18 100644
> --- a/net/nfc/nci/uart.c
> +++ b/net/nfc/nci/uart.c
> @@ -119,22 +119,22 @@ static int nci_uart_set_driver(struct tty_struct *tty, unsigned int driver)
>  
>  	memcpy(nu, nci_uart_drivers[driver], sizeof(struct nci_uart));
>  	nu->tty = tty;
> -	tty->disc_data = nu;
>  	skb_queue_head_init(&nu->tx_q);
>  	INIT_WORK(&nu->write_work, nci_uart_write_work);
>  	spin_lock_init(&nu->rx_lock);
>  
>  	ret = nu->ops.open(nu);
>  	if (ret) {
> -		tty->disc_data = NULL;
>  		kfree(nu);
> +		return ret;
>  	} else if (!try_module_get(nu->owner)) {
>  		nu->ops.close(nu);
> -		tty->disc_data = NULL;
>  		kfree(nu);
>  		return -ENOENT;
>  	}
> -	return ret;
> +	tty->disc_data = nu;
> +
> +	return 0;
>  }

Looks good, thanks for cleaning this up:

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  reply	other threads:[~2025-06-18  7:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  7:36 [PATCH] NFC: nci: uart: Set tty->disc_data only in success path Krzysztof Kozlowski
2025-06-18  7:44 ` Greg KH [this message]
2025-06-19 15:40 ` patchwork-bot+netdevbpf

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=2025061838-frustrate-operative-bd34@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cuissard@marvell.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sameo@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linuxfoundation.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).