linux-kernel - Re: [PATCH v3 3/3] selftests: livepatch: Test livepatching a heavily called syscall

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5a7cdb47541e357629437e0b482a1ca506c3b9f7.camel@suse.com>
Date: Wed, 20 Dec 2023 08:33:42 -0300
From: Marcos Paulo de Souza <mpdesouza@...e.com>
To: Shuah Khan <skhan@...uxfoundation.org>, Joe Lawrence
	 <joe.lawrence@...hat.com>
Cc: Marcos Paulo de Souza <mpdesouza@...e.de>, Shuah Khan
 <shuah@...nel.org>,  Jonathan Corbet <corbet@....net>, Heiko Carstens
 <hca@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>, Alexander Gordeev
 <agordeev@...ux.ibm.com>, Christian Borntraeger
 <borntraeger@...ux.ibm.com>, Sven Schnelle <svens@...ux.ibm.com>, Josh
 Poimboeuf <jpoimboe@...nel.org>, Jiri Kosina <jikos@...nel.org>, Petr
 Mladek <pmladek@...e.com>, linux-kselftest@...r.kernel.org,
 linux-doc@...r.kernel.org,  linux-kernel@...r.kernel.org,
 linux-s390@...r.kernel.org,  live-patching@...r.kernel.org, Miroslav Benes
 <mbenes@...e.cz>
Subject: Re: [PATCH v3 3/3] selftests: livepatch: Test livepatching a
 heavily called syscall

On Mon, 2023-12-18 at 13:47 -0700, Shuah Khan wrote:
> On 12/15/23 13:36, Joe Lawrence wrote:
> > On 12/11/23 16:53, Shuah Khan wrote:
> > > On 12/6/23 07:39, Miroslav Benes wrote:
> > > > Hi,
> > > > 
> > > > On Tue, 5 Dec 2023, Shuah Khan wrote:
> > > > 
> > > > > On 12/5/23 05:52, mpdesouza@...e.com wrote:
> > > > > > On Fri, 2023-12-01 at 16:38 +0000, Shuah Khan wrote:
> > > > > 
> > > > > > 0003-selftests-livepatch-Test-livepatching-a-heavily-
> > > > > > call.patch has
> > > > > > style problems, please review.
> > > > > > 
> > > > > > NOTE: If any of the errors are false positives, please
> > > > > > report
> > > > > >          them to the maintainer, see CHECKPATCH in
> > > > > > MAINTAINERS.
> > > > > > 
> > > > > > I couldn't find any mention about "missing module name". Is
> > > > > > your script
> > > > > > showing more warnings than these ones? Can you please share
> > > > > > your
> > > > > > output?
> > > > > > 
> > > > > > I'll fix MAINTAINERS file but I'll wait until I understand
> > > > > > what's
> > > > > > missing in your checkpatch script to resend the patchset.
> > > > > > 
> > > > > 
> > > > > Looks like it is coming a script - still my question stands
> > > > > on
> > > > > whether or not you would need a module name for this module?
> > > > 
> > > > I admit I am also clueless here. The module name is given in
> > > > Makefile. In
> > > > this case in test_modules/Makefile. I do not know of anything
> > > > else. There
> > > > is no MODULE_NAME macro. Could you elaborate, please?
> > > > 
> > > 
> > > I see that now.
> > > 
> > 
> > Hi Shuah,
> > 
> > In the other replies to this thread, Marcos noted that he would add
> > some
> > text to the commit / documentation on running and building the
> > selftests
> > directly in the kernel tree (that would get my Ack) ... is there
> > anything else to be updated for a hopefully final v4 (for your
> > Ack)?
> > 
> 
> 
> I am waiting for v4 with your comments are addressed. I can take
> this through kselftest tree.

Ok. I'm already preparing the v4. The plan is to send in the next few
days.

Thanks,
  Marcos

> 
> thanks,
> -- Shuah
>