linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aishwarya TCV <aishwarya.tcv@arm.com>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	jack@suse.cz, david@fromorbit.com, hch@lst.de,
	Josef Bacik <josef@toxicpanda.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	amir73il@gmail.com, Mark Brown <broonie@kernel.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH] fs: don't block i_writecount during exec
Date: Thu, 6 Jun 2024 13:45:05 +0100	[thread overview]
Message-ID: <f8586f0c-f62c-4d92-8747-0ba20a03f681@arm.com> (raw)
In-Reply-To: <20240531-vfs-i_writecount-v1-1-a17bea7ee36b@kernel.org>



On 31/05/2024 14:01, Christian Brauner wrote:
> Back in 2021 we already discussed removing deny_write_access() for
> 
> executables. Back then I was hesistant because I thought that this might
> 
> cause issues in userspace. But even back then I had started taking some
> 
> notes on what could potentially depend on this and I didn't come up with
> 
> a lot so I've changed my mind and I would like to try this.
> 
> 
> 

Hi Christian,

LTP test "execve04" is failing when run against
next-master(next-20240606) kernel with Arm64 on JUNO in our CI.

A bisect identified 244ebddd34a0ab7b1ef865811864136873f4b67c as the
first bad commit. Bisected it on the tag "next-20240604" at repo
"https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git".

This works fine on Linux version 6.10-rc2

Failure log
------------
tst_test.c:1690: TINFO: LTP version: 20230929
tst_test.c:1574: TINFO: Timeout per run is 0h 01m 30s
execve_child.c:27: TFAIL: execve_child shouldn't be executed
tst_test.c:1622: TINFO: Killed the leftover descendant processes

Summary:
passed   0
failed   1
broken   0
skipped  0
warnings 0

Bisect log:
----------
git bisect start
# good: [c3f38fa61af77b49866b006939479069cd451173] Linux 6.10-rc2
git bisect good c3f38fa61af77b49866b006939479069cd451173
# bad: [d97496ca23a2d4ee80b7302849404859d9058bcd] Add linux-next
specific files for 20240604
git bisect bad d97496ca23a2d4ee80b7302849404859d9058bcd
# bad: [f89ceec12d7134c9be89f880655b72e36dd3c681] Merge branch
'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
git bisect bad f89ceec12d7134c9be89f880655b72e36dd3c681
# good: [a933c8b54a9ea9bb6b10d168351638933c40b487] Merge branch
'for-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
git bisect good a933c8b54a9ea9bb6b10d168351638933c40b487
# bad: [2d893301453cefb11116f6095a791b8013bbc3e9] Merge branch
'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git
git bisect bad 2d893301453cefb11116f6095a791b8013bbc3e9
# good: [a6a2e13e3bc64365c70b52d42b5d3a674152d5cd] Merge branch
'nfsd-next' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
git bisect good a6a2e13e3bc64365c70b52d42b5d3a674152d5cd
# bad: [e4c1aa3f74bcc90cff6cf8ea575e222066f5be7b] Merge branch 'fs-next'
of linux-next
git bisect bad e4c1aa3f74bcc90cff6cf8ea575e222066f5be7b
# good: [37007c875042e5f5fc65087ea7d67ca388412875] Merge branch
'renesas-clk' of
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
git bisect good 37007c875042e5f5fc65087ea7d67ca388412875
# bad: [4247aca2219daab5ea6aeebc3d27d32ad56d2472] Merge branch
'vfs.module.description' into vfs.all
git bisect bad 4247aca2219daab5ea6aeebc3d27d32ad56d2472
# bad: [68efe7d9f3055ee986c51178e76061bdad782ff9] Merge branch
'vfs.xattr' into vfs.all
git bisect bad 68efe7d9f3055ee986c51178e76061bdad782ff9
# good: [1f9ccdf69c9ffb9a9084cc6e1a47c5030cebed26] readdir: Add missing
quote in macro comment
git bisect good 1f9ccdf69c9ffb9a9084cc6e1a47c5030cebed26
# bad: [03950a7a6f1a511a372bc46cd4fddd2df7e37a62] Merge branch
'vfs.misc' into vfs.all
git bisect bad 03950a7a6f1a511a372bc46cd4fddd2df7e37a62
# bad: [f113ef08b6bde5f4c74eb4d66f7ca52e09305bb0] tmpfs: don't interrupt
fallocate with EINTR
git bisect bad f113ef08b6bde5f4c74eb4d66f7ca52e09305bb0
# bad: [244ebddd34a0ab7b1ef865811864136873f4b67c] fs: don't block
i_writecount during exec
git bisect bad 244ebddd34a0ab7b1ef865811864136873f4b67c
# first bad commit: [244ebddd34a0ab7b1ef865811864136873f4b67c] fs: don't
block i_writecount during exec

Thanks,
Aishwarya

  parent reply	other threads:[~2024-06-06 12:46 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 [this message]
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
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=f8586f0c-f62c-4d92-8747-0ba20a03f681@arm.com \
    --to=aishwarya.tcv@arm.com \
    --cc=amir73il@gmail.com \
    --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=linux-fsdevel@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=torvalds@linux-foundation.org \
    --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).