linux-kernel - LSI Fusion mpt driver queue full message really harmless?

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]

Date:	Thu, 24 Apr 2014 15:36:30 +0200
From:	Raphaël Bauduin <rblists@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: LSI Fusion mpt driver queue full message really harmless?

Hi,

I'm sending this mail here as a last resort [1], hoping someone can help me, as on recent kernels (tested 3.2, 3.11, 3.12, 3.13, 3.14), I get 
this message from the LSI Fusion mpt driver for the disk containing the root partition of the server:
  strange observation, the queue depth is (64) meanwhile fw queue depth (65)

Seems that handling the queue full event (http://lxr.oss.org.cn/source/drivers/message/fusion/mptsas.c#L4091 ) was added in 2.6.31, but running 
2.6.32.61 I do not have this message.

I've seen one discussion on the web of this problem (but related to the 2.6.32 kernel) where it was said that this message is harmless, but I'd 
like a confirmation of this. Can I be sure there won't be any data loss related to this message?

System information are available in the ticket I opened at https://bugzilla.kernel.org/show_bug.cgi?id=74011
This is happening for 2 similar servers, one of which seeing very low load.

Thanks in advance for your help!

Raphaël

[1] having contacted the linux-scsi ml, the LSI driver devs, opened a bug report and contacted one individual LSI dev before, but getting no 
response.

--
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/