From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751990AbcF3LMo (ORCPT ); Thu, 30 Jun 2016 07:12:44 -0400 Received: from mail-pa0-f67.google.com ([209.85.220.67]:35670 "EHLO mail-pa0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751575AbcF3LMm (ORCPT ); Thu, 30 Jun 2016 07:12:42 -0400 From: "Pranay Kr. Srivastava" To: tytso@mit.edu, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Cc: "Pranay Kr. Srivastava" Subject: [PATCH 0/1]ext4: Fix for WARN_ON_ONCE when marking buffer dirty Date: Thu, 30 Jun 2016 14:12:29 +0300 Message-Id: <1467285150-15977-1-git-send-email-pranjas@gmail.com> X-Mailer: git-send-email 2.6.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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