From: Mike Snitzer <snitzer@redhat.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Milan Broz <gmazyland@gmail.com>, NeilBrown <neilb@suse.com>,
device-mapper development <dm-devel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DM Regression in 4.16-rc1 - read() returns data when it shouldn't
Date: Mon, 19 Feb 2018 12:15:32 -0500 [thread overview]
Message-ID: <20180219171531.GA27498@redhat.com> (raw)
In-Reply-To: <5fca4e3f-536c-9c52-31bb-927e8ab5b6c8@leemhuis.info>
On Mon, Feb 19 2018 at 8:44am -0500,
Thorsten Leemhuis <regressions@leemhuis.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
next prev parent reply other threads:[~2018-02-19 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:02 DM Regression in 4.16-rc1 - read() returns data when it shouldn't Milan Broz
2018-02-14 20:39 ` NeilBrown
2018-02-14 23:05 ` Mike Snitzer
2018-02-15 0:07 ` [dm-devel] " NeilBrown
2018-02-15 7:37 ` Milan Broz
2018-02-15 8:52 ` NeilBrown
2018-02-15 9:00 ` [PATCH] dm: correctly handle chained bios in dec_pending() NeilBrown
2018-02-15 9:01 ` [RFC PATCH] dm: don't assign zero to ->bi_status of an active bio NeilBrown
2018-02-15 9:09 ` [PATCH] block: be more careful about status in __bio_chain_endio NeilBrown
2019-02-22 21:10 ` Mike Snitzer
2019-02-22 22:46 ` Jens Axboe
2019-02-22 23:55 ` Mike Snitzer
2019-02-23 2:02 ` John Dorminy
2019-02-23 2:44 ` Mike Snitzer
2019-02-23 3:10 ` John Dorminy
2019-06-12 2:56 ` John Dorminy
2019-06-12 7:01 ` Christoph Hellwig
2019-06-17 7:32 ` Hannes Reinecke
2018-02-19 13:44 ` DM Regression in 4.16-rc1 - read() returns data when it shouldn't Thorsten Leemhuis
2018-02-19 17:15 ` Mike Snitzer [this message]
2018-02-26 10:14 ` Thorsten Leemhuis
2018-02-26 11:01 ` NeilBrown
2018-02-26 17:31 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180219171531.GA27498@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=regressions@leemhuis.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox