Bug 762042 (GLUSTER-310) - While trying to create a file on replicate with write behind set-up, client crashes.
Summary: While trying to create a file on replicate with write behind set-up, client c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-310
Product: GlusterFS
Classification: Community
Component: write-behind
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-12 09:54 UTC by Vinayak Hegde
Modified: 2009-10-27 18:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Vinayak Hegde 2009-10-12 09:54:58 UTC
The core generated is:

wb_process_queue (frame=0x0, file=0x0, flush_all=0 '\0')
    at write-behind.c:1728
#1  0xb80d2cfa in wb_setattr_cbk (frame=Cannot access memory at address 0x8
) at write-behind.c:1074
#2  0xb7687246 in afr_setattr_unwind (frame=Cannot access memory at address 0x8
) at afr-inode-write.c:751
#3  0xb7688c98 in afr_setattr_wind_cbk (frame=Cannot access memory at address 0x8
) at afr-inode-write.c:812
#4  0xb76bd0c1 in client_setattr_cbk (frame=Cannot access memory at address 0x8
) at client-protocol.c:4703
#5  0xb76a9b25 in protocol_client_interpret (this=Cannot access memory at address 0x8
)   
    at client-protocol.c:5915
#6  0xb76a9ccf in protocol_client_pollin (this=Cannot access memory at address 0x8
) at client-protocol.c:6209
#7  0xb76b9c42 in notify (this=Cannot access memory at address 0x8
) at client-protocol.c:6328
#8  0xb809bd9f in xlator_notify (xl=Cannot access memory at address 0x8
#9  0xb6e48aed in socket_event_poll_in (this=0x0) at socket.c:713
#10 0xb6e48bab in socket_event_handler (fd=Cannot access memory at address 0x8
) at socket.c:813
#11 0x00000000 in ?? ()
(gdb) bt
#0  wb_process_queue (frame=0x0, file=0x0, flush_all=0 '\0')
    at write-behind.c:1728
#1  0xb80d2cfa in wb_setattr_cbk (frame=Cannot access memory at address 0x8
) at write-behind.c:1074
#2  0xb7687246 in afr_setattr_unwind (frame=Cannot access memory at address 0x8
) at afr-inode-write.c:751
#3  0xb7688c98 in afr_setattr_wind_cbk (frame=Cannot access memory at address 0x8
) at afr-inode-write.c:812
#4  0xb76bd0c1 in client_setattr_cbk (frame=Cannot access memory at address 0x8
) at client-protocol.c:4703
#5  0xb76a9b25 in protocol_client_interpret (this=Cannot access memory at address 0x8
)
    at client-protocol.c:5915
#6  0xb76a9ccf in protocol_client_pollin (this=Cannot access memory at address 0x8
) at client-protocol.c:6209
#7  0xb76b9c42 in notify (this=Cannot access memory at address 0x8
) at client-protocol.c:6328
#8  0xb809bd9f in xlator_notify (xl=Cannot access memory at address 0x8
) at xlator.c:929
#9  0xb6e48aed in socket_event_poll_in (this=0x0) at socket.c:713
#10 0xb6e48bab in socket_event_handler (fd=Cannot access memory at address 0x8
) at socket.c:813
#11 0x00000000 in ?? ()

Comment 1 Anand Avati 2009-10-12 14:18:42 UTC
PATCH: http://patches.gluster.com/patch/1864 in master (performance/write-behind: file is referenced, without checking for NULL)

Comment 2 Anand Avati 2009-10-13 08:53:17 UTC
PATCH: http://patches.gluster.com/patch/1864 in master (performance/write-behind: file is referenced, without checking for NULL)

Comment 3 Anand Avati 2009-10-13 08:53:21 UTC
PATCH: http://patches.gluster.com/patch/1868 in master (performance/write-behind: In wb_setattr file is used before getting fd context)

Comment 4 Anand Avati 2009-10-15 13:30:55 UTC
PATCH: http://patches.gluster.com/patch/1904 in master (performance/write-behind: In wb_setattr, inode is checked twice)

Comment 5 Anand Avati 2009-10-16 07:18:07 UTC
PATCH: http://patches.gluster.com/patch/1922 in master (performance/write-behind: initialize frame->local before goto out label)


Note You need to log in before you can comment on or make changes to this bug.