| To: | Oleg Nesterov <oleg@xxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: Fix f_flags races without the BKL |
| From: | Andi Kleen <andi@xxxxxxxxxxxxxx> |
| Date: | Mon, 29 Dec 2008 16:27:32 +0100 |
| Cc: | Jonathan Corbet <corbet@xxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Andi Kleen <andi@xxxxxxxxxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, bfields@xxxxxxxxxxxx, xfs-masters@xxxxxxxxxxx |
| In-reply-to: | <20081229124151.GA29634@redhat.com> |
| References: | <20081229041352.6bbdf57c@tpl> <20081229124151.GA29634@redhat.com> |
| User-agent: | Mutt/1.4.2.1i |
On Mon, Dec 29, 2008 at 01:41:51PM +0100, Oleg Nesterov wrote: > On 12/29, Jonathan Corbet wrote: > > > > After pondering for a while, I couldn't come up with anything better than a > > global file->f_flags mutex. There's no point in bloating struct file with > > a mutex just for this purpose; it's hard to imagine that there will be any > > real contention for this lock. > > Yes, this patch is simple and straightforward, but now we can't change > ->f_flags in non-preempible context. And the global lock is not very > nice anyway. > > Once again, can't we use O_LOCK_FLAGS bit? I agree, it is a bit ugly, > and I won't insist if you don't like is. I would prefer O_LOCK_FLAGS bit too. The global lock is not very nice and I don't doubt someone will come up with a workload which pounds on it. -Andi -- ak@xxxxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [xfs-masters] RFC: Fix f_flags races without the BKL, Andi Kleen |
|---|---|
| Next by Date: | [Bug 809] New: s, bugzilla-daemon |
| Previous by Thread: | Re: RFC: Fix f_flags races without the BKL, Oleg Nesterov |
| Next by Thread: | Re: RFC: Fix f_flags races without the BKL, Jonathan Corbet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |