linux-kernel - RFE: kernel message "rport-2:0-10: blocked FC remote port time out: removing rport"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <544A2550020000A100017826@gwsmtp1.uni-regensburg.de>
Date:	Fri, 24 Oct 2014 10:09:20 +0200
From:	"Ulrich Windl" <Ulrich.Windl@...uni-regensburg.de>
To:	<linux-kernel@...r.kernel.org>
Subject: RFE: kernel message "rport-2:0-10: blocked FC remote port time
 out: removing rport"

Hi!

I'd like to point out that the following Fibre CHannel error message is of little practical use, because it lacks essential information:

kernel: [   68.406963]  rport-2:0-10: blocked FC remote port time out: removing rport
(Seen in the current SLES11 SP3 kernel 3.0.101-0.40-default)

As the logical port is removed (as the message says), you cannot find out what device (i.e. WWN) the problem message refers to.

For existing ports in /sys/class/fc_remote_ports/ you can query port_id, port_name, port_state, etc. But once the port is removed, you cannot get any information about it.

In a real environment, you cannot easily guess where the problem might be, especially as there is no other message about "rport-2:0-10" before it's being removed.

I suggest to include the port ID (you can get the HBA WWN from that) and port WWN (the target device port) in the erro message if possible.

Regards,
Ulrich Windl

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/