From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>, Christoph Hellwig <hch@lst.de>,
Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@kernel.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the device-mapper tree with Linus' tree
Date: Tue, 22 Dec 2020 14:15:28 +0100 [thread overview]
Message-ID: <20201222131528.GA29822@lst.de> (raw)
In-Reply-To: <20201222095056.7a5ac0a0@canb.auug.org.au>
Mike, Hannes,
I think this patch is rather harmful. Why does device mapper even
mix file system path with a dev_t and all the other weird forms
parsed by name_to_dev_t, which was supposed to be be for the early
init code where no file system is available.
Can we please kick off a proper discussion for this on the linux-block
list?
next prev parent reply other threads:[~2020-12-22 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 22:50 linux-next: manual merge of the device-mapper tree with Linus' tree Stephen Rothwell
2020-12-22 13:15 ` Christoph Hellwig [this message]
2020-12-22 14:53 ` DM's filesystem lookup in dm_get_dev_t() [was: Re: linux-next: manual merge of the device-mapper tree with Linus' tree] Mike Snitzer
2020-12-22 17:24 ` Hannes Reinecke
2020-12-22 21:06 ` [dm-devel] " Alasdair G Kergon
2020-12-23 8:06 ` Christoph Hellwig
2020-12-23 8:05 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-03-29 22:53 linux-next: manual merge of the device-mapper tree with Linus' tree Stephen Rothwell
2013-03-04 0:36 Stephen Rothwell
2009-10-05 3:41 Stephen Rothwell
2009-10-05 15:40 ` Jiri Slaby
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=20201222131528.GA29822@lst.de \
--to=hch@lst.de \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox