From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
AliOS system security <alios_sys_security@linux.alibaba.com>,
Colin Ian King <colin.king@canonical.com>,
Eric Biggers <ebiggers@google.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Milan Broz <gmazyland@gmail.com>,
Nikos Tsironis <ntsironis@arrikto.com>,
Shenghui Wang <shhuiw@foxmail.com>,
Sweet Tea <sweettea@redhat.com>,
wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
Subject: Re: [git pull] device mapper changes for 4.21
Date: Sun, 30 Dec 2018 01:06:46 -0800 [thread overview]
Message-ID: <20181230090646.GB1022@infradead.org> (raw)
In-Reply-To: <20181227160944.GA12190@redhat.com>
On Thu, Dec 27, 2018 at 11:09:44AM -0500, Mike Snitzer wrote:
> - Fix various DM targets to check for device sector overflow if
> CONFIG_LBDAF is not set.
Question to Jens and Linus:
is there any good reason to keep the CONFIG_LBDAF=n option around?
Less than 2gig block devices seem to be an absolutele niche, and I
wonder if it is still worth maintaining the special case just for that.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Sweet Tea <sweettea@redhat.com>,
wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>,
AliOS system security <alios_sys_security@linux.alibaba.com>,
Nikos Tsironis <ntsironis@arrikto.com>,
Eric Biggers <ebiggers@google.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
Shenghui Wang <shhuiw@foxmail.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Mikulas Patocka <mpatocka@redhat.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Colin Ian King <colin.king@canonical.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Milan Broz <gmazyland@gmail.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [git pull] device mapper changes for 4.21
Date: Sun, 30 Dec 2018 01:06:46 -0800 [thread overview]
Message-ID: <20181230090646.GB1022@infradead.org> (raw)
In-Reply-To: <20181227160944.GA12190@redhat.com>
On Thu, Dec 27, 2018 at 11:09:44AM -0500, Mike Snitzer wrote:
> - Fix various DM targets to check for device sector overflow if
> CONFIG_LBDAF is not set.
Question to Jens and Linus:
is there any good reason to keep the CONFIG_LBDAF=n option around?
Less than 2gig block devices seem to be an absolutele niche, and I
wonder if it is still worth maintaining the special case just for that.
next prev parent reply other threads:[~2018-12-30 9:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 16:09 [git pull] device mapper changes for 4.21 Mike Snitzer
2018-12-27 16:09 ` Mike Snitzer
2018-12-29 1:30 ` pr-tracker-bot
2018-12-29 1:30 ` pr-tracker-bot
2018-12-30 9:06 ` Christoph Hellwig [this message]
2018-12-30 9:06 ` Christoph Hellwig
2018-12-30 19:15 ` Mikulas Patocka
2018-12-30 19:15 ` Mikulas Patocka
2018-12-31 0:25 ` Linus Torvalds
2018-12-31 0:25 ` Linus Torvalds
2019-01-03 7:27 ` Christoph Hellwig
2019-01-03 7:27 ` Christoph Hellwig
2019-01-03 7:45 ` Milan Broz
2019-01-03 7:45 ` Milan Broz
2018-12-30 19:40 ` James Bottomley
2018-12-30 19:40 ` James Bottomley
2018-12-31 20:10 ` Jens Axboe
2018-12-31 20:10 ` Jens Axboe
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=20181230090646.GB1022@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=alios_sys_security@linux.alibaba.com \
--cc=colin.king@canonical.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=gmazyland@gmail.com \
--cc=heinzm@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=ntsironis@arrikto.com \
--cc=shhuiw@foxmail.com \
--cc=snitzer@redhat.com \
--cc=sweettea@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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.