ipc_addid() initializes kern_ipc_perm.id after having called
ipc_idr_alloc().
Thus a parallel semop() or msgrcv() that uses ipc_obtain_object_idr()
may see an uninitialized value.
The patch moves all accesses to kern_ipc_perm.id under the spin_lock().
The issues is related to the finding of
ipc_addid() initializes kern_ipc_perm.id after having called
ipc_idr_alloc().
Thus a parallel semop() or msgrcv() that uses ipc_obtain_object_idr()
may see an uninitialized value.
The patch moves all accesses to kern_ipc_perm.id under the spin_lock().
The issues is related to the finding of
Hi,
Dmitry convinced me that I should properly review the initialization
of new ipc objects, and I found another issue.
The series corrects 3 issues with ipc_addid(), and also renames
two functions and corrects a wrong comment.
0001-ipc-reorganize-initialization-of-kern_ipc_perm.id:
Hi,
Dmitry convinced me that I should properly review the initialization
of new ipc objects, and I found another issue.
The series corrects 3 issues with ipc_addid(), and also renames
two functions and corrects a wrong comment.
0001-ipc-reorganize-initialization-of-kern_ipc_perm.id:
* Faiz Abbas [180704 13:37]:
> After taking a second look at this thread, I don't see anything big to
> be modified.
>
> We both agree that "reset status bit in sysconfig register" is the quirk
> case which can be added once such an IP is discovered in ti-sysc.
Yes agreed.
> All I need to
* Faiz Abbas [180704 13:37]:
> After taking a second look at this thread, I don't see anything big to
> be modified.
>
> We both agree that "reset status bit in sysconfig register" is the quirk
> case which can be added once such an IP is discovered in ti-sysc.
Yes agreed.
> All I need to
On Wed, 04 Jul 2018, Enric Balletbo Serra wrote:
> Missatge de Dmitry Torokhov del dia dc., 4
> de jul. 2018 a les 17:10:
> >
> > Hi Enric,
> >
> > On Tue, Jun 26, 2018 at 11:06:33AM +0200, Enric Balletbo Serra wrote:
> > > Hi Matti,
> > >
> > > Thanks for the patch, a few comments below, some
On Wed, 04 Jul 2018, Enric Balletbo Serra wrote:
> Missatge de Dmitry Torokhov del dia dc., 4
> de jul. 2018 a les 17:10:
> >
> > Hi Enric,
> >
> > On Tue, Jun 26, 2018 at 11:06:33AM +0200, Enric Balletbo Serra wrote:
> > > Hi Matti,
> > >
> > > Thanks for the patch, a few comments below, some
Hi there,
The problem is still in kernel-v4.18-rc3.
Panic was caused by command:
# ./read_all -d /sys -q -r 10
Or, you can try the full steps to reproduce:
# git clone https://github.com/linux-test-project/ltp/
# cd ltp
# ./build.sh
# cd ../ltp-install
# ./runltp -s read_all_sys
dmesg
On Thu, Jul 5, 2018 at 4:37 AM, Linus Torvalds
wrote:
> On Wed, Jul 4, 2018 at 4:34 PM Al Viro wrote:
>>
>> I don't hate that patch, but there are immediate followup questions - e.g.
>> how sensitive is relative position of i_lock/i_hash/i_sb? Those are *not*
>> close to each other. E.g. what
On Wed, 04 Jul 2018, Janusz Krzysztofik wrote:
> On Tuesday, July 3, 2018 7:31:41 PM CEST Boris Brezillon wrote:
> > Hi Janusz,
> >
> > On Tue, 3 Jul 2018 19:26:35 +0200
> >
> > Janusz Krzysztofik wrote:
> > > Avoid replication of error code conversion in non-DT GPIO consumers'
> > > code by
Hi there,
The problem is still in kernel-v4.18-rc3.
Panic was caused by command:
# ./read_all -d /sys -q -r 10
Or, you can try the full steps to reproduce:
# git clone https://github.com/linux-test-project/ltp/
# cd ltp
# ./build.sh
# cd ../ltp-install
# ./runltp -s read_all_sys
dmesg
On Thu, Jul 5, 2018 at 4:37 AM, Linus Torvalds
wrote:
> On Wed, Jul 4, 2018 at 4:34 PM Al Viro wrote:
>>
>> I don't hate that patch, but there are immediate followup questions - e.g.
>> how sensitive is relative position of i_lock/i_hash/i_sb? Those are *not*
>> close to each other. E.g. what
On Wed, 04 Jul 2018, Janusz Krzysztofik wrote:
> On Tuesday, July 3, 2018 7:31:41 PM CEST Boris Brezillon wrote:
> > Hi Janusz,
> >
> > On Tue, 3 Jul 2018 19:26:35 +0200
> >
> > Janusz Krzysztofik wrote:
> > > Avoid replication of error code conversion in non-DT GPIO consumers'
> > > code by
Sorry for the misunderstanding. I mean I will improve the check loop in patch
v2.
I just submitted patch v2. Thanks in advance for your kind review.
Thanks,
Bin
On 05/07/2018, 1:30 PM, "Thomas Gleixner" wrote:
Sorry, I don't see in which way your patch would improve the check loop.
Sorry for the misunderstanding. I mean I will improve the check loop in patch
v2.
I just submitted patch v2. Thanks in advance for your kind review.
Thanks,
Bin
On 05/07/2018, 1:30 PM, "Thomas Gleixner" wrote:
Sorry, I don't see in which way your patch would improve the check loop.
Hi.
2018-07-02 23:47 GMT+09:00 Christoph Hellwig :
> Hi Masahiro,
>
> what do you think about the series below, which moves the includes
> of all the architecture independ Kconfig files to the top-level
> Kconfig instead of duplicating the includes in all architectures?
>
> Note that this only
Hi.
2018-07-02 23:47 GMT+09:00 Christoph Hellwig :
> Hi Masahiro,
>
> what do you think about the series below, which moves the includes
> of all the architecture independ Kconfig files to the top-level
> Kconfig instead of duplicating the includes in all architectures?
>
> Note that this only
When changing a 4K page attr inside 1G/2M large page range,
__change_page_attr() will call try_preserve_large_page() to decide
to split the big page or not. And try_preserve_large_page() will
call static_protections() to check all 4K pages inside the large page
range one by one. The check loop is
When changing a 4K page attr inside 1G/2M large page range,
__change_page_attr() will call try_preserve_large_page() to decide
to split the big page or not. And try_preserve_large_page() will
call static_protections() to check all 4K pages inside the large page
range one by one. The check loop is
2018-07-02 23:47 GMT+09:00 Christoph Hellwig :
> Move the source of lib/Kconfig.debug and arch/$(ARCH)/Kconfig.debug to
> the top-level Kconfig. For two architectures that means moving their
> arch-specific symbols in that menu into a new arch Kconfig.debug file,
> and for a few more creating a
2018-07-02 23:47 GMT+09:00 Christoph Hellwig :
> Move the source of lib/Kconfig.debug and arch/$(ARCH)/Kconfig.debug to
> the top-level Kconfig. For two architectures that means moving their
> arch-specific symbols in that menu into a new arch Kconfig.debug file,
> and for a few more creating a
2018-07-04 1:11 GMT+09:00 Randy Dunlap :
> On 07/03/18 06:36, Christoph Hellwig wrote:
>> On Mon, Jul 02, 2018 at 01:08:16PM -0700, Randy Dunlap wrote:
I would prefer to have init/Kconfig before arch/$(SRCARCH)/Kconfig.
>>>
>>> Ugh, that won't get this set correctly on x86_64:
>>>
2018-07-04 1:11 GMT+09:00 Randy Dunlap :
> On 07/03/18 06:36, Christoph Hellwig wrote:
>> On Mon, Jul 02, 2018 at 01:08:16PM -0700, Randy Dunlap wrote:
I would prefer to have init/Kconfig before arch/$(SRCARCH)/Kconfig.
>>>
>>> Ugh, that won't get this set correctly on x86_64:
>>>
On Wed, Jul 04, 2018 at 11:04:37PM +0200, Arnd Bergmann wrote:
> Right, I do understand what it's used for, my point was that you
> don't really need a separate system call number for it, just redirect
> the entry point using the same trick that nds32 has in
> arch/nds32/kernel/syscall_table.c:
>
On Wed, Jul 04, 2018 at 11:04:37PM +0200, Arnd Bergmann wrote:
> Right, I do understand what it's used for, my point was that you
> don't really need a separate system call number for it, just redirect
> the entry point using the same trick that nds32 has in
> arch/nds32/kernel/syscall_table.c:
>
On Wed, Jul 4, 2018 at 9:31 PM, Raslan, KarimAllah wrote:
> Dmitry,
>
> Can you share the host kernel version?
>
> I can not reproduce any of these crash signatures and I think it's
> really a nested virtualization bug. So I will need the exact host
> kernel version as well.
>
> I am currently
On Wed, Jul 4, 2018 at 9:31 PM, Raslan, KarimAllah wrote:
> Dmitry,
>
> Can you share the host kernel version?
>
> I can not reproduce any of these crash signatures and I think it's
> really a nested virtualization bug. So I will need the exact host
> kernel version as well.
>
> I am currently
On Thu, 5 Jul 2018, Yang, Bin wrote:
Please do not top post.
> This is what my new patch tries to improve.
> On 04/07/2018, 10:02 PM, "Thomas Gleixner" wrote:
>
> The check loop itself is stupid as well. Instead of looping in 4K steps
> the thing can be rewritten to check for
On Thu, 5 Jul 2018, Yang, Bin wrote:
Please do not top post.
> This is what my new patch tries to improve.
> On 04/07/2018, 10:02 PM, "Thomas Gleixner" wrote:
>
> The check loop itself is stupid as well. Instead of looping in 4K steps
> the thing can be rewritten to check for
Hello,
On Wed, Jul 04, 2018 at 09:13:42PM +0200, Janusz Krzysztofik wrote:
> On Tuesday, July 3, 2018 7:31:41 PM CEST Boris Brezillon wrote:
> > Hi Janusz,
> >
> > On Tue, 3 Jul 2018 19:26:35 +0200
> >
> > Janusz Krzysztofik wrote:
> > > Avoid replication of error code conversion in non-DT
Hello,
On Wed, Jul 04, 2018 at 09:13:42PM +0200, Janusz Krzysztofik wrote:
> On Tuesday, July 3, 2018 7:31:41 PM CEST Boris Brezillon wrote:
> > Hi Janusz,
> >
> > On Tue, 3 Jul 2018 19:26:35 +0200
> >
> > Janusz Krzysztofik wrote:
> > > Avoid replication of error code conversion in non-DT
This patch remove all following fall through warnings by
adding /* fall through */ markers.
Note that we cannot add "__attribute__ ((fallthrough));" due to it is GCC7 only
arch/arm/boot/compressed/../../../../lib/zlib_inflate/inflate.c:384:25:
warning: this statement may fall through
arm, arm64, mips, parisc, sh, x86 architectures use the
same version of hugetlb_free_pgd_range, so move this generic
implementation into asm-generic/hugetlb.h.
Signed-off-by: Alexandre Ghiti
---
arch/arm/include/asm/hugetlb.h | 12 ++--
arch/arm64/include/asm/hugetlb.h | 10
This patch remove all following fall through warnings by
adding /* fall through */ markers.
Note that we cannot add "__attribute__ ((fallthrough));" due to it is GCC7 only
arch/arm/boot/compressed/../../../../lib/zlib_inflate/inflate.c:384:25:
warning: this statement may fall through
arm, arm64, mips, parisc, sh, x86 architectures use the
same version of hugetlb_free_pgd_range, so move this generic
implementation into asm-generic/hugetlb.h.
Signed-off-by: Alexandre Ghiti
---
arch/arm/include/asm/hugetlb.h | 12 ++--
arch/arm64/include/asm/hugetlb.h | 10
Hi Matthew,
After merging the ida tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
lib/test_xarray.c: In function 'xa_alloc_value':
lib/test_xarray.c:39:16: error: implicit declaration of function 'xa_alloc';
did you mean 'ida_alloc'?
Hi Matthew,
After merging the ida tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
lib/test_xarray.c: In function 'xa_alloc_value':
lib/test_xarray.c:39:16: error: implicit declaration of function 'xa_alloc';
did you mean 'ida_alloc'?
Allow cooling devices sharing same trip point with same contribution
value to share the cooling map as well. Otherwise the same information
will be duplicated for each device sharing the trip point.
Signed-off-by: Viresh Kumar
---
Documentation/devicetree/bindings/thermal/thermal.txt | 11
Hi,
This is an attempt to fix the broken or partially defined DT bindings
for cooling-maps. We should list every device that participates in
cooling down at a certain trip point, instead of just the first in the
list as that depends on certain ordering of events to work properly.
The first patch
Allow cooling devices sharing same trip point with same contribution
value to share the cooling map as well. Otherwise the same information
will be duplicated for each device sharing the trip point.
Signed-off-by: Viresh Kumar
---
Documentation/devicetree/bindings/thermal/thermal.txt | 11
Hi,
This is an attempt to fix the broken or partially defined DT bindings
for cooling-maps. We should list every device that participates in
cooling down at a certain trip point, instead of just the first in the
list as that depends on certain ordering of events to work properly.
The first patch
Each CPU can (and does) participate in cooling down the system but the
DT only captures the CPU0 in the cooling maps. Things work by chance as
under normal circumstances its the CPU0 which is used by the operating
systems to probe the cooling devices. But as soon as that ordering
changes and any
Each CPU can (and does) participate in cooling down the system but the
DT only captures the CPU0 in the cooling maps. Things work by chance as
under normal circumstances its the CPU0 which is used by the operating
systems to probe the cooling devices. But as soon as that ordering
changes and any
On Wed, Jul 04, 2018 at 04:35:43PM +0200, Thomas Gleixner wrote:
> On Wed, 4 Jul 2018, Guo Ren wrote:
> > On Tue, Jul 03, 2018 at 11:39:05AM +0200, Thomas Gleixner wrote:
> > > > +static inline u64 get_ccvr(void)
> > > > +{
> > > > + u32 lo, hi, t;
> > > > +
> > > > + do {
> > > > +
On Wed, Jul 04, 2018 at 04:35:43PM +0200, Thomas Gleixner wrote:
> On Wed, 4 Jul 2018, Guo Ren wrote:
> > On Tue, Jul 03, 2018 at 11:39:05AM +0200, Thomas Gleixner wrote:
> > > > +static inline u64 get_ccvr(void)
> > > > +{
> > > > + u32 lo, hi, t;
> > > > +
> > > > + do {
> > > > +
Hi Stephen,
On 05-07-18, 12:47, Stephen Rothwell wrote:
> On Wed, 4 Jul 2018 09:50:17 +0530 Vinod wrote:
> > On 04-07-18, 13:30, Stephen Rothwell wrote:
> > >
> > > After merging the slave-dma tree, today's linux-next build (x86_64
> > > allmodconfig) produced this warning:
> > >
> > >
Hi Stephen,
On 05-07-18, 12:47, Stephen Rothwell wrote:
> On Wed, 4 Jul 2018 09:50:17 +0530 Vinod wrote:
> > On 04-07-18, 13:30, Stephen Rothwell wrote:
> > >
> > > After merging the slave-dma tree, today's linux-next build (x86_64
> > > allmodconfig) produced this warning:
> > >
> > >
The previous documentation was wrongly stating about the order
of magnitude of CONVERT_V result files contents (vad, vdd).
This commit is correcting this.
Reported-by: Adam Stolarczyk
Signed-off-by: Mariusz Bialonczyk
---
Resending as V2 because it was malformed by mail mail app recently.
I
The previous documentation was wrongly stating about the order
of magnitude of CONVERT_V result files contents (vad, vdd).
This commit is correcting this.
Reported-by: Adam Stolarczyk
Signed-off-by: Mariusz Bialonczyk
---
Resending as V2 because it was malformed by mail mail app recently.
I
Hello,
syzbot found the following crash on:
HEAD commit:2bdea157b999 Merge branch 'sctp-fully-support-for-dscp-and..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15438ad040
kernel config: https://syzkaller.appspot.com/x/.config?x=f62553dc846b0692
Hello,
syzbot found the following crash on:
HEAD commit:2bdea157b999 Merge branch 'sctp-fully-support-for-dscp-and..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15438ad040
kernel config: https://syzkaller.appspot.com/x/.config?x=f62553dc846b0692
Hello,
syzbot found the following crash on:
HEAD commit:2bdea157b999 Merge branch 'sctp-fully-support-for-dscp-and..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17d35aa440
kernel config: https://syzkaller.appspot.com/x/.config?x=f62553dc846b0692
Hello,
syzbot found the following crash on:
HEAD commit:2bdea157b999 Merge branch 'sctp-fully-support-for-dscp-and..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17d35aa440
kernel config: https://syzkaller.appspot.com/x/.config?x=f62553dc846b0692
Hi Willy,
On Wed, 4 Jul 2018 15:54:31 -0700 Matthew Wilcox wrote:
>
> I have some additional patches for the IDA that I'd like to
> send to Linus as a separate pull request. Unfortunately, they conflict with
> the XArray patches, so I've done them as a separate branch in the same tree:
>
>
Hi Willy,
On Wed, 4 Jul 2018 15:54:31 -0700 Matthew Wilcox wrote:
>
> I have some additional patches for the IDA that I'd like to
> send to Linus as a separate pull request. Unfortunately, they conflict with
> the XArray patches, so I've done them as a separate branch in the same tree:
>
>
Hi all,
After merging the ida tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/linux/kernel.h:14:0,
from include/asm-generic/bug.h:18,
from arch/powerpc/include/asm/bug.h:128,
from
Hi all,
After merging the ida tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/linux/kernel.h:14:0,
from include/asm-generic/bug.h:18,
from arch/powerpc/include/asm/bug.h:128,
from
On 7/4/2018 10:43 PM, Jarkko Sakkinen wrote:
On Wed, Jul 04, 2018 at 02:33:40PM +0530, Shirish S wrote:
During system shutdown,
tpm_class_shutdown() when called with TPM_CHIP_FLAG_TPM2
flag set, makes chip->ops NULL.
However tpm_chip_unregister() called later in shutdown
sequence tries to
On 7/4/2018 10:43 PM, Jarkko Sakkinen wrote:
On Wed, Jul 04, 2018 at 02:33:40PM +0530, Shirish S wrote:
During system shutdown,
tpm_class_shutdown() when called with TPM_CHIP_FLAG_TPM2
flag set, makes chip->ops NULL.
However tpm_chip_unregister() called later in shutdown
sequence tries to
From: Ulf Magnusson
.PHONY is a target, not a variable.
Signed-off-by: Ulf Magnusson
Signed-off-by: Masahiro Yamada
---
Ulf sent this a long time ago.
https://patchwork.kernel.org/patch/7111711/
Unfortunately, it was lost for some reason.
I am resending to apply it if Ulf does not mind it.
From: Ulf Magnusson
.PHONY is a target, not a variable.
Signed-off-by: Ulf Magnusson
Signed-off-by: Masahiro Yamada
---
Ulf sent this a long time ago.
https://patchwork.kernel.org/patch/7111711/
Unfortunately, it was lost for some reason.
I am resending to apply it if Ulf does not mind it.
The comment is the same as in the top-level Makefile.
Also, the comments contain typos:
- the .PHONY variable -> the PHONY variable
- se we can ...-> so we can ...
Instead of fixing the typos, just remove the duplicated comments.
Signed-off-by: Masahiro Yamada
---
The comment is the same as in the top-level Makefile.
Also, the comments contain typos:
- the .PHONY variable -> the PHONY variable
- se we can ...-> so we can ...
Instead of fixing the typos, just remove the duplicated comments.
Signed-off-by: Masahiro Yamada
---
On Wed, Jul 04, 2018 at 07:05:05PM +0200, Daniel Lezcano wrote:
> > create mode 100644 drivers/clocksource/timer-csky-v1.c
> > create mode 100644 drivers/clocksource/timer-nationalchip.c
>
> Provide two separates patches, one for each timer.
Ok.
> > +obj-$(CONFIG_CSKY) +=
On Wed, Jul 04, 2018 at 07:05:05PM +0200, Daniel Lezcano wrote:
> > create mode 100644 drivers/clocksource/timer-csky-v1.c
> > create mode 100644 drivers/clocksource/timer-nationalchip.c
>
> Provide two separates patches, one for each timer.
Ok.
> > +obj-$(CONFIG_CSKY) +=
Hi
> From: Andrew Gabbasov
>
> To comply with the style of all kernel messages, add newline
> to the end of every message.
>
> Fixes: 70fb10529f61 ("ASoC: rsnd: add MIX (Mixer) support")
> Signed-off-by: Andrew Gabbasov
> Signed-off-by: Jiada Wang
> ---
Acked-by: Kuninori Morimoto
Best
Hi
> From: Andrew Gabbasov
>
> To comply with the style of all kernel messages, add newline
> to the end of every message.
>
> Fixes: 70fb10529f61 ("ASoC: rsnd: add MIX (Mixer) support")
> Signed-off-by: Andrew Gabbasov
> Signed-off-by: Jiada Wang
> ---
Acked-by: Kuninori Morimoto
Best
When using ACPI node, binding clock devices are
not available as device tree, So clock-frequency
property given in _DSD object of ACPI device is
used to calculate Watchdog rate.
Signed-off-by: Srinath Mannam
---
drivers/watchdog/sp805_wdt.c | 29 -
1 file changed, 24
When using ACPI node, binding clock devices are
not available as device tree, So clock-frequency
property given in _DSD object of ACPI device is
used to calculate Watchdog rate.
Signed-off-by: Srinath Mannam
---
drivers/watchdog/sp805_wdt.c | 29 -
1 file changed, 24
HI Neil
On 07/04/18 22:57, Neil Armstrong wrote:
> Hi Yixun,
>
> On 05/07/2018 00:45, Yixun Lan wrote:
>> This patch series try to add pinctrl driver support for
>> the Meson-G12A SoC.
>
> Thanks for submitting these patches.
>
> Can you explicit this patchset with more details on the G12A SoC
> -Original Message-
> From: Stefan Agner [mailto:ste...@agner.ch]
> Sent: Thursday, June 28, 2018 4:13 PM
> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
> Cc: Fabio Estevam ; Bough Chen
> ; A.s. Dong ;
> mich...@amarulasolutions.com; rmk+ker...@armlinux.org.uk; linux-
>
> -Original Message-
> From: Stefan Agner [mailto:ste...@agner.ch]
> Sent: Thursday, June 28, 2018 4:13 PM
> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
> Cc: Fabio Estevam ; Bough Chen
> ; A.s. Dong ;
> mich...@amarulasolutions.com; rmk+ker...@armlinux.org.uk; linux-
>
HI Neil
On 07/04/18 22:57, Neil Armstrong wrote:
> Hi Yixun,
>
> On 05/07/2018 00:45, Yixun Lan wrote:
>> This patch series try to add pinctrl driver support for
>> the Meson-G12A SoC.
>
> Thanks for submitting these patches.
>
> Can you explicit this patchset with more details on the G12A SoC
The comment line for addtree says "skip if -I has no parameter".
What it actually does is "drop if -I has no parameter". For example,
if you have the compiler flag '-I foo' (a space between), it will be
converted to 'foo'. This completely changes the meaning.
What we want is, "do nothing" for
The comment line for addtree says "skip if -I has no parameter".
What it actually does is "drop if -I has no parameter". For example,
if you have the compiler flag '-I foo' (a space between), it will be
converted to 'foo'. This completely changes the meaning.
What we want is, "do nothing" for
As you see in mconf.c and nconf.c, conf_message_callback() hooks are
likely to end up with the boilerplate of vsnprintf(). Process the
string format before calling conf_message_callback() so that it
receives a simple string.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/confdata.c | 17
From: Randy Dunlap
Add usage info for the Kbuild environment variable KBUILD_KCONFIG.
Signed-off-by: Randy Dunlap
---
Documentation/kbuild/kbuild.txt |5 +
1 file changed, 5 insertions(+)
--- lnx-418-rc3.orig/Documentation/kbuild/kbuild.txt
+++
From: Randy Dunlap
Add usage info for the Kbuild environment variable KBUILD_KCONFIG.
Signed-off-by: Randy Dunlap
---
Documentation/kbuild/kbuild.txt |5 +
1 file changed, 5 insertions(+)
--- lnx-418-rc3.orig/Documentation/kbuild/kbuild.txt
+++
As you see in mconf.c and nconf.c, conf_message_callback() hooks are
likely to end up with the boilerplate of vsnprintf(). Process the
string format before calling conf_message_callback() so that it
receives a simple string.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/confdata.c | 17
' before string constant
MODULE_LICENSE("GPL v2");
^~~~
presumable a missing include of module.h ...
I have gone back to the slave-dma tree from next-20180704 for today.
--
Cheers,
Stephen Rothwell
pgpfIhizur9j_.pgp
Description: OpenPGP digital signature
' before string constant
MODULE_LICENSE("GPL v2");
^~~~
presumable a missing include of module.h ...
I have gone back to the slave-dma tree from next-20180704 for today.
--
Cheers,
Stephen Rothwell
pgpfIhizur9j_.pgp
Description: OpenPGP digital signature
Split out helpers:
is_file() - check if the given path exists and it is a regular file
is_dir() - check if the given path exists and it is a directory
mkdir_p() - create the parent directories of the given path
These helpers will be reused in later commits.
Signed-off-by: Masahiro Yamada
---
The main motivation of this patch series is to suppress the syncconfig
during running installation targets.
V1 consisted of only two patches:
https://patchwork.kernel.org/patch/10468105/
https://patchwork.kernel.org/patch/10468103/
I noticed that installation targets would continue running
Split out helpers:
is_file() - check if the given path exists and it is a regular file
is_dir() - check if the given path exists and it is a directory
mkdir_p() - create the parent directories of the given path
These helpers will be reused in later commits.
Signed-off-by: Masahiro Yamada
---
The main motivation of this patch series is to suppress the syncconfig
during running installation targets.
V1 consisted of only two patches:
https://patchwork.kernel.org/patch/10468105/
https://patchwork.kernel.org/patch/10468103/
I noticed that installation targets would continue running
'make syncconfig' creates some files such as include/config/auto.conf,
include/generate/autoconf.h, etc. but the necessary directory creation
relies on scripts/kconfig/Makefile.
To make Kconfig self-contained, create directories as needed in
conf_write_autoconf().
This change allows
'make syncconfig' creates some files such as include/config/auto.conf,
include/generate/autoconf.h, etc. but the necessary directory creation
relies on scripts/kconfig/Makefile.
To make Kconfig self-contained, create directories as needed in
conf_write_autoconf().
This change allows
Currently, only syncconfig creates or updates include/config/auto.conf
and some other files. Other config targets create or update only the
.config file.
When you configure and build the kernel from a pristine source tree,
any config target is followed by syncconfig in the build stage since
Currently, only syncconfig creates or updates include/config/auto.conf
and some other files. Other config targets create or update only the
.config file.
When you configure and build the kernel from a pristine source tree,
any config target is followed by syncconfig in the build stage since
syncconfig updates the .config only when sym_change_count > 0, i.e.
any change in config symbols has been detected.
Not only symbols but also comments are contained in the .config file.
If only comments are updated, they are not fed back to the .config,
then the stale comments are left-over. Of
file_write_dep() is called only from conf_write_autoconf().
Move it from util.c to confdata.c to make it static.
Also, rename it to conf_write_dep() since it should belong to
the group of conf_write* functions.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/confdata.c | 31
syncconfig updates the .config only when sym_change_count > 0, i.e.
any change in config symbols has been detected.
Not only symbols but also comments are contained in the .config file.
If only comments are updated, they are not fed back to the .config,
then the stale comments are left-over. Of
file_write_dep() is called only from conf_write_autoconf().
Move it from util.c to confdata.c to make it static.
Also, rename it to conf_write_dep() since it should belong to
the group of conf_write* functions.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/confdata.c | 31
Commit 17263baf958b ("kconfig: Create include/generated for
localmodconfig") added the 'mkdir' line because local{yes,mod}config
ran streamline_config.pl followed by silentoldconfig at that time.
Since commit 81d2bc227305 ("kconfig: invoke oldconfig instead of
silentoldconfig from local*config"),
Commit 17263baf958b ("kconfig: Create include/generated for
localmodconfig") added the 'mkdir' line because local{yes,mod}config
ran streamline_config.pl followed by silentoldconfig at that time.
Since commit 81d2bc227305 ("kconfig: invoke oldconfig instead of
silentoldconfig from local*config"),
Em Thu, 5 Jul 2018 10:58:42 +0900
"Katsuhiro Suzuki" escreveu:
> Hi Mauro,
>
> > -Original Message-
> > From: Mauro Carvalho Chehab
> > Sent: Thursday, July 5, 2018 1:58 AM
> > To: Suzuki, Katsuhiro/鈴木 勝博
> > Cc: linux-me...@vger.kernel.org; Masami Hiramatsu
> ;
> > Jassi Brar ;
>
Em Thu, 5 Jul 2018 10:58:42 +0900
"Katsuhiro Suzuki" escreveu:
> Hi Mauro,
>
> > -Original Message-
> > From: Mauro Carvalho Chehab
> > Sent: Thursday, July 5, 2018 1:58 AM
> > To: Suzuki, Katsuhiro/鈴木 勝博
> > Cc: linux-me...@vger.kernel.org; Masami Hiramatsu
> ;
> > Jassi Brar ;
>
When you build targets that require the kernel configuration, dot-config
is set to 1, then the top-level Makefile includes auto.conf. However,
Make considers its inclusion is optional because the '-include' directive
is used here.
If a necessary configuration file is missing for the external
When you build targets that require the kernel configuration, dot-config
is set to 1, then the top-level Makefile includes auto.conf. However,
Make considers its inclusion is optional because the '-include' directive
is used here.
If a necessary configuration file is missing for the external
1 - 100 of 1312 matches
Mail list logo
