From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 200951] kernel NULL pointer dereference in update_sit_entry
Date: Tue, 04 Sep 2018 12:51:57 +0000 [thread overview]
Message-ID: <bug-200951-202145-Y1vjW1dOLZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200951-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #16 from vicencb@gmail.com ---
Hi,
thank you for being that fast!
I have tried it against v4.19-rc2
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=57361846b52bc686112da6ca5368d11210796804
but it does not apply
checking file fs/f2fs/debug.c
Hunk #1 succeeded at 190 (offset -3 lines).
checking file fs/f2fs/f2fs.h
Hunk #1 FAILED at 3436.
1 out of 1 hunk FAILED
checking file fs/f2fs/file.c
checking file fs/f2fs/segment.c
Hunk #1 succeeded at 1725 (offset -43 lines).
...
Hunk #8 succeeded at 3959 (offset -45 lines).
checking file fs/f2fs/super.c
Hunk #1 succeeded at 360 (offset -3 lines).
Hunk #2 FAILED at 417.
Hunk #3 succeeded at 1031 (offset -29 lines).
Hunk #4 FAILED at 1440.
2 out of 4 hunks FAILED
Which kernel tree should i be using?
Regards,
Vicenç.
--
You are receiving this mail because:
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2018-09-04 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 13:44 [Bug 200951] New: kernel NULL pointer dereference in update_sit_entry bugzilla-daemon
2018-08-27 13:45 ` [Bug 200951] " bugzilla-daemon
2018-08-27 13:46 ` bugzilla-daemon
2018-08-31 8:17 ` bugzilla-daemon
2018-09-01 12:53 ` bugzilla-daemon
2018-09-01 12:54 ` bugzilla-daemon
2018-09-01 13:18 ` bugzilla-daemon
2018-09-02 6:52 ` bugzilla-daemon
2018-09-02 16:47 ` bugzilla-daemon
2018-09-02 16:49 ` bugzilla-daemon
2018-09-02 16:50 ` bugzilla-daemon
2018-09-03 1:27 ` bugzilla-daemon
2018-09-03 9:35 ` bugzilla-daemon
2018-09-03 9:41 ` bugzilla-daemon
2018-09-03 9:54 ` bugzilla-daemon
2018-09-04 9:43 ` bugzilla-daemon
2018-09-04 12:51 ` bugzilla-daemon [this message]
2018-09-04 14:13 ` bugzilla-daemon
2018-09-11 3:15 ` bugzilla-daemon
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=bug-200951-202145-Y1vjW1dOLZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.