Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) client-ip=23.128.96.36;
From:   =?utf-8?Q?Bj=C3=B8rn_Mork?= <bjorn@mork.no>
To:     Stefan x Nilsson <stefan.x.nilsson@axis.com>
Cc:     "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
        <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <kernel@axis.com>
Subject: Re: [PATCH net-next] qmi_wwan: Add rawip module param
Organization: m
References: <20230912-qmiraw-v1-1-21bc812fa0cf@axis.com>
        <87a5tramab.fsf@miraculix.mork.no>
        <42522712-b739-3db4-9111-a4b378a65809@axis.com>
Date:   Tue, 12 Sep 2023 11:45:36 +0200
In-Reply-To: <42522712-b739-3db4-9111-a4b378a65809@axis.com> (Stefan
        x. Nilsson's message of "Tue, 12 Sep 2023 09:44:26 +0200")
Message-ID: <874jjzafnj.fsf@miraculix.mork.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Stefan x Nilsson <stefan.x.nilsson@axis.com> writes:

> Would a quirk on the affected modem be an better/acceptable solution?

More acceptable but still needs justification.

I'm probably missing something, but I don't see the described issue even
if I assume a device crashing if it sees an ethernet header.

The netdev and associated chardev are created when a USB device is
connected.  The device knows nothing about this.  It answers a few USB
descriptor requests and that's it.  The host is free to switch the
netdev to raw-ip framing before bringing it up.  There is no need to
send any frames with eithernet header.  There is no relationship between
framing and the QMI control channel.  But the host is in complete
control of any communication there too, so it wouldn't be a problam if
there were.


Bj=C3=B8rn