smbd segfault during failed oplock break (Re: Problems with Samba 4 Beta 1 and a possible bug that was previously reported)
abartlet at samba.org
Fri Jun 29 02:54:12 MDT 2012
On Fri, 2012-06-29 at 02:33 -0600, Trever L. Adams wrote:
> On 06/29/2012 02:20 AM, Andrew Bartlett wrote:
> > I've retitled the bug to get the attention of those who work on the file
> > server, as this isn't a specifically AD related bug as far as I can see.
> > If you can get it all under valgrind, it may help working out the
> > details of the use-after-free().
> > Thanks!
> > Andrew Bartlett
> Thank you Andrew. Are there any special instructions for using valgrind
> with S4? Or can I just do like I would with any other program and just
> put valgrind before with --memcheck=full (I probably have that a bit off)?
Run with --trace-children=yes
> The use-after-free() is still happening it seems under load even with
> the off-line-files gone, so I think I should be able to duplicate it.
> (In fact it seems to be more related to the "destination unreachable" I
> mentioned an hour or so ago.)
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical