.
Cc: sta...@vger.kernel.org # v5.7+
Signed-off-by: Artem Labazov <123321art...@gmail.com>
---
v2: replace vmalloc with vzalloc to avoid uninitialized memory access
v3: use kv* functions to attempt kmalloc first
fs/exfat/nls.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -
...@vger.kernel.org # v5.7+
Signed-off-by: Artem Labazov <123321art...@gmail.com>
---
v2: replace vmalloc with vzalloc to avoid uninitialized memory access
fs/exfat/nls.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/exfat/nls.c b/fs/exfat/nls.c
index 675d0e
> I have not yet received a report of the same issue.
> But I agree that this problem is likely to occur even if it is low
> probability.
Perhaps I should clarify my setup a little bit more.
The issue can be reliably reproduced on my laptop. It has 8 GBs of RAM
(pretty common amount nowadays) and
...@vger.kernel.org # v5.7+
Signed-off-by: Artem Labazov <123321art...@gmail.com>
---
fs/exfat/nls.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/exfat/nls.c b/fs/exfat/nls.c
index 675d0e7058c5..0582faf8de77 100644
--- a/fs/exfat/nls.c
+++ b/fs/exfat/nls.c
@@ -6,
...@vger.kernel.org # v5.7+
Signed-off-by: Artem Labazov <123321art...@gmail.com>
---
fs/exfat/nls.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/exfat/nls.c b/fs/exfat/nls.c
index 675d0e7058c5..e415794e3ffc 100644
--- a/fs/exfat/nls.c
+++ b/fs/exfat/nls.c
@@ -6,
5 matches
Mail list logo