On (01/23/15 12:57), Sergey Senozhatsky wrote: > > Am 23.01.2015 um 03:06 schrieb Sergey Senozhatsky: > > > On (01/23/15 01:30), Al Viro wrote: > > >> On Fri, Jan 23, 2015 at 09:42:21AM +0900, Sergey Senozhatsky wrote: > > >>> Hello gents, > > >>> > > >>> I observe this sick behaviour for the past few days. (sorry, some lines are > > >>> over 80 symbols). all of the things above are happening during kernel compilation. > > >>> attached .config. > > >> > > >>> happens both on reiserfs and ext4, both on current linus's tree and linux-next. > > >>> no doubt, an attempt to rm -fr pkg/ kills /usr/, etc. > > >>> > > >> > > >>> I'm puzzled. any thoughts? > > >> > > >> Try to bisect, perhaps? > > >> > > > > There are some weird pieces in the kernel buildsysten which are > > generating Makefile content based on some filenames and might brake or > > confuse future builds. See e.g. https://lkml.org/lkml/2014/10/19/10. > > > > Maybe you've stumbled over a similiar thing. > > > > Hm, basically, I don't add any new files, especially with commas, etc., > just kernel.org vanilla and linux-next. > > > things like this: > > $ ll > ls: cannot access /ho: No such file or directory > total 12 > d????????? ? ? ? ? ? /ho > drwxr-xr-x 3 ss ss 4096 Jan 23 08:44 ethernet > -rw-r--r-- 1 ss ss 3195 Jan 23 08:44 mii.ko.gz > drwxr-xr-x 2 ss ss 4096 Jan 23 08:44 usb > > make me think that I'm facing a bit different kind of issues. > > gonna bisect for a while. marked Sept 19th tree as good. the issue is not I meant Jan 19th... apparently, it's january. good 12ba8571ab6b232f5facef6b1dd28c5ebc2b530a (just randomly picked up). -ss > 100% reproducible, and 1 `ok build' doesn't mean anything. let's see if > this will fly. > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
