linux-kernel - Ramdisk Vs NFS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <D83235F0F3C86D4D889D8B9A0DA8C6D762CA83@corpexc01.corp.networkrobots.com>
Date:	Tue, 24 Apr 2007 20:27:23 -0700
From:	"Siva Prasad" <sprasad@...io.net>
To:	<linux-kernel@...r.kernel.org>
Subject: Ramdisk Vs NFS

Hi,

What is the primary difference between Ramdisk and NFS with respect to
the wait_queue's?

If I use ramdisk, every thing works fine, but with NFS (or you may read
as 'no ramdisk') kernel/sched.c:__wake_up_common() routines has a
problem. Basically the value of "&q->task_list->next" is out of our
memory range (not between 0xc0000000 and 0xF0000000), and this causes
trouble of accessing non-existing memory. Why would this happen?

Interesting thing is, this happens much before we even load the ramdisk
drivers.

Appreciate if any one has some insight into this. At least a pointer to
where to start looking would be great.

Thanks
Siva

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/