lkml.org 
[lkml]   [2021]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH v2 04/12] module: Add printk format to add module build ID to stacktraces
    From
    Date
    On 24/03/2021 20.11, Stephen Boyd wrote:
    > Quoting Rasmus Villemoes (2021-03-24 02:57:13)

    >>
    >> Is there any reason you didn't just make b an optional flag that could
    >> be specified with or without R? I suppose the parsing is more difficult
    >> with several orthogonal flags (see escaped_string()), but it's a little
    >> easier to understand. Dunno, it's not like we're gonna think of 10 other
    >> things that could be printed for a symbol, so perhaps it's fine.
    >>
    >
    > I think I follow. So %pSb or %pSRb? If it's easier to understand then
    > sure. I was trying to avoid checking another character beyond fmt[1] but
    > it should be fine if fmt[1] is already 'R'.
    >

    I don't know. On the one hand, it seems sensible to allow such "flag"
    modifiers to appear independently and in any order. Because what if some
    day we think of some other property of the symbol we might want to
    provide access to via a "z" flag; when to allow all combinations of the
    R, b and z functionality we'd have to use four more random letters to
    stand for various combinations of those flags. On the other hand,
    vsprintf.c is already a complete wild west of odd conventions for
    %p<foo>, and it's not like symbol_string() gets extended every other
    release, and I can certainly understand the desire to keep the parsing
    of fmt minimal. So 'r' to mean 'Rb' is ok by me if you prefer that.

    Rasmus

    \
     
     \ /
      Last update: 2021-03-24 23:22    [W:2.516 / U:0.044 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site