linux-kernel - Re: [PATCH 0/2] fix regression in direct I/O to pmem devices

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]

Date:	Fri, 14 Aug 2015 16:27:49 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	Matthew R Wilcox <matthew.r.wilcox@...el.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-nvdimm <linux-nvdimm@...1.01.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] fix regression in direct I/O to pmem devices

Dan Williams <dan.j.williams@...el.com> writes:

> On Fri, Aug 14, 2015 at 1:22 PM, Dan Williams <dan.j.williams@...el.com> wrote:
>> On Fri, Aug 14, 2015 at 1:15 PM, Jeff Moyer <jmoyer@...hat.com> wrote:
>>> Linda Knippers noticed that commit bbab37ddc20b (block: Add support
>>> for DAX reads/writes to block devices) caused a regression in mkfs.xfs.
>>> Further investigation also uncovered issues related to misaligned
>>> partitions.  This patch set addresses the two issues.
>>>
>>> [PATCH 1/2] dax: fix O_DIRECT I/O to the last block of a blockdev
>>> [PATCH 2/2] blockdev: don't set S_DAX for misaligned partitions
>>
>> Should these be "Cc: <stable@...r.kernel.org>" given the regression
>> fix is applicable back to 4.0?
>
> Sorry, regression *since* 4.0.

$ git describe --contains bbab37ddc20b
v4.2-rc1~2^2~4

Looks like this was not sprung on the public yet.

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