linux-kernel - Re: linux-next: Tree for Feb 4

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <yq1zj8tactc.fsf@sermon.lab.mkp.net>
Date:	Wed, 04 Feb 2015 10:58:23 -0500
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	sedat.dilek@...il.com
Cc:	Jens Axboe <axboe@...nel.dk>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: linux-next: Tree for Feb 4

>>>>> "Sedat" == Sedat Dilek <sedat.dilek@...il.com> writes:

>>>>> I am seeing the following in my logs several times...
>>>>> 
>>>>> Feb 4 02:53:13 fambox kernel: [15507.397482] blk_update_request:
>>>>> I/O error, dev loop0, sector 21261344 Feb 4 02:53:13 fambox
>>>>> kernel: [15507.397531] loop0: DISCARD failed.  Manually zeroing.

Sedat> What's the plan... s/pr_warn/pr_debug ?

The rationale here is that we'd like to log (once) if discard or write
same fail on a given device.

In SCSI we disable these commands if they get failed by the storage. But
it looks like loop keeps advertising discard support after a failure.

Is your loop device encrypted? Do you know why the discard is failing?

-- 
Martin K. Petersen	Oracle Linux Engineering
--
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/