From: Florian Fainelli <f.fainelli@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>, Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, ard.biesheuvel@linaro.org,
labbott@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Peter Zijlstra <peterz@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Nicholas Piggin <npiggin@gmail.com>,
Olof Johansson <olof@lixom.net>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Matthew Wilcox <mawilcox@microsoft.com>,
Al Viro <viro@zeniv.linux.org.uk>, Jiri Pirko <jiri@mellanox.com>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL
Date: Tue, 8 Aug 2017 11:04:11 -0700 [thread overview]
Message-ID: <eabb661e-0442-b274-2c79-95bc52f2a79b@gmail.com> (raw)
In-Reply-To: <20170808175708.GR27873@wotan.suse.de>
On 08/08/2017 10:57 AM, Luis R. Rodriguez wrote:
> On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote:
>> Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works
>> correctly, at least that it can catch invalid calls to virt_to_phys()
>> against the non-linear kernel virtual address map.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> +static int __init test_debug_virtual_init(void)
>> +{
>> + phys_addr_t pa;
>> + void *va;
>> +
>> + va = (void *)VMALLOC_START;
>> + pa = virt_to_phys(va);
>> +
>> + pr_info("PA: %pa for VA: 0x%lx\n", &pa, (unsigned long)va);
>> +
>> + foo = kzalloc(sizeof(*foo), GFP_KERNEL);
>> + if (!foo)
>> + return -ENOMEM;
>> +
>> + pa = virt_to_phys(foo);
>> + va = foo;
>> + pr_info("PA: %pa for VA: 0x%lx\n", &pa, (unsigned long)va);
>
> Should there be a tests here of some sort? When should this fail, why?
There is no test per-se, the kernel will produce warning with
CONFIG_DEBUG_VIRTUAL telling you that what you are doing is wrong.
> There is no docs on this self test, could one be added?
I suppose I could add one even though that just means pointing out the
code that produces the warning?
--
Florian
next prev parent reply other threads:[~2017-08-08 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 16:40 Florian Fainelli
2017-08-08 17:57 ` Luis R. Rodriguez
2017-08-08 18:04 ` Florian Fainelli [this message]
2017-08-08 18:35 ` Luis R. Rodriguez
2017-08-08 19:58 ` Kees Cook
2017-08-19 17:44 ` Florian Fainelli
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=eabb661e-0442-b274-2c79-95bc52f2a79b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bart.vanassche@sandisk.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jgross@suse.com \
--cc=jiri@mellanox.com \
--cc=jlayton@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=olof@lixom.net \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--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
all inboxes | Powered by JetHome®