linux-kernel - Re: [torture] BUG: unable to handle kernel NULL pointer dereference at (null)

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:	Thu, 18 Sep 2014 21:17:51 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Jet Chen <jet.chen@...el.com>, Su Tao <tao.su@...el.com>,
	Yuanhan Liu <yuanhan.liu@...el.com>, LKP <lkp@...org>,
	linux-kernel@...r.kernel.org
Subject: Re: [torture] BUG: unable to handle kernel NULL pointer dereference
 at (null)

Hi Paul,

> > > > plymouth-upstart-bridge: ply-event-loop.c:497: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed.
> > > > /etc/lsb-base-logging.sh: line 5:  2580 Aborted                 plymouth --ping > /dev/null 2>&1
> > > > /etc/lsb-base-logging.sh: line 5:  2585 Aborted                 plymouth --ping > /dev/null 2>&1
> > > > mount: proc has wrong device number or fs type proc not supported
> > > > /etc/lsb-base-logging.sh: line 5:  2601 Aborted                 plymouth --ping > /dev/null 2>&1
> > > > /etc/rc6.d/S40umountfs: line 20: /proc/mounts: No such file or directory
> > > > cat: /proc/1/maps: No such file or directory
> > > > cat: /proc/1/maps: No such file or directory
> > > > cat: /proc/1/maps: No such file or directory
> > > > cat: /proc/1/maps: No such file or directory
> > > > cat: /proc/1/maps: No such file or directory
> > > > cat: /proc/1/maps: No such file or directory
> > > > umount: /var/run: not mounted
> > > > umount: /var/lock: not mounted
> > > > umount: /dev/shm: not mounted
> > > > mount: / is busy
> > > >  * Will now restart
> 
> Are these expected behavior?

Yes, because it's randconfig boot tests, the user space may well
complain about random stuff and I'll ignore them all as long as it
will eventually call the shutdown command to finish the test in time.  :)

> So again, I can invoke this commit without losing much (sendkey
> alt-sysrq-z is after all my friend), but it is not clear to me that we
> have gotten to the root of this problem.

Sorry about that! If you see any debug tricks that I can try, or
information I can collect, please let me know.

Regards,
Fengguang
--
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/