From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>
Cc: Linux Networking Development Mailing List <netdev@oss.sgi.com>
Subject: [PATCH] LLC: fix procfs reading when there are saps without sockets
Date: Sat, 1 Nov 2003 04:55:04 -0200 [thread overview]
Message-ID: <20031101065504.GK3705@conectiva.com.br> (raw)
Hi David,
Noticed while on a ssh over PF_LLC session on a machine that had
Appletalk/SNAP running, doing a cat /proc/net/llc/socket returned nothing
when there were the sshd listening socket and the ssh connection. Just
removing this anyway uneeded test fix this bug. Please apply.
Best Regards,
- Arnaldo
===== net/llc/llc_proc.c 1.20 vs edited =====
--- 1.20/net/llc/llc_proc.c Thu Oct 30 16:35:41 2003
+++ edited/net/llc/llc_proc.c Sat Nov 1 04:48:06 2003
@@ -48,8 +48,6 @@
--pos;
}
read_unlock_bh(&sap->sk_list.lock);
- if (!pos)
- break;
}
sk = NULL;
found:
next reply other threads:[~2003-11-01 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 6:55 Arnaldo Carvalho de Melo [this message]
2003-11-02 7:10 ` [PATCH] LLC: fix procfs reading when there are saps without sockets David S. 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=20031101065504.GK3705@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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).