From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Jiri Slaby <jslaby@suse.cz>, Alan Cox <alan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc+0x1de/0x1f0()
Date: Tue, 11 Dec 2012 22:01:24 -0500 [thread overview]
Message-ID: <20121212030124.GA10828@redhat.com> (raw)
Fuzz-testing fallout from post 3.7 tree as of commit 414a6750e59b0b687034764c464e9ddecac0f7a6
[ 2181.230579] ------------[ cut here ]------------
[ 2181.231277] WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc+0x1de/0x1f0()
[ 2181.232358] Hardware name: GA-MA78GM-S2H
[ 2181.232925] tty is NULL
[ 2181.233430] Modules linked in: l2tp_ppp l2tp_core fuse rfcomm binfmt_misc hidp bnep scsi_transport_iscsi ipt_ULOG nfnetlink rose ipx p8023 p8022 caif_socket caif af_rxrpc x25 irda af_key appletalk pppoe netrom pppox ppp_generic decnet phonet slhc psnap crc_ccitt ax25 llc2 rds atm llc nfc can nfsv3 nfs_acl nfs fscache lockd sunrpc ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack nf_conntrack ip6table_filter ip6_tables snd_hda_codec_realtek btusb snd_hda_intel bluetooth usb_debug snd_hda_codec microcode snd_pcm serio_raw pcspkr snd_page_alloc snd_timer edac_core snd soundcore r8169 mii vhost_net tun macvtap macvlan kvm_amd kvm
[ 2181.245632] Pid: 29787, comm: kworker/0:1 Not tainted 3.7.0+ #12
[ 2181.246503] Call Trace:
[ 2181.246851] [<ffffffff8104da4f>] warn_slowpath_common+0x7f/0xc0
[ 2181.247725] [<ffffffff8104db46>] warn_slowpath_fmt+0x46/0x50
[ 2181.248558] [<ffffffff8132e6ba>] ? ___ratelimit+0x9a/0x120
[ 2181.249347] [<ffffffff813e897e>] flush_to_ldisc+0x1de/0x1f0
[ 2181.250164] [<ffffffff81071237>] process_one_work+0x207/0x750
[ 2181.251013] [<ffffffff810711c7>] ? process_one_work+0x197/0x750
[ 2181.251893] [<ffffffff8106de50>] ? destroy_work_on_stack+0x20/0x20
[ 2181.252809] [<ffffffff813e87a0>] ? tty_insert_flip_string_fixed_flag+0x110/0x110
[ 2181.253993] [<ffffffff81071b56>] worker_thread+0x156/0x440
[ 2181.254815] [<ffffffff81071a00>] ? rescuer_thread+0x240/0x240
[ 2181.255638] [<ffffffff810784bd>] kthread+0xed/0x100
[ 2181.256374] [<ffffffff810b80ce>] ? put_lock_stats.isra.23+0xe/0x40
[ 2181.257290] [<ffffffff810783d0>] ? kthread_create_on_node+0x160/0x160
[ 2181.258223] [<ffffffff816a8ddc>] ret_from_fork+0x7c/0xb0
[ 2181.259018] [<ffffffff810783d0>] ? kthread_create_on_node+0x160/0x160
[ 2181.259969] ---[ end trace 12dd9f01acd7e09f ]---
next reply other threads:[~2012-12-12 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 3:01 Dave Jones [this message]
2012-12-15 2:29 ` WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc+0x1de/0x1f0() Greg Kroah-Hartman
2012-12-15 3:53 ` Peter Hurley
2012-12-15 16:17 ` Dave Jones
2012-12-15 17:25 ` Greg Kroah-Hartman
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=20121212030124.GA10828@redhat.com \
--to=davej@redhat.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@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.