linux-ext4 - [Bug 201631] WARNING: CPU: 11 PID: 29593 at fs/ext4/inode.c:3927 .ext4_set_page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-201631-13602-tUbLDvhdb6@https.bugzilla.kernel.org/>
Date:   Fri, 21 Dec 2018 00:26:15 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 201631] WARNING: CPU: 11 PID: 29593 at fs/ext4/inode.c:3927
 .ext4_set_page_dirty+0x70/0xb0

https://bugzilla.kernel.org/show_bug.cgi?id=201631

--- Comment #33 from Benjamin Herrenschmidt (benh@...nel.crashing.org) ---
Jan,

For KVM, it can... you can back the guest using a file, and there's some
interest in doing just that to back guests using large "new memory" pmem stuff
for example.

This actually leads to more generic variant of that issue which is the need to
be able to provide proper "pinned" memory for some adapters in guest even if
they use ATSD, as not all adapters can deal with faults on everything (for
example they might be able to deal with fault on user buffers but not the
descriptor ring).

A discussion for another day I suppose..

As for AMD, I was looking at attachment
https://bugzilla.kernel.org/attachment.cgi?id=280057 posted in comment 18

-- 
You are receiving this mail because:
You are watching the assignee of the bug.