Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756533AbbFQQQF (ORCPT ); Wed, 17 Jun 2015 12:16:05 -0400 Received: from mailrelay103.isp.belgacom.be ([195.238.20.130]:27034 "EHLO mailrelay103.isp.belgacom.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753584AbbFQQQC (ORCPT ); Wed, 17 Jun 2015 12:16:02 -0400 X-Belgacom-Dynamic: yes X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=gx4LFt9C7U8MVtlopYu6y61Gbp9nqOyhneTyg/i0HKM= c=1 sm=2 a=H2QJzfRzYHzTEK9cwfIA:9 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BrEQDsnIFV/yMnQ1dcgxCBM6s5BQUBBQGBBIxjjA0EAoE5PBEBAQEBAQEBgQpBBYQKLyOBGjeIMwHKWYYaijAdhBUFk2iLR41iij4mY2YBQRyBVDwxgkgBAQE From: Fabian Frederick To: linux-kernel@vger.kernel.org Cc: Alexander Viro , Andrew Morton , Fabian Frederick , Evgeniy Dushistov Subject: [PATCH 1/1 linux-next] fs/ufs: restore s_lock mutex_init() Date: Wed, 17 Jun 2015 18:15:45 +0200 Message-Id: <1434557745-22595-1-git-send-email-fabf@skynet.be> X-Mailer: git-send-email 2.4.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 31 Add last missing line in commit "cdd9eefdf905" ("fs/ufs: restore s_lock mutex") Signed-off-by: Fabian Frederick --- Second part of the patch with 2 fixes was not applied. Meanwhile, Al already fixed remount(). fs/ufs/super.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/ufs/super.c b/fs/ufs/super.c index bd13356..250579a 100644 --- a/fs/ufs/super.c +++ b/fs/ufs/super.c @@ -802,6 +802,7 @@ static int ufs_fill_super(struct super_block *sb, void *data, int silent) UFSD("flag %u\n", (int)(sb->s_flags & MS_RDONLY)); mutex_init(&sbi->mutex); + mutex_init(&sbi->s_lock); spin_lock_init(&sbi->work_lock); INIT_DELAYED_WORK(&sbi->sync_work, delayed_sync_fs); /* -- 2.4.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/