linux-kernel - Re: [patch 0/4 v2] vfs: fix utimensat() non-conformances to spec

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

Message-Id: <E1K3sxT-0000hy-9Z@pomaz-ex.szeredi.hu>
Date:	Wed, 04 Jun 2008 15:23:19 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	mtk.manpages@...glemail.com
CC:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	hch@....de, miklos@...redi.hu, viro@...iv.linux.org.uk,
	jamie@...reable.org, drepper@...hat.com,
	linux-fsdevel@...r.kernel.org, subrata@...ux.vnet.ibm.com
Subject: Re: [patch 0/4 v2] vfs: fix utimensat() non-conformances to spec

> This patch series is a revised version of the patch series
> that I sent yesterday to fix various utimensat()
> non-conformances.  Patches 1 and 2 are unchanged (and were
> Acked by Miklos); patches 3 and 4 are revised following
> comments by Miklos.
> 
> As requested I've split the original patch
> ("utimensat() non-conformances and fixes [v4] (patch)";
> http://article.gmane.org/gmane.linux.file-systems/24325 )
> into four parts.  Ideally, these should be applied for
> 2.6.26-rc, for the reasons outlined in my earlier mail
> "utimensat() non-conformances and fixes [v4] (test results)",
> http://article.gmane.org/gmane.linux.kernel/689411/ .
> 
> The four patches can be applied independently, except that
> patch 3 needs patch 2 to be applied first.

ACK for all four patches.

In patch 3/4 the indentation of that big "if" looks really horribly
broken, but it will be cleaned out completely, so I won't complain...

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