Dear listmembers,
the latest smbfs.o module in 2.4.33 makes headache on sparc. The reason for this is the fact, that a new patch had been introduced into dir.c that is based on memchr().
Unfortunately memchr() is not defined in asm-sparcXX/string.h; therefore depmod fails for smbfs.o and smbfs.o remains unusable if i am right.
Any suggestions? I was thinking of replacing memchr () by memscan (), however, memscan () gives a different result, so could someone tell me whether replacing
/* Do not allow lookup of names with backslashes in */
error = -EINVAL;
if (memchr(dentry->d_name.name, '\\', dentry->d_name.len))
goto out;
by
/* Do not allow lookup of names with backslashes in */
error = -EINVAL;
if ( dentry->d_name.name == ((memscan(dentry->d_name.name, '\\', dentry->d_name.len))-dentry->d_name.len) )
goto out;
would be ok?
Thank you for helping out,
take care
Dieter Jurzitza
--
________________________________________________
HARMAN BECKER AUTOMOTIVE SYSTEMS
Dr.-Ing. Dieter Jurzitza
Manager Hardware Systems
System Development
Industriegebiet Ittersbach
Becker-Göring Str. 16
D-76307 Karlsbad / Germany
Phone: +49 (0)7248 71-1577
Fax: +49 (0)7248 71-1216
eMail: DJurzitza@xxxxxxxxxxxxxxxx
Internet: http://www.becker.de
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
