From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f42.google.com ([209.85.215.42]:33117 "EHLO mail-lf0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751012AbdAQJkS (ORCPT ); Tue, 17 Jan 2017 04:40:18 -0500 Received: by mail-lf0-f42.google.com with SMTP id k86so101972748lfi.0 for ; Tue, 17 Jan 2017 01:39:39 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20170117075702.GB10417@rei.lan> References: <18a5b416-ad6a-e679-d993-af7ffa0dcc10@redhat.com> <280513509.810300.1484639500985.JavaMail.zimbra@redhat.com> <20170117075702.GB10417@rei.lan> From: Miklos Szeredi Date: Tue, 17 Jan 2017 10:39:37 +0100 Message-ID: Subject: Re: utimensat EACCES vs. EPERM in 4.8+ To: Cyril Hrubis Cc: Jan Stancek , mtk manpages , linux-fsdevel , viro , guaneryu@gmail.com, ltp@lists.linux.it, Linux API , Dave Chinner Content-Type: text/plain; charset=UTF-8 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Jan 17, 2017 at 8:57 AM, Cyril Hrubis wrote: > Hi! >> > Jan, thanks for spotting this. >> >> Credit goes to Cyril. As for LTP-20170116 (released yesterday) we went >> with current documented behavior - few failures are expected on 4.8+. > > Actually credit goes to SUSE QAM that caught the change on kernel > update :-). And while this makes for a nice discussion, it is almost completely irrelevant in real life, since the only thing broken by this change will be test suites (in other words immutable files are rare as hen's teeth). If you find that this change actually breaks something other than a test suite, then yes, please lets revert it. Otherwise there's not much point (distros can revert it for themselves if they want be paranoid). Thanks, Miklos