netdev - [RFC][LAPB] write_queue limit in lapb_data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <8496f91a0804020250o35e08732ya68e799550e074fa@mail.gmail.com>
Date:	Wed, 2 Apr 2008 13:50:17 +0400
From:	"Matvejchikov Ilya" <matvejchikov@...il.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: [RFC][LAPB] write_queue limit in lapb_data_request

>  > LAPB doesn't check for write_queue length in lapb_data_request(). So
>  > in some conditions it may grow unlimited. There is a potential problem
>  > for small systems.
>  >
>  > It seems like this for me:
>
>  It doesn't enforce limits on any of it's queued from what
>  I can tell.

I'm sorry. It's not quiet clear to me what you mean. As far as I know
LAPB internals there is only one place where write_queue may increase.
In other cases the ack_queue is used.

>
>  Without a thorough audit of resource limit enforcement in
>  this protocol stack, changing things here might be more
>  trouble than it's worth.
>

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html