linux-kernel - [PATCH 0/1]ext4: Fix for WARN_ON

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-next>] [day] [month] [year] [list]

Message-Id: <1467285150-15977-1-git-send-email-pranjas@gmail.com>
Date:	Thu, 30 Jun 2016 14:12:29 +0300
From:	"Pranay Kr. Srivastava" <pranjas@...il.com>
To:	tytso@....edu, adilger.kernel@...ger.ca,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	"Pranay Kr. Srivastava" <pranjas@...il.com>
Subject: [PATCH 0/1]ext4: Fix for WARN_ON_ONCE when marking buffer dirty

1) Fix WARN_ON_ONCE when marking buffer dirty
   it's possible that a writeback for the super block
   buffer head is triggered after setting the buffer
   uptodate on a buffer write_io_error.

   If however there's an error while writing the buffer
   head then the buffer is cleared from being uptodate.

   If the buffer uptodate is not set while calling
   mark_buffer_dirty, it throws a WARN_ON_ONCE.
   This patch fixes it by locking the buffer while marking
   the buffer uptodate and then marking it dirty while holding
   the buffer head lock.

Pranay Kr. Srivastava (5):
   Fix WARN_ON_ONCE when marking buffer dirty

 fs/ext4/super.c     |  30 +++++-----
 1 files changed, 16 insertions(+), 14 deletions(-)

-- 
1.9.1