Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Ralf Baechle DO1GRB <ralf@linux-mips.org>
To: Steve Whitehouse <Steve@ChyGwyn.com>
Cc: M Taylor <mctylr@privacy.nb.ca>, linux-hams@vger.kernel.org
Subject: Re: AX.25 in kernel 2.5 status?
Date: Fri, 11 Oct 2002 16:35:42 +0200	[thread overview]
Message-ID: <20021011163542.A17419@linux-mips.org> (raw)
In-Reply-To: <200210111347.OAA20311@gw.chygwyn.com>; from steve@gw.chygwyn.com on Fri, Oct 11, 2002 at 02:47:36PM +0100

On Fri, Oct 11, 2002 at 02:47:36PM +0100, Steven Whitehouse wrote:

> > I yesterday published my changes to redo the /proc files for AX.25,
> > NET/ROM and ROSE with the seq_file stuff.  As usually these changesets
> > are available at http://linux-ham.bkbits.net/linux-2.5.
> > 
> > 73 de DO1GRB op Ralf
> 
> It seems you beat me to it :-) though there is one extra thing that still needs
> to be fixed in the uid code from my patch where ax25_findbyuid() returns
> a pointer to a structure which might disappear at any time. Its only use
> is to check permissions at bind time, so I just moved the check under
> the lock,

Unfortunately the code is full of such funnies.  Remember as the code is
in 2.5 there are no more locks outside protecting us from our own thread
safety - or rather the lack thereof.  In particular the socket locking
is rather hard to get right.

Another problem we still have - and we're sharing it with other protocols
such ipv4 - is that our proc code is holding a lock for the time the
/proc file is open.  That's not a significant time but it may delay
access, so I've made most of those loads rw locks.  Worst case a buggy
or malicious piece of software might even hold a proc file open for a long
time thereby stalling the functioning of the stack partially or fully.

If you could update your fix I certainly would accept it :)

73 de DO1GRB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21

  reply	other threads:[~2002-10-11 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10  2:57 AX.25 in kernel 2.5 status? M Taylor
2002-10-10 17:22 ` Ralf Baechle DO1GRB
2002-10-11  9:49 ` Steven Whitehouse
2002-10-11 13:03   ` Ralf Baechle DO1GRB
2002-10-11 13:47     ` Steven Whitehouse
2002-10-11 14:35       ` Ralf Baechle DO1GRB [this message]
2002-10-11 14:56         ` Steven Whitehouse
2002-10-11 15:38           ` Ralf Baechle DO1GRB

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=20021011163542.A17419@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Steve@ChyGwyn.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=mctylr@privacy.nb.ca \
    /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