linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 195729] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 1766784).There's a risk of filesystem corruption in case of system crash.
Date: Fri, 12 May 2017 14:53:51 +0000	[thread overview]
Message-ID: <bug-195729-13602-zHVWZWx6Wd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195729-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=195729

--- Comment #2 from jqiaoulk@gmail.com ---
So briefly speaking, one following call must incorrect call spin_lock or other
functions that disable the preemption in this failure case:

For example:

Failure case:

stm_display_output_start()
spin_lock()
_ZN16CSTmMasterOutput5StartEPK18stm_display_mode_s  -------> We can't sleep
here since it is in the critical section !!!
spin_unlock()
Call Sequence:

(1) vibe_os_clk_set_parent

(2)
_ZN12CSTmClockLLA6EnableE29stm_clk_divider_output_name_t31stm_clk_divider_output_source_t31stm_clk_divider_output_divide_t

(3) _ZN16CSTmMainTVOutput15SetOutputFormatEj

(4) _ZN16CSTmMasterOutput5StartEPK18stm_display_mode_s

(5) stm_display_output_start()

(6) dil_blender_output_start

(7) cdi_hdmi_exit

(8) dil_hdmi_set_video_code

(9) hdmi_release

(10) hdmi_ioctl()

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2017-05-12 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 13:31 [Bug 195729] New: JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 1766784).There's a risk of filesystem corruption in case of system crash bugzilla-daemon
2017-05-12 14:53 ` [Bug 195729] " bugzilla-daemon
2017-05-12 14:53 ` bugzilla-daemon [this message]
2017-05-12 14:54 ` bugzilla-daemon
2017-05-12 14:54 ` bugzilla-daemon
2017-05-12 14:58 ` bugzilla-daemon
2017-05-12 14:59 ` 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-195729-13602-zHVWZWx6Wd@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@kernel.org \
    /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).