linux-kernel - vfs and permission() locking policy

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: <1837b62c0901130605q12769960h8fc61d3cf878609a@mail.gmail.com>
Date:	Tue, 13 Jan 2009 15:05:44 +0100
From:	"Tomasz Turski" <turtomek.ey@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: vfs and permission() locking policy

Hi,

I would like to know what is the locking policy in permission() function
in vfs (in file fs/namei.c).
I would like to lock inode->i_mutex in permission(), but I don't know if
I don't have any deadlock.

Regards,
Tomasz Turski
--
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/