From: David Miller <davem@davemloft.net>
To: frank.blaschka@de.ibm.com
Cc: jgarzik@pobox.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, ursula.braun@de.ibm.com
Subject: Re: [patch 3/6] qeth: avoid crash in case of layer mismatch for VSWITCH
Date: Sun, 04 Jan 2009 17:36:53 -0800 (PST) [thread overview]
Message-ID: <20090104.173653.42738205.davem@davemloft.net> (raw)
In-Reply-To: <20090102150254.617580000@de.ibm.com>
From: frank.blaschka@de.ibm.com
Date: Fri, 02 Jan 2009 16:01:42 +0100
> For z/VM GuestLAN or VSWITCH devices the transport layer is
> configured in z/VM. The layer2 attribute of a participating Linux
> device has to match the z/VM definition. In case of a mismatch
> Linux currently crashes in qeth recovery due to a reference to the
> not yet existing net_device.
> Solution: add a check for existence of net_device and add a message
> pointing to the mismatch of layer definitions in Linux and z/VM.
>
> Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
> Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Applied.
next prev parent reply other threads:[~2009-01-05 1:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 15:01 [patch 0/6] s390: qeth fixes 2.6.29 frank.blaschka
2009-01-02 15:01 ` [patch 1/6] HiperSockets mcl string conversion (pre z9 mach) frank.blaschka
2009-01-05 1:36 ` David Miller
2009-01-02 15:01 ` [patch 2/6] qeth: exploit source MAC address for inbound layer3 packets frank.blaschka
2009-01-05 1:36 ` David Miller
2009-01-02 15:01 ` [patch 3/6] qeth: avoid crash in case of layer mismatch for VSWITCH frank.blaschka
2009-01-05 1:36 ` David Miller [this message]
2009-01-02 15:01 ` [patch 4/6] qeth: do not spin for SETIP ip assist command frank.blaschka
2009-01-05 1:37 ` David Miller
2009-01-02 15:01 ` [patch 5/6] qeth: No large send using EDDP for HiperSockets frank.blaschka
2009-01-05 1:37 ` David Miller
2009-01-02 15:01 ` [patch 6/6] qeth: get rid of extra argument after printk to dev_* conversion frank.blaschka
2009-01-05 1:37 ` 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=20090104.173653.42738205.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=frank.blaschka@de.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ursula.braun@de.ibm.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).