linux-kernel - Re: [PATCH 4/4] xen/blkfront: cope with backend that fail empty BLKIF_OP_WRITE

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

Message-ID: <20101102165434.GA19703@lst.de>
Date:	Tue, 2 Nov 2010 17:54:34 +0100
From:	Christoph Hellwig <hch@....de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Daniel Stodden <daniel.stodden@...rix.com>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: [PATCH 4/4] xen/blkfront: cope with backend that fail empty BLKIF_OP_WRITE_BARRIER requests

>  				       info->gd->disk_name);
>  				error = -EOPNOTSUPP;
> +			}
> +			if (unlikely(bret->status == BLKIF_RSP_ERROR &&
> +				     info->shadow[id].req.nr_segments == 0)) {
> +				printk(KERN_WARNING "blkfront: %s: empty write barrier op failed\n",
> +				       info->gd->disk_name);
> +				error = -EOPNOTSUPP;
> +			}

We don't use -EOPNOTSUPP anymore in the new world order, anything
barrier related is just a normal I/O error now.

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