From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: mtk manpages <mtk.manpages@gmail.com>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
viro <viro@zeniv.linux.org.uk>,
guaneryu@gmail.com, ltp@lists.linux.it,
Linux API <linux-api@vger.kernel.org>,
Dave Chinner <dchinner@redhat.com>
Subject: Re: utimensat EACCES vs. EPERM in 4.8+
Date: Tue, 17 Jan 2017 08:57:03 +0100 [thread overview]
Message-ID: <20170117075702.GB10417@rei.lan> (raw)
In-Reply-To: <280513509.810300.1484639500985.JavaMail.zimbra@redhat.com>
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 :-).
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-01-17 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18a5b416-ad6a-e679-d993-af7ffa0dcc10@redhat.com>
[not found] ` <CAOssrKfb1-C8c=9bAPiairh+Lyf=w28r+RjSXTLQcQZ-=eWMRA@mail.gmail.com>
2017-01-17 0:04 ` utimensat EACCES vs. EPERM in 4.8+ Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjTkBMY0wrj3wsH39YF=bHp=8mbYrXkSPzn0X4ezfso1w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-17 4:50 ` Carlos O'Donell
2017-01-17 7:51 ` Jan Stancek
2017-01-17 7:57 ` Cyril Hrubis [this message]
[not found] ` <20170117075702.GB10417-2UyX9mZUyMU@public.gmane.org>
2017-01-17 9:39 ` Miklos Szeredi
[not found] ` <CAOssrKd32K-e5794m9KOjrMm_E3VZ7P-bvZW2P8UpGFTOgi8JQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-17 15:43 ` Cyril Hrubis
2017-01-18 8:23 ` Michael Kerrisk (man-pages)
[not found] ` <cb15e28d-8c5e-e3d7-441a-9165c4e57133-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-31 12:09 ` Cyril Hrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170117075702.GB10417@rei.lan \
--to=chrubis@suse.cz \
--cc=dchinner@redhat.com \
--cc=guaneryu@gmail.com \
--cc=jstancek@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mszeredi@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).