From: <bug...@an...> - 2006-03-13 00:56:34
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 Summary: [agp mach64] Use DMA buffers for mach64_dma_vertex Product: DRI Version: DRI CVS Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: DRM modules AssignedTo: dri...@li... ReportedBy: fuf...@ho... BugsThisDependsOn: 6209 Here is my first attempt to use DMA buffers for vertex submission. It depends on https://bugs.freedesktop.org/show_bug.cgi?id=6209 As this is my first attempt to hack on the drm, any comments would be greatly appreciated. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-13 00:58:08
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-03-13 11:58 ------- Created an attachment (id=4911) --> (https://bugs.freedesktop.org/attachment.cgi?id=4911&action=view) mach64: DMA buffers for vertices patch for drm -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-13 00:58:51
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-03-13 11:58 ------- Created an attachment (id=4912) --> (https://bugs.freedesktop.org/attachment.cgi?id=4912&action=view) mach64-dri: DMA buffers for vertices patch for dri -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-13 00:59:30
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-03-13 11:59 ------- Created an attachment (id=4913) --> (https://bugs.freedesktop.org/attachment.cgi?id=4913&action=view) mach64-ddx: DMA buffers for vertices patch for ddx -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-13 14:24:11
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #4911 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-03-14 01:24 ------- Created an attachment (id=4925) --> (https://bugs.freedesktop.org/attachment.cgi?id=4925&action=view) mach64-drm: DMA buffers for vertices - try 1 Set the discard flag of the DMA correctly. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-29 18:27:09
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #4925 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-03-30 04:27 ------- Created an attachment (id=5123) --> (https://bugs.freedesktop.org/attachment.cgi?id=5123&action=view) mach64-drm: DMA buffers for vertices - try 2 enable test of register values in the vertex buffer. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-31 03:19:59
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From lde...@gm... 2006-03-31 13:19 ------- (In reply to comment #5) > Created an attachment (id=5123) --> (https://bugs.freedesktop.org/attachment.cgi?id=5123&action=view) [edit] > mach64-drm: DMA buffers for vertices - try 2 > > enable test of register values in the vertex buffer. It's good to see this driver getting some attention again, I'm sorry I don't have time to help out with the code right now. I wanted to point out that if you go this route (using client DMA buffers for vertices), you'll need to unmap the buffers from userspace before verifying and submitting them to make this secure. If you look at the CVS history, you'll see that we actually used to use DMA buffers, but changed to the current method when beginning the work to make the driver secure. We decided that copying the data from client memory into a pool of unmapped DMA buffers in the kernel would be faster than unmapping and re-mapping the buffers for each submit. Copying the userspace data into DMA buffers allocated from the mapped pool was a stopgap until we had a way to allocate unmapped buffers in the kernel for this purpose. It's been a while since I looked at the code in detail, but the problem at the time was a limitation of the DRM buffer management infrastructure. As I recall, there wasn't an easy way to create two sets of DMA buffers, one mapped to userspace, and one which wasn't mapped. You may want to look into the mailing list archives for more discussion on this. I think that this was the last remaining issue in securing the driver. -Leif -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-31 16:50:49
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fku...@at... 2006-04-01 02:50 ------- (In reply to comment #6) > It's been a while since I looked at the code in detail, but the problem at the > time was a limitation of the DRM buffer management infrastructure. As I recall, > there wasn't an easy way to create two sets of DMA buffers, one mapped to > userspace, and one which wasn't mapped. I did something that sounds like what you're trying to do, in the Savage driver for command DMA. Instead of using the DMA buffer infractructure I simply created a map of a chunck of AGP memory that can't be mapped to unprivileged clients. The DRM uses that map as a command buffer with its own ageing and buffer management implementation. I was going to try something like that in the Mach64 driver. Not sure how feasible this is or if there are any hardware issues that may prevent this. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-03-31 20:39:52
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-04-01 06:39 ------- (In reply to comment #6) > (In reply to comment #5) > > Created an attachment (id=5123) --> (https://bugs.freedesktop.org/attachment.cgi?id=5123&action=view) [edit] [edit] > > mach64-drm: DMA buffers for vertices - try 2 > > > > enable test of register values in the vertex buffer. > > It's good to see this driver getting some attention again, I'm sorry I don't > have time to help out with the code right now. > > I wanted to point out that if you go this route (using client DMA buffers for > vertices), you'll need to unmap the buffers from userspace before verifying and > submitting them to make this secure. If you look at the CVS history, you'll see > that we actually used to use DMA buffers, but changed to the current method when > beginning the work to make the driver secure. We decided that copying the data > from client memory into a pool of unmapped DMA buffers in the kernel would be > faster than unmapping and re-mapping the buffers for each submit. Copying the > userspace data into DMA buffers allocated from the mapped pool was a stopgap > until we had a way to allocate unmapped buffers in the kernel for this purpose. > Grrh, I knew I was missing something basic when I tried to touch this stuff ... also a bit stupid of me to lurk and search mesa-dev for mach64 DMA instead of dri-devel. I'll probably do my "homework" over the weekend. Just a question to make sure I am not completely mixed up: As it stands now, is drm_blit secure ? I mean a malicious client can still change the contents of the DMA buffer after submission to the drm in the case of a blit also, esp. the first MACH64_HOSTDATA_BLIT_OFFSET bytes. > It's been a while since I looked at the code in detail, but the problem at the > time was a limitation of the DRM buffer management infrastructure. As I recall, > there wasn't an easy way to create two sets of DMA buffers, one mapped to > userspace, and one which wasn't mapped. You may want to look into the mailing > list archives for more discussion on this. I think that this was the last > remaining issue in securing the driver. > > -Leif Thanks for your comments and your work on open source drivers, george. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-04 00:52:06
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-04-04 10:51 ------- What about the following approach: Do not map the DMA buffers to user-space. For dma_vertex, nothing changes. For dma_blit, the client submits a pointer to user-space memory. In the AGP case nothing changes since the default method is AGP texturing (in fact "local_textures" do not currently work with AGP, bug #6209). In the PCI case, the simple thing is copy_from_user to a private DMA buffer. If the performance regression is unacceptable, we can change the blit ioctl to submit w/h/pitch parameters and turn the memcpy currently done in user-space to copy_from_user. I presume that its easy to determine that the pointer actually points to memory owned by the process. Hopefully, we can reuse the current buffer management routines. If it is possible to do drmAddBufs without drmMapBufs, then very little changes are required (I saw a comment in drm_mapbufs that PCI buffers are actually mapped in drm_addbufs ...). Sorry if I am waisting your time with uninformed assumptions, george. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-10 01:35:09
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-04-10 11:34 ------- (In reply to comment #9) > What about the following approach: > > Do not map the DMA buffers to user-space. > > [...] > > Hopefully, we can reuse the current buffer management routines. If it is > possible to do drmAddBufs without drmMapBufs, then very little changes are > required (I saw a comment in drm_mapbufs that PCI buffers are actually mapped > in drm_addbufs ...). > I'am trying to tackle this by mapping the DMA buffers READ_ONLY. My current understanding is that PCI DMA buffers do actually get mapped in drm_mapbufs: drm_mapbufs -> do_mmap(..., 0) -> drm_mmap -> drm_mmap_dma If this is correct, can someone piggyback the following change at the description of drm_mapbufs? * Maps the AGP, SG or PCI buffer region with do_mmap(), and copies information * about each buffer into user space. For PCI buffers, it calls do_mmap() with * offset equal to 0, which drm_mmap interpretes as PCI buffers and calls * drm_mmap_dma(). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-12 00:44:55
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[agp mach64] Use DMA buffers|[mach64] Use private DMA |for mach64_dma_vertex |buffers (only) ------- Additional Comments From fuf...@ho... 2006-04-12 10:44 ------- Start over. The following patches implement the suggestion at comment 9. For AGP, they reserve the AGP memory to be used for DMA buffers as READ_ONLY. For PCI, they make drm_mmap_dma to return as soon as it is called to prevent mapping of the DMA buffers, this will have to be handled with a flag in drm_buf_desc_t. mach64_dma_blit was also converted to submit a pointer to user-space and subsituted the memcpy currently done in user-space with a copy_from_user (I presume this is secure or can be done so easily ...). Wrt performace for PCI, I see a ~12% speedup for some Mesa demos I tested. Also, the patches contain some other mainly consmetic changes: o factor out from mach64_dma_dispatch_vertex the code to reclaim an used buffer, it is now used by mach64_dma_dispatch_blit also o factor out from mach64_freelist_get the code to reclaim a completed buffer, this was to improve readability for me o move the memory reservation for the DMA ring in the PCI case to DDX, this unifies a couple of PCI/AGP code paths for ring memory in the drm Hope haven't managed to enter ingore lists with this bug report, any comments are greatly appreciated, george. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-12 00:46:09
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #4912 is|0 |1 obsolete| | Attachment #4913 is|0 |1 obsolete| | Attachment #5123 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-04-12 10:46 ------- Created an attachment (id=5269) --> (https://bugs.freedesktop.org/attachment.cgi?id=5269&action=view) private DMA buffers / mach64-ddx -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-12 00:46:35
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-04-12 10:46 ------- Created an attachment (id=5270) --> (https://bugs.freedesktop.org/attachment.cgi?id=5270&action=view) private DMA buffers / mach64-dri -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-12 00:47:16
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-04-12 10:47 ------- Created an attachment (id=5271) --> (https://bugs.freedesktop.org/attachment.cgi?id=5271&action=view) private DMA buffers / mach64-drm -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-12 20:24:29
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #5269 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-04-13 06:24 ------- Created an attachment (id=5283) --> (https://bugs.freedesktop.org/attachment.cgi?id=5283&action=view) private DMA buffers / mach64-ddx - try 1 Add DRM_PCI_READ_ONLY flag in drmBufDescFlags. This flag has also to be added at o libdrm/xf86drm.h o xorg/hw/xfree86/os-support/xf86drm.h -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-04-12 20:28:01
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #5271 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-04-13 06:27 ------- Created an attachment (id=5284) --> (https://bugs.freedesktop.org/attachment.cgi?id=5284&action=view) private DMA buffers / mach64-drm - try 1 Add DRM_PCI_READ_ONLY flag in drmBufDescFlags. When drm_mmap_dma sees this flag (set from drmAddBufs), it maps the PCI DMA buffers as read-only (I just copied the code from drm_mmap). An additional flag is needed, since PCI DMA buffers do not have an associated map. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-05-23 18:01:10
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-05-24 04:01 ------- Anybody willing to review this ? Needless to say, I am willing to do any changes or submit in pieces if this is in the right direction and I am not still confused. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-05-24 21:16:34
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fku...@at... 2006-05-25 07:16 ------- I'd like to review your patches. Someone needs to kick my b*tt so I get a card and try this stuff. I also got a private email from someone interested in mach64. I suggested to try your patches. Give me a few weekends and don't forget to remind me every once in a while. ;-) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-06-22 15:48:00
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 ------- Additional Comments From fuf...@ho... 2006-06-22 08:47 ------- > Give me a few weekends and don't forget > to remind me every once in a while. ;-) what are doing this weekend ? do you like reviewing drm patches ;-) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-06-22 19:51:19
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fx...@gm... changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dri- | |de...@li... AssignedTo|dri- |fx...@gm... |de...@li... | Status|NEW |ASSIGNED ------- Additional Comments From fx...@gm... 2006-06-22 12:51 ------- (In reply to comment #19) > > Give me a few weekends and don't forget > > to remind me every once in a while. ;-) > > what are doing this weekend ? do you like reviewing drm patches ;-) Yep. I haven't forgotten about it yet. I spent the last few evenings upgrading my home box to Dapper, so I have now modular Xorg by default. I also installed a PCI Mach64 with 4MB Ram. I'll get and build the relevant sources from GIT/CVS soon. I can't promise anything for this weekend though. I have to watch Soccer World Cup on Saturday (Germany against Sweden) ;-) and Sunday is booked for a company family event. Assigning to myself and adding dri-devel to the CC list to maintain visibility. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-07-16 14:01:12
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #5284 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-07-16 07:01 ------- Created an attachment (id=6234) --> (https://bugs.freedesktop.org/attachment.cgi?id=6234&action=view) private DMA buffers / mach64-drm - try 2 This is the same as previous version with the mach64 version major bumped. It is a patchset with different commits for the preparation code, the changes to the DRM core and lastly the backwards incompatible changes to the mach64 DRM. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-07-16 14:03:31
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #5283 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-07-16 07:02 ------- Created an attachment (id=6235) --> (https://bugs.freedesktop.org/attachment.cgi?id=6235&action=view) private DMA buffers / mach64-ddx - try 2 Require a new mach64 DRM, also free the PCI DMA ring memory. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-07-16 14:04:17
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #5270 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-07-16 07:03 ------- Created an attachment (id=6236) --> (https://bugs.freedesktop.org/attachment.cgi?id=6236&action=view) private DMA buffers / mach64-dri - try 1 Require new mach64 DRM. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-07-16 16:38:18
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=6242 fuf...@ho... changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #6235 is|0 |1 obsolete| | ------- Additional Comments From fuf...@ho... 2006-07-16 09:38 ------- Created an attachment (id=6241) --> (https://bugs.freedesktop.org/attachment.cgi?id=6241&action=view) private DMA buffers / mach64-ddx - try 3 stupid: check that PCI DMA ring was actually allocated before freeing. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |