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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 5 Jul 2014 20:27:39 +0530 From: Sachin Kamat <spk.linux@...il.com> To: "J. Bruce Fields" <bfields@...ldses.org> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, open list <linux-kernel@...r.kernel.org> Subject: Re: linux-next: Tree for Jul 4 On Sat, Jul 5, 2014 at 6:18 AM, J. Bruce Fields <bfields@...ldses.org> wrote: > On Sat, Jul 05, 2014 at 01:10:58AM +1000, Stephen Rothwell wrote: >> Hi Sachin, >> >> On Fri, 4 Jul 2014 14:12:11 +0530 Sachin Kamat <spk.linux@...il.com> wrote: >> > >> > Was bisecting a kernel crash on Arndale octa board (Exynos5420). It >> > points to a merge >> > commit: >> > 40556a4c485d12d324f1ea196cc30f590e564237 is the first bad commit >> > ("Merge remote-tracking branch 'nfsd/nfsd-next'"). >> > >> > How do I proceed with this? >> >> I guess we get the owner of the tree (possibly) in question involved >> (cc'd). > > Looking at the total diffstat for that branch, it's almost all contained > in fs/nfsd with a little in include/linux/sunrpc/ and net/sunrpc. So > it's extremely unlikely that it would be causing a problem unless you're > actually testing nfsd. I found it surprising too as I do not use nfsd. I will try out the things suggested by Stephen and update. -- Regards, Sachin. -- 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/
Powered by blists - more mailing lists