Ted Kremenek wrote:
> Currently we are looking primarily into the
> ioctls in drivers/net,
Just as a small aside, a little over five years ago (wow does time fly!) I
did a manual audit for mistakes like this:
http://lkml.org/lkml/2000/3/7/156
Not sure if that's relevant to your work your not...
Tomasz Torcz wrote:
See: http://home-tj.org/m15w/
...but this link just doesn't explain why performance is sooo bad with
2.6.11.x kernels (Timing buffered disk reads at 10-20 MB/sec), and is
just OK with older 2.6 kernels (Timing buffered disk reads even at about
100 MB/sec with 2.6.8.1).
any c
Chris Wright wrote:
* Tomasz Chmielewski ([EMAIL PROTECTED]) wrote:
or should I wait for 2.6.11.7 (?), where it should be corrected?
well, indeed, a week ago or more :)
Wait, no longer, 2.6.11.7 has been here already ;-) However, nothing in
this area was touched. If there's an outstanding issue,
Hi Im trying to boot an encrypted file system using an initrd on a USB.
I use syslinux for the actual boot process as I couldnt get Grub to boot
of it for some reason. This is the .cfg
default vmlinuz
timeout 100
prompt 1
label linux
kernel vmlinuz
append initrd=/initrd.gz root=/dev/ram0 ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomasz Chmielewski wrote:
>
> OK so Tomasz Torch suggested that my drive was blacklisted somewhere
> after 2.6.8.1 (it's the last kernel on which I have good performance).
>
> Does drive blacklisting = very poor performance?
> And no drive blacklisti
Um yes it is.
How could I otherwise have booted far enough to get the panic?
My boot partition is on the usb I cant boot from hard drive.
Ursprungligt meddelande
Från: [EMAIL PROTECTED]
Datum: Apr 15, 2005 9:29:06 AM
Till: gabriel <[EMAIL PROTECTED]>
Ärende: RE: Booting from USB with initr
> gabriel <[EMAIL PROTECTED]> writes:
> Hi Im trying to boot an encrypted file system using an initrd on a
> USB. I use syslinux for the actual boot process as I couldnt get
> Grub to boot of it for some reason. This is the .cfg
> ...
> ...
> ...
> Kernel panic - not syncing: VFS: Unable t
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
(1,0)
> followed by the USB information and stop.
> <5> Vendor SWISSBIT Mode: Victorinox 2.0 Rev 2.00
> Type Direct-Access ANSI SCSI Revision: 02
> SCSI device sdb: 1022720 512 byte hdwr sectors (524mb)
> sdb: Write Protec
* Jesper Juhl <[EMAIL PROTECTED]> wrote:
> As per this patch perhaps? :
>
> Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
this is still not enough (there was one more comparison to cover). Also,
it's a bit cleaner to just cast the left side to signed than cast every
member separately.
Hi,
I've been stumbling the last couple of weeks, getting a new box
working. The problem is that I have a Promise FastTrack SX4 with 512MB
cache and four 300GB Maxtor SATA drives connected to it. I've used
mdadm to create a RAID5 array, which is about 879G.
On this array, I've tried LVM (with Rei
* William Weston <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Apr 2005, Ingo Molnar wrote:
>
> > what are you using kprobes for? Do you get lockups even if you disable
> > kprobes?
>
> Various processes will lockup on the P4/HT system, usually while under
> some load. The processes cannot be kill
On Fri, 2005-04-15 at 09:27 +0200, gabriel wrote:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Hi Gabriel!
It looks like initrd.gz could not be mounted. The unknown-block(1,0)
is /dev/ram0 (and has normally initrd attached to it) as specified on
kernel command
Christian Kujau wrote:
> oh, this sounds good. strange though, that my 2.6.11-gentoo-r5 (whatever
> they've patched in there) *never* oopsed the days ago but all of a sudden
> started to oops yesterday
Probably because you changed alsa-lib versions. By the way, it is fixed in
gentoo-sources-2.
On 2005-04-15T00:56:35, Domen Puncer <[EMAIL PROTECTED]> wrote:
> This is permissions in sysfs (or 0 if no file is to be created).
Duh. Should have caught that. Try this one.
Index: linux-2.6.11/drivers/block/nbd.c
===
--- linux-2.6
On Fri, 15 Apr 2005, Matthew Wilcox wrote:
> On Fri, Apr 15, 2005 at 03:07:42AM +0200, Jesper Juhl wrote:
> > 'arg' is unsigned so it can never be less than zero, so testing for that
> > is pointless and also generates a warning when building with gcc -W. This
> > patch eliminates the pointless
On Fri, Apr 15, 2005 at 02:31:00AM +0100, Matthew Wilcox wrote:
> On Fri, Apr 15, 2005 at 03:07:42AM +0200, Jesper Juhl wrote:
> > 'arg' is unsigned so it can never be less than zero, so testing for that
> > is pointless and also generates a warning when building with gcc -W. This
> > patch elimi
At Thu, 14 Apr 2005 19:35:19 -0400,
Lee Revell wrote:
>
> On Fri, 2005-04-15 at 01:22 +0200, Christian Kujau wrote:
> > maybe some guru can shed some light on what's going on in xmms-oops.txt
> > and tell me who's to bug here :->
>
> Fixed in 2.6.11.7.
Also, the latest CVS alsa-lib checks the ti
Hello all,
I have a question that I could not figure out from other sources. I have
the following hardware: an integrated CardBus USB host adapter with a
connected USB serial device with three interfaces (normally
ttyUSB0...ttyUSB2). Now I want to use 3 of these devices (remember: they
are integrat
On Fri, 2005-04-15 at 09:27 +0200, gabriel wrote:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
(1,0)
>Hi Gabriel!
Hi!
>It looks like initrd.gz could not be mounted. The unknown-block(1,0)
>is /dev/ram0 (and has normally initrd attached to it) as specified on
>kerne
Guillaume Chazarain wrote:
From 2.6.11 to 2.6.12-rc2, there are some changes in the joystick
behaviour
that I don't think are expected. It's a simple joystick using
analog.ko plugged
on a sound board using snd-ens1371. So here we go:
Reverting
http://linux.bkbits.net:8080/linux-2.5/diffs/drivers
Matt Mackall wrote:
> Zero only the mlocked regions. This should take essentially no time at
> all. Swsusp knows which these are because they have to be mlocked
> after resume as well. If it's not mlocked, it's liable to be swapped
> out anyway.
Nitpicking:
What happens if the disk decides to relo
Matt Mackall wrote:
> A much more likely vector is stealing the laptop while it's suspended.
> And the encrypted swsusp patch has -zero- security here: it writes the
> key in the header in the clear. It's rather odd that everyone's hung
> up on the "box rooted after resume" attack and completely ig
Pavel Machek wrote:
> Andreas, do you think you could write nice, long, FAQ entries so that
> we don't have to go through this discussion over and over?
I can do so over the weekend. Am I right that you mean the FAQ section
of Documentation/power/swsusp.txt?
BTW: would it make sense to reset the
Hi!
> > Andreas, do you think you could write nice, long, FAQ entries so that
> > we don't have to go through this discussion over and over?
>
> I can do so over the weekend. Am I right that you mean the FAQ section
> of Documentation/power/swsusp.txt?
Yes.
> BTW: would it make sense to reset t
Dear all,
I have a query here regarding how does a touch screen driver work?
I have TS driver working but the calibration points seem to be not set
properly. When I launch an qt application, the touch on edit dropdown
button opens the file dropdown button.
Any clink on any button of the appli
On Thu, 14 Apr 2005, Randy.Dunlap wrote:
> On Fri, 15 Apr 2005 02:58:54 +0200 (CEST) Jesper Juhl wrote:
>
> | When building with gcc -W fs/reiserfs/namei.c:602 has a few warnings
> | about 'empty body in an if-statement'. This patch silences those warnings.
>
> So fix include/linux/reiserfs_x
Good morning,
On Thu, Apr 14, 2005 at 10:20:08PM -0500, Alejandro Bonilla wrote:
> Matti,
>
> Where do we stand here? Now that you have two of those outputs, so I
> can have some hope... Do you think we can make the driver for this
> hardware?
>
> How about the firmware that the documents menti
Vadim Lobanov <[EMAIL PROTECTED]> wrote:
> I think I misspoke a bit in my email above. The intent was not to
> eliminate all might_sleep() calls from the copy_from_user() code path;
> but rather juggle the source around a bit so there is only one
> might_sleep() call per each code path. Currently,
On Fri, Apr 15, 2005 at 10:00:39AM +0200, Eduard de Boer wrote:
> I use rsync to copy a bunch of files (several GB's) to the designated
> filesystems. But after a while, all file systems get corrupted and
> 'dmesg' lists all kinds of memory corruptions in 'dm' and so on.
> Hence, the file copying s
Hi!
> This is a small set of bugfixes for 2.6.12-rc2 ... you asked me to try
> git, so I did (I actually updated my bk backport script simply to export
> from a BK tree to a git tree). For the time being, I plan to keep the
> scsi changes in BK, but I'll export them for you to try merging
>
> Th
Andre Bender wrote:
OK so Tomasz Torch suggested that my drive was blacklisted somewhere
after 2.6.8.1 (it's the last kernel on which I have good performance).
Does drive blacklisting = very poor performance?
And no drive blacklisting = good performance, and possibly data corruption?
That's what h
Darren Williams wrote:
Hi All
Thanks to the team at [EMAIL PROTECTED] we now have a
no so complete Git archive at
http://www.gelato.unsw.edu.au/archives/git/
If somebody could send me a complete Git mbox I will
update the archive with it.
- dsw
gmane.org is already archiving this list.
-
To unsub
Hi!
> > This is a small set of bugfixes for 2.6.12-rc2 ... you asked me to try
> > git, so I did (I actually updated my bk backport script simply to export
> > from a BK tree to a git tree). For the time being, I plan to keep the
> > scsi changes in BK, but I'll export them for you to try merging
On Fri, Apr 15, 2005 at 09:21:50AM +0100, Christoph Hellwig wrote:
> On Fri, Apr 15, 2005 at 02:31:00AM +0100, Matthew Wilcox wrote:
> > On Fri, Apr 15, 2005 at 03:07:42AM +0200, Jesper Juhl wrote:
> > > 'arg' is unsigned so it can never be less than zero, so testing for that
> > > is pointless an
On Fri, Apr 15, 2005 at 12:29:08PM +0100, Matthew Wilcox wrote:
> > I think Linux only complained if we're using some typedef that actually
> > may be signed. For fcntl that 'arg' argument is unsigned and that's
> > hardcoded
> > in the ABI. So the check doesn't make sense at all.
>
> No, it wa
Hi,
Is there currently a kernel tree that Linus is working ?
I mean, now that we have 2.6.12-rc2 not being
developed with BK, is that code getting fixes and other patches
as we speak or the development will continue in a while someplace
else ?
Regards,
Maciej
-
To unsubscribe from this list: se
On Fri, 15 Apr 2005, Darren Williams wrote:
> Hi All
>
> Thanks to the team at [EMAIL PROTECTED] we now have a
> no so complete Git archive at
> http://www.gelato.unsw.edu.au/archives/git/
>
> If somebody could send me a complete Git mbox I will
> update the archive with it.
Apparently gmane.o
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
>> No, it was exactly this patch:
>> http://www.ussg.iu.edu/hypermail/linux/kernel/0401.0/1816.html
>
> Hmm. Looks I absolutely disagree with Linus on this one ;-)
Me too. The compiler doesn't really have much choice here. If
it ignores all compar
On Thu, Apr 14, 2005 at 07:02:44AM +0200, Willy Tarreau wrote:
> You may try to unload the ehci-hcd driver and load only uhci and check if
> it still happens. I guess from the trace that the problem lies in the ehci
> driver itself.
Your guess is right. With only uhci loaded it works (dog slow of
Have you edit the build-initrd.sh script to fit your needs?
Does
http://featherlinux.berlios.de/usb-instructions.htm or
http://www.ussg.iu.edu/hypermail/linux/kernel/0211.1/0551.html help?)
Totally different Q's:
Have you called syslinux with the correct parameter to find your
initrd.gz?
Siddha, Suresh B wrote:
Appended patch makes sched domain degenerate really work.
For example, now NUMA domain really gets removed on a non-NUMA system.
Signed-off-by: Suresh Siddha <[EMAIL PROTECTED]>
--- linux-2.6.12-rc2-mm3/kernel/sched.c 2005-04-13 11:15:00.942609504 -0700
+++ linux-mc/kernel/s
You can not remove the entries in sys_info.h (osMajorVersion & friends),
this communicates information to the application via the ioctls and the
structure shape is important. Change the code to zero the values, leave
osType set to OS_LINUX.
Sincerely -- Mark Salyzyn
-Original Message-
Fr
On Fri, Apr 15, 2005 at 10:03:05PM +1000, Herbert Xu wrote:
> I suppose it could be smart and stay quiet about
>
> val < 0 || val > BOUND
>
> However, gcc is slow enough as it is without adding unnecessary
> smarts like this.
It only warns with -W on, not with -Wall, so I see no compelling
reaso
On Fri, 2005-04-15 at 13:25 +0200, Pavel Machek wrote:
> Okay, so du -s is:
>
> [EMAIL PROTECTED]:~# du -sh /tmp/delme.git/
> 109M/tmp/delme.git/
>
> Not as bad as I expected, but still quite a lot of data for few
> changes.
Erm, but that's why it's an rsync archive. You're supposed to have
There are currently two different boot_cpu_logical_apicid variables:
- a global one in mpparse.c
- a static one in smpboot.c
Of these two, only the one in smpboot.c might be used (through
boot_cpu_apicid).
This patch therefore removes the one in mpparse.c .
Signed-off-by: Adrian Bunk <[EMAIL PR
On Fri, Apr 15, 2005 at 01:34:17AM -, [EMAIL PROTECTED] wrote:
> (Speaking of which, perhaps it's time, in light of the breaking of MD5,
> to revisit the cut-down MD4 routine used in the TCP ISN selection?
> I haven't read the MD5 & SHA1 papers in enough detail to understand the
> flaw, but per
On Mer, 2005-04-13 at 17:03, Miquel van Smoorenburg wrote:
> I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard,
> 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32
> bits mode it runs fine, both with the dpt_i2o driver and the
> generic i2o_block driver using kernel 2.
The attached patch adds 32-bit compatibility for mounting an NFSv4 mount on a
64-bit kernel (such as happens with PPC64).
The problem is that the mount data for the NFS4 mount process includes
auxilliary data pointers, probably because the NFS4 mount data may conceivably
exceed PAGE_SIZE in size
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Takashi Iwai wrote:
>
> Also, the latest CVS alsa-lib checks the timer protocol version to
> avoid this Oops with the older kenel. 1.0.9-rc3 is planned to be
> released soon, so wait for a moment...
um, i'll wait for the next release as i don't trac
On Mer, 2005-04-13 at 14:23, Lennart Sorensen wrote:
> On Wed, Apr 13, 2005 at 03:06:46PM +0200, Lars Marowsky-Bree wrote:
> Graphics card companies don't realize they are hardware companies not
> software companies and that it is hardware they make their money from?
> Oh and they have too many law
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 4 Mar 2005
--- linux-2.6.11-rc5-mm1-full/kernel/kallsyms.c.old 2005-03-04
00:49:34.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/kallsyms.c 20
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 4 Mar 2005
--- linux-2.6.11-rc5-mm1-full/kernel/sys.c.old 2005-03-04 01:19:18.0
+0100
+++ linux-2.6.11-rc5-mm1-full/kernel/sys.c 2005-03-04
On Llu, 2005-04-11 at 17:01, Jonas Diemer wrote:
> Yes, but a new video-card or Motherboard can be easily bought (although it
> costs), but the data on a locked disk is lost forever, unless you pay for
> professional recovery (which is also a time-issue, if time critical data is
> stored on the
This patch makes a needlessly global struct static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Eric Biederman <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 3 Mar 2005
include/linux/kexec.h |1 -
kernel/kexec.c|2 +-
2 files changed, 1 insertion(+)
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 4 Mar 2005
--- linux-2.6.11-rc5-mm1-full/kernel/panic.c.old2005-03-04
00:54:46.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/panic.c20
This patch makes a needlessly global function static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 3 Mar 2005
include/linux/irq.h |1 -
kernel/irq/spurious.c |2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
--- linux-2.6.11-rc5-mm1-full/
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 4 Mar 2005
--- linux-2.6.11-rc5-mm1-full/kernel/printk.c.old 2005-03-04
00:58:16.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/printk.c 20
Trial and error (and hope they are always the same, which I think they
are with 2.6).
On Fri, 15 Apr 2005, Joerg Pommnitz wrote:
> Hello all,
> I have a question that I could not figure out from other sources. I have
> the following hardware: an integrated CardBus USB host adapter with a
> connec
On Fri, 15 Apr 2005, Joerg Pommnitz wrote:
> Hello all,
> I have a question that I could not figure out from other sources. I have
> the following hardware: an integrated CardBus USB host adapter with a
> connected USB serial device with three interfaces (normally
> ttyUSB0...ttyUSB2). Now I want
This patch contains the following cleanups:
- make some needlessly global functions static
- remove one more kernel 2.2 #ifdef
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 28 Feb 2005
drivers/scsi/gdth.c | 24
drivers/scsi/gdth
This patch makes a needlessly global variable static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 1 Mar 2005
--- linux-2.6.11-rc4-mm1-full/drivers/serial/8250.c.old 2005-02-28
23:03:34.0 +0100
+++ linux-2.6.11-rc4-mm1-full/drivers/serial/8250.c
This patch fixes the following warning:
<-- snip -->
...
CC drivers/serial/8250_acpi.o
drivers/serial/8250_acpi.c: In function `acpi_serial_ext_irq':
drivers/serial/8250_acpi.c:51: warning: implicit declaration of function
`acpi_register_gsi'
...
<-- snip -->
This patch was already
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 4 Mar 2005
--- linux-2.6.11-rc5-mm1-full/kernel/resource.c.old 2005-03-04
01:01:30.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/resource.c 20
> The ISN selection is there only to make it harder to accomplish TCP
> hijacking attacks from people who are on networking path between the
> source and destination. And you have to guess the ISI before the
> 3-way TCP handshake has been negotiated (or if you can stop the SYN
> packet in flight,
On Fri, 15 Apr 2005, Catalin Marinas wrote:
> Vadim Lobanov <[EMAIL PROTECTED]> wrote:
> > I think I misspoke a bit in my email above. The intent was not to
> > eliminate all might_sleep() calls from the copy_from_user() code path;
> > but rather juggle the source around a bit so there is only one
* Ted Kremenek ([EMAIL PROTECTED]) wrote:
> In several network drivers that handle the ioctl command SIOCSMIIREG
> (writes a register on the network card) most implementations check for
> the CAP_NET_ADMIN capability. Several drivers use the function
> "generic_mii_ioctl" to process this comman
Hi,
I was curious about how kernel rootkits become a part of the kernel ?
One way I guess is by inserting a kernel module. And rootkits also
manage to hide themselves from rootkit detectors.
few questions:
1. Are there any other ways by which rootkits become part of the kernel ?
2. If modules c
On 4/16/05, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Mer, 2005-04-13 at 14:23, Lennart Sorensen wrote:
> > On Wed, Apr 13, 2005 at 03:06:46PM +0200, Lars Marowsky-Bree wrote:
> > Graphics card companies don't realize they are hardware companies not
> > software companies and that it is hardware the
On Fri, 15 Apr 2005 17:10:53 +0200, Adrian Bunk wrote:
> This patch fixes the following warning:
> CC drivers/serial/8250_acpi.o
> drivers/serial/8250_acpi.c: In function `acpi_serial_ext_irq':
> drivers/serial/8250_acpi.c:51: warning: implicit declaration of function
> `acpi_register_gsi
Benjamin LaHaise <[EMAIL PROTECTED]> wrote:
> Oh dear, this is going to take a while. In any case, here is such a
> first step in creating such a sequence of patches. Located at
> http://www.kvack.org/~bcrl/patches/mutex-A0/ are the following patches:
> ...
> 10_new_mutex.diff - Replace
On Fri, 2005-04-15 at 15:52 +0100, Alan Cox wrote:
> On Mer, 2005-04-13 at 17:03, Miquel van Smoorenburg wrote:
> > I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard,
> > 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32
> > bits mode it runs fine, both with the dpt_i2
> I still don't think they would lose out by much.. I've just being
> trying to RE the ATI Mpeg2 IDCT/MC hardware, ATI know this, I know
> this, they are only wasting my time and my employers money (we still
> are going to buy their chips... no choice..) will they give out specs
> .. no .. why? cau
On Fri, Apr 15, 2005 at 10:42:16AM -0400, Theodore Ts'o wrote:
> > Just to be clear, I don't remember it ever throwing entropy away, but
> > it hoards some for years, thereby making it effectively unavailable.
> > Any catastrophic reseeding solution has to hold back entropy for some
> > time.
>
>
I had hoped that one can figure things out from /proc and /sys. SHould'n
there be a way to do this? And no, trial and error is not really an
option. The devices in question are WCDMA/UMTS mobile data cards. They
will differ only by the SIM card inserted by the user. The ICCID of the
SIM is unknown
Hello,
Does anyone happen to know how the upcoming multi-core CPU will be handled
by the kernel? Does it see each core as a physical or logical CPU or ?
Vanderpool is a hardware support for OS virtualization (running multiple OS
"at the same time"), how does Linux kernel make use of this, particul
Hi,
we are running some pretty large applications in 32bit mode on 64bit
AMD kernels (8GB Ram, Dual AMD64 CPUs, SMP). Kernel is 2.6.11.4 or
2.4.21.
Some of these applications run consistently out of memory but only
on 2.6 machines. In fact large memory allocations that libc answers
> And the argument that "random.c doesn't rely on the strength of crypto
> primitives" is kinda lame, though I see where you're coming from.
> random.c's entropy mixing and output depends on the (endian incorrect)
> SHA-1 implementation hard coded in that file to be pre-image resistant.
> If that f
On Fri, Apr 15, 2005 at 11:44:06AM +0200, Andreas Steinmetz wrote:
> Matt Mackall wrote:
> > Zero only the mlocked regions. This should take essentially no time at
> > all. Swsusp knows which these are because they have to be mlocked
> > after resume as well. If it's not mlocked, it's liable to be
On Fri, Apr 15, 2005 at 04:50:36PM -, [EMAIL PROTECTED] wrote:
> (And as for the endianness of the SHA-1, are you trying to imply
> something? Because it makes zero difference, and reduces the code
> size and execution time. Which is obviously a Good Thing.)
It just bugged me when I was read
On Fri, 15 Apr 2005, Allison wrote:
Hi,
I was curious about how kernel rootkits become a part of the kernel ?
One way I guess is by inserting a kernel module. And rootkits also
manage to hide themselves from rootkit detectors.
I'm not sure there really are any "kernel" rootkits. You need to be
roo
On Thu, Apr 14, 2005 at 11:27:12AM -0700, Chris Wright wrote:
> * Andi Kleen ([EMAIL PROTECTED]) wrote:
> > > I will take a closer look at the rc1/rc2 patches later this evening
> > > and see if I can spot something. Can only report back tomorrow though.
> >
> > Actually itt started in .11 already
* Andi Kleen ([EMAIL PROTECTED]) wrote:
> On Thu, Apr 14, 2005 at 11:27:12AM -0700, Chris Wright wrote:
> > Yes, I've seen it in .11 and earlier kernels. Happen to have same
> > "x86_64" string on my bad pmd dumps, but can't reproduce it at all.
> > So, for now, I can hold off on adding the reload
On Fri, Apr 15, 2005 at 11:43:55AM +0530, Hariprasad Nellitheertha wrote:
> Hi Andi,
>
> In order to port kdump to x86_64, we need to have the
> memmap= kernel command line option available. This is so
> that the dump-capture kernel can be booted with a custom
> memory map.
>
> The attached pa
On Fri, 2005-04-15 at 13:16 -0400, Richard B. Johnson wrote:
> I'm not sure there really are any "kernel" rootkits. You need to be
> root to install a module and you need to be root to replace a kernel
> with a new (possibly altered) one. If you are root, you don't
> need an exploit.
rootkit !=
On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote:
> However, I removed 2 GB from the box as Alan sugggested and now the box
> comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back,
> and booted with the kernel "mem=2048" command line option - that also
> works, the i2o_bl
On Fri, 15 Apr 2005, Chris Wright wrote:
> * Andi Kleen ([EMAIL PROTECTED]) wrote:
> > On Thu, Apr 14, 2005 at 11:27:12AM -0700, Chris Wright wrote:
> > > Yes, I've seen it in .11 and earlier kernels. Happen to have same
> > > "x86_64" string on my bad pmd dumps, but can't reproduce it at all.
> >
On Gwe, 2005-04-15 at 00:20, Adrian Bunk wrote:
> On Sun, Mar 27, 2005 at 05:38:38PM +0100, Alan Cox wrote:
> > On Sul, 2005-03-27 at 15:34, Adrian Bunk wrote:
> > > - syncppp.c: sppp_input
> > > - syncppp.c: sppp_change_mtu
> > > - z85230.c: z8530_dma_sync
> > > - z85230.c: z8530_txdma_syn
* Linda Luu ([EMAIL PROTECTED]) wrote:
> Vanderpool is a hardware support for OS virtualization (running multiple OS
> "at the same time"), how does Linux kernel make use of this, particularly
> which part of the kernel code?
There's Xen support for upcoming VT, which will allow running unmodifie
Hello,
We are working on a LKM for the 2.6 kernel.
We HAVE to intercept system calls. I understand this could be
something developers are no encouraged to do these days, but we need
this.
Patching kernel to export sys_call_table is not an option. The fast
and dirty way to do this would be by using
On Fri, Apr 15, 2005 at 06:58:20PM +0100, Hugh Dickins wrote:
> > > If there was a fix for the bad pmd problem it might be a candidate
> > > for stable, but so far we dont know what causes it yet.
> > If I figure a way to trigger here, I'll report back.
>
> Dave, earlier on you were quite ab
Hello,
Alan Cox wrote:
On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote:
However, I removed 2 GB from the box as Alan sugggested and now the box
comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back,
and booted with the kernel "mem=2048" command line option - that also
wo
On Fri, 2005-04-15 at 13:33 -0400, Malita, Florin wrote:
> On Fri, 2005-04-15 at 13:16 -0400, Richard B. Johnson wrote:
> > I'm not sure there really are any "kernel" rootkits. You need to be
> > root to install a module and you need to be root to replace a kernel
> > with a new (possibly altered
* Igor Shmukler ([EMAIL PROTECTED]) wrote:
> We are working on a LKM for the 2.6 kernel.
> We HAVE to intercept system calls. I understand this could be
> something developers are no encouraged to do these days, but we need
> this.
I don't think you'll find much empathy or support here. This is s
On Fri, 2005-04-15 at 14:04 -0400, Igor Shmukler wrote:
> Hello,
> We are working on a LKM for the 2.6 kernel.
> We HAVE to intercept system calls. I understand this could be
> something developers are no encouraged to do these days, but we need
> this.
your module is GPL licensed right ? (You're
On Fri, 2005-04-15 at 20:10 +0200, Markus Lidel wrote:
> Hello,
>
> Alan Cox wrote:
> > On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote:
> >>However, I removed 2 GB from the box as Alan sugggested and now the box
> >>comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back
My Linux SATA software/hardware status reports have just been updated.
To see where libata (SATA) support stands for a particular piece of
hardware, or a particular feature, go to
http://linux.yyz.us/sata/
I've still got several patches from EMC (Brett) and IBM (Albert) to go
through, a
hi,
I got the terminology mixed up. I guess what I really want to know is,
what are the different types of exploits by which rootkits
(specifically the ones that modify the kernel) can get installed on
your system.(other than buffer overflow and somebody stealing the root
password)
I know that Su
Igor Shmukler wrote:
Hello,
We are working on a LKM for the 2.6 kernel.
We HAVE to intercept system calls. I understand this could be
something developers are no encouraged to do these days, but we need
this.
Too bad.
Patching kernel to export sys_call_table is not an option. The fast
and dirty way
On Fri, Apr 15, 2005 at 03:38:01PM -, [EMAIL PROTECTED] wrote:
>
> First of all, people *on* the netowrk path can just *see* the packets.
> Or modify them. Or whatever.
> The point is to prevent hijacking by people *not* on the path.
Yes, you're correct of course. Of course, I'll note that
Juergen Kreileder <[EMAIL PROTECTED]> writes:
> Andrew Morton <[EMAIL PROTECTED]> writes:
>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm3/
>
> I'm getting frequent lockups on my PowerMac G5 with rc2-mm3.
I think I finally found the culprit. Both rc2-m
1 - 100 of 193 matches
Mail list logo
