From: Michal Marek <mmarek@suse.cz>
To: Hiromu Yakura <hiromu1996@gmail.com>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
zippel@linux-m68k.org
Subject: Re: [PATCH] Kconfig: add warning about permission of config file
Date: Tue, 24 May 2011 15:23:28 +0200 [thread overview]
Message-ID: <4DDBB150.2090602@suse.cz> (raw)
In-Reply-To: <1306242400.7501.10.camel@hiromu-MacBook>
On 24.5.2011 15:06, Hiromu Yakura wrote:
> Hello,
> thanks for replying.
>
> On Mon, May 23, 2011 at 13:58, Arnaud Lacombe<lacombar@gmail.com> wrote:
>> Do you have a precise way to reproduce this, in particular which
>> target is involved ? I tried to `chmod 555' the kernel root directory,
>> re-ran `conf' (through the `defconfig' target) and `mconf' (manually
>> for this one, as check-lxdialog.sh fails when invoked though make).
>> The former failed with:
>>
>> *** Error during writing of the configuration.
>>
>> gmake[1]: *** [defconfig] Error 1
>> gmake: *** [defconfig] Error 2
> In my environment, this patch is working properly.
> The output is as follows:
>
> hiromu@hiromu-MacBook:/usr/src/linux-2.6$ ls -ld .
> dr-xr-sr-x 25 hiromu hiromu 4096 May 24 21:41 .
> hiromu@hiromu-MacBook:/usr/src/linux-2.6$ make defconfig
> *** Default configuration is based on 'x86_64_defconfig'
> *** Permission denied to write the configuration.
Arnaud's point is that your patch should not be necessary at all,
because kconfig already checks the return value of the fopen() call in
conf_write() and prints the above message if it fails. So do you have a
testcase where make <...>config without your patch returns without
error, but the configuration is not written?
Michal
next prev parent reply other threads:[~2011-05-24 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1306167401.18840.8.camel@hiromu-MacBook>
[not found] ` <BANLkTikhFdd_PRzCg3w9HD1TO=cmdmm6_A@mail.gmail.com>
2011-05-24 13:06 ` [PATCH] Kconfig: add warning about permission of config file Hiromu Yakura
2011-05-24 13:23 ` Michal Marek [this message]
2011-05-24 14:26 ` Hiromu Yakura
2011-05-24 15:01 ` Michal Marek
2011-05-24 15:50 ` Arnaud Lacombe
2011-05-24 16:49 ` Sam Ravnborg
2011-05-24 17:38 ` Hiromu Yakura
2011-05-24 17:59 ` Arnaud Lacombe
2011-05-24 20:46 ` Hiromu Yakura
2011-05-24 21:49 ` Arnaud Lacombe
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=4DDBB150.2090602@suse.cz \
--to=mmarek@suse.cz \
--cc=hiromu1996@gmail.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/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