All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Gordeev <alex@gordick.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Chao Yu <chao@kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: video archive on a microSD card
Date: Fri, 02 Sep 2016 15:05:10 +0300	[thread overview]
Message-ID: <225181472817910@web16m.yandex.ru> (raw)
In-Reply-To: <20160901201555.GC20281@jaegeuk>

Hi Jaegeuk,

01.09.2016, 23:16, "Jaegeuk Kim" <jaegeuk@kernel.org>:
> On Thu, Sep 01, 2016 at 10:37:36PM +0300, Alexander Gordeev wrote:
>>  Hi ,
>>
>>  01.09.2016, 21:25, "Jaegeuk Kim" <jaegeuk@kernel.org>:
>>  > Hello,
>>  >
>>  > On Thu, Sep 01, 2016 at 08:40:07PM +0300, Alexander Gordeev wrote:
>>  > ...
>>  >>  >>  [ 49.274678] ------------[ cut here ]------------
>>  >>  >>  [ 49.280216] WARNING: at /home/alex/work/s2l/amb_S2l_SDK_2.5/SDK2.5/s2l_linux_sdk/ambarella/kernel/linux-3.10/fs/f2fs/segment.c:1105 new_curseg+0x268/0x394 [f2fs]()
>>  >>  >
>>  >>  > This means there is no free segment.
>>  >>  > Could you print out the below information before this f2fs_bug_on?
>>  >>  > - prefree_segments(sbi)
>>  >>  > - free_segments(sbi)
>>  >>  >
>>  >>  >>  ...
>>  >>  >>  [ 49.518054] ---[ end trace 49dca462b4f988ff ]---
>>  >>  >>  [ 49.522689] ------------[ cut here ]------------
>>  >>  >>  [ 49.527375] WARNING: at /home/alex/work/s2l/amb_S2l_SDK_2.5/SDK2.5/s2l_linux_sdk/ambarella/kernel/linux-3.10/fs/f2fs/segment.c:1144 new_curseg+0x2f0/0x394 [f2fs]()
>>  >>  >
>>  >>  > This is caused by the above segno which was -1.
>>  >>  >
>>  >>  >>  ...
>>  >>  >>  [ 49.764853] ---[ end trace 49dca462b4f98900 ]---
>>  >>  >>  [ 49.857344] ------ segno = 7540, next_blkoff = 0, next_segno = 4294967295 --------
>>  >>  >>  [ 49.913664] ------ blkaddr = 3889152 --------
>>  >>  >>  [ 49.918173] Unable to handle kernel NULL pointer dereference at virtual address 00000000
>>  >>  >
>>  >>  > Also, we can see next_segno was -1, which incur no se entry for this segment.
>>  >>  > At this moment, I'd really like to see its /sys/kernel/debug/f2fs/status whether
>>  >>  > there is really not enough free segments.
>>  >>
>>  >>  I collected both /sys/kernel/debug/f2fs/status and numbers of blocks.
>>  >>  The oops happens only when I try to delete anything. Also it can be caused
>>  >>  by GC, but I turned background GC off. So I mounted the fs, dumped the status
>>  >>  and then tried to remove a file. Here is what I got:
>>  >>
>>  >>  =====[ partition info(sda). #0, RW]=====
>>  >>  [SB: 1] [CP: 2] [SIT: 2] [NAT: 34] [SSA: 16] [MAIN: 7540(OverProv:424 Resv:50)]
>>  >
>>  > Could you check your mkfs.f2fs version?
>>  > I want to check ovp and resv numbers.
>>
>>  I currently used mkfs.f2fs from my board's SDK. It prints this:
>>  F2FS-tools: mkfs.f2fs Ver: 1.4.1 (2015-03-04)
>>
>>  Should I upgrade it?
>>  I think the problem will go away if I recreate the FS. At the moment
>>  it reproduces every time. I wonder if we need it again.
>
> Yes, please upgrade to the latest version to make sure.
> And, it needs to format it again.
> Seems there is no further information that we can use from the old partition.

Ok, thanks! I upgraded f2fs-tools and recreated the FS. Works fine so far!
Still IMHO this might be a problem, if someone with a specially crafted FS on a USB
stick can cause a kernel oops on any modern Linux system. Isn't it?

-- 
 Alexander

------------------------------------------------------------------------------
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2016-09-02 12:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12 11:52 video archive on a microSD card Alexander Gordeev
2016-08-15 10:47 ` Alexander Gordeev
2016-08-15 11:41   ` Chao Yu
2016-08-15 12:22     ` Alexander Gordeev
2016-08-16 15:29       ` Chao Yu
2016-08-17  9:47       ` Alexander Gordeev
2016-08-17 15:54         ` Chao Yu
2016-08-18 11:04           ` Alexander Gordeev
2016-08-19  2:41             ` Jaegeuk Kim
2016-08-19 11:56               ` Alexander Gordeev
2016-08-22 20:52                 ` Alexander Gordeev
2016-08-23 21:12                   ` Jaegeuk Kim
2016-08-25 20:14                     ` Alexander Gordeev
2016-08-27  1:20                       ` Jaegeuk Kim
     [not found]                         ` <549571472473386@web20g.yandex.ru>
2016-08-29 18:23                           ` Jaegeuk Kim
     [not found]                             ` <9581472749471@web24h.yandex.ru>
2016-09-01 20:07                               ` Jaegeuk Kim
2016-09-02 12:15                                 ` Alexander Gordeev
2016-08-23 20:27                 ` Jaegeuk Kim
2016-08-19 17:22               ` Alexander Gordeev
2016-08-23 21:27                 ` Jaegeuk Kim
2016-08-25 20:22                   ` Alexander Gordeev
2016-08-26 16:04                   ` Alexander Gordeev
2016-08-27  1:15                     ` Jaegeuk Kim
2016-08-27 13:00                       ` Alexander Gordeev
2016-08-29 16:50                 ` Alexander Gordeev
2016-08-29 18:00                   ` Jaegeuk Kim
2016-08-31  8:52                     ` Alexander Gordeev
2016-08-31 23:46                       ` Jaegeuk Kim
2016-09-01 17:40                         ` Alexander Gordeev
2016-09-01 18:25                           ` Jaegeuk Kim
2016-09-01 19:37                             ` Alexander Gordeev
2016-09-01 20:15                               ` Jaegeuk Kim
2016-09-02 12:05                                 ` Alexander Gordeev [this message]
2016-09-02 18:50                                   ` Jaegeuk Kim
2016-08-15 12:57   ` [PATCH] f2fs: fix build for v3.10 Alexander Gordeev

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=225181472817910@web16m.yandex.ru \
    --to=alex@gordick.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.