linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Mark Brown <broonie@kernel.org>, Josef Bacik <josef@toxicpanda.com>
Cc: "Aishwarya TCV" <aishwarya.tcv@arm.com>,
	"Christian Brauner" <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	jack@suse.cz, david@fromorbit.com, hch@lst.de,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	amir73il@gmail.com, "Naresh Kamboju" <naresh.kamboju@linaro.org>,
	ltp@lists.linux.it, "lee@kernel.org" <lee@kernel.org>,
	"Peter Griffin" <peter.griffin@linaro.org>,
	"André Draszik" <andre.draszik@linaro.org>,
	"William McVicker" <willmcvicker@google.com>
Subject: Re: [PATCH] fs: don't block i_writecount during exec
Date: Wed, 7 Aug 2024 10:59:57 +0100	[thread overview]
Message-ID: <79fb2439-db38-4aad-bf91-2d3b031309a8@linaro.org> (raw)
In-Reply-To: <550734af-e115-4048-8a8f-0fdaa199c956@sirena.org.uk>



On 6/6/24 6:49 PM, Mark Brown wrote:
> On Thu, Jun 06, 2024 at 06:33:34PM +0100, Mark Brown wrote:
>> On Thu, Jun 06, 2024 at 12:53:18PM -0400, Josef Bacik wrote:
>>> On Thu, Jun 06, 2024 at 04:37:49PM +0100, Mark Brown wrote:
>>>> On Thu, Jun 06, 2024 at 01:45:05PM +0100, Aishwarya TCV wrote:
>>
>>>>> LTP test "execve04" is failing when run against
>>>>> next-master(next-20240606) kernel with Arm64 on JUNO in our CI.
>>
>>>> It's also causing the LTP creat07 test to fail with basically the same
>>>> bisection (I started from next/pending-fixes rather than the -rc so the
>>>> initial phases were different):
>>
>>>> tst_test.c:1690: TINFO: LTP version: 20230929
>>>> tst_test.c:1574: TINFO: Timeout per run is 0h 01m 30s
>>>> creat07.c:37: TFAIL: creat() succeeded unexpectedly
>>>> Test timeouted, sending SIGKILL!
>>>> tst_test.c:1622: TINFO: Killed the leftover descendant processes
>>>> tst_test.c:1628: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
>>>> tst_test.c:1630: TBROK: Test killed! (timeout?)
>>
>>>> The code in the testcase is below:
>>
>>> These tests will have to be updated, as this patch removes that behavior.
>>
>> Adding the LTP list - looking at execve04 it seems to be trying for a
>> similar thing to creat07, it's looking for an ETXTBUSY.
> 
> Or not since they reject signed mail :/

FYI, I encountered the same test failures. I opened a bug on the github
ltp project suggesting that the tests need to be updated. Here it is:
https://github.com/linux-test-project/ltp/issues/1184

Cheers,
ta

  reply	other threads:[~2024-08-07 10:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 20:41 [PATCH][RFC] fs: add levels to inode write access Josef Bacik
2024-05-29 22:00 ` Jeff Layton
2024-05-30  1:14 ` Matthew Wilcox
2024-05-30 10:32 ` Christian Brauner
2024-05-30 12:57   ` Amir Goldstein
2024-05-30 14:58   ` Josef Bacik
2024-05-30 15:23   ` Christian Brauner
2024-05-30 15:49   ` Linus Torvalds
2024-05-31 10:02     ` Christian Brauner
2024-05-31 12:32       ` Christian Brauner
2024-05-31 13:01         ` [PATCH] fs: don't block i_writecount during exec Christian Brauner
2024-05-31 15:40           ` Linus Torvalds
2024-05-31 18:08             ` Jeff Layton
2024-05-31 22:08           ` Josef Bacik
2024-06-03 13:52           ` (subset) " Christian Brauner
2024-06-06 12:45           ` Aishwarya TCV
2024-06-06 15:37             ` Mark Brown
2024-06-06 16:53               ` Josef Bacik
2024-06-06 17:33                 ` Mark Brown
2024-06-06 17:49                   ` Mark Brown
2024-08-07  9:59                     ` Tudor Ambarus [this message]
2024-09-04 17:04           ` Jann Horn
2024-09-05  7:38             ` Roberto Sassu
2024-05-31 13:09         ` [PATCH][RFC] fs: add levels to inode write access Amir Goldstein
2024-05-31 14:50           ` Christian Brauner
2024-05-31 15:47             ` Matthew Wilcox
2024-05-31 22:14               ` Matthew Wilcox

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=79fb2439-db38-4aad-bf91-2d3b031309a8@linaro.org \
    --to=tudor.ambarus@linaro.org \
    --cc=aishwarya.tcv@arm.com \
    --cc=amir73il@gmail.com \
    --cc=andre.draszik@linaro.org \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=lee@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=naresh.kamboju@linaro.org \
    --cc=peter.griffin@linaro.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willmcvicker@google.com \
    /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).