[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180219171531.GA27498@redhat.com>
Date: Mon, 19 Feb 2018 12:15:32 -0500
From: Mike Snitzer <snitzer@...hat.com>
To: Thorsten Leemhuis <regressions@...mhuis.info>
Cc: Milan Broz <gmazyland@...il.com>, NeilBrown <neilb@...e.com>,
device-mapper development <dm-devel@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: DM Regression in 4.16-rc1 - read() returns data when it shouldn't
On Mon, Feb 19 2018 at 8:44am -0500,
Thorsten Leemhuis <regressions@...mhuis.info> wrote:
> JFYI: This issues is tracked in the regression reports for Linux 4.16
> (http://bit.ly/lnxregrep416 ) with this id:
>
> Linux-Regression-ID: lr#9e195f
>
> Please include this line in the comment section of patches that are
> supposed to fix the issue. Please also mention the string once in other
> mailinglist threads or different bug tracking entries if you or someone
> else start to discuss the issue there. By including that string you make
> it a whole lot easier to track where an issue gets discussed and how far
> patches to fix it have made it. For more details on this please see
> here: http://bit.ly/lnxregtrackid
>
> Thx for your help. Ciao, Thorsten
The fix was already merged by Linus on Friday, see:
git.kernel.org/linus/8dd601fa8317243be887458c49f6c29c2f3d719f
But moving forward I have no interest in sprinkling external metadata
references in Linux commit headers.
Seems more like you're engineering something that gives you, and
possibly a select few others, meaning but that is make work for all
Linux maintainers.
Mike
Powered by blists - more mailing lists