From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Mark Jackson <mpfj@mimc.co.uk>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
David Woodhouse <dwmw2@infradead.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Badness at mm/backing-dev.c:179
Date: Mon, 8 Dec 2008 13:54:42 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0812081353540.21492@anakin> (raw)
In-Reply-To: <ac3eb2510812080442u749eb997o1ad6d6036b6d7c5c@mail.gmail.com>
On Mon, 8 Dec 2008, Kay Sievers wrote:
> On Mon, Dec 8, 2008 at 09:16, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Wed, 3 Dec 2008, Kay Sievers wrote:
> >> On Wed, Dec 3, 2008 at 13:07, Mark Jackson <mpfj@mimc.co.uk> wrote:
> >> > The following commit causes a "Badness at mm/backing-dev.c:179":-
> >> >
> >> > f1d0b063d993527754f062c589b73f125024d216 is first bad commit
> >> > commit f1d0b063d993527754f062c589b73f125024d216
> >> > Author: Kay Sievers <kay.sievers@vrfy.org>
> >> > Date: Tue Dec 2 10:31:50 2008 -0800
> >> >
> >> > bdi: register sysfs bdi device only once per queue
> >>
> >> > Below is the extract from dmesg:-
> >> >
> >> > ------------[ cut here ]------------
> >> > Badness at mm/backing-dev.c:179
> >>
> >> That's a known issue, and will not cause any harm besides printing
> >> this warning. Andrew added the warning to catch drivers who use one
> >> single request queue for multiple devices. Currently known are mtd and
> >> floppy (triggers only if you have more than one device per driver).
> >> The drivers need to be changed to use a separate queue per device, to
> >> get rid of this warning.
> >
> > I guess this one (introduced after 2.6.28-rc7) is an incarnation of the same
> > issue?
>
> You have more than one floppy device registered at the same time,
> right? Then it's very likely the same issue, that both devices share
> the same request queue, like the x86 floppy.c.
Yep, ataflop.c (and amiflop.c) forked from floppy.c a long time ago...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2008-12-08 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 12:07 Mark Jackson
2008-12-03 12:22 ` Kay Sievers
2008-12-03 12:26 ` Mark Jackson
2008-12-03 19:06 ` Andrew Morton
2008-12-08 8:16 ` Geert Uytterhoeven
2008-12-08 12:42 ` Kay Sievers
2008-12-08 12:54 ` Geert Uytterhoeven [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=Pine.LNX.4.64.0812081353540.21492@anakin \
--to=geert@linux-m68k.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=haavard.skinnemoen@atmel.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mpfj@mimc.co.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®