From: Joe Perches <joe@perches.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [RFC PATCH] vsprintf: Add %pv extension replacement for print_vma_addr
Date: Fri, 14 Aug 2020 21:18:35 -0700 [thread overview]
Message-ID: <2364837d5dcf80f3bdece75d8bfc2f9747467571.camel@perches.com> (raw)
In-Reply-To: <20200815035228.GC582@jagdpanzerIV.localdomain>
On Sat, 2020-08-15 at 12:52 +0900, Sergey Senozhatsky wrote:
> Cc-ing John
>
> On (20/08/14 10:53), Joe Perches wrote:
> [..]
>
> In general, the idea looks nice.
>
> > +static noinline_for_stack
> > +char *vma_addr(char *buf, char *end, void *ip,
> > + struct printf_spec spec, const char *fmt)
> > +{
> > +#ifdef CONFIG_MMU
> > + struct mm_struct *mm = current->mm;
> > + struct vm_area_struct *vma;
> > +
> > + /*
> > + * we might be running from an atomic context so we cannot sleep
> > + */
> > + if (!mmap_read_trylock(mm))
> > + return buf;
> > +
> > + vma = find_vma(mm, (unsigned long)ip);
> > + if (vma && vma->vm_file) {
> > + char *p;
> > + struct file *f = vma->vm_file;
> > + char *page = (char *)__get_free_page(GFP_NOWAIT);
>
> Hmm, this is huge. For the time being this is going to introduce lock
> inversion chains:
>
> PRINTK -> printk_locks -> MM -> mm_locks
>
> vs
> MM -> mm_locks -> PRINTK -> printk_locks
>
> Another thing to mention is
>
> PRINTK -> printk_locks -> MM (WANR_ON/etc) -> PRINTK
>
> we are in printk_safe, currently, but that's going to change.
>
> We might not be ready to take this as of now, but things can change
> once we drop printk_locks.
>
> > + if (page) {
> > + p = file_path(f, page, PAGE_SIZE);
> > + if (IS_ERR(p))
> > + p = "?";
> > + buf = string(buf, end, kbasename(p), default_str_spec);
> > + buf = string_nocheck(buf, end, "[", default_str_spec);
> > + buf = pointer_string(buf, end,
> > + (void *)vma->vm_start,
> > + default_hex_spec);
> > + buf = string_nocheck(buf, end, "+", default_str_spec);
> > + buf = pointer_string(buf, end,
> > + (void *)(vma->vm_end - vma->vm_start),
> > + default_hex_spec);
> > + buf = string_nocheck(buf, end, "]", default_str_spec);
> > + free_page((unsigned long)page);
> > + }
> > + }
> > + mmap_read_unlock(mm);
> > +#else
> > + buf = string_nocheck(buf, end, "CONFIG_MMU=n", default_str_spec);
>
> Hmm, we don't usually do that CONFIG_FOO=n thing, I think we just need
> to skip %pv and print nothing.
I don't.
Right now, include/linux/mm.h has
#ifdef CONFIG_MMU
void print_vma_addr(char *prefix, unsigned long rip);
#else
static inline void print_vma_addr(char *prefix, unsigned long rip)
{
}
#endif
and the 'v' can't be #ifdef'd in vsprintf/pointer()
otherwise %pv would fallthrough to
return ptr_to_id(buf, end, ptr, spec);
next prev parent reply other threads:[~2020-08-15 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 17:53 Joe Perches
2020-08-14 18:38 ` Steven Rostedt
2020-08-14 19:24 ` Joe Perches
2020-08-15 3:52 ` Sergey Senozhatsky
2020-08-15 4:18 ` Joe Perches [this message]
2020-08-17 11:44 ` Andy Shevchenko
2020-08-17 14:39 ` Joe Perches
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=2364837d5dcf80f3bdece75d8bfc2f9747467571.camel@perches.com \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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
all inboxes | Powered by JetHome®