Re: [PATCH] add a new command: ipcs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry, I made some mistake.

At 2012-4-11 17:06, qiaonuohan wrote:

what is struct nsproxy? Or is there any symbol referring to ipc_ns?

I want to know how does the kernel get struct ipc_ids. the previous and the hind kernel uses current->nsproxy->ipc_ns to get the pointer to struct ipc_namespace and then use a macro shm_ids to get struct ipc_ids. What about this kernel?




(d) On *all* RHEL4 2.6.9-era and SLES9 2.6.5-era kernels, the command
fail like this:

     ------ Shared Memory Segments ------
     KEY        SHMID      UID        PERMS      BYTES      NATTCH
STATUS
     ipcs: invalid structure member offset: ipc_id_ary_p
           FILE: ipcs.c  LINE: 540  FUNCTION: ipc_search_array()

     or this:

     ------ Shared Memory Segments ------
     KEY        SHMID      UID        PERMS      BYTES      NATTCH
STATUS
     (none allocated)------ Semaphore Arrays --------
     KEY        SEMID      UID        PERMS      NSEMS
     ipcs: invalid structure member offset: ipc_id_ary_p
           FILE: ipcs.c  LINE: 540  FUNCTION: ipc_search_array()


what is struct ipc_id? And what is entries in struct ipc_id or something
similar to it?

I mean struct ipc_ids, not ipc_id.


--
--
Regards
Qiao Nuohan
--------------------------------------------------
Qiao Nuohan
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
No. 6 Wenzhu Road, Nanjing, Nanjing, 210012, China
TEL: +86+25-86630566-8526 FUJITSU
INTERNAL: 7998-8526 FAX: +86+25-83317685
EMail: qiaonuohan@xxxxxxxxxxxxxx
--------------------------------------------------
This communication is for use by the intended
recipient(s) only and may contain information that
is privileged, confidential and exempt from
disclosure under applicable law. If you are not an
intended recipient of this communication, you are
hereby notified that any dissemination,
distribution or copying hereof is strictly
prohibited. If you have received this communication
in error, please notify me by reply e-mail,
permanently delete this communication from your
system, and destroy any hard copies you may have
printed


--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility


[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux