netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernard Pidoux <bpidoux@free.fr>
To: Linux Netdev <netdev@vger.kernel.org>,
	Linux Hams <linux-hams@vger.kernel.org>
Cc: Ralf DL5RB <ralf@linux-mips.org>, David Miller <davem@davemloft.net>
Subject: [PATCH] [ROSE] zero length frame filtering in af_rose.c
Date: Sat, 22 Nov 2008 11:08:52 +0100	[thread overview]
Message-ID: <200811221108.54242.bpidoux@free.fr> (raw)

Since changeset e79ad711a0108475c1b3a03815527e7237020b08 from  mainline.
From: David S. Miller <davem@davemloft.net>
empty packet can be transmitted on connected socket for datagram protocols.

However, this patch broke a high level application using ROSE network 
protocole with connected datagram.

Bulletin Board Stations perform bulletins forwarding between BBS stations by  
radio and ROSE network using a forward protocole.
Now, if for some reason, a sending buffer in the application software happens 
to be empty at a specific moment, ROSE relays an empty packet via unfiltred 
packet socket.
When received, this ROSE packet introduces perturbations of BBS data 
forwarding protocole, for the application protocole is waiting for something 
else than an empty packet.
We agree that a more carefull programming of the application protocole would 
avoid this situation and we are willing to debug it.
But, as an empty frame is no use, and does not have any meaning for ROSE 
protocole, we may consider filtering zero length data both when sending and 
receiving socket data.

The proposed patch repairs BBS data exchange through ROSE network that were 
broken since 2.6.22.11 kernel.

Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>
---
 net/rose/af_rose.c |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/net/rose/af_rose.c b/net/rose/af_rose.c
index 8a54cff..92af3a6 100644
--- a/net/rose/af_rose.c
+++ b/net/rose/af_rose.c
@@ -1075,6 +1075,10 @@ static int rose_sendmsg(struct kiocb *iocb, struct 
socket *sock,
        unsigned char *asmptr;
        int n, size, qbit = 0;
 
+       /* ROSE empty frame has no meaning : don't send */
+       if (len == 0)
+               return 0;
+
        if (msg->msg_flags & ~(MSG_DONTWAIT|MSG_EOR|MSG_CMSG_COMPAT))
                return -EINVAL;
 
@@ -1268,6 +1272,12 @@ static int rose_recvmsg(struct kiocb *iocb, struct 
socket *sock,
        skb_reset_transport_header(skb);
        copied     = skb->len;
 
+       /* ROSE empty frame has no meaning : ignore it */
+       if (copied == 0) {
+               skb_free_datagram(sk, skb);
+               return copied;
+       }
+
        if (copied > size) {
                copied = size;
                msg->msg_flags |= MSG_TRUNC;
-- 
1.5.5

             reply	other threads:[~2008-11-22 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 10:08 Bernard Pidoux [this message]
2008-11-23 23:56 ` [PATCH] [ROSE] zero length frame filtering in af_rose.c David Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-11-24 21:49 Bernard Pidoux
2008-11-25  8:57 ` David Miller

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=200811221108.54242.bpidoux@free.fr \
    --to=bpidoux@free.fr \
    --cc=davem@davemloft.net \
    --cc=f6bvp@amsat.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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).