linux-kernel - Re: [PATCH] nfs: init req_lock in nfs_alloc

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

Message-ID: <20070222201315.GA14686@lixom.net>
Date:	Thu, 22 Feb 2007 14:13:15 -0600
From:	olof@...om.net (Olof Johansson)
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nfs: init req_lock in nfs_alloc_inode

On Tue, Feb 20, 2007 at 07:37:18PM -0500, Trond Myklebust wrote:

> Looks like we need a check in nfs_getattr() for a regular file. It makes
> no sense to call nfs_sync_mapping_range() on anything else. I think that
> should fix your problem: it will stop the NFS client from interfering
> with dirty pages on that inode's mapping.

Yep, that works here. I also verified that my previous patch really
didn't change the behaviour. I wonder why it did once. Probably just
pure luck with memory contents.

> From: Trond Myklebust <Trond.Myklebust@...app.com>
> Date: Tue, 20 Feb 2007 19:28:07 -0500
> Subject: No Subject
> 
> Signed-off-by: Trond Myklebust <Trond.Myklebust@...app.com>

Acked-by: Olof Johansson <olof@...om.net>


-Olof
-
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/