https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #8 from Michal Ruprich ---
Great, thanks Wayne.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change
https://bugzilla.samba.org/show_bug.cgi?id=11338
Wayne Davison changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #6 from Michal Ruprich ---
This has just freshly arrived yesterday. Same bug as before and as described
here.
https://bugzilla.redhat.com/show_bug.cgi?id=1683737
--
You are receiving this mail because:
You are the QA Contact for
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #5 from Michal Ruprich ---
Created attachment 14872
--> https://bugzilla.samba.org/attachment.cgi?id=14872=edit
Patch for the rwrite function
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #4 from Michal Ruprich ---
Hi,
we have encountered similar segfault a couple of years ago. As you can see here
in comment #2, the p *in shows that the input buffer's size and len are
unreasonably huge - len = 18446744073709532799,
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #3 from Ralph Corderoy ---
Hi Wayne,
I don't know if James's SEGV is the same root cause as Balveer's that
was two years earlier, but I'm seeing SEGV like James's. Both times, my
network connection
https://bugzilla.samba.org/show_bug.cgi?id=11338
--- Comment #2 from James Stevenson ---
I seem to see the same crash. Here is some additional details with symbols. It
seems to happen during network timeouts.
#0 0x7fcc2e167b05 in utf8_internal_loop (step=0x560710d73f90,
https://bugzilla.samba.org/show_bug.cgi?id=11338
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1