tty: n_gsm: fix missing mux reset on config change at responder
authorDaniel Starke <daniel.starke@siemens.com>
Thu, 14 Apr 2022 09:42:06 +0000 (02:42 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 9 May 2022 07:16:31 +0000 (09:16 +0200)
commit50736d3a4ca6878c3c0c82812bdcee9f28469b2c
tree20120bea61e84bc7324e1199d3fa1b2e03569eb8
parent30eddc3fa32649ad2b1521942e19bc60f4b33b08
tty: n_gsm: fix missing mux reset on config change at responder

commit 11451693e4081d32ef65147c6ca08cd0094ae252 upstream.

Currently, only the initiator resets the mux protocol if the user requests
new parameters that are incompatible to those of the current connection.
The responder also needs to reset the multiplexer if the new parameter set
requires this. Otherwise, we end up with an inconsistent parameter set
between initiator and responder.
Revert the old behavior to inform the peer upon an incompatible parameter
set change from the user on the responder side by re-establishing the mux
protocol in such case.

Fixes: 509067bbd264 ("tty: n_gsm: Delete gsm_disconnect when config requester")
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
Link: https://lore.kernel.org/r/20220414094225.4527-1-daniel.starke@siemens.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/tty/n_gsm.c