On Thu, Aug 27, 2020 at 2:25 PM Ross Zwisler wrote:
> On Thu, Aug 27, 2020 at 09:10:15PM +0100, Al Viro wrote:
> > On Thu, Aug 27, 2020 at 09:08:01PM +0100, Al Viro wrote:
> > Applied (to -rc1) and pushed
>
> Many thanks!
(apologies for the resend, the previous one had
On Thu, Aug 27, 2020 at 09:10:15PM +0100, Al Viro wrote:
> On Thu, Aug 27, 2020 at 09:08:01PM +0100, Al Viro wrote:
> > AFAICS, it applies clean to -rc1; what was the rebase about?
Oh, sorry if that was confusing, I just wanted to make sure that it still
applied cleanly to the latest -rc so that
with
the 'nosymfollow' option.
Signed-off-by: Ross Zwisler
---
tools/testing/selftests/mount/.gitignore | 1 +
tools/testing/selftests/mount/Makefile| 4 +-
.../selftests/mount/nosymfollow-test.c| 218 ++
.../selftests/mount/run_nosymfollow.sh| 4
dening-against-malicious-stateful-data#TOC-Restricting-symlink-traversal
Signed-off-by: Mattias Nissler
Signed-off-by: Ross Zwisler
Reviewed-by: Aleksa Sarai
---
Changes since v8 [1]:
* Look for MNT_NOSYMFOLLOW in link->mnt->mnt_flags so we are testing
the link itself rather than t
On Fri, Aug 28, 2020 at 01:41:39AM +1000, Aleksa Sarai wrote:
> On 2020-08-27, Al Viro wrote:
> > On Wed, Aug 26, 2020 at 02:48:19PM -0600, Ross Zwisler wrote:
> >
> > > Al, now that the changes to fs/namei.c have landed and we're past the
> > > merge
>
O Wed, Aug 19, 2020 at 10:43:16AM -0600, Ross Zwisler wrote:
> From: Mattias Nissler
>
> For mounts that have the new "nosymfollow" option, don't follow symlinks
> when resolving paths. The new option is similar in spirit to the
> existing "nodev", &quo
with
the 'nosymfollow' option.
Signed-off-by: Ross Zwisler
---
tools/testing/selftests/mount/.gitignore | 1 +
tools/testing/selftests/mount/Makefile| 4 +-
.../selftests/mount/nosymfollow-test.c| 218 ++
.../selftests/mount/run_nosymfollow.sh| 4
dening-against-malicious-stateful-data#TOC-Restricting-symlink-traversal
Signed-off-by: Mattias Nissler
Signed-off-by: Ross Zwisler
Reviewed-by: Aleksa Sarai
---
Changes since v7 [1]:
* Rebased onto v5.9-rc1.
* Added selftest in second patch.
* Added Aleska's Reviewed-By tag. Thank you fo
On Wed, Aug 12, 2020 at 12:36 PM Matthew Wilcox wrote:
> On Tue, Aug 11, 2020 at 04:28:03PM -0600, Ross Zwisler wrote:
> > diff --git a/include/uapi/linux/mount.h b/include/uapi/linux/mount.h
> > index 96a0240f23fed..dd8306ea336c1 100644
> > --- a/include/uapi/linux/mount.h
&
On Tue, Aug 11, 2020 at 7:43 PM Aleksa Sarai wrote:
> On 2020-08-11, Ross Zwisler wrote:
> > From: Mattias Nissler
> >
> > For mounts that have the new "nosymfollow" option, don't follow symlinks
> > when resolving paths. The new option is similar in spirit
dening-against-malicious-stateful-data#TOC-Restricting-symlink-traversal
Signed-off-by: Mattias Nissler
Signed-off-by: Ross Zwisler
---
Changes since v6 [1]:
* Rebased onto v5.8.
* Another round of testing including readlink(1), readlink(2),
realpath(1), realpath(3), statfs(2) and mount(2) t
Commit-ID: 013c66edf207ddb78422b8b636f56c87939c9e34
Gitweb: https://git.kernel.org/tip/013c66edf207ddb78422b8b636f56c87939c9e34
Author: Ross Zwisler
AuthorDate: Mon, 1 Jul 2019 09:52:08 -0600
Committer: Ingo Molnar
CommitDate: Tue, 9 Jul 2019 13:57:31 +0200
Revert "x86/build:
Commit-ID: 77a1619947ab31564aed54621d5b1e34af9b395d
Gitweb: https://git.kernel.org/tip/77a1619947ab31564aed54621d5b1e34af9b395d
Author: Ross Zwisler
AuthorDate: Mon, 1 Jul 2019 09:52:08 -0600
Committer: Thomas Gleixner
CommitDate: Tue, 2 Jul 2019 21:09:44 +0200
Revert "x86/build:
the ability to compile the kernel with these
tools.
Signed-off-by: Ross Zwisler
---
arch/x86/kernel/vmlinux.lds.S | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
index 0850b5149345..4d1517022a14 100644
--- a/arch
tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Ross-Zwisler/mm-add-filemap_fdatawait_range_keep_errors/20190623-181603
> config: x86_64-rhel-7.6 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
>
On Thu, Jun 20, 2019 at 3:25 PM Theodore Ts'o wrote:
> On Thu, Jun 20, 2019 at 09:18:38AM -0600, Ross Zwisler wrote:
> > diff --git a/include/linux/jbd2.h b/include/linux/jbd2.h
> > index 5c04181b7c6d8..0e0393e7f41a4 100644
> > --- a/include/linux/jbd2.h
> >
tion is still being appended to.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
Cc: sta...@vger.kernel.org
---
fs/jbd2/commit.c | 23 ++--
fs/jbd2/journal.c | 2 ++
fs/jbd2/transaction.c | 49 ---
include/linux/jbd2.h
the old behavior.
Ross Zwisler (3):
mm: add filemap_fdatawait_range_keep_errors()
jbd2: introduce jbd2_inode dirty range scoping
ext4: use jbd2_inode dirty range scoping
fs/ext4/ext4_jbd2.h | 12 +--
fs/ext4/inode.c | 13 +---
fs/ext4/move_extent.c | 3 ++-
fs/jbd2
Use the newly introduced jbd2_inode dirty range scoping to prevent us
from waiting forever when trying to complete a journal transaction.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
Cc: sta...@vger.kernel.org
---
fs/ext4/ext4_jbd2.h | 12 ++--
fs/ext4/inode.c | 13
In the spirit of filemap_fdatawait_range() and
filemap_fdatawait_keep_errors(), introduce
filemap_fdatawait_range_keep_errors() which both takes a range upon
which to wait and does not clear errors from the address space.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
Cc: sta
On Thu, Jun 20, 2019 at 01:04:54PM +0200, Jan Kara wrote:
> On Wed 19-06-19 11:21:55, Ross Zwisler wrote:
> > Currently both journal_submit_inode_data_buffers() and
> > journal_finish_inode_data_buffers() operate on the entire address space
> > of each of the inodes associated
On Sun, Jun 9, 2019 at 1:00 PM Johannes Hirte
wrote:
> On 2019 Jun 09, Klaus Kusche wrote:
> > Hello,
> >
> > Same problem for linux 5.1.7:
> > Kernel building fails with the same relocation error.
> >
> > 5.1.5 does not have the problem, builds fine for me.
> >
> > Is there anything I can do to
which don't (yet?) take advantage of this scoping (ocfs2) will continue to
have the old behavior.
Ross Zwisler (3):
mm: add filemap_fdatawait_range_keep_errors()
jbd2: introduce jbd2_inode dirty range scoping
ext4: use jbd2_inode dirty range scoping
fs/ext4/ext4_jbd2.h | 12 +--
fs
Use the newly introduced jbd2_inode dirty range scoping to prevent us
from waiting forever when trying to complete a journal transaction.
Signed-off-by: Ross Zwisler
---
fs/ext4/ext4_jbd2.h | 12 ++--
fs/ext4/inode.c | 13 ++---
fs/ext4/move_extent.c | 3 ++-
3 files
In the spirit of filemap_fdatawait_range() and
filemap_fdatawait_keep_errors(), introduce
filemap_fdatawait_range_keep_errors() which both takes a range upon
which to wait and does not clear errors from the address space.
Signed-off-by: Ross Zwisler
---
include/linux/fs.h | 2 ++
mm/filemap.c
tion is still being appended to.
Signed-off-by: Ross Zwisler
---
fs/jbd2/commit.c | 26 +--
fs/jbd2/journal.c | 2 ++
fs/jbd2/transaction.c | 49 ---
include/linux/jbd2.h | 22 +++
4 files changed, 72 insertions(+)
On Thu, May 09, 2019 at 07:41:47PM +0200, Greg KH wrote:
> On Sun, May 05, 2019 at 03:15:53PM +0200, Greg KH wrote:
> > On Fri, May 03, 2019 at 01:45:03PM -0600, Ross Zwisler wrote:
> > > From: Ross Zwisler
> > >
> > > commit 0efa3334d65b7
From: Ross Zwisler
commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream.
Currently in sst_dsp_new() if we get an error return from sst_dma_new()
we just print an error message and then still complete the function
successfully. This means that we are trying to run without sst->dma
prope
On Fri, May 3, 2019 at 2:17 AM Takashi Iwai wrote:
>
> On Thu, 02 May 2019 19:27:00 +0200,
> Ross Zwisler wrote:
> >
> > Several sound related entries in MAINTAINERS refer to the old git tree
> > at "git://git.alsa-project.org/alsa-kernel.git". This
Several sound related entries in MAINTAINERS refer to the old git tree
at "git://git.alsa-project.org/alsa-kernel.git". This is no longer used
for development, and Takashi Iwai's kernel.org tree is used instead.
Signed-off-by: Ross Zwisler
---
MAINTAINERS | 13 ++---
1 file
On Fri, Apr 26, 2019 at 06:52:45PM +, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees:
18
IP: sst_dsp_dma_get_channel+0x4f/0x125 [snd_soc_sst_firmware]
Fix this by adding proper error handling for the case where we fail to
set up DMA.
This change only affects Haswell and Broadwell systems. Baytrail
systems explicilty opt-out of DMA via sst->pdata->resindex_dma_base
being set to -1.
S
On Fri, Apr 26, 2019 at 04:03:47PM -0500, Pierre-Louis Bossart wrote:
> On 4/26/19 11:47 AM, Ross Zwisler wrote:
> > Currently in sst_dsp_new() if we get an error return from sst_dma_new()
> > we just print an error message and then still complete the function
> > successfully
18
IP: sst_dsp_dma_get_channel+0x4f/0x125 [snd_soc_sst_firmware]
Fix this by adding proper error handling for the case where we fail to
set up DMA.
Signed-off-by: Ross Zwisler
Cc: sta...@vger.kernel.org
---
sound/soc/intel/common/sst-firmware.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
On Mon, Apr 15, 2019 at 03:00:31PM -0600, Raul E Rangel wrote:
> The SD Physical Layer Spec says the following: Since the SD Memory Card
> shall support at least the two bus modes 1-bit or 4-bit width, then any SD
> Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101").
>
> This change
version: 0, command: GET_VERSION */
> /* cros_ec_cmd: version: 0, command: GET_PROTOCOL_INFO */
> /* cros_ec_cmd: version: 1, command: GET_CMD_VERSIONS */
> /* cros_ec_cmd: version: 1, command: USB_PD_CONTROL */
>
> Signed-off-by: Raul E Rangel
Reviewed-by: Ross Zwisler
l requests.
> >
> > Ira and Keith are now involved with the NVDIMM and Device-DAX
> > sub-systems.
> >
> > The linux-nvdimm mailing hosts a patchwork instance for both DAX and
> > NVDIMM patches.
> >
> > Cc: Jan Kara
> > Cc: Ira Weiny
> > C
On Thu, Dec 20, 2018 at 04:25:55PM -0700, Ross Zwisler wrote:
> From: Dylan Reid
>
> The DACs volume can go over 0, both according to the data sheet and
> real world testing. The control can go up to +30dB.
>
> This was tested by playing audio at full volume on a samus chrom
On Fri, Dec 21, 2018 at 11:23:07AM -0800, Dhinakaran Pandiyan wrote:
> On Fri, 2018-12-21 at 10:23 -0700, Ross Zwisler wrote:
> > The following commit:
> >
> > commit 2bdd045e3a30 ("drm/i915/psr: Check if VBT says PSR can be
> > enabled.")
> >
>
aults to 0.
Remove this dead code, simplify the way that enable_psr is handled and
update the module parameter string to match the actual functionality.
Cc: Dhinakaran Pandiyan
Cc: Rodrigo Vivi
Signed-off-by: Ross Zwisler
---
drivers/gpu/drm/i915/i915_drv.h| 1 -
drivers/gpu/drm/i915/i915_pa
From: Dylan Reid
The DACs volume can go over 0, both according to the data sheet and
real world testing. The control can go up to +30dB.
This was tested by playing audio at full volume on a samus chromebook.
Signed-off-by: Dylan Reid
Reviewed-by: Hsinyu Chao
Signed-off-by: Ross Zwisler
On Wed, Oct 24, 2018 at 1:22 AM Viresh Kumar wrote:
> On 22-10-18, 14:29, Ross Zwisler wrote:
> > From: Ricky Liang
> >
> > Add thermal logs in devfreq_cooling and cpu_cooling.
>
> Why should we add them ?
>
> > Also add logging to
> > power
On Wed, Oct 24, 2018 at 1:22 AM Viresh Kumar wrote:
> On 22-10-18, 14:29, Ross Zwisler wrote:
> > From: Ricky Liang
> >
> > Add thermal logs in devfreq_cooling and cpu_cooling.
>
> Why should we add them ?
>
> > Also add logging to
> > power
-by: Duncan Laurie
Reviewed-by: Vincent Palatin
Reviewed-by: Olof Johansson
[ rez: updated changelog for upstream ]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmware/google
-by: Duncan Laurie
Reviewed-by: Vincent Palatin
Reviewed-by: Olof Johansson
[ rez: updated changelog for upstream ]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmware/google
passed
to the cpu_cooling notifier chain so it is not useful for logging.
Signed-off-by: Duncan Laurie
Reviewed-by: Olof Johansson
Reviewed-by: Vincent Palatin
[ rez: updated changelog for upstream ]
Signed-off-by: Ross Zwisler
---
drivers/thermal/thermal_core.c | 38 ++
include
passed
to the cpu_cooling notifier chain so it is not useful for logging.
Signed-off-by: Duncan Laurie
Reviewed-by: Olof Johansson
Reviewed-by: Vincent Palatin
[ rez: updated changelog for upstream ]
Signed-off-by: Ross Zwisler
---
drivers/thermal/thermal_core.c | 38 ++
include
from each of those subsystems.
Signed-off-by: Ricky Liang
Co-authored-by: Stephen Barber
Signed-off-by: Stephen Barber
Reviewed-by: Daniel Kurtz
[ rez: squashed initial implementation & fixes, updated changelog for
upstream. ]
Signed-off-by: Ross Zwisler
---
drivers/thermal/cpu_cooli
from each of those subsystems.
Signed-off-by: Ricky Liang
Co-authored-by: Stephen Barber
Signed-off-by: Stephen Barber
Reviewed-by: Daniel Kurtz
[ rez: squashed initial implementation & fixes, updated changelog for
upstream. ]
Signed-off-by: Ross Zwisler
---
drivers/thermal/cpu_cooli
On Thu, Oct 18, 2018 at 2:31 PM Kees Cook wrote:
>
> On Thu, Oct 18, 2018 at 8:33 AM, Dan Williams
> wrote:
> > [ add Ross ]
>
> Hi Ross! :)
>
> > On Thu, Oct 18, 2018 at 12:15 AM Kees Cook wrote:
> >> As for nvdimm specifically, yes, I'd love to get pstore hooked up
> >> correctly to nvdimm.
On Thu, Oct 18, 2018 at 2:31 PM Kees Cook wrote:
>
> On Thu, Oct 18, 2018 at 8:33 AM, Dan Williams
> wrote:
> > [ add Ross ]
>
> Hi Ross! :)
>
> > On Thu, Oct 18, 2018 at 12:15 AM Kees Cook wrote:
> >> As for nvdimm specifically, yes, I'd love to get pstore hooked up
> >> correctly to nvdimm.
changelog for upstream]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/Kconfig | 6 +++---
drivers/firmware/google/gsmi.c | 16
2 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/drivers/firmware/google/Kconfig b/drivers/firmware/google/Kconfig
index
iewed-by: Aaron Durbin
Reviewed-by: Justin TerAvest
[zwisler: updated changelog for 2nd bug fix and upstream]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmwa
This series contains some Google specific firmware patches that we've
been carrying out of tree. I've updated the changelog for each so that
it is suitable for upstream, and I've retested them to make sure I know
what the patches are doing.
Duncan Laurie (3):
gsmi: Fix bug in
off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmware/google/gsmi.c
index 62337be07afc..252884787266 100644
--- a/drivers/firmware/google/gsmi.c
+++ b/drivers/firmware/google/gsmi.c
@@ -71
-by: Furquan Shaikh
Tested-by: Furquan Shaikh
Reviewed-by: Aaron Durbin
[zwisler: update changelog for upstream]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 93 +-
1 file changed, 92 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware
changelog for upstream]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/Kconfig | 6 +++---
drivers/firmware/google/gsmi.c | 16
2 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/drivers/firmware/google/Kconfig b/drivers/firmware/google/Kconfig
index
iewed-by: Aaron Durbin
Reviewed-by: Justin TerAvest
[zwisler: updated changelog for 2nd bug fix and upstream]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmwa
This series contains some Google specific firmware patches that we've
been carrying out of tree. I've updated the changelog for each so that
it is suitable for upstream, and I've retested them to make sure I know
what the patches are doing.
Duncan Laurie (3):
gsmi: Fix bug in
off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmware/google/gsmi.c
index 62337be07afc..252884787266 100644
--- a/drivers/firmware/google/gsmi.c
+++ b/drivers/firmware/google/gsmi.c
@@ -71
-by: Furquan Shaikh
Tested-by: Furquan Shaikh
Reviewed-by: Aaron Durbin
[zwisler: update changelog for upstream]
Signed-off-by: Ross Zwisler
---
drivers/firmware/google/gsmi.c | 93 +-
1 file changed, 92 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware
On Wed, Jul 25, 2018 at 02:03:23PM -0700, Matthew Wilcox wrote:
> On Wed, Jun 27, 2018 at 01:44:38PM -0600, Ross Zwisler wrote:
> > On Wed, Jun 27, 2018 at 04:05:29AM -0700, Matthew Wilcox wrote:
> > > On Tue, Jun 19, 2018 at 10:16:38AM -0700, Matthew Wilcox wrote:
> >
On Wed, Jul 25, 2018 at 02:03:23PM -0700, Matthew Wilcox wrote:
> On Wed, Jun 27, 2018 at 01:44:38PM -0600, Ross Zwisler wrote:
> > On Wed, Jun 27, 2018 at 04:05:29AM -0700, Matthew Wilcox wrote:
> > > On Tue, Jun 19, 2018 at 10:16:38AM -0700, Matthew Wilcox wrote:
> >
at
> is to say callers may have no need for kaddr or pfn, so this series of
> patch are prepared for allowing them to pass in NULL instead of having
> to pass in a local pointer or variable that they then just throw away.
Looks good. For the series:
Reviewed-by: Ross Zwisler
at
> is to say callers may have no need for kaddr or pfn, so this series of
> patch are prepared for allowing them to pass in NULL instead of having
> to pass in a local pointer or variable that they then just throw away.
Looks good. For the series:
Reviewed-by: Ross Zwisler
On Mon, Jul 2, 2018 at 12:48 PM Pavel Tatashin
wrote:
>
> On Mon, Jul 2, 2018 at 11:43 AM wrote:
> >
> > From: Oscar Salvador
> >
> > sparse_init_one_section() is being called from two sites:
> > sparse_init() and sparse_add_one_section().
> > The former calls it from a
On Mon, Jul 2, 2018 at 12:48 PM Pavel Tatashin
wrote:
>
> On Mon, Jul 2, 2018 at 11:43 AM wrote:
> >
> > From: Oscar Salvador
> >
> > sparse_init_one_section() is being called from two sites:
> > sparse_init() and sparse_add_one_section().
> > The former calls it from a
orton
> Cc: Andy Lutomirski
> Cc: Borislav Petkov
> Cc: Linus Torvalds
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Tony Luck
> Reported-by: Ross Zwisler
> Signed-off-by: Dan Williams
Tested-by: Ross Zwisler
orton
> Cc: Andy Lutomirski
> Cc: Borislav Petkov
> Cc: Linus Torvalds
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Tony Luck
> Reported-by: Ross Zwisler
> Signed-off-by: Dan Williams
Tested-by: Ross Zwisler
Morton
> Cc: Andy Lutomirski
> Cc: Borislav Petkov
> Cc: Linus Torvalds
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Tony Luck
> Reported-by: Ross Zwisler
> Signed-off-by: Dan Williams
Tested-by: Ross Zwisler
Morton
> Cc: Andy Lutomirski
> Cc: Borislav Petkov
> Cc: Linus Torvalds
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Tony Luck
> Reported-by: Ross Zwisler
> Signed-off-by: Dan Williams
Tested-by: Ross Zwisler
Morton
> Cc: Andy Lutomirski
> Cc: Borislav Petkov
> Cc: Linus Torvalds
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Tony Luck
> Reported-by: Ross Zwisler
> Signed-off-by: Dan Williams
> ---
> Hi Ingo,
>
> I'm submitting this fix back through the ti
Morton
> Cc: Andy Lutomirski
> Cc: Borislav Petkov
> Cc: Linus Torvalds
> Cc: Peter Zijlstra
> Cc: Thomas Gleixner
> Cc: Tony Luck
> Reported-by: Ross Zwisler
> Signed-off-by: Dan Williams
> ---
> Hi Ingo,
>
> I'm submitting this fix back through the ti
On Thu, Jun 28, 2018 at 05:42:34PM +, Kani, Toshi wrote:
> On Tue, 2018-06-26 at 16:04 -0600, Ross Zwisler wrote:
> > On Tue, Jun 26, 2018 at 02:51:52PM -0700, Dan Williams wrote:
> > > On Tue, Jun 26, 2018 at 2:31 PM, Kani, Toshi wrote:
> > > > On Tue, 2018-06-2
On Thu, Jun 28, 2018 at 05:42:34PM +, Kani, Toshi wrote:
> On Tue, 2018-06-26 at 16:04 -0600, Ross Zwisler wrote:
> > On Tue, Jun 26, 2018 at 02:51:52PM -0700, Dan Williams wrote:
> > > On Tue, Jun 26, 2018 at 2:31 PM, Kani, Toshi wrote:
> > > > On Tue, 2018-06-2
and no DAX
support returns false.
Signed-off-by: Dave Jiang
Signed-off-by: Ross Zwisler
---
drivers/dax/super.c | 16
fs/ext2/super.c | 3 +--
fs/ext4/super.c | 3 +--
fs/xfs/xfs_ioctl.c | 4 ++--
fs/xfs/xfs_super.c | 12 ++--
include/linux/dax.h | 8
6
and no DAX
support returns false.
Signed-off-by: Dave Jiang
Signed-off-by: Ross Zwisler
---
drivers/dax/super.c | 16
fs/ext2/super.c | 3 +--
fs/ext4/super.c | 3 +--
fs/xfs/xfs_ioctl.c | 4 ++--
fs/xfs/xfs_super.c | 12 ++--
include/linux/dax.h | 8
6
actually fix all the parts of XFS where we need to be able to
distinguish between datadev and rtdev.
This patch fixes the problem where we screw up the dax support checking
in xfs if the datadev and rtdev have different dax capabilities.
Signed-off-by: Darrick J. Wong <darrick.w...@oracle.com&g
S where we need to be able to
distinguish between datadev and rtdev.
This patch fixes the problem where we screw up the dax support checking
in xfs if the datadev and rtdev have different dax capabilities.
Signed-off-by: Darrick J. Wong
Signed-off-by: Ross Zwisler
---
drivers/dax/su
This stub was added so that we could use dm-snap with DM_TYPE_DAX_BIO_BASED
mode devices. That mode and the transition issues associated with it no
longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
---
drivers/md/dm-snap.c | 8 -
feel that this series simplifies the
handling of DAX devices in DM, and the last 5 DM-related patches have a
net code reduction of 50 lines.
Darrick J. Wong (1):
fs: allow per-device dax status checking for filesystems
Dave Jiang (1):
dax: change bdev_dax_supported() to support boolean returns
ported then return true and no DAX
support returns false.
Signed-off-by: Dave Jiang <dave.ji...@intel.com>
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
Reviewed-by: Darrick J. Wong <darrick.w...@oracle.com>
---
drivers/dax/super.c | 16
fs/ext2/super
This stub was added so that we could use dm-snap with DM_TYPE_DAX_BIO_BASED
mode devices. That mode and the transition issues associated with it no
longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler
---
drivers/md/dm-snap.c | 8
1 file changed, 8 deletions
feel that this series simplifies the
handling of DAX devices in DM, and the last 5 DM-related patches have a
net code reduction of 50 lines.
Darrick J. Wong (1):
fs: allow per-device dax status checking for filesystems
Dave Jiang (1):
dax: change bdev_dax_supported() to support boolean returns
and no DAX
support returns false.
Signed-off-by: Dave Jiang
Signed-off-by: Ross Zwisler
Reviewed-by: Darrick J. Wong
---
drivers/dax/super.c | 16
fs/ext2/super.c | 3 +--
fs/ext4/super.c | 3 +--
fs/xfs/xfs_ioctl.c | 4 ++--
fs/xfs/xfs_super.c | 12
This stub was added so that we could use dm-error with
DM_TYPE_DAX_BIO_BASED mode devices. That mode and the transition issues
associated with it no longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
---
drivers/md/dm-target
the dax_direct_access() path works.
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
Fixes: commit 545ed20e6df6 ("dm: add infrastructure for DAX support")
---
drivers/md/dm-table.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/md/dm-tabl
This stub was added so that we could use dm-error with
DM_TYPE_DAX_BIO_BASED mode devices. That mode and the transition issues
associated with it no longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler
---
drivers/md/dm-target.c | 7 ---
1 file changed, 7 deletions
the dax_direct_access() path works.
Signed-off-by: Ross Zwisler
Fixes: commit 545ed20e6df6 ("dm: add infrastructure for DAX support")
---
drivers/md/dm-table.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index 05
then know at mount time whether DAX is a
supported mount option or not.
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
---
drivers/md/dm-ioctl.c | 16 ++--
drivers/md/dm-table.c | 25 ++---
drivers/md/dm.c | 2 --
then know at mount time whether DAX is a
supported mount option or not.
Signed-off-by: Ross Zwisler
---
drivers/md/dm-ioctl.c | 16 ++--
drivers/md/dm-table.c | 25 ++---
drivers/md/dm.c | 2 --
include/linux/device-mapper.h | 8 ++
() if QUEUE_FLAG_DAX isn't set we let
the filesystem know we don't support DAX at mount time. The filesystem
will then silently fall back and remove the dax mount option, causing it to
work properly.
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
Fixes: commit 545ed20e6df6 (&q
() if QUEUE_FLAG_DAX isn't set we let
the filesystem know we don't support DAX at mount time. The filesystem
will then silently fall back and remove the dax mount option, causing it to
work properly.
Signed-off-by: Ross Zwisler
Fixes: commit 545ed20e6df6 ("dm: add infrastructure for DAX su
On Fri, May 25, 2018 at 03:54:10PM -0400, Mike Snitzer wrote:
> On Thu, May 24 2018 at 10:55pm -0400,
> Ross Zwisler <ross.zwis...@linux.intel.com> wrote:
>
> > Currently the code in dm_dax_direct_access() only checks whether the target
> > type has a direct
On Fri, May 25, 2018 at 03:54:10PM -0400, Mike Snitzer wrote:
> On Thu, May 24 2018 at 10:55pm -0400,
> Ross Zwisler wrote:
>
> > Currently the code in dm_dax_direct_access() only checks whether the target
> > type has a direct_access() operation defined, not whether the
On Thu, May 24, 2018 at 10:02:18PM -0700, Darrick J. Wong wrote:
> On Thu, May 24, 2018 at 08:55:12PM -0600, Ross Zwisler wrote:
> > From: "Darrick J. Wong" <darrick.w...@oracle.com>
> >
> > Remove __bdev_dax_supported and change to bdev_dax_supp
On Thu, May 24, 2018 at 10:02:18PM -0700, Darrick J. Wong wrote:
> On Thu, May 24, 2018 at 08:55:12PM -0600, Ross Zwisler wrote:
> > From: "Darrick J. Wong"
> >
> > Remove __bdev_dax_supported and change to bdev_dax_supported that takes a
> > bdev
This stub was added so that we could use dm-snap with DM_TYPE_DAX_BIO_BASED
mode devices. That mode and the transition issues associated with it no
longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com>
---
drivers/md/dm-snap.c | 8 -
actually fix all the parts of XFS where we need to be able to
distinguish between datadev and rtdev.
This patch fixes the problem where we screw up the dax support checking
in xfs if the datadev and rtdev have different dax capabilities.
Signed-off-by: Darrick J. Wong <darrick.w...@oracle.com&g
This stub was added so that we could use dm-snap with DM_TYPE_DAX_BIO_BASED
mode devices. That mode and the transition issues associated with it no
longer exist, so we can remove this dead code.
Signed-off-by: Ross Zwisler
---
drivers/md/dm-snap.c | 8
1 file changed, 8 deletions
1 - 100 of 2219 matches
Mail list logo
