From: Alexander Holler <holler@ahsoftware.de>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Al Viro <viro@ZenIV.linux.org.uk>
Cc: Paul Moore <pmoore@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: weird and wrong directory entries
Date: Fri, 23 Jan 2015 04:30:20 +0100 [thread overview]
Message-ID: <54C1C04C.40205@ahsoftware.de> (raw)
In-Reply-To: <20150123020644.GA466@swordfish>
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.
Regards,
Alexander Holler
next prev parent reply other threads:[~2015-01-23 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 0:42 weird and wrong directory entries Sergey Senozhatsky
2015-01-23 1:30 ` Al Viro
2015-01-23 2:06 ` Sergey Senozhatsky
2015-01-23 3:30 ` Alexander Holler [this message]
2015-01-23 3:57 ` Sergey Senozhatsky
2015-01-23 5:53 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C1C04C.40205@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoore@redhat.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).