From: naga suresh kumar <nagasureshkumarrelli@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michal Simek <michals@xilinx.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
siva durga paladugu <siva.durga.paladugu@xililnx.com>,
Naga Sureshkumar Relli <nagasure@xilinx.com>
Subject: Re: ubifs mount failure
Date: Tue, 3 Dec 2019 16:06:12 +0530 [thread overview]
Message-ID: <CALgLF9KPAk_AsecnTMmbdF5qbgqXe7HNOrNariNVbhSr6FVN2g@mail.gmail.com> (raw)
In-Reply-To: <614898763.105471.1575364223372.JavaMail.zimbra@nod.at>
Hi Richard,
On Tue, Dec 3, 2019 at 2:40 PM Richard Weinberger <richard@nod.at> wrote:
>
> ----- Ursprüngliche Mail -----
> > Von: "Naga Sureshkumar Relli" <nagasure@xilinx.com>
> > https://elixir.bootlin.com/linux/v5.4/source/fs/ubifs/sb.c#L164
> > we are trying to allocate 4325376 (~4MB)
>
> 4MiB? Is ->min_io_size that large?
if you see https://elixir.bootlin.com/linux/latest/source/fs/ubifs/sb.c#L164
The size is actually ALIGN(tmp, c->min_io_size).
Here tmp is of 4325376 Bytes and min_io_size is 16384 Bytes
Thanks,
Naga Sureshkumar Relli
>
> Thanks,
> //richard
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-12-03 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR02MB5727000CBE70BAF31F60FEE4AF420@MN2PR02MB5727.namprd02.prod.outlook.com>
2019-12-03 8:41 ` ubifs mount failure Sascha Hauer
2019-12-03 9:00 ` Naga Sureshkumar Relli
2019-12-03 9:10 ` Richard Weinberger
2019-12-03 10:36 ` naga suresh kumar [this message]
2019-12-03 10:45 ` Sascha Hauer
2019-12-03 10:53 ` naga suresh kumar
2019-12-04 10:08 ` Sascha Hauer
2019-12-03 19:08 ` Richard Weinberger
2019-12-04 7:17 ` Sascha Hauer
2019-12-04 9:05 ` Richard Weinberger
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=CALgLF9KPAk_AsecnTMmbdF5qbgqXe7HNOrNariNVbhSr6FVN2g@mail.gmail.com \
--to=nagasureshkumarrelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michals@xilinx.com \
--cc=miquel.raynal@bootlin.com \
--cc=nagasure@xilinx.com \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
--cc=siva.durga.paladugu@xililnx.com \
/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).