MySQL Bugs: #23718: MySQL crashes when --skip-name-resolve and adding user 'user'@'10.*'

Bug #23718	MySQL crashes when --skip-name-resolve and adding user 'user'@'10.*'
Submitted:	27 Oct 2006 13:40	Modified:	30 Nov 2006 12:31
Reporter:	Mikhail Petrov	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.15-standart	OS:	Linux (SLES 9 (x64))
Assigned to:		CPU Architecture:	Any
Tags:	grant, server crash, skip-name-resolve

Description:
If server started with --skip-name-resolve, "grant" with a hostname restriction such as @`10.*`, server crashes after "flush privileges" and can't start while switch `skip-name-resolve` exists.

In mysql error-log I have following:

mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=1048576
read_buffer_size=8384512
max_used_connections=0
max_connections=128
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2097663 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

I have enough RAM, more than 2097663K, so problem imho can't be concerned with RAM.

How to repeat:
Start server with --skip-name-resolve.
Do queries:
grant select on test.* to 'foe'@'10.*' identified by 'password';
flush privileges;

Then server crashes immediately.

I test it with 4.1.21 and 4.1.15 on Pentium D (x86, Gentoo Linux) and 4.1.15 on Xeon 2.80GHz (x86, SLES 9.1 i586) - there are no crashes.
So crash happens only with 4.1.10 on x64 (AMD Opteron 275,280).

Thank you for a problem report. Sorry, but nobody will fix this in 4.1.10 (it may be already fixed!). Please, try to repeat with the latest version, 4.1.21, and inform about any similar crash (on x64 or any platfrom).

Sorry it was a typo - crash happens in _4.1.15_ on x64.
In 4.1.21 on x86 there is no crash.
I'll try to see 4.1.21 on x64 in next 3-4 days.

Please, do, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Do you have any results with 4.1.21 on x64? You may also try 4.1.22, already released.

Oh, great!
I'll try 4.1.22 on new server today or tomorrow and give you results.

Sorry, in 4.1.22 on AMD64 there is no such bug.
May be it's a duplicate of http://bugs.mysql.com/bug.php?id=15598 ?

I am not sure it is related to bug #15598 (that was fixed in 4.1.17 already). Anyway, as this bug is not repeatable any more, we can close this report.