From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>,
ltp@lists.linux.it, Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [LTP] [PATCH] syscalls/execve04, creat07: skip for kernels 6.11 and later
Date: Mon, 12 Aug 2024 15:31:03 +0200 [thread overview]
Message-ID: <20240812133103.GA437233@pevik> (raw)
In-Reply-To: <20240812120221.GA195572@pevik>
Hi Jan,
> Hi Jan,
> > The behaviour is allowed since commit:
> > 2a010c412853 ("fs: don't block i_writecount during exec")
> > that landed in 6.11-rc1.
> Thanks for noticing and fixing this!
> It was reported some time ago:
> https://lore.kernel.org/all/202406141431.2b72ca61-oliver.sang@intel.com/
> https://lore.kernel.org/ltp/202407162117.7730986d-oliver.sang@intel.com/
I have no idea, if you found it yourself, but let's give them the credit:
Reported-by: kernel test robot <oliver.sang@intel.com>
Kind regards,
Petr
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Kind regards,
> Petr
> > Signed-off-by: Jan Stancek <jstancek@redhat.com>
...
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>,
ltp@lists.linux.it, Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [LTP] [PATCH] syscalls/execve04, creat07: skip for kernels 6.11 and later
Date: Mon, 12 Aug 2024 15:31:03 +0200 [thread overview]
Message-ID: <20240812133103.GA437233@pevik> (raw)
In-Reply-To: <20240812120221.GA195572@pevik>
Hi Jan,
> Hi Jan,
> > The behaviour is allowed since commit:
> > 2a010c412853 ("fs: don't block i_writecount during exec")
> > that landed in 6.11-rc1.
> Thanks for noticing and fixing this!
> It was reported some time ago:
> https://lore.kernel.org/all/202406141431.2b72ca61-oliver.sang@intel.com/
> https://lore.kernel.org/ltp/202407162117.7730986d-oliver.sang@intel.com/
I have no idea, if you found it yourself, but let's give them the credit:
Reported-by: kernel test robot <oliver.sang@intel.com>
Kind regards,
Petr
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Kind regards,
> Petr
> > Signed-off-by: Jan Stancek <jstancek@redhat.com>
...
next prev parent reply other threads:[~2024-08-12 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:31 [LTP] [PATCH] syscalls/execve04, creat07: skip for kernels 6.11 and later Jan Stancek
2024-08-12 12:02 ` Petr Vorel
2024-08-12 12:02 ` Petr Vorel
2024-08-12 13:31 ` Petr Vorel [this message]
2024-08-12 13:31 ` Petr Vorel
2024-08-14 6:41 ` Li Wang
2024-08-14 6:45 ` Jan Stancek
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=20240812133103.GA437233@pevik \
--to=pvorel@suse.cz \
--cc=brauner@kernel.org \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ltp@lists.linux.it \
--cc=oliver.sang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.