linux-kernel - Re: [Bug #16306] 2.6.35-rc3 BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 cifs_show

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 9 Jul 2010 11:03:23 +1000
From:	Andrew Hendry <andrew.hendry@...il.com>
To:	Jeff Layton <jlayton@...hat.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>
Subject: Re: [Bug #16306] 2.6.35-rc3 BUG: unable to handle kernel NULL pointer 
	dereference at 0000000000000048 cifs_show_options

It might not be a regression, and so far i haven't been able to reproduce.
Its seems to be related to suspend/resume interface up/down and mount/unmount.
Also potentially with cifs waiting for a NAS to spinup to complete mount.

On Fri, Jul 9, 2010 at 10:49 AM, Jeff Layton <jlayton@...hat.com> wrote:
> On Fri,  9 Jul 2010 01:41:39 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
>
>> This message has been generated automatically as a part of a summary report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.34.  Please verify if it still should be listed and let the tracking team
>> know (either way).
>>
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=16306
>> Subject               : 2.6.35-rc3 BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 cifs_show_options
>> Submitter     : Andrew Hendry <andrew.hendry@...il.com>
>> Date          : 2010-06-26 10:46 (13 days old)
>> Message-ID    : <AANLkTilhTrEBYZd4HxeXQk8B6-yV8rCJ2C0jXsEREgIR@...l.gmail.com>
>> References    : http://marc.info/?l=linux-kernel&m=127754922110501&w=2
>> Handled-By    : Jeff Layton <jlayton@...hat.com>
>>
>>
>
> Not sure if this is a new bug or not...
>
> I don't think this is really a CIFS bug, per-se. It seems like the
> problem may be that the iterator for /proc/pid/mountinfo is not
> sufficiently protected against removal from the vfsmount list.
>
> Filesystems don't seem to be expected to do any locking in their
> show_options routines though so I'm guessing that something is borked
> in the generic vfs layer.
>
> Either that or this is some sort of generic mem corruption? I'm open to
> input from others that have a better grasp of this stuff at the VFS
> layer...
>
> --
> Jeff Layton <jlayton@...hat.com>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/