Fix the following whitescan warning:
Calling "zlib_inflateEnd()" is only useful for its return value,
which is ignored.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
fs/cramfs/uncompress.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/cramfs/uncompress.c b
On Thu, 26 Nov 2020, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in the Kconfig help text. Fix it.
>
> Signed-off-by: Colin Ian King
Acked-by: Nicolas Pitre
> ---
> fs/cramfs/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion
From: Colin Ian King
There is a spelling mistake in the Kconfig help text. Fix it.
Signed-off-by: Colin Ian King
---
fs/cramfs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig
index d98cef0dbb6b..a8af8c6ac15d 100644
--- a/fs
On Mon, 23 Nov 2020, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> Remove open coded kmap/memcpy/kunmap and use mempcy_from_page() instead.
>
> Cc: Nicolas Pitre
> Signed-off-by: Ira Weiny
Acked-by: Nicolas Pitre
> ---
> fs/cramfs/inode.c | 3 +--
> 1 file
From: Ira Weiny
Remove open coded kmap/memcpy/kunmap and use mempcy_from_page() instead.
Cc: Nicolas Pitre
Signed-off-by: Ira Weiny
---
fs/cramfs/inode.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 4b90cfd1ec36
On Tue, Oct 13, 2020 at 09:01:49PM +0100, Al Viro wrote:
> On Tue, Oct 13, 2020 at 08:36:43PM +0100, Matthew Wilcox wrote:
>
> > static inline void copy_to_highpage(struct page *to, void *vfrom, unsigned
> > int size)
> > {
> > char *vto = kmap_atomic(to);
> >
> > memcpy(vto, vfrom,
S are localized to a single thread. To avoid
> > > the over head of global PKRS updates use the new kmap_thread() call.
> > >
> > > Cc: Nicolas Pitre
> > > Signed-off-by: Ira Weiny
> > > ---
> > > fs/cramfs/inode.c | 10 +-
> > > 1
On Tue, Oct 13, 2020 at 08:36:43PM +0100, Matthew Wilcox wrote:
> static inline void copy_to_highpage(struct page *to, void *vfrom, unsigned
> int size)
> {
> char *vto = kmap_atomic(to);
>
> memcpy(vto, vfrom, size);
> kunmap_atomic(vto);
> }
>
> in linux/highmem.h ?
You
o a single thread. To avoid
> > > the over head of global PKRS updates use the new kmap_thread() call.
> > >
> > > Cc: Nicolas Pitre
> > > Signed-off-by: Ira Weiny
> > > ---
> > > fs/cramfs/inode.c | 10 +-
> > > 1 file chan
ew kmap_thread() call.
> >
> > Cc: Nicolas Pitre
> > Signed-off-by: Ira Weiny
> > ---
> > fs/cramfs/inode.c | 10 +-
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
> > index 91
On Fri, Oct 9, 2020 at 12:52 PM wrote:
>
> From: Ira Weiny
>
> The kmap() calls in this FS are localized to a single thread. To avoid
> the over head of global PKRS updates use the new kmap_thread() call.
>
> Cc: Nicolas Pitre
> Signed-off-by: Ira Weiny
> --
ked-by: Nicolas Pitre
> fs/cramfs/inode.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
> index 912308600d39..003c014a42ed 100644
> --- a/fs/cramfs/inode.c
> +++ b/fs/cramfs/inode.c
> @@ -247,8 +24
From: Ira Weiny
The kmap() calls in this FS are localized to a single thread. To avoid
the over head of global PKRS updates use the new kmap_thread() call.
Cc: Nicolas Pitre
Signed-off-by: Ira Weiny
---
fs/cramfs/inode.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff
The cramfs readpage implementation was already synchronous, so use
AOP_UPDATED_PAGE to avoid cycling the page lock.
Signed-off-by: Matthew Wilcox (Oracle)
---
fs/cramfs/inode.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index
The cramfs readpage implementation was already synchronous, so use
AOP_UPDATED_PAGE to avoid cycling the page lock.
Signed-off-by: Matthew Wilcox (Oracle)
---
fs/cramfs/inode.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index
On Wed, 27 Mar 2019, David Howells wrote:
> Convert the cramfs filesystem to the new internal mount API as the old
> one will be obsoleted and removed. This allows greater flexibility in
> communication of mount parameters between userspace, the VFS and the
> filesystem.
>
>
Signed-off-by: David Howells
cc: Nicolas Pitre
cc: linux-...@lists.infradead.org
cc: linux-bl...@vger.kernel.org
---
fs/cramfs/inode.c | 69 ++---
1 file changed, 39 insertions(+), 30 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs
Here's a set of patches that convert romfs, cramfs, jffs2 and squashfs to
use the new fs_context struct and replace mount_mtd(). They have
prerequisite commits (such as replacing mount_bdev()) that can be found in
the branch detailed below.
(1) Provide a replacement for mount_mtd() that takes
Signed-off-by: David Howells
cc: Nicolas Pitre
cc: linux-...@lists.infradead.org
cc: linux-bl...@vger.kernel.org
---
fs/cramfs/inode.c | 69 ++---
1 file changed, 39 insertions(+), 30 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Signed-off-by: Ben Hutchings
---
fs/cramfs/inode.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
@@ -183,7 +183,8 @@ static void
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
, and wrongly pass
the buffer size test.
Reported-by: Anatoly Trosinenko
Signed-off-by: Nicolas Pitre
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
fs/cramfs/inode.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
Tested in fresh torvalds/master branch. Thank you!
Best regards
Anatoly
пн, 29 окт. 2018 г. в 19:03, Nicolas Pitre :
>
> On Mon, 29 Oct 2018, Anatoly Trosinenko wrote:
>
> > > How do I populate /vtmp? Mine is empty at this point. I imagine I
> > > should put the cramfs
Tested in fresh torvalds/master branch. Thank you!
Best regards
Anatoly
пн, 29 окт. 2018 г. в 19:03, Nicolas Pitre :
>
> On Mon, 29 Oct 2018, Anatoly Trosinenko wrote:
>
> > > How do I populate /vtmp? Mine is empty at this point. I imagine I
> > > should put the cramfs
On Tue, 30 Oct 2018, Linus Torvalds wrote:
> On Tue, Oct 30, 2018 at 12:09 PM Nicolas Pitre
> wrote:
> >
> > Make the Cramfs code more robust against filesystem corruptions,
> > plus trivial indentation fixes.
>
> Shortlog?
Sorry, I will next time.
> Anyway, pulled.
Thanks.
Nicolas
On Tue, 30 Oct 2018, Linus Torvalds wrote:
> On Tue, Oct 30, 2018 at 12:09 PM Nicolas Pitre
> wrote:
> >
> > Make the Cramfs code more robust against filesystem corruptions,
> > plus trivial indentation fixes.
>
> Shortlog?
Sorry, I will next time.
> Anyway, pulled.
Thanks.
Nicolas
On Tue, Oct 30, 2018 at 12:09 PM Nicolas Pitre wrote:
>
> Make the Cramfs code more robust against filesystem corruptions,
> plus trivial indentation fixes.
Shortlog?
Anyway, pulled.
Linus
On Tue, Oct 30, 2018 at 12:09 PM Nicolas Pitre wrote:
>
> Make the Cramfs code more robust against filesystem corruptions,
> plus trivial indentation fixes.
Shortlog?
Anyway, pulled.
Linus
Linus,
Please pull from:
git://git.linaro.org/people/nicolas.pitre/linux tags/cramfs_fixes
Make the Cramfs code more robust against filesystem corruptions,
plus trivial indentation fixes.
Tag: 37b13f91069f87579018f4870da082bd172be005
Branch: 56ce68bceeefa38e5b3509bf3d39259138e2d76a
fs
Linus,
Please pull from:
git://git.linaro.org/people/nicolas.pitre/linux tags/cramfs_fixes
Make the Cramfs code more robust against filesystem corruptions,
plus trivial indentation fixes.
Tag: 37b13f91069f87579018f4870da082bd172be005
Branch: 56ce68bceeefa38e5b3509bf3d39259138e2d76a
fs
On Mon, 29 Oct 2018, Anatoly Trosinenko wrote:
> > How do I populate /vtmp? Mine is empty at this point. I imagine I
> > should put the cramfs image somewhere on the host, but I'm not that
> > familiar withkvm.
>
> Oops, forgot to say, it is the /tmp/kvm-xfstests-$USER
On Mon, 29 Oct 2018, Anatoly Trosinenko wrote:
> > How do I populate /vtmp? Mine is empty at this point. I imagine I
> > should put the cramfs image somewhere on the host, but I'm not that
> > familiar withkvm.
>
> Oops, forgot to say, it is the /tmp/kvm-xfstests-$USER
> How do I populate /vtmp? Mine is empty at this point. I imagine I should
put the cramfs image somewhere on the host, but I'm not that familiar
withkvm.
Oops, forgot to say, it is the /tmp/kvm-xfstests-$USER directory on
the host (it will be created when you first launch kvm-xfste
> How do I populate /vtmp? Mine is empty at this point. I imagine I should
put the cramfs image somewhere on the host, but I'm not that familiar
withkvm.
Oops, forgot to say, it is the /tmp/kvm-xfstests-$USER directory on
the host (it will be created when you first launch kvm-xfste
On Sun, 28 Oct 2018, Anatoly Trosinenko wrote:
> Hello,
>
> When reading a file from a fuzzed cramfs image, unhandled kernel
> paging request occurs.
Hmmm... It doesn't show up on my test system.
> How to reproduce with kvm-xfstests:
> 1) Checkout the v4.19 tag, copy
On Sun, 28 Oct 2018, Anatoly Trosinenko wrote:
> Hello,
>
> When reading a file from a fuzzed cramfs image, unhandled kernel
> paging request occurs.
Hmmm... It doesn't show up on my test system.
> How to reproduce with kvm-xfstests:
> 1) Checkout the v4.19 tag, copy
On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> On Tue, Aug 28, 2018 at 01:49:25PM -0400, Nicolas Pitre wrote:
> > On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> > > - ret = vm_insert_mixed(vma, vma->vm_start + off, pfn);
> > > + vmf = vmf_insert_mixed(vma,
On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> On Tue, Aug 28, 2018 at 01:49:25PM -0400, Nicolas Pitre wrote:
> > On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> > > - ret = vm_insert_mixed(vma, vma->vm_start + off, pfn);
> > > + vmf = vmf_insert_mixed(vma,
On Tue, Aug 28, 2018 at 01:49:25PM -0400, Nicolas Pitre wrote:
> On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> > - ret = vm_insert_mixed(vma, vma->vm_start + off, pfn);
> > + vmf = vmf_insert_mixed(vma, vma->vm_start + off, pfn);
> > + if (vmf &
On Tue, Aug 28, 2018 at 01:49:25PM -0400, Nicolas Pitre wrote:
> On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> > - ret = vm_insert_mixed(vma, vma->vm_start + off, pfn);
> > + vmf = vmf_insert_mixed(vma, vma->vm_start + off, pfn);
> > + if (vmf &
On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> cramfs is the only remaining user of vm_insert_mixed; convert it.
>
> Signed-off-by: Matthew Wilcox
> ---
> fs/cramfs/inode.c | 9 +++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/fs/cramfs/ino
On Tue, 28 Aug 2018, Matthew Wilcox wrote:
> cramfs is the only remaining user of vm_insert_mixed; convert it.
>
> Signed-off-by: Matthew Wilcox
> ---
> fs/cramfs/inode.c | 9 +++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/fs/cramfs/ino
cramfs is the only remaining user of vm_insert_mixed; convert it.
Signed-off-by: Matthew Wilcox
---
fs/cramfs/inode.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index f408994fc632..b72449c19cd1 100644
--- a/fs/cramfs
cramfs is the only remaining user of vm_insert_mixed; convert it.
Signed-off-by: Matthew Wilcox
---
fs/cramfs/inode.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index f408994fc632..b72449c19cd1 100644
--- a/fs/cramfs
On Sun, May 13, 2018 at 06:21:18PM -0400, Nicolas Pitre wrote:
> On Sun, 13 May 2018, Joe Perches wrote:
>
> > There's an extra C here...
> >
> > Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
> > Signed-off-by: Joe Perches <j...@perch
On Sun, May 13, 2018 at 06:21:18PM -0400, Nicolas Pitre wrote:
> On Sun, 13 May 2018, Joe Perches wrote:
>
> > There's an extra C here...
> >
> > Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
> > Signed-off-by: Joe Perches
>
>
On Sun, 13 May 2018, Joe Perches wrote:
> There's an extra C here...
>
> Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
> Signed-off-by: Joe Perches <j...@perches.com>
Indeed.
Acked-by: Nicolas Pitre <n...@linaro.org>
@Al: could you pick up
On Sun, 13 May 2018, Joe Perches wrote:
> There's an extra C here...
>
> Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
> Signed-off-by: Joe Perches
Indeed.
Acked-by: Nicolas Pitre
@Al: could you pick up this one too?
> ---
> fs/cramfs/inode.c
There's an extra C here...
Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
Signed-off-by: Joe Perches <j...@perches.com>
---
fs/cramfs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 017b0ab19b
There's an extra C here...
Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
Signed-off-by: Joe Perches
---
fs/cramfs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 017b0ab19bc4..124b093d14e5 10064
Signed-off-by: Mark Fasheh <mfas...@suse.de>
---
fs/cramfs/inode.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 017b0ab19bc4..eb633de7ccbe 100644
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
@@
Signed-off-by: Mark Fasheh
---
fs/cramfs/inode.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 017b0ab19bc4..eb633de7ccbe 100644
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
@@ -294,7 +294,7 @@ static void
On Thu, 8 Feb 2018, Linus Torvalds wrote:
> On Wed, Feb 7, 2018 at 7:08 PM, Nicolas Pitre <nicolas.pi...@linaro.org>
> wrote:
> >
> > Viro once told me that my cramfs pull requests could go either to him or
> > to you. I have only this one patch at th
On Thu, 8 Feb 2018, Linus Torvalds wrote:
> On Wed, Feb 7, 2018 at 7:08 PM, Nicolas Pitre
> wrote:
> >
> > Viro once told me that my cramfs pull requests could go either to him or
> > to you. I have only this one patch at the moment, and since it depends
> > on a
On 02/08/2018 11:38 AM, Linus Torvalds wrote:
> On Wed, Feb 7, 2018 at 7:08 PM, Nicolas Pitre <nicolas.pi...@linaro.org>
> wrote:
>>
>> Viro once told me that my cramfs pull requests could go either to him or
>> to you. I have only this one patch at the moment, and s
On 02/08/2018 11:38 AM, Linus Torvalds wrote:
> On Wed, Feb 7, 2018 at 7:08 PM, Nicolas Pitre
> wrote:
>>
>> Viro once told me that my cramfs pull requests could go either to him or
>> to you. I have only this one patch at the moment, and since it depends
>> on a
On Wed, Feb 7, 2018 at 7:08 PM, Nicolas Pitre <nicolas.pi...@linaro.org> wrote:
>
> Viro once told me that my cramfs pull requests could go either to him or
> to you. I have only this one patch at the moment, and since it depends
> on a commit that recently appeared in your
On Wed, Feb 7, 2018 at 7:08 PM, Nicolas Pitre wrote:
>
> Viro once told me that my cramfs pull requests could go either to him or
> to you. I have only this one patch at the moment, and since it depends
> on a commit that recently appeared in your tree I'm therefore sending it
>
Commit b9f5fb1800d8 ("cramfs: fix MTD dependency") did what it says.
Since commit 9059a3493efe ("kconfig: fix relational operators for bool
and tristate symbols") it is possible to do it slightly better though.
Signed-off-by: Nicolas Pitre <n...@linaro.org>
---
Linus,
Commit b9f5fb1800d8 ("cramfs: fix MTD dependency") did what it says.
Since commit 9059a3493efe ("kconfig: fix relational operators for bool
and tristate symbols") it is possible to do it slightly better though.
Signed-off-by: Nicolas Pitre
---
Linus,
Viro once told me
Hi Nicolas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051
commit: 99c18ce580c6cc6763e694b4ce320d7b226ab59b cramfs: direct memory access
support
date: 9 weeks ago
config
Hi Nicolas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051
commit: 99c18ce580c6cc6763e694b4ce320d7b226ab59b cramfs: direct memory access
support
date: 9 weeks ago
config
On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>
> fs/cramfs/inode.o: In function `cramfs_mount':
> inode.c:(.text+0x220): undefined reference to `mount_mtd'
> fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
&
On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>
> fs/cramfs/inode.o: In function `cramfs_mount':
> inode.c:(.text+0x220): undefined reference to `mount_mtd'
> fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
&
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e1d1ea549b57790a3d8cf6300e6ef86118d692a3
commit: 99c18ce580c6cc6763e694b4ce320d7b226ab59b cramfs: direct memory access
support
date: 5 weeks ago
config: i386-randconfig-i1-201747 (attached as .config
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e1d1ea549b57790a3d8cf6300e6ef86118d692a3
commit: 99c18ce580c6cc6763e694b4ce320d7b226ab59b cramfs: direct memory access
support
date: 5 weeks ago
config: i386-randconfig-i1-201747 (attached as .config
Nicolas Pitre cramfs work.
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.cramfs
for you to fetch
Nicolas Pitre cramfs work.
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.cramfs
for you to fetch
gt;> On Fri, Nov 10, 2017 at 5:35 PM, Nicolas Pitre
> > >> <nicolas.pi...@linaro.org> wrote:
> > >> > On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> > >> >
> > >> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
icolas Pitre
> > >> wrote:
> > >> > On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> > >> >
> > >> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
> > >> >>
> > >> >> fs/cramfs/i
> >> wrote:
> >> > On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> >> >
> >> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
> >> >>
> >> >> fs/cramfs/inode.o: In function `cramfs_mount':
> >&
d Bergmann wrote:
> >> >
> >> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
> >> >>
> >> >> fs/cramfs/inode.o: In function `cramfs_mount':
> >> >> inode.c:(.text+0x220): undefined reference to `mount
ann wrote:
>> >
>> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>> >>
>> >> fs/cramfs/inode.o: In function `cramfs_mount':
>> >> inode.c:(.text+0x220): undefined reference to `mount_mtd'
>> >> fs/cramfs/
m and CONFIG_CRAMFS=y, we now get a link failure:
>> >>
>> >> fs/cramfs/inode.o: In function `cramfs_mount':
>> >> inode.c:(.text+0x220): undefined reference to `mount_mtd'
>> >> fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
>> >>
On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> On Fri, Nov 10, 2017 at 5:35 PM, Nicolas Pitre <nicolas.pi...@linaro.org>
> wrote:
> > On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> >
> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
> &g
On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> On Fri, Nov 10, 2017 at 5:35 PM, Nicolas Pitre
> wrote:
> > On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> >
> >> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
> >>
> >> fs/cramfs/inod
On Fri, Nov 10, 2017 at 5:35 PM, Nicolas Pitre <nicolas.pi...@linaro.org> wrote:
> On Fri, 10 Nov 2017, Arnd Bergmann wrote:
>
>> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>>
>> fs/cramfs/inode.o: In function `cramfs_mount':
>> inode.
On Fri, Nov 10, 2017 at 5:35 PM, Nicolas Pitre wrote:
> On Fri, 10 Nov 2017, Arnd Bergmann wrote:
>
>> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>>
>> fs/cramfs/inode.o: In function `cramfs_mount':
>> inode.c:(.text+0x220): undefined referen
On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>
> fs/cramfs/inode.o: In function `cramfs_mount':
> inode.c:(.text+0x220): undefined reference to `mount_mtd'
> fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
&
On Fri, 10 Nov 2017, Arnd Bergmann wrote:
> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>
> fs/cramfs/inode.o: In function `cramfs_mount':
> inode.c:(.text+0x220): undefined reference to `mount_mtd'
> fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
&
With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
fs/cramfs/inode.o: In function `cramfs_mount':
inode.c:(.text+0x220): undefined reference to `mount_mtd'
fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
inode.c:(.text+0x6d8): undefined reference to `mtd_point'
inode.c
With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
fs/cramfs/inode.o: In function `cramfs_mount':
inode.c:(.text+0x220): undefined reference to `mount_mtd'
fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
inode.c:(.text+0x6d8): undefined reference to `mtd_point'
inode.c
hat's what I thought you meant, which corresponds to the second
> part of my comment above. And as I said I'm not convinced this hiding of
> kernel config effects is better for understanding what is actually going
> on locally, and my own preference is how things are right now.
Anot
hat's what I thought you meant, which corresponds to the second
> part of my comment above. And as I said I'm not convinced this hiding of
> kernel config effects is better for understanding what is actually going
> on locally, and my own preference is how things are right now.
Anot
On Sat, 14 Oct 2017, Al Viro wrote:
> On Fri, Oct 13, 2017 at 04:09:23PM -0400, Nicolas Pitre wrote:
> > On Fri, 13 Oct 2017, Al Viro wrote:
> >
> > > OK... I wonder if it should simply define stubs for kill_mtd_super(),
> > > mtd_unpoint() and kill_block_super() in !CONFIG_MTD and
On Sat, 14 Oct 2017, Al Viro wrote:
> On Fri, Oct 13, 2017 at 04:09:23PM -0400, Nicolas Pitre wrote:
> > On Fri, 13 Oct 2017, Al Viro wrote:
> >
> > > OK... I wonder if it should simply define stubs for kill_mtd_super(),
> > > mtd_unpoint() and kill_block_super() in !CONFIG_MTD and
On Fri, Oct 13, 2017 at 04:09:23PM -0400, Nicolas Pitre wrote:
> On Fri, 13 Oct 2017, Al Viro wrote:
>
> > OK... I wonder if it should simply define stubs for kill_mtd_super(),
> > mtd_unpoint() and kill_block_super() in !CONFIG_MTD and !CONFIG_BLOCK
> > cases. mount_mtd() and mount_bdev() as
On Fri, Oct 13, 2017 at 04:09:23PM -0400, Nicolas Pitre wrote:
> On Fri, 13 Oct 2017, Al Viro wrote:
>
> > OK... I wonder if it should simply define stubs for kill_mtd_super(),
> > mtd_unpoint() and kill_block_super() in !CONFIG_MTD and !CONFIG_BLOCK
> > cases. mount_mtd() and mount_bdev() as
s is worth it in the end given this is not a common
occurrence in the kernel either.
Still, I've rearanged it slightly and fixed the null deref you spotted
earlier. Latest patch below:
- >8
Subject: [PATCH] cramfs: direct memory access support
Small embedded systems typically execute the
s is worth it in the end given this is not a common
occurrence in the kernel either.
Still, I've rearanged it slightly and fixed the null deref you spotted
earlier. Latest patch below:
- >8
Subject: [PATCH] cramfs: direct memory access support
Small embedded systems typically execute the
1 - 100 of 664 matches
Mail list logo
