From: Christoph Hellwig <hch@infradead.org>
To: "Михаил Гаврилов" <mikhail.v.gavrilov@gmail.com>
Cc: linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kernel BUG at fs/xfs/xfs_aops.c:853! in kernel 4.13 rc6
Date: Sun, 3 Sep 2017 00:43:06 -0700 [thread overview]
Message-ID: <20170903074306.GA8351@infradead.org> (raw)
In-Reply-To: <CABXGCsOL+_OgC0dpO1+Zeg=iu7ryZRZT4S7k-io8EGB0ZRgZGw@mail.gmail.com>
On Sun, Sep 03, 2017 at 09:22:17AM +0500, D?D,N?D?D,D>> D?D?D2N?D,D>>D 3/4 D2 wrote:
> [281502.961248] ------------[ cut here ]------------
> [281502.961257] kernel BUG at fs/xfs/xfs_aops.c:853!
This is:
bh = head = page_buffers(page);
Which looks odd and like some sort of VM/writeback change might
have triggered that we get a page without buffers, despite always
creating buffers in iomap_begin/end and page_mkwrite.
Ccing linux-mm if anything odd happen in that area recently.
Can you tell anything about the workload you are running?
> [281502.961263] invalid opcode: 0000 [#1] SMP
> [281502.961299] Modules linked in: xt_CHECKSUM ipt_MASQUERADE
> nf_nat_masquerade_ipv4 tun nls_utf8 isofs rfcomm fuse
> nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter
> ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat
> ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6
> nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw
> ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4
> nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw
> iptable_security ebtable_filter ebtables ip6table_filter ip6_tables
> bnep sunrpc vfat fat xfs libcrc32c snd_usb_audio snd_usbmidi_lib
> snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp
> kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul btrfs
> ghash_clmulni_intel intel_cstate iTCO_wdt iTCO_vendor_support
> [281502.961684] ppdev intel_uncore xor intel_rapl_perf i2c_i801
> huawei_cdc_ncm option raid6_pq cdc_wdm joydev cdc_ncm btusb usb_wwan
> snd_hda_codec_hdmi snd_hda_codec_realtek btrtl btbcm
> snd_hda_codec_ca0132 btintel snd_hda_codec_generic bluetooth
> gspca_zc3xx gspca_main v4l2_common snd_hda_intel videodev cdc_ether
> snd_hda_codec usbnet media ecdh_generic snd_hda_core rfkill snd_hwdep
> snd_seq snd_seq_device snd_pcm snd_timer mei_me snd mei lpc_ich
> soundcore shpchp parport_pc parport tpm_infineon tpm_tis tpm_tis_core
> tpm binfmt_misc hid_logitech_hidpp hid_logitech_dj uas usb_storage
> i915 crc32c_intel i2c_algo_bit drm_kms_helper drm r8169 mii video bfq
> [281502.962014] CPU: 7 PID: 81 Comm: kswapd0 Not tainted
> 4.13.0-0.rc6.git4.1.fc28.x86_64 #1
> [281502.962052] Hardware name: Gigabyte Technology Co., Ltd.
> Z87M-D3H/Z87M-D3H, BIOS F11 08/12/2014
> [281502.962094] task: ffff9f5b31acb300 task.stack: ffffabcd43e48000
> [281502.962161] RIP: 0010:xfs_do_writepage+0x735/0x830 [xfs]
> [281502.962188] RSP: 0018:ffffabcd43e4b988 EFLAGS: 00010246
> [281502.962216] RAX: 0000000000001000 RBX: ffffabcd43e4ba98 RCX:
> 000000000000000c
> [281502.962251] RDX: 0017ffffc0030009 RSI: ffffe8881f3cf900 RDI:
> 0000000000000246
> [281502.962287] RBP: ffffabcd43e4ba30 R08: ffffe8881f3cf900 R09:
> 0000000000000002
> [281502.962321] R10: ffffabcd43e4b9e0 R11: 0000000000000000 R12:
> ffff9f57fa7b6110
> [281502.962356] R13: ffffabcd43e4bc40 R14: ffffabcd43e4ba40 R15:
> ffffe8881f3cf920
> [281502.962392] FS: 0000000000000000(0000) GS:ffff9f5b5da00000(0000)
> knlGS:0000000000000000
> [281502.962430] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [281502.962458] CR2: 00007ff86cb39018 CR3: 0000000815e11000 CR4:
> 00000000001426e0
> [281502.962494] Call Trace:
> [281502.962515] ? sched_clock+0x9/0x10
> [281502.962539] ? clear_page_dirty_for_io+0x140/0x2b0
> [281502.962590] xfs_vm_writepage+0x3b/0x70 [xfs]
> [281502.962618] pageout.isra.54+0x103/0x420
> [281502.962646] shrink_page_list+0x982/0xdf0
> [281502.962674] shrink_inactive_list+0x225/0x630
> [281502.962704] shrink_node_memcg+0x36c/0x770
> [281502.962734] shrink_node+0xf7/0x2f0
> [281502.962753] ? shrink_node+0xf7/0x2f0
> [281502.962779] kswapd+0x325/0x990
> [281502.962804] kthread+0x133/0x150
> [281502.962824] ? mem_cgroup_shrink_node+0x330/0x330
> [281502.962849] ? kthread_create_on_node+0x70/0x70
> [281502.962875] ret_from_fork+0x2a/0x40
> [281502.962898] Code: ce 48 c7 00 00 00 00 00 48 c7 44 30 f8 00 00 00
> 00 48 83 e7 f8 48 29 f8 01 c1 89 c8 c1 e8 03 89 c1 31 c0 f3 48 ab e9
> 0f fe ff ff <0f> 0b e8 54 44 3a d9 85 c0 0f 85 44 fe ff ff 48 c7 c2 48
> a2 df
> [281502.963085] RIP: xfs_do_writepage+0x735/0x830 [xfs] RSP: ffffabcd43e4b988
> [281502.972614] ---[ end trace 1ba3042d56323a9c ]---
>
>
> Anybody can look what is culprit here?
>
>
> --
> Best Regards,
> Mike Gavrilov.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---end quoted text---
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2017-09-03 7:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABXGCsOL+_OgC0dpO1+Zeg=iu7ryZRZT4S7k-io8EGB0ZRgZGw@mail.gmail.com>
2017-09-03 7:43 ` Christoph Hellwig [this message]
2017-09-03 14:08 ` kernel BUG at fs/xfs/xfs_aops.c:853! in kernel 4.13 rc6 Михаил Гаврилов
2017-09-04 12:30 ` Jan Kara
2017-10-07 8:10 ` Михаил Гаврилов
2017-10-07 9:22 ` Михаил Гаврилов
2017-10-09 0:05 ` Dave Chinner
2017-10-09 18:31 ` Luis R. Rodriguez
2017-10-09 19:02 ` Eric W. Biederman
2017-10-15 8:53 ` Aleksa Sarai
2017-10-15 13:06 ` Theodore Ts'o
2017-10-15 22:14 ` Eric W. Biederman
2017-10-15 23:22 ` Dave Chinner
2017-10-16 17:44 ` Eric W. Biederman
2017-10-16 21:38 ` Dave Chinner
2017-10-16 1:13 ` Theodore Ts'o
2017-10-16 17:53 ` Eric W. Biederman
2017-10-16 18:50 ` Theodore Ts'o
2017-10-16 22:00 ` Dave Chinner
2017-10-17 1:34 ` Theodore Ts'o
2017-10-17 0:59 ` Aleksa Sarai
2017-10-17 9:20 ` Jan Kara
2017-10-17 14:12 ` Theodore Ts'o
2017-11-06 19:25 ` Luis R. Rodriguez
2017-11-07 15:26 ` Jan Kara
2017-10-09 22:28 ` Dave Chinner
2017-10-10 7:57 ` Jan Kara
2017-09-04 1:43 ` Dave Chinner
2017-09-04 2:20 ` Darrick J. Wong
2017-09-04 12:14 ` Jan Kara
2017-09-04 22:36 ` Dave Chinner
2017-09-05 16:17 ` Jan Kara
2017-09-05 23:42 ` Dave Chinner
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=20170903074306.GA8351@infradead.org \
--to=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.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).