All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: allan.stephens@windriver.com, netdev@vger.kernel.org,
	jon.maloy@ericsson.com, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH]: tipc: Fix oops on send prior to entering networked mode
Date: Wed, 24 Feb 2010 20:42:07 -0500	[thread overview]
Message-ID: <20100225014207.GB10527@localhost.localdomain> (raw)
In-Reply-To: <20100224.173436.212403104.davem@davemloft.net>

On Wed, Feb 24, 2010 at 05:34:36PM -0800, David Miller wrote:
> From: "Stephens, Allan" <allan.stephens@windriver.com>
> Date: Wed, 24 Feb 2010 11:05:12 -0800
> 
> > Have you tried upgrading your system to use TIPC 1.7.6 (available at
> > http://tipc.sourceforge.net/tipc_linux.html)?  This is a significant
> > revised and enhanced version of TIPC that hasn't yet made its way into
> > mainsteam Linux, and seems to be the version-of-choice for most TIPC
> > users.  It also appears to avoid a number of the issues that currently
> > exist in TIPC 1.6, including the one caused by the random configuration
> > command you mentioned in your email below.
> > 
> > I didn't have a problem with you working on a small patch for TIPC 1.6
> > to get around a limited problem, but I'd hate to see you waste time on
> > fixing issues that have already been addressed in TIPC 1.7.
> 
> Why is the TIPC kernel protocol code being developed out of tree
> instead of directly upstream?
> 
> Regardless of that, if the code is in the kernel tree and it can be
> OOPS'd, we must fix it.
> 
Agreed, with a combination of:
1) The patch which Allan posted to check tipc_net.zone and tipc_local_nodes for
being NULL in tipc_select_node

2) The patch that I asked Allan to extract from the sourceforge package which
adds checks for TIPC_NET_MODE in the appropriate places

3) The patch I posted to close the race in the setting of tipc_mode

we should fix all the oopses I've found so far.

Ideally it would seem what would be most appropriate would be to wholesale
import tipc 1.7.6 from sourceforge to the kernel to get all the fixes that have
gone in there.  That seems like its been waiting in the wings for over a year
now.

Neil


  reply	other threads:[~2010-02-25  1:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 19:40 [PATCH]: tipc: Fix oops on send prior to entering networked mode Neil Horman
2010-02-22 22:44 ` Stephens, Allan
2010-02-23  1:11   ` Neil Horman
2010-02-23 15:02     ` Stephens, Allan
2010-02-23 16:09       ` Neil Horman
2010-02-23 16:21         ` Stephens, Allan
2010-02-24 18:53           ` Neil Horman
2010-02-24 19:05             ` Stephens, Allan
2010-02-24 21:15               ` Neil Horman
2010-02-25  1:38                 ` David Miller
2010-02-25 14:24                   ` Stephens, Allan
2010-02-25 15:06                     ` David Miller
2010-02-25 16:24                       ` Stephens, Allan
2010-02-25 15:13                     ` David Miller
2010-02-25 15:23                     ` Neil Horman
2010-02-25 20:33                       ` Stephens, Allan
2010-02-25 21:14                         ` Neil Horman
2010-02-24 21:19               ` Neil Horman
2010-02-25  1:34               ` David Miller
2010-02-25  1:42                 ` Neil Horman [this message]
2010-03-02 18:33 ` [PATCH]: tipc: Fix oops on send prior to entering networked mode (v2) Neil Horman
2010-03-03 16:51   ` Stephens, Allan
2010-03-03 18:31     ` [PATCH]: tipc: Fix oops on send prior to entering networked mode (v3) Neil Horman
2010-03-04  8:40       ` David Miller
2010-03-08 20:19   ` [PATCH]: tipc: Fix oops on send prior to entering networked mode (v2) David Miller
2010-03-08 20:49     ` Neil Horman
2010-03-08 21:13     ` Neil Horman
2010-03-08 21:26       ` 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=20100225014207.GB10527@localhost.localdomain \
    --to=nhorman@tuxdriver.com \
    --cc=allan.stephens@windriver.com \
    --cc=davem@davemloft.net \
    --cc=jon.maloy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.