From: Dan Carpenter <dan.carpenter@oracle.com>
To: Austin Kim <austindh.kim@gmail.com>
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] xfs: Use BUG_ON rather than BUG() to remove unreachable code
Date: Thu, 22 Aug 2019 08:11:53 +0000 [thread overview]
Message-ID: <20190822081153.GG4451@kadam> (raw)
In-Reply-To: <20190822062320.GA35267@LGEARND20B15>
Depending on the config BUG() might be a no-op. Outside of filesystems
everyone ignores that and crashes ungracefully, but in filesystems they
don't want to risk corrupting your files.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Austin Kim <austindh.kim@gmail.com>
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] xfs: Use BUG_ON rather than BUG() to remove unreachable code
Date: Thu, 22 Aug 2019 11:11:53 +0300 [thread overview]
Message-ID: <20190822081153.GG4451@kadam> (raw)
In-Reply-To: <20190822062320.GA35267@LGEARND20B15>
Depending on the config BUG() might be a no-op. Outside of filesystems
everyone ignores that and crashes ungracefully, but in filesystems they
don't want to risk corrupting your files.
regards,
dan carpenter
next prev parent reply other threads:[~2019-08-22 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 6:23 [PATCH] xfs: Use BUG_ON rather than BUG() to remove unreachable code Austin Kim
2019-08-22 6:23 ` Austin Kim
2019-08-22 8:11 ` Dan Carpenter [this message]
2019-08-22 8:11 ` Dan Carpenter
2019-08-22 14:44 ` Darrick J. Wong
2019-08-22 14:44 ` Darrick J. Wong
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=20190822081153.GG4451@kadam \
--to=dan.carpenter@oracle.com \
--cc=austindh.kim@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.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 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.