2019-05-20 20:08:06 +03:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
2005-04-17 02:20:36 +04:00
|
|
|
/*
|
|
|
|
* LAPB release 002
|
|
|
|
*
|
|
|
|
* This code REQUIRES 2.1.15 or higher/ NET3.038
|
|
|
|
*
|
|
|
|
* History
|
|
|
|
* LAPB 001 Jonathan Naylor Started Coding
|
|
|
|
* LAPB 002 Jonathan Naylor New timer architecture.
|
|
|
|
*/
|
|
|
|
|
2012-05-17 14:25:49 +04:00
|
|
|
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
#include <linux/errno.h>
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/socket.h>
|
|
|
|
#include <linux/in.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/jiffies.h>
|
|
|
|
#include <linux/timer.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/sockios.h>
|
|
|
|
#include <linux/net.h>
|
|
|
|
#include <linux/inet.h>
|
|
|
|
#include <linux/skbuff.h>
|
|
|
|
#include <net/sock.h>
|
2016-12-24 22:46:01 +03:00
|
|
|
#include <linux/uaccess.h>
|
2005-04-17 02:20:36 +04:00
|
|
|
#include <linux/fcntl.h>
|
|
|
|
#include <linux/mm.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <net/lapb.h>
|
|
|
|
|
2017-10-17 03:28:46 +03:00
|
|
|
static void lapb_t1timer_expiry(struct timer_list *);
|
|
|
|
static void lapb_t2timer_expiry(struct timer_list *);
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
void lapb_start_t1timer(struct lapb_cb *lapb)
|
|
|
|
{
|
|
|
|
del_timer(&lapb->t1timer);
|
|
|
|
|
2017-10-23 10:40:42 +03:00
|
|
|
lapb->t1timer.function = lapb_t1timer_expiry;
|
2005-04-17 02:20:36 +04:00
|
|
|
lapb->t1timer.expires = jiffies + lapb->t1;
|
|
|
|
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t1timer_running = true;
|
2005-04-17 02:20:36 +04:00
|
|
|
add_timer(&lapb->t1timer);
|
|
|
|
}
|
|
|
|
|
|
|
|
void lapb_start_t2timer(struct lapb_cb *lapb)
|
|
|
|
{
|
|
|
|
del_timer(&lapb->t2timer);
|
|
|
|
|
2017-10-23 10:40:42 +03:00
|
|
|
lapb->t2timer.function = lapb_t2timer_expiry;
|
2005-04-17 02:20:36 +04:00
|
|
|
lapb->t2timer.expires = jiffies + lapb->t2;
|
|
|
|
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t2timer_running = true;
|
2005-04-17 02:20:36 +04:00
|
|
|
add_timer(&lapb->t2timer);
|
|
|
|
}
|
|
|
|
|
|
|
|
void lapb_stop_t1timer(struct lapb_cb *lapb)
|
|
|
|
{
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t1timer_running = false;
|
2005-04-17 02:20:36 +04:00
|
|
|
del_timer(&lapb->t1timer);
|
|
|
|
}
|
|
|
|
|
|
|
|
void lapb_stop_t2timer(struct lapb_cb *lapb)
|
|
|
|
{
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t2timer_running = false;
|
2005-04-17 02:20:36 +04:00
|
|
|
del_timer(&lapb->t2timer);
|
|
|
|
}
|
|
|
|
|
|
|
|
int lapb_t1timer_running(struct lapb_cb *lapb)
|
|
|
|
{
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
return lapb->t1timer_running;
|
2005-04-17 02:20:36 +04:00
|
|
|
}
|
|
|
|
|
2017-10-17 03:28:46 +03:00
|
|
|
static void lapb_t2timer_expiry(struct timer_list *t)
|
2005-04-17 02:20:36 +04:00
|
|
|
{
|
2017-10-17 03:28:46 +03:00
|
|
|
struct lapb_cb *lapb = from_timer(lapb, t, t2timer);
|
2005-04-17 02:20:36 +04:00
|
|
|
|
2021-01-26 07:09:39 +03:00
|
|
|
spin_lock_bh(&lapb->lock);
|
|
|
|
if (timer_pending(&lapb->t2timer)) /* A new timer has been set up */
|
|
|
|
goto out;
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
if (!lapb->t2timer_running) /* The timer has been stopped */
|
2021-01-26 07:09:39 +03:00
|
|
|
goto out;
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
if (lapb->condition & LAPB_ACK_PENDING_CONDITION) {
|
|
|
|
lapb->condition &= ~LAPB_ACK_PENDING_CONDITION;
|
|
|
|
lapb_timeout_response(lapb);
|
|
|
|
}
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t2timer_running = false;
|
2021-01-26 07:09:39 +03:00
|
|
|
|
|
|
|
out:
|
|
|
|
spin_unlock_bh(&lapb->lock);
|
2005-04-17 02:20:36 +04:00
|
|
|
}
|
|
|
|
|
2017-10-17 03:28:46 +03:00
|
|
|
static void lapb_t1timer_expiry(struct timer_list *t)
|
2005-04-17 02:20:36 +04:00
|
|
|
{
|
2017-10-17 03:28:46 +03:00
|
|
|
struct lapb_cb *lapb = from_timer(lapb, t, t1timer);
|
2005-04-17 02:20:36 +04:00
|
|
|
|
2021-01-26 07:09:39 +03:00
|
|
|
spin_lock_bh(&lapb->lock);
|
|
|
|
if (timer_pending(&lapb->t1timer)) /* A new timer has been set up */
|
|
|
|
goto out;
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
if (!lapb->t1timer_running) /* The timer has been stopped */
|
2021-01-26 07:09:39 +03:00
|
|
|
goto out;
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
switch (lapb->state) {
|
|
|
|
|
|
|
|
/*
|
2020-11-26 09:35:55 +03:00
|
|
|
* If we are a DCE, send DM up to N2 times, then switch to
|
|
|
|
* STATE_1 and send SABM(E).
|
2005-04-17 02:20:36 +04:00
|
|
|
*/
|
|
|
|
case LAPB_STATE_0:
|
2020-11-26 09:35:55 +03:00
|
|
|
if (lapb->mode & LAPB_DCE &&
|
|
|
|
lapb->n2count != lapb->n2) {
|
|
|
|
lapb->n2count++;
|
2005-04-17 02:20:36 +04:00
|
|
|
lapb_send_control(lapb, LAPB_DM, LAPB_POLLOFF, LAPB_RESPONSE);
|
2020-11-26 09:35:55 +03:00
|
|
|
} else {
|
|
|
|
lapb->state = LAPB_STATE_1;
|
|
|
|
lapb_establish_data_link(lapb);
|
|
|
|
}
|
2005-04-17 02:20:36 +04:00
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Awaiting connection state, send SABM(E), up to N2 times.
|
|
|
|
*/
|
2007-02-09 17:24:59 +03:00
|
|
|
case LAPB_STATE_1:
|
2005-04-17 02:20:36 +04:00
|
|
|
if (lapb->n2count == lapb->n2) {
|
|
|
|
lapb_clear_queues(lapb);
|
|
|
|
lapb->state = LAPB_STATE_0;
|
|
|
|
lapb_disconnect_indication(lapb, LAPB_TIMEDOUT);
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(0, "(%p) S1 -> S0\n", lapb->dev);
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t1timer_running = false;
|
2021-01-26 07:09:39 +03:00
|
|
|
goto out;
|
2005-04-17 02:20:36 +04:00
|
|
|
} else {
|
|
|
|
lapb->n2count++;
|
|
|
|
if (lapb->mode & LAPB_EXTENDED) {
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(1, "(%p) S1 TX SABME(1)\n",
|
|
|
|
lapb->dev);
|
2005-04-17 02:20:36 +04:00
|
|
|
lapb_send_control(lapb, LAPB_SABME, LAPB_POLLON, LAPB_COMMAND);
|
|
|
|
} else {
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(1, "(%p) S1 TX SABM(1)\n",
|
|
|
|
lapb->dev);
|
2005-04-17 02:20:36 +04:00
|
|
|
lapb_send_control(lapb, LAPB_SABM, LAPB_POLLON, LAPB_COMMAND);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Awaiting disconnection state, send DISC, up to N2 times.
|
|
|
|
*/
|
|
|
|
case LAPB_STATE_2:
|
|
|
|
if (lapb->n2count == lapb->n2) {
|
|
|
|
lapb_clear_queues(lapb);
|
|
|
|
lapb->state = LAPB_STATE_0;
|
|
|
|
lapb_disconnect_confirmation(lapb, LAPB_TIMEDOUT);
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(0, "(%p) S2 -> S0\n", lapb->dev);
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t1timer_running = false;
|
2021-01-26 07:09:39 +03:00
|
|
|
goto out;
|
2005-04-17 02:20:36 +04:00
|
|
|
} else {
|
|
|
|
lapb->n2count++;
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(1, "(%p) S2 TX DISC(1)\n", lapb->dev);
|
2005-04-17 02:20:36 +04:00
|
|
|
lapb_send_control(lapb, LAPB_DISC, LAPB_POLLON, LAPB_COMMAND);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Data transfer state, restransmit I frames, up to N2 times.
|
|
|
|
*/
|
|
|
|
case LAPB_STATE_3:
|
|
|
|
if (lapb->n2count == lapb->n2) {
|
|
|
|
lapb_clear_queues(lapb);
|
|
|
|
lapb->state = LAPB_STATE_0;
|
|
|
|
lapb_stop_t2timer(lapb);
|
|
|
|
lapb_disconnect_indication(lapb, LAPB_TIMEDOUT);
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(0, "(%p) S3 -> S0\n", lapb->dev);
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t1timer_running = false;
|
2021-01-26 07:09:39 +03:00
|
|
|
goto out;
|
2005-04-17 02:20:36 +04:00
|
|
|
} else {
|
|
|
|
lapb->n2count++;
|
|
|
|
lapb_requeue_frames(lapb);
|
2013-09-18 14:00:35 +04:00
|
|
|
lapb_kick(lapb);
|
2005-04-17 02:20:36 +04:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Frame reject state, restransmit FRMR frames, up to N2 times.
|
|
|
|
*/
|
|
|
|
case LAPB_STATE_4:
|
|
|
|
if (lapb->n2count == lapb->n2) {
|
|
|
|
lapb_clear_queues(lapb);
|
|
|
|
lapb->state = LAPB_STATE_0;
|
|
|
|
lapb_disconnect_indication(lapb, LAPB_TIMEDOUT);
|
2012-05-17 14:25:49 +04:00
|
|
|
lapb_dbg(0, "(%p) S4 -> S0\n", lapb->dev);
|
net: lapb: Make "lapb_t1timer_running" able to detect an already running timer
Problem:
The "lapb_t1timer_running" function in "lapb_timer.c" is used in only
one place: in the "lapb_kick" function in "lapb_out.c". "lapb_kick" calls
"lapb_t1timer_running" to check if the timer is already pending, and if
it is not, schedule it to run.
However, if the timer has already fired and is running, and is waiting to
get the "lapb->lock" lock, "lapb_t1timer_running" will not detect this,
and "lapb_kick" will then schedule a new timer. The old timer will then
abort when it sees a new timer pending.
I think this is not right. The purpose of "lapb_kick" should be ensuring
that the actual work of the timer function is scheduled to be done.
If the timer function is already running but waiting for the lock,
"lapb_kick" should not abort and reschedule it.
Changes made:
I added a new field "t1timer_running" in "struct lapb_cb" for
"lapb_t1timer_running" to use. "t1timer_running" will accurately reflect
whether the actual work of the timer is pending. If the timer has fired
but is still waiting for the lock, "t1timer_running" will still correctly
reflect whether the actual work is waiting to be done.
The old "t1timer_stop" field, whose only responsibility is to ask a timer
(that is already running but waiting for the lock) to abort, is no longer
needed, because the new "t1timer_running" field can fully take over its
responsibility. Therefore "t1timer_stop" is deleted.
"t1timer_running" is not simply a negation of the old "t1timer_stop".
At the end of the timer function, if it does not reschedule itself,
"t1timer_running" is set to false to indicate that the timer is stopped.
For consistency of the code, I also added "t2timer_running" and deleted
"t2timer_stop".
Signed-off-by: Xie He <xie.he.0141@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-03-21 12:39:35 +03:00
|
|
|
lapb->t1timer_running = false;
|
2021-01-26 07:09:39 +03:00
|
|
|
goto out;
|
2005-04-17 02:20:36 +04:00
|
|
|
} else {
|
|
|
|
lapb->n2count++;
|
|
|
|
lapb_transmit_frmr(lapb);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
lapb_start_t1timer(lapb);
|
2021-01-26 07:09:39 +03:00
|
|
|
|
|
|
|
out:
|
|
|
|
spin_unlock_bh(&lapb->lock);
|
2005-04-17 02:20:36 +04:00
|
|
|
}
|