linux-kernel - Re: [PATCH 1/2] Add new spin_lock for i_flags of xfs

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

Message-ID: <20060809110718.B2508736@wobbly.melbourne.sgi.com>
Date:	Wed, 9 Aug 2006 11:07:18 +1000
From:	Nathan Scott <nathans@....com>
To:	Masayuki Saito <m-saito@...s.nec.co.jp>
Cc:	David Chinner <dgc@....com>, xfs@....sgi.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Add new spin_lock for i_flags of xfs_inode

On Tue, Aug 08, 2006 at 08:58:55PM +0900, Masayuki Saito wrote:
> It is the problem that i_flags of xfs_inode has no consistent
> locking protection.
> 
> For the reason, I define a new spin_lock(i_flags_lock) for i_flags
> of xfs_inode.  And I add this spin_lock for appropriate places.

Thanks Masayuki.  I've queued these two patches in my test
kernels, and if Dave has no more comments, I will get this
merged soon (probably 2.6.19 material, as its not had much
exposure yet afaik).

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/