public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Reviewing 4.4 stable updates
Date: Tue, 15 May 2018 15:44:19 +0900	[thread overview]
Message-ID: <000501d3ec18$26ef17d0$74cd4770$@toshiba.co.jp> (raw)
In-Reply-To: <003601d3ec02$20158f90$6040aeb0$@toshiba.co.jp>

It seems that backporting "fanotify: Release SRCU lock when waiting for userspace response" was too complicated:
https://lists.debian.org/debian-kernel/2017/06/msg00170.html

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Daniel Sangorrin
> Sent: Tuesday, May 15, 2018 1:07 PM
> To: 'Ben Hutchings' <ben.hutchings@codethink.co.uk>;
> cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] Reviewing 4.4 stable updates
> 
> > -----Original Message-----
> > From: cip-dev-bounces at lists.cip-project.org
> > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Daniel Sangorrin
> > Sent: Thursday, April 26, 2018 8:53 AM
> > To: 'Ben Hutchings' <ben.hutchings@codethink.co.uk>;
> > cip-dev at lists.cip-project.org
> > Subject: Re: [cip-dev] Reviewing 4.4 stable updates
> ...
> > I saw there is already a 4.4.129 on the linux-stable-rc.git linux-4.4.y.
> > Test results so far show no regressions (altough i see failures that might need
> > investigation?):
> > Pixel: https://lkml.org/lkml/2018/4/22/732
> > Linaro: https://lkml.org/lkml/2018/4/23/116
> > Kerneltests: https://lkml.org/lkml/2018/4/23/823
> > dmseg: https://lkml.org/lkml/2018/4/23/1028
> >
> > I will run some tests with Fuego.
> 
> Sorry for the late response. I tested LTS 4.4.129 with Fuego and most tests worked
> correctly.
> There were a few errors on some of the LTP tests (see the file attached).
> 
> fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536
> unexpectedly, expected 4096
> getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute
> inotify07.c:157: FAIL: didn't get event: mask=40000004
> inotify08.c:150: FAIL: didn't get event: mask=4
> [Note] These 4 errors could be related with some configuration, so I need to
> investigate them further.
> 
> For fanotify07 and fanotify08 I got some timeout errors:
> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Test timeouted, sending SIGKILL!
> Cannot kill test processes!
> Congratulation, likely test hit a kernel bug.
> Exitting uncleanly...
> 
> Dhinakar Kalyanasundaram mentioned that this bug was fixed in kernel 4.14, and
> Tim Bird updated the Fuego LTP documentation suggesting that backporting the
> patch "fanotify: Release SRCU lock when waiting for userspace response" should fix
> the hang.
> https://patchwork.kernel.org/patch/9659809/
> 
> Shall I backport it and test?
> 
> Thanks,
> Daniel

  reply	other threads:[~2018-05-15  6:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 13:18 [cip-dev] Reviewing 4.4 stable updates Ben Hutchings
2018-04-25 23:52 ` Daniel Sangorrin
2018-04-26 14:30   ` Ben Hutchings
2018-05-15  4:06   ` Daniel Sangorrin
2018-05-15  6:44     ` Daniel Sangorrin [this message]
2018-05-15  7:44       ` Agustín Benito Bethencourt
2018-05-15  7:53         ` Daniel Wagner
2018-05-17  1:44           ` Daniel Sangorrin
2018-05-17  5:35             ` Daniel Wagner

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='000501d3ec18$26ef17d0$74cd4770$@toshiba.co.jp' \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    /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