From: Vishal Verma <vishal@kernel.org>
To: "hch@infradead.org" <hch@infradead.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"axboe@fb.com" <axboe@fb.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"david@fromorbit.com" <david@fromorbit.com>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io
Date: Tue, 26 Apr 2016 09:01:32 -0600 [thread overview]
Message-ID: <1461682892.26226.23.camel@kernel.org> (raw)
In-Reply-To: <20160426083332.GB364@infradead.org>
On Tue, 2016-04-26 at 01:33 -0700, hch@infradead.org wrote:
> On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote:
> >
> > - Application hits EIO doing dax_IO or load/store io
> >
> > - It checks badblocks and discovers it's files have lost data
> >
> > - It write()s those sectors (possibly converted to file offsets
> > using
> > fiemap)
> > ?? ?? * This triggers the fallback path, but if the application is
> > doing
> > this level of recovery, it will know the sector is bad, and write
> > the
> > entire sector
> This sounds like a mess.
>
> >
> > I think if we want to keep allowing arbitrary alignments for the
> > dax_do_io path, we'd need:
> > 1. To represent badblocks at a finer granularity (likely cache
> > lines)
> > 2. To allow the driver to do IO to a *block device* at sub-sector
> > granularity
> It's not a block device if it supports DAX. It's byte addressable
> memory masquerading as a block device.
Yes but we made that decision a while back with pmem :)
Are you saying it should stop being a block device anymore?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Vishal Verma <vishal@kernel.org>
To: "hch@infradead.org" <hch@infradead.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"axboe@fb.com" <axboe@fb.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"david@fromorbit.com" <david@fromorbit.com>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io
Date: Tue, 26 Apr 2016 09:01:32 -0600 [thread overview]
Message-ID: <1461682892.26226.23.camel@kernel.org> (raw)
In-Reply-To: <20160426083332.GB364@infradead.org>
On Tue, 2016-04-26 at 01:33 -0700, hch@infradead.org wrote:
> On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote:
> >
> > - Application hits EIO doing dax_IO or load/store io
> >
> > - It checks badblocks and discovers it's files have lost data
> >
> > - It write()s those sectors (possibly converted to file offsets
> > using
> > fiemap)
> > ?? ?? * This triggers the fallback path, but if the application is
> > doing
> > this level of recovery, it will know the sector is bad, and write
> > the
> > entire sector
> This sounds like a mess.
>
> >
> > I think if we want to keep allowing arbitrary alignments for the
> > dax_do_io path, we'd need:
> > 1. To represent badblocks at a finer granularity (likely cache
> > lines)
> > 2. To allow the driver to do IO to a *block device* at sub-sector
> > granularity
> It's not a block device if it supports DAX. It's byte addressable
> memory masquerading as a block device.
Yes but we made that decision a while back with pmem :)
Are you saying it should stop being a block device anymore?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Vishal Verma <vishal@kernel.org>
To: "hch@infradead.org" <hch@infradead.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "axboe@fb.com" <axboe@fb.com>, "jack@suse.cz" <jack@suse.cz>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io
Date: Tue, 26 Apr 2016 09:01:32 -0600 [thread overview]
Message-ID: <1461682892.26226.23.camel@kernel.org> (raw)
In-Reply-To: <20160426083332.GB364@infradead.org>
On Tue, 2016-04-26 at 01:33 -0700, hch@infradead.org wrote:
> On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote:
> >
> > - Application hits EIO doing dax_IO or load/store io
> >
> > - It checks badblocks and discovers it's files have lost data
> >
> > - It write()s those sectors (possibly converted to file offsets
> > using
> > fiemap)
> > ?? ?? * This triggers the fallback path, but if the application is
> > doing
> > this level of recovery, it will know the sector is bad, and write
> > the
> > entire sector
> This sounds like a mess.
>
> >
> > I think if we want to keep allowing arbitrary alignments for the
> > dax_do_io path, we'd need:
> > 1. To represent badblocks at a finer granularity (likely cache
> > lines)
> > 2. To allow the driver to do IO to a *block device* at sub-sector
> > granularity
> It's not a block device if it supports DAX. It's byte addressable
> memory masquerading as a block device.
Yes but we made that decision a while back with pmem :)
Are you saying it should stop being a block device anymore?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Vishal Verma <vishal@kernel.org>
To: "hch@infradead.org" <hch@infradead.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"axboe@fb.com" <axboe@fb.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"david@fromorbit.com" <david@fromorbit.com>,
"jack@suse.cz" <jack@suse.cz>
Subject: Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io
Date: Tue, 26 Apr 2016 09:01:32 -0600 [thread overview]
Message-ID: <1461682892.26226.23.camel@kernel.org> (raw)
In-Reply-To: <20160426083332.GB364@infradead.org>
On Tue, 2016-04-26 at 01:33 -0700, hch@infradead.org wrote:
> On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote:
> >
> > - Application hits EIO doing dax_IO or load/store io
> >
> > - It checks badblocks and discovers it's files have lost data
> >
> > - It write()s those sectors (possibly converted to file offsets
> > using
> > fiemap)
> > ?? ?? * This triggers the fallback path, but if the application is
> > doing
> > this level of recovery, it will know the sector is bad, and write
> > the
> > entire sector
> This sounds like a mess.
>
> >
> > I think if we want to keep allowing arbitrary alignments for the
> > dax_do_io path, we'd need:
> > 1. To represent badblocks at a finer granularity (likely cache
> > lines)
> > 2. To allow the driver to do IO to a *block device* at sub-sector
> > granularity
> It's not a block device if it supports DAX.A A It's byte addressable
> memory masquerading as a block device.
Yes but we made that decision a while back with pmem :)
Are you saying it should stop being a block device anymore?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info atA A http://vger.kernel.org/majordomo-info.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-04-26 15:01 UTC|newest]
Thread overview: 216+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 1:59 [PATCH v2 0/5] dax: handling of media errors Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` [PATCH v2 1/5] block, dax: pass blk_dax_ctl through to drivers Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 4:19 ` kbuild test robot
2016-03-30 4:19 ` kbuild test robot
2016-03-30 4:19 ` kbuild test robot
2016-03-30 4:19 ` kbuild test robot
2016-04-15 14:55 ` Jeff Moyer
2016-04-15 14:55 ` Jeff Moyer
2016-04-15 14:55 ` Jeff Moyer
2016-03-30 1:59 ` [PATCH v2 2/5] dax: fallback from pmd to pte on error Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-04-15 14:55 ` Jeff Moyer
2016-04-15 14:55 ` Jeff Moyer
2016-04-15 14:55 ` Jeff Moyer
2016-03-30 1:59 ` [PATCH v2 3/5] dax: enable dax in the presence of known media errors (badblocks) Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-04-15 14:56 ` Jeff Moyer
2016-04-15 14:56 ` Jeff Moyer
2016-04-15 14:56 ` Jeff Moyer
2016-03-30 1:59 ` [PATCH v2 4/5] dax: use sb_issue_zerout instead of calling dax_clear_sectors Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-04-15 15:18 ` Jeff Moyer
2016-04-15 15:18 ` Jeff Moyer
2016-04-15 15:18 ` Jeff Moyer
2016-03-30 1:59 ` [PATCH v2 5/5] dax: handle media errors in dax_do_io Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 1:59 ` Vishal Verma
2016-03-30 3:00 ` kbuild test robot
2016-03-30 3:00 ` kbuild test robot
2016-03-30 3:00 ` kbuild test robot
2016-03-30 3:00 ` kbuild test robot
2016-03-30 3:00 ` kbuild test robot
2016-03-30 3:00 ` kbuild test robot
2016-03-30 6:34 ` Christoph Hellwig
2016-03-30 6:34 ` Christoph Hellwig
2016-03-30 6:34 ` Christoph Hellwig
2016-03-30 6:54 ` Vishal Verma
2016-03-30 6:54 ` Vishal Verma
2016-03-30 6:54 ` Vishal Verma
2016-03-30 6:56 ` Christoph Hellwig
2016-03-30 6:56 ` Christoph Hellwig
2016-03-30 6:56 ` Christoph Hellwig
2016-04-15 16:11 ` Jeff Moyer
2016-04-15 16:11 ` Jeff Moyer
2016-04-15 16:11 ` Jeff Moyer
2016-04-15 16:54 ` Verma, Vishal L
2016-04-15 16:54 ` Verma, Vishal L
2016-04-15 16:54 ` Verma, Vishal L
2016-04-15 17:11 ` Jeff Moyer
2016-04-15 17:11 ` Jeff Moyer
2016-04-15 17:11 ` Jeff Moyer
2016-04-15 17:11 ` Jeff Moyer
2016-04-15 17:37 ` Verma, Vishal L
2016-04-15 17:37 ` Verma, Vishal L
2016-04-15 17:57 ` Dan Williams
2016-04-15 17:57 ` Dan Williams
2016-04-15 17:57 ` Dan Williams
2016-04-15 18:06 ` Jeff Moyer
2016-04-15 18:06 ` Jeff Moyer
2016-04-15 18:06 ` Jeff Moyer
2016-04-15 18:06 ` Jeff Moyer
2016-04-15 18:17 ` Dan Williams
2016-04-15 18:17 ` Dan Williams
2016-04-15 18:17 ` Dan Williams
2016-04-15 18:24 ` Jeff Moyer
2016-04-15 18:24 ` Jeff Moyer
2016-04-15 18:24 ` Jeff Moyer
2016-04-15 18:24 ` Jeff Moyer
2016-04-15 18:56 ` Dan Williams
2016-04-15 18:56 ` Dan Williams
2016-04-15 18:56 ` Dan Williams
2016-04-15 19:13 ` Jeff Moyer
2016-04-15 19:13 ` Jeff Moyer
2016-04-15 19:13 ` Jeff Moyer
2016-04-15 19:13 ` Jeff Moyer
2016-04-15 19:01 ` Toshi Kani
2016-04-15 19:01 ` Toshi Kani
2016-04-15 19:01 ` Toshi Kani
2016-04-15 19:01 ` Toshi Kani
2016-04-15 19:08 ` Toshi Kani
2016-04-15 19:08 ` Toshi Kani
2016-04-15 19:08 ` Toshi Kani
2016-04-15 19:08 ` Toshi Kani
2016-04-20 20:59 ` Christoph Hellwig
2016-04-20 20:59 ` Christoph Hellwig
2016-04-20 20:59 ` Christoph Hellwig
2016-04-23 18:08 ` Verma, Vishal L
2016-04-23 18:08 ` Verma, Vishal L
2016-04-25 8:31 ` hch
2016-04-25 8:31 ` hch
2016-04-25 8:31 ` hch
2016-04-25 15:32 ` Jeff Moyer
2016-04-25 15:32 ` Jeff Moyer
2016-04-25 15:32 ` Jeff Moyer
2016-04-25 15:32 ` Jeff Moyer
2016-04-26 8:32 ` hch
2016-04-26 8:32 ` hch
2016-04-26 8:32 ` hch
2016-04-25 17:14 ` Verma, Vishal L
2016-04-25 17:14 ` Verma, Vishal L
2016-04-25 17:21 ` Dan Williams
2016-04-25 17:21 ` Dan Williams
2016-04-25 17:21 ` Dan Williams
2016-04-25 23:25 ` Dave Chinner
2016-04-25 23:25 ` Dave Chinner
2016-04-25 23:25 ` Dave Chinner
2016-04-25 23:25 ` Dave Chinner
2016-04-25 23:25 ` Dave Chinner
2016-04-25 23:34 ` Darrick J. Wong
2016-04-25 23:34 ` Darrick J. Wong
2016-04-25 23:34 ` Darrick J. Wong
2016-04-25 23:34 ` Darrick J. Wong
2016-04-25 23:34 ` Darrick J. Wong
2016-04-25 23:43 ` Dan Williams
2016-04-25 23:43 ` Dan Williams
2016-04-25 23:43 ` Dan Williams
2016-04-26 0:11 ` Dave Chinner
2016-04-26 0:11 ` Dave Chinner
2016-04-26 0:11 ` Dave Chinner
2016-04-26 1:45 ` Dan Williams
2016-04-26 1:45 ` Dan Williams
2016-04-26 1:45 ` Dan Williams
2016-04-26 2:56 ` Dave Chinner
2016-04-26 2:56 ` Dave Chinner
2016-04-26 2:56 ` Dave Chinner
2016-04-26 4:18 ` Dan Williams
2016-04-26 4:18 ` Dan Williams
2016-04-26 4:18 ` Dan Williams
2016-04-26 8:27 ` Dave Chinner
2016-04-26 8:27 ` Dave Chinner
2016-04-26 8:27 ` Dave Chinner
2016-04-26 14:59 ` Dan Williams
2016-04-26 14:59 ` Dan Williams
2016-04-26 14:59 ` Dan Williams
2016-04-26 15:31 ` Jan Kara
2016-04-26 15:31 ` Jan Kara
2016-04-26 15:31 ` Jan Kara
2016-04-26 17:16 ` Dan Williams
2016-04-26 17:16 ` Dan Williams
2016-04-26 17:16 ` Dan Williams
2016-04-25 23:53 ` Verma, Vishal L
2016-04-25 23:53 ` Verma, Vishal L
2016-04-25 23:53 ` Verma, Vishal L
2016-04-26 0:41 ` Dave Chinner
2016-04-26 0:41 ` Dave Chinner
2016-04-26 0:41 ` Dave Chinner
2016-04-26 0:41 ` Dave Chinner
2016-04-26 0:41 ` Dave Chinner
2016-04-26 14:58 ` Vishal Verma
2016-04-26 14:58 ` Vishal Verma
2016-04-26 14:58 ` Vishal Verma
2016-04-26 14:58 ` Vishal Verma
2016-05-02 15:18 ` Jeff Moyer
2016-05-02 15:18 ` Jeff Moyer
2016-05-02 15:18 ` Jeff Moyer
2016-05-02 15:18 ` Jeff Moyer
2016-05-02 17:53 ` Dan Williams
2016-05-02 17:53 ` Dan Williams
2016-05-02 17:53 ` Dan Williams
2016-05-03 0:42 ` Dave Chinner
2016-05-03 0:42 ` Dave Chinner
2016-05-03 0:42 ` Dave Chinner
2016-05-03 1:26 ` Rudoff, Andy
2016-05-03 1:26 ` Rudoff, Andy
2016-05-03 2:49 ` Dave Chinner
2016-05-03 2:49 ` Dave Chinner
2016-05-03 2:49 ` Dave Chinner
2016-05-03 18:30 ` Rudoff, Andy
2016-05-03 18:30 ` Rudoff, Andy
2016-05-03 18:30 ` Rudoff, Andy
2016-05-04 1:36 ` Dave Chinner
2016-05-04 1:36 ` Dave Chinner
2016-05-04 1:36 ` Dave Chinner
2016-05-02 23:04 ` Dave Chinner
2016-05-02 23:04 ` Dave Chinner
2016-05-02 23:04 ` Dave Chinner
2016-05-02 23:04 ` Dave Chinner
2016-05-02 23:04 ` Dave Chinner
2016-05-02 23:17 ` Verma, Vishal L
2016-05-02 23:17 ` Verma, Vishal L
2016-05-02 23:25 ` Dan Williams
2016-05-02 23:25 ` Dan Williams
2016-05-02 23:25 ` Dan Williams
2016-05-03 1:51 ` Dave Chinner
2016-05-03 1:51 ` Dave Chinner
2016-05-03 1:51 ` Dave Chinner
2016-05-03 17:28 ` Dan Williams
2016-05-03 17:28 ` Dan Williams
2016-05-03 17:28 ` Dan Williams
2016-05-04 3:18 ` Dave Chinner
2016-05-04 3:18 ` Dave Chinner
2016-05-04 3:18 ` Dave Chinner
2016-05-04 5:05 ` Dan Williams
2016-05-04 5:05 ` Dan Williams
2016-05-04 5:05 ` Dan Williams
2016-04-26 8:33 ` hch
2016-04-26 8:33 ` hch
2016-04-26 8:33 ` hch
2016-04-26 15:01 ` Vishal Verma [this message]
2016-04-26 15:01 ` Vishal Verma
2016-04-26 15:01 ` Vishal Verma
2016-04-26 15:01 ` Vishal Verma
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=1461682892.26226.23.camel@kernel.org \
--to=vishal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=matthew.r.wilcox@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.