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 for Android: free password hash cracker in your pocket

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

Message-ID: <bug-201631-13602-ZM720EUAOJ@https.bugzilla.kernel.org/>
Date:   Tue, 18 Dec 2018 22:27:49 +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 #20 from Benjamin Herrenschmidt (benh@...nel.crashing.org) ---
Pardon my ignorance here, but I was under the impression that this was normal
:) The whole point being that the PTE dirty bit gets set when accesses happen,
and latter on gets harvested into the struct page dirty bit.

Otherwise, what would be the point of having a PTE dirty bit in the PTE at all
or transferring a dirty bit from PTE to struct page in try_to_unmap_one() (for
example) if a writable page is always mapped dirty ?

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