public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Pedro Francisco <pedrogfrancisco@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ath5k misbehaving affecting other kernel parts unrelated?
Date: Fri, 23 Apr 2010 21:13:42 +0200	[thread overview]
Message-ID: <20100423191342.GI29093@bicker> (raw)
In-Reply-To: <201004230806.13628.pedrogfrancisco@gmail.com>

On Fri, Apr 23, 2010 at 08:06:13AM +0100, Pedro Francisco wrote:
> Greetings!
> 
> Is it possible a faulty ath5k module to affect diverse parts of kernel causing 
> different oopses to happen referencing things as different as cdrom_ioctl, 
> find_vma, i915_gem_object_get_pages, get_vfs_caps_from_disk, 
> warn_slowpath_common (ath5k_tasklet_rx), proc_lookup_de and 
> _spin_lock(ext4_getattr) [soft lookup]?
> 

Yes.

A bug a kernel module could corrupt any memory.

If you know a working version of the kernel try a git bisect otherwise
just post your dmesg with the crash etc.

regards,
dan carpenter

  parent reply	other threads:[~2010-04-23 19:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  7:06 ath5k misbehaving affecting other kernel parts unrelated? Pedro Francisco
2010-04-23 13:48 ` John W. Linville
2010-04-23 16:37   ` me
2010-04-23 16:43     ` Maciej Żenczykowski
2010-04-24  8:59       ` Pedro Francisco
2010-04-24  8:56     ` Pedro Francisco
2010-04-24 12:05       ` me
2010-04-24 12:09       ` Vegard Nossum
2010-04-24 17:28         ` Pedro Francisco
2010-04-25 19:22           ` me
2010-04-25 20:29             ` Jiri Slaby
2010-04-25 21:24               ` Pedro Francisco
2010-04-27 11:04                 ` Pedro Francisco
2010-04-28 21:52           ` Pedro Francisco
2010-04-29  7:17             ` Vegard Nossum
2010-04-29 10:25               ` Pedro Francisco
2010-04-23 19:13 ` Dan Carpenter [this message]
2010-04-24  9:27   ` Pedro Francisco
2010-04-24 12:13     ` Dan Carpenter
2010-04-24 13:13       ` Pedro Francisco

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=20100423191342.GI29093@bicker \
    --to=error27@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pedrogfrancisco@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