Re: 2.6.8.1-mm2 breaks vmware

[Ville Herva]

On Fri, Aug 20, 2004 at 04:18:25PM +0300, you [Ville Herva] wrote:
> 
> I just noticed I had missed get_user_pages-handle-VM_IO.patch - I'll try
> backing that out first. I'll report back if I find anything interesting 
> with different patch mixtures.

Well, I just tried 2.6.8.1-mm2 minus get_user_pages-handle-VM_IO.patch but
that didn't help with the "cannot allocate memory" problem. Curiously, I
didn't get the "get_user_pages() returns -EFAULT" warning with this kernel.

Also, neither "echo 1 > /proc/sys/vm/overcommit_memory" nor "echo 1 >
/proc/sys/vm/legacy_va_layout" helped.

It seems this is "cannot allocate memory" might have something to do with
/dev/mem mmap() permissions - here's a strace:

--8<-----------------------------------------------------------------------
5022  geteuid32()                       = 1414
5022  setresuid32(-1, 0, -1)            = 0
5022  open("/dev/mem", O_RDWR)          = 8
5022  getuid32()                        = 1414
5022  setresuid32(-1, 1414, -1)         = 0
5022  old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x3d6000) = -1 EPERM (Operation not permitted)
5022  close(8)                          = 0
5022  ioctl(4, 0xf0, 0x3d6000)          = 0
5022  time(NULL)                        = 1093011756
5022  open("/etc/localtime", O_RDONLY)  = 8
5022  fstat64(8, {st_mode=S_IFREG|0644, st_size=682, ...}) = 0
5022  close(8)                          = 0
5022  writev(3, [{"Aug 20 17:22:36: ", 17}, {"VMX|", 4}, {"Msg_Post: Error\n", 16}], 3) = 37
5022  writev(3, [{"Aug 20 17:22:36: ", 17}, {"VMX|", 4}, {"[msg.msg.noMem] Cannot allocate "..., 40}], 3) = 61
5022  writev(3, [{"Aug 20 17:22:36: ", 17}, {"VMX|", 4}, {"--------------------------------"..., 41}], 3) = 62
--8<-----------------------------------------------------------------------

I just put get_user_pages-handle-VM_IO.patch back and reverted
dev-mem-restriction-patch.patch - I'll report back when it has compiled. 


-- v -- 

v@xxxxxx

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