All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitry Kasatkin <d.kasatkin@samsung.com>
Cc: linux-kernel@vger.kernel.org, sarah.a.sharp@linux.intel.com,
	dmitry.kasatkin@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] dev-core: fix build break when DEBUG is enabled
Date: Thu, 15 Aug 2013 10:11:51 -0700	[thread overview]
Message-ID: <20130815171151.GA30547@kroah.com> (raw)
In-Reply-To: <520D0779.4020903@samsung.com>

On Thu, Aug 15, 2013 at 07:53:13PM +0300, Dmitry Kasatkin wrote:
> On 15/08/13 19:37, Greg KH wrote:
> > On Thu, Aug 15, 2013 at 07:04:54PM +0300, Dmitry Kasatkin wrote:
> >> When DEBUG is defined, dev_dbg_ratelimited uses dynamic debug data
> >> structures even when CONFIG_DYNAMIC_DEBUG is not defined.
> >> It leads to build break.
> >> For example, when I try to use dev_dbg_ratelimited in USB code and
> >> CONFIG_USB_DEBUG is enabled, but CONFIG_DYNAMIC_DEBUG is not, I get:
> >>
> >>   CC [M]  drivers/usb/host/xhci-ring.o
> >>   drivers/usb/host/xhci-ring.c: In function ‘xhci_queue_intr_tx’:
> >>   drivers/usb/host/xhci-ring.c:3059:3: error: implicit declaration of function ‘DEFINE_DYNAMIC_DEBUG_METADATA’ [-Werror=implicit-function-declaration]
> >>   drivers/usb/host/xhci-ring.c:3059:3: error: ‘descriptor’ undeclared (first use in this function)
> >>   drivers/usb/host/xhci-ring.c:3059:3: note: each undeclared identifier is reported only once for each function it appears in
> >>   drivers/usb/host/xhci-ring.c:3059:3: error: implicit declaration of function ‘__dynamic_pr_debug’ [-Werror=implicit-function-declaration]
> >>   drivers/usb/host/xhci-ring.c: In function ‘xhci_queue_isoc_tx_prepare’:
> >>   drivers/usb/host/xhci-ring.c:3847:3: error: ‘descriptor’ undeclared (first use in this function)
> >>   cc1: some warnings being treated as errors
> >>   make[2]: *** [drivers/usb/host/xhci-ring.o] Error 1
> >>   make[1]: *** [drivers/usb/host] Error 2
> >>   make: *** [drivers/usb/] Error 2
> >>
> >> This patch separates definition for CONFIG_DYNAMIC_DEBUG and DEBUG cases.
> >>
> >> Signed-off-by: Dmitry Kasatkin <d.kasatkin@samsung.com>
> >> Cc: stable@vger.kernel.org
> > How is this a stable issue?  I don't see how the rules listed in
> > Documentation/stable_kernel_rules.txt apply here, what am I missing?
> >
> > Not to say your patch isn't correct, just that it's not stable material,
> > right?
> >
> > thanks,
> >
> > greg k-h
> >
> 
> There are few drivers which uses dev_dbg_ratelimited().
> In the case someone tries to build kernel with those drivers with DEBUG
> enabled and without CONFIG_DYNAMIC_DEBUG,
> will get the build break. It will happen also on stable kernel.

Do you have specific examples of this happening?  Given that this code
has been this way for a very long time now, and Randy's excellent
'random .config bot' normally catches this type of thing, I think the
applicability to a stable release is pretty low.

Please read that Documentation file again about "actual" issues, not
just theoretical ones.

thanks,

greg k-h

      reply	other threads:[~2013-08-15 17:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 16:04 [PATCH 1/2] dev-core: fix build break when DEBUG is enabled Dmitry Kasatkin
2013-08-15 16:04 ` [PATCH 2/2] xhci:prevent "callbacks suppressed" when debug is not enabled Dmitry Kasatkin
2013-08-16  0:17   ` Greg KH
2013-08-16 17:26     ` Sarah Sharp
2013-08-16 17:30       ` Sarah Sharp
2013-08-16 17:37         ` Greg KH
2013-08-16 17:38         ` Dmitry Kasatkin
2013-08-16 17:45           ` Greg KH
2013-08-16 17:50             ` Sarah Sharp
2013-08-27 14:16             ` Dmitry Kasatkin
2013-08-27 17:39               ` Greg KH
2013-08-27 17:40                 ` Dmitry Kasatkin
2013-08-16 17:30       ` Greg KH
2013-08-16 17:38         ` Sarah Sharp
2013-08-16 17:42           ` Dmitry Kasatkin
2013-08-15 16:37 ` [PATCH 1/2] dev-core: fix build break when DEBUG is enabled Greg KH
2013-08-15 16:53   ` Dmitry Kasatkin
2013-08-15 17:11     ` Greg KH [this message]

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=20130815171151.GA30547@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=d.kasatkin@samsung.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stable@vger.kernel.org \
    /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.