From: Ralf Baechle <ralf@linux-mips.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-hams@vger.kernel.org, netdev@vger.kernel.org,
Steven Whitehouse <swhiteho@redhat.com>,
Richard Stearn <richard@rns-stearn.demon.co.uk>,
f6bvp <f6bvp@free.fr>
Subject: Re: Bpqether broken in 4.1
Date: Thu, 2 Jul 2015 23:55:54 +0200 [thread overview]
Message-ID: <20150702215553.GB20390@linux-mips.org> (raw)
In-Reply-To: <873816e0hg.fsf@x220.int.ebiederm.org>
On Thu, Jul 02, 2015 at 04:03:07PM -0500, Eric W. Biederman wrote:
> > Eric's Commit 1d5da757da860a6916adbf68b09e868062b4b3b8 (ax25: Stop using
> > magic neighbour cache operations.) breaks IP traffic over the AX.25 bpqether
> > driver.
>
> Sigh. NETIF_F_LLTX is not set so recursion does not work :(
>
> So we can either set NETIF_F_LLTX or just rever the offending commit.
The AX.25 stack has a sufficient number of hacks that attempts to fix
any hack is likely to cause issues somewhere else and the header and
neighbour stuff is the worst minefield. I'm happy that your patch at
least concentrates all those hacks in the AX.25 stack itself removing
the impact from the generic networking code.
> I think either will work. ax25 is so very weird it just abuses the
> neighbour table something awful. It ax25 is not caching ip address to
> ax25 address translations in there, ax25 should really not be using the
> neighbour table. Sigh.
>
> So perhaps something like the below will be good enough.
>
> diff --git a/drivers/net/hamradio/bpqether.c b/drivers/net/hamradio/bpqether.c
> index 63ff08a26da8..fc2be36c9425 100644
> --- a/drivers/net/hamradio/bpqether.c
> +++ b/drivers/net/hamradio/bpqether.c
> @@ -483,6 +483,7 @@ static void bpq_setup(struct net_device *dev)
> memcpy(dev->dev_addr, &ax25_defaddr, AX25_ADDR_LEN);
>
> dev->flags = 0;
> + dev->features = NETIF_F_LLTX; /* Allow recursion */
>
> #if defined(CONFIG_AX25) || defined(CONFIG_AX25_MODULE)
> dev->header_ops = &ax25_header_ops;
Thanks, that restored bpqether to work. I will cook up a patch to fix
all other AX.25 drivers.
Thanks!
Ralf
prev parent reply other threads:[~2015-07-02 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 18:38 Bpqether broken in 4.1 Ralf Baechle
2015-07-02 21:03 ` Eric W. Biederman
2015-07-02 21:55 ` Ralf Baechle [this message]
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=20150702215553.GB20390@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ebiederm@xmission.com \
--cc=f6bvp@free.fr \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richard@rns-stearn.demon.co.uk \
--cc=swhiteho@redhat.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).