X-Git-Url: http://git.pld-linux.org/?p=packages%2Fkernel.git;a=blobdiff_plain;f=kernel-small_fixes.patch;h=f0584fb5d2bf489cc24ac7eaf952c345766e3c27;hp=f0c5c8544c3d844042a5473d7b2dda189b01dced;hb=900330d09423f0bbe8527a4a346818b563a3b284;hpb=5d571d7a71f536754d32d054942603910b9f14b6 diff --git a/kernel-small_fixes.patch b/kernel-small_fixes.patch index f0c5c854..f0584fb5 100644 --- a/kernel-small_fixes.patch +++ b/kernel-small_fixes.patch @@ -1,477 +1,117 @@ ---- linux-2.6.33/scripts/mod/modpost.c~ 2010-02-24 19:52:17.000000000 +0100 -+++ linux-2.6.33/scripts/mod/modpost.c 2010-03-07 14:26:47.242168558 +0100 -@@ -15,7 +15,8 @@ - #include - #include - #include "modpost.h" --#include "../../include/generated/autoconf.h" -+// PLD architectures don't use CONFIG_SYMBOL_PREFIX -+//#include "../../include/generated/autoconf.h" - #include "../../include/linux/license.h" - - /* Some toolchains use a `_' prefix for all user symbols. */ - ---- linux-3.0/scripts/kconfig/lxdialog/check-lxdialog.sh~ 2011-07-22 04:17:23.000000000 +0200 -+++ linux-3.0/scripts/kconfig/lxdialog/check-lxdialog.sh 2011-08-25 21:26:04.799150642 +0200 -@@ -9,6 +9,12 @@ - $cc -print-file-name=lib${lib}.${ext} | grep -q / - if [ $? -eq 0 ]; then - echo "-l${lib}" -+ for libt in tinfow tinfo ; do -+ $cc -print-file-name=lib${libt}.${ext} | grep -q / -+ if [ $? -eq 0 ]; then -+ echo "-l${libt}" -+ fi -+ done - exit - fi - done - -From: Dave Chinner - -When we do inode readahead in log recovery, we do can do the -readahead before we've replayed the icreate transaction that stamps -the buffer with inode cores. The inode readahead verifier catches -this and marks the buffer as !done to indicate that it doesn't yet -contain valid inodes. - -In adding buffer error notification (i.e. setting b_error = -EIO at -the same time as as we clear the done flag) to such a readahead -verifier failure, we can then get subsequent inode recovery failing -with this error: - -XFS (dm-0): metadata I/O error: block 0xa00060 ("xlog_recover_do..(read#2)") error 5 numblks 32 - -This occurs when readahead completion races with icreate item replay -such as: - - inode readahead - find buffer - lock buffer - submit RA io - .... - icreate recovery - xfs_trans_get_buffer - find buffer - lock buffer - - ..... - - fails verifier - clear XBF_DONE - set bp->b_error = -EIO - release and unlock buffer - - icreate initialises buffer - marks buffer as done - adds buffer to delayed write queue - releases buffer - -At this point, we have an initialised inode buffer that is up to -date but has an -EIO state registered against it. When we finally -get to recovering an inode in that buffer: - - inode item recovery - xfs_trans_read_buffer - find buffer - lock buffer - sees XBF_DONE is set, returns buffer - sees bp->b_error is set - fail log recovery! - -Essentially, we need xfs_trans_get_buf_map() to clear the error status of -the buffer when doing a lookup. This function returns uninitialised -buffers, so the buffer returned can not be in an error state and -none of the code that uses this function expects b_error to be set -on return. Indeed, there is an ASSERT(!bp->b_error); in the -transaction case in xfs_trans_get_buf_map() that would have caught -this if log recovery used transactions.... - -This patch firstly changes the inode readahead failure to set -EIO -on the buffer, and secondly changes xfs_buf_get_map() to never -return a buffer with an error state set so this first change doesn't -cause unexpected log recovery failures. - -Signed-off-by: Dave Chinner ---- - fs/xfs/libxfs/xfs_inode_buf.c | 12 +++++++----- - fs/xfs/xfs_buf.c | 7 +++++++ - 2 files changed, 14 insertions(+), 5 deletions(-) - -diff --git a/fs/xfs/libxfs/xfs_inode_buf.c b/fs/xfs/libxfs/xfs_inode_buf.c -index 1b8d98a..ff17c48 100644 ---- a/fs/xfs/libxfs/xfs_inode_buf.c -+++ b/fs/xfs/libxfs/xfs_inode_buf.c -@@ -62,11 +62,12 @@ xfs_inobp_check( - * has not had the inode cores stamped into it. Hence for readahead, the buffer - * may be potentially invalid. - * -- * If the readahead buffer is invalid, we don't want to mark it with an error, -- * but we do want to clear the DONE status of the buffer so that a followup read -- * will re-read it from disk. This will ensure that we don't get an unnecessary -- * warnings during log recovery and we don't get unnecssary panics on debug -- * kernels. -+ * If the readahead buffer is invalid, we need to mark it with an error and -+ * clear the DONE status of the buffer so that a followup read will re-read it -+ * from disk. We don't report the error otherwise to avoid warnings during log -+ * recovery and we don't get unnecssary panics on debug kernels. We use EIO here -+ * because all we want to do is say readahead failed; there is no-one to report -+ * the error to, so this will distinguish it from a non-ra verifier failure. - */ - static void - xfs_inode_buf_verify( -@@ -93,6 +94,7 @@ xfs_inode_buf_verify( - XFS_RANDOM_ITOBP_INOTOBP))) { - if (readahead) { - bp->b_flags &= ~XBF_DONE; -+ xfs_buf_ioerror(bp, -EIO); - return; - } - -diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c -index 45a8ea7..ae86b16 100644 ---- a/fs/xfs/xfs_buf.c -+++ b/fs/xfs/xfs_buf.c -@@ -604,6 +604,13 @@ found: - } - } - -+ /* -+ * Clear b_error if this is a lookup from a caller that doesn't expect -+ * valid data to be found in the buffer. -+ */ -+ if (!(flags & XBF_READ)) -+ xfs_buf_ioerror(bp, 0); -+ - XFS_STATS_INC(target->bt_mount, xb_get); - trace_xfs_buf_get(bp, flags, _RET_IP_); - return bp; --- -2.5.0 - -_______________________________________________ -xfs mailing list -xfs@oss.sgi.com -http://oss.sgi.com/mailman/listinfo/xfs -From: Dave Chinner - -When we do dquot readahead in log recovery, we do not use a verifier -as the underlying buffer may not have dquots in it. e.g. the -allocation operation hasn't yet been replayed. Hence we do not want -to fail recovery because we detect an operation to be replayed has -not been run yet. This problem was addressed for inodes in commit -d891400 ("xfs: inode buffers may not be valid during recovery -readahead") but the problem was not recognised to exist for dquots -and their buffers as the dquot readahead did not have a verifier. - -The result of not using a verifier is that when the buffer is then -next read to replay a dquot modification, the dquot buffer verifier -will only be attached to the buffer if *readahead is not complete*. -Hence we can read the buffer, replay the dquot changes and then add -it to the delwri submission list without it having a verifier -attached to it. This then generates warnings in xfs_buf_ioapply(), -which catches and warns about this case. - -Fix this and make it handle the same readahead verifier error cases -as for inode buffers by adding a new readahead verifier that has a -write operation as well as a read operation that marks the buffer as -not done if any corruption is detected. Also make sure we don't run -readahead if the dquot buffer has been marked as cancelled by -recovery. - -This will result in readahead either succeeding and the buffer -having a valid write verifier, or readahead failing and the buffer -state requiring the subsequent read to resubmit the IO with the new -verifier. In either case, this will result in the buffer always -ending up with a valid write verifier on it. - -Note: we also need to fix the inode buffer readahead error handling -to mark the buffer with EIO. Brian noticed the code I copied from -there wrong during review, so fix it at the same time. Add comments -linking the two functions that handle readahead verifier errors -together so we don't forget this behavioural link in future. - -cc: # 3.12 - current -Signed-off-by: Dave Chinner -Reviewed-by: Brian Foster -Signed-off-by: Dave Chinner ---- - fs/xfs/libxfs/xfs_dquot_buf.c | 36 ++++++++++++++++++++++++++++++------ - fs/xfs/libxfs/xfs_inode_buf.c | 2 ++ - fs/xfs/libxfs/xfs_quota_defs.h | 2 +- - fs/xfs/libxfs/xfs_shared.h | 1 + - fs/xfs/xfs_log_recover.c | 9 +++++++-- - 5 files changed, 41 insertions(+), 9 deletions(-) - -diff --git a/fs/xfs/libxfs/xfs_dquot_buf.c b/fs/xfs/libxfs/xfs_dquot_buf.c -index 11cefb2..3cc3cf7 100644 ---- a/fs/xfs/libxfs/xfs_dquot_buf.c -+++ b/fs/xfs/libxfs/xfs_dquot_buf.c -@@ -54,7 +54,7 @@ xfs_dqcheck( - xfs_dqid_t id, - uint type, /* used only when IO_dorepair is true */ - uint flags, -- char *str) -+ const char *str) +; https://lkml.org/lkml/2019/7/10/244 +diff -ur linux-5.3/drivers/scsi/aacraid.org/aacraid.h linux-5.3/drivers/scsi/aacraid/aacraid.h +--- linux-5.3/drivers/scsi/aacraid.org/aacraid.h 2019-11-01 22:42:37.011469816 +0100 ++++ linux-5.3/drivers/scsi/aacraid/aacraid.h 2019-11-04 09:29:51.321486211 +0100 +@@ -2740,17 +2740,6 @@ + int aac_rx_deliver_producer(struct fib * fib); + void aac_reinit_aif(struct aac_dev *aac, unsigned int index); + +-static inline int aac_is_src(struct aac_dev *dev) +-{ +- u16 device = dev->pdev->device; +- +- if (device == PMC_DEVICE_S6 || +- device == PMC_DEVICE_S7 || +- device == PMC_DEVICE_S8) +- return 1; +- return 0; +-} +- + static inline int aac_supports_2T(struct aac_dev *dev) { - xfs_dqblk_t *d = (xfs_dqblk_t *)ddq; - int errs = 0; -@@ -207,7 +207,8 @@ xfs_dquot_buf_verify_crc( - STATIC bool - xfs_dquot_buf_verify( - struct xfs_mount *mp, -- struct xfs_buf *bp) -+ struct xfs_buf *bp, -+ int warn) + return (dev->adapter_info.options & AAC_OPT_NEW_COMM_64); +diff -ur linux-5.3/drivers/scsi/aacraid.org/comminit.c linux-5.3/drivers/scsi/aacraid/comminit.c +--- linux-5.3/drivers/scsi/aacraid.org/comminit.c 2019-11-01 22:42:37.014803249 +0100 ++++ linux-5.3/drivers/scsi/aacraid/comminit.c 2019-11-04 09:29:51.321486211 +0100 +@@ -41,8 +41,11 @@ { - struct xfs_dqblk *d = (struct xfs_dqblk *)bp->b_addr; - xfs_dqid_t id = 0; -@@ -240,8 +241,7 @@ xfs_dquot_buf_verify( - if (i == 0) - id = be32_to_cpu(ddq->d_id); - -- error = xfs_dqcheck(mp, ddq, id + i, 0, XFS_QMOPT_DOWARN, -- "xfs_dquot_buf_verify"); -+ error = xfs_dqcheck(mp, ddq, id + i, 0, warn, __func__); - if (error) - return false; - } -@@ -256,7 +256,7 @@ xfs_dquot_buf_read_verify( - - if (!xfs_dquot_buf_verify_crc(mp, bp)) - xfs_buf_ioerror(bp, -EFSBADCRC); -- else if (!xfs_dquot_buf_verify(mp, bp)) -+ else if (!xfs_dquot_buf_verify(mp, bp, XFS_QMOPT_DOWARN)) - xfs_buf_ioerror(bp, -EFSCORRUPTED); + u32 status = 0; - if (bp->b_error) -@@ -264,6 +264,25 @@ xfs_dquot_buf_read_verify( - } - - /* -+ * readahead errors are silent and simply leave the buffer as !done so a real -+ * read will then be run with the xfs_dquot_buf_ops verifier. See -+ * xfs_inode_buf_verify() for why we use EIO and ~XBF_DONE here rather than -+ * reporting the failure. -+ */ -+static void -+xfs_dquot_buf_readahead_verify( -+ struct xfs_buf *bp) -+{ -+ struct xfs_mount *mp = bp->b_target->bt_mount; -+ -+ if (!xfs_dquot_buf_verify_crc(mp, bp) || -+ !xfs_dquot_buf_verify(mp, bp, 0)) { -+ xfs_buf_ioerror(bp, -EIO); -+ bp->b_flags &= ~XBF_DONE; +- if (aac_is_src(dev)) ++ if (dev->pdev->device == PMC_DEVICE_S6 || ++ dev->pdev->device == PMC_DEVICE_S7 || ++ dev->pdev->device == PMC_DEVICE_S8) { + status = src_readl(dev, MUnit.OMR); + } -+} -+ -+/* - * we don't calculate the CRC here as that is done when the dquot is flushed to - * the buffer after the update is done. This ensures that the dquot in the - * buffer always has an up-to-date CRC value. -@@ -274,7 +293,7 @@ xfs_dquot_buf_write_verify( - { - struct xfs_mount *mp = bp->b_target->bt_mount; - -- if (!xfs_dquot_buf_verify(mp, bp)) { -+ if (!xfs_dquot_buf_verify(mp, bp, XFS_QMOPT_DOWARN)) { - xfs_buf_ioerror(bp, -EFSCORRUPTED); - xfs_verifier_error(bp); - return; -@@ -287,3 +306,8 @@ const struct xfs_buf_ops xfs_dquot_buf_ops = { - .verify_write = xfs_dquot_buf_write_verify, - }; - -+const struct xfs_buf_ops xfs_dquot_buf_ra_ops = { -+ -+ .verify_read = xfs_dquot_buf_readahead_verify, -+ .verify_write = xfs_dquot_buf_write_verify, -+}; -diff --git a/fs/xfs/libxfs/xfs_inode_buf.c b/fs/xfs/libxfs/xfs_inode_buf.c -index ff17c48..1aabfda 100644 ---- a/fs/xfs/libxfs/xfs_inode_buf.c -+++ b/fs/xfs/libxfs/xfs_inode_buf.c -@@ -68,6 +68,8 @@ xfs_inobp_check( - * recovery and we don't get unnecssary panics on debug kernels. We use EIO here - * because all we want to do is say readahead failed; there is no-one to report - * the error to, so this will distinguish it from a non-ra verifier failure. -+ * Changes to this readahead error behavour also need to be reflected in -+ * xfs_dquot_buf_readahead_verify(). - */ - static void - xfs_inode_buf_verify( -diff --git a/fs/xfs/libxfs/xfs_quota_defs.h b/fs/xfs/libxfs/xfs_quota_defs.h -index 1b0a083..f51078f 100644 ---- a/fs/xfs/libxfs/xfs_quota_defs.h -+++ b/fs/xfs/libxfs/xfs_quota_defs.h -@@ -153,7 +153,7 @@ typedef __uint16_t xfs_qwarncnt_t; - #define XFS_QMOPT_RESBLK_MASK (XFS_QMOPT_RES_REGBLKS | XFS_QMOPT_RES_RTBLKS) - - extern int xfs_dqcheck(struct xfs_mount *mp, xfs_disk_dquot_t *ddq, -- xfs_dqid_t id, uint type, uint flags, char *str); -+ xfs_dqid_t id, uint type, uint flags, const char *str); - extern int xfs_calc_dquots_per_chunk(unsigned int nbblks); - - #endif /* __XFS_QUOTA_H__ */ -diff --git a/fs/xfs/libxfs/xfs_shared.h b/fs/xfs/libxfs/xfs_shared.h -index 5be5297..15c3ceb 100644 ---- a/fs/xfs/libxfs/xfs_shared.h -+++ b/fs/xfs/libxfs/xfs_shared.h -@@ -49,6 +49,7 @@ extern const struct xfs_buf_ops xfs_inobt_buf_ops; - extern const struct xfs_buf_ops xfs_inode_buf_ops; - extern const struct xfs_buf_ops xfs_inode_buf_ra_ops; - extern const struct xfs_buf_ops xfs_dquot_buf_ops; -+extern const struct xfs_buf_ops xfs_dquot_buf_ra_ops; - extern const struct xfs_buf_ops xfs_sb_buf_ops; - extern const struct xfs_buf_ops xfs_sb_quiet_buf_ops; - extern const struct xfs_buf_ops xfs_symlink_buf_ops; -diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c -index c5ecaac..5991cdc 100644 ---- a/fs/xfs/xfs_log_recover.c -+++ b/fs/xfs/xfs_log_recover.c -@@ -3204,6 +3204,7 @@ xlog_recover_dquot_ra_pass2( - struct xfs_disk_dquot *recddq; - struct xfs_dq_logformat *dq_f; - uint type; -+ int len; - - - if (mp->m_qflags == 0) -@@ -3224,8 +3225,12 @@ xlog_recover_dquot_ra_pass2( - ASSERT(dq_f); - ASSERT(dq_f->qlf_len == 1); - -- xfs_buf_readahead(mp->m_ddev_targp, dq_f->qlf_blkno, -- XFS_FSB_TO_BB(mp, dq_f->qlf_len), NULL); -+ len = XFS_FSB_TO_BB(mp, dq_f->qlf_len); -+ if (xlog_peek_buffer_cancelled(log, dq_f->qlf_blkno, len, 0)) -+ return; -+ -+ xfs_buf_readahead(mp->m_ddev_targp, dq_f->qlf_blkno, len, -+ &xfs_dquot_buf_ra_ops); + return (status & AAC_INT_MODE_MSIX); } - STATIC void --- -2.5.0 - -_______________________________________________ -xfs mailing list -xfs@oss.sgi.com -http://oss.sgi.com/mailman/listinfo/xfs -From david at fromorbit.com Tue Jan 12 23:12:48 2016 -From: david at fromorbit.com (Dave Chinner) -Date: Wed, 13 Jan 2016 16:12:48 +1100 -Subject: [PATCH] Revert "xfs: clear PF_NOFREEZE for xfsaild kthread" -Message-ID: <1452661968-11482-1-git-send-email-david@fromorbit.com> -Content-Length: 916 -Lines: 30 - -This reverts commit 24ba16bb3d499c49974669cd8429c3e4138ab102 as it -prevents machines from suspending. This regression occurs when the -xfsaild is idle on entry to suspend, and so there s no activity to -wake it from it's idle sleep and hence see that it is supposed to -freeze. Hence the freezer times out waiting for it and suspend is -cancelled. - -There is no obvious fix for this short of freezing the filesystem -properly, so revert this change for now. - -Signed-off-by: Dave Chinner ---- - fs/xfs/xfs_trans_ail.c | 1 - - 1 file changed, 1 deletion(-) - -diff --git a/fs/xfs/xfs_trans_ail.c b/fs/xfs/xfs_trans_ail.c -index aa67339..4f18fd9 100644 ---- a/fs/xfs/xfs_trans_ail.c -+++ b/fs/xfs/xfs_trans_ail.c -@@ -497,7 +497,6 @@ xfsaild( - long tout = 0; /* milliseconds */ - - current->flags |= PF_MEMALLOC; -- set_freezable(); - - while (!kthread_should_stop()) { - if (tout && tout <= 20) --- -2.5.0 - - -From 7ca88764d45c209791e8813131c1457c2e9e51e7 Mon Sep 17 00:00:00 2001 -From: Yevgeny Pats -Date: Mon, 11 Jan 2016 12:05:28 +0000 -Subject: KEYS: Fix keyring ref leak in join_session_keyring() - -If a thread is asked to join as a session keyring the keyring that's already -set as its session, we leak a keyring reference. - -This can be tested with the following program: - - #include - #include - #include - #include - - int main(int argc, const char *argv[]) - { - int i = 0; - key_serial_t serial; - - serial = keyctl(KEYCTL_JOIN_SESSION_KEYRING, - "leaked-keyring"); - if (serial < 0) { - perror("keyctl"); - return -1; - } - - if (keyctl(KEYCTL_SETPERM, serial, - KEY_POS_ALL | KEY_USR_ALL) < 0) { - perror("keyctl"); - return -1; - } - - for (i = 0; i < 100; i++) { - serial = keyctl(KEYCTL_JOIN_SESSION_KEYRING, - "leaked-keyring"); - if (serial < 0) { - perror("keyctl"); - return -1; - } - } - - return 0; - } - -If, after the program has run, there something like the following line in -/proc/keys: - -3f3d898f I--Q--- 100 perm 3f3f0000 0 0 keyring leaked-keyring: empty - -with a usage count of 100 * the number of times the program has been run, -then the kernel is malfunctioning. If leaked-keyring has zero usages or -has been garbage collected, then the problem is fixed. - -Reported-by: Yevgeny Pats -Signed-off-by: David Howells ---- - security/keys/process_keys.c | 1 + - 1 file changed, 1 insertion(+) - -diff --git a/security/keys/process_keys.c b/security/keys/process_keys.c -index a3f85d2..e6d50172 100644 ---- a/security/keys/process_keys.c -+++ b/security/keys/process_keys.c -@@ -794,6 +794,7 @@ long join_session_keyring(const char *name) - ret = PTR_ERR(keyring); - goto error2; - } else if (keyring == new->session_keyring) { -+ key_put(keyring); - ret = 0; - goto error2; +@@ -349,7 +352,8 @@ + /* FIB should be freed only after getting the response from the F/W */ + if (status != -ERESTARTSYS) + aac_fib_free(fibctx); +- if (aac_is_src(dev) && ++ if ((dev->pdev->device == PMC_DEVICE_S7 || ++ dev->pdev->device == PMC_DEVICE_S8) && + dev->msi_enabled) + aac_set_intx_mode(dev); + return status; +@@ -610,7 +614,8 @@ + dev->max_fib_size = status[1] & 0xFFE0; + host->sg_tablesize = status[2] >> 16; + dev->sg_tablesize = status[2] & 0xFFFF; +- if (aac_is_src(dev)) { ++ if (dev->pdev->device == PMC_DEVICE_S7 || ++ dev->pdev->device == PMC_DEVICE_S8) { + if (host->can_queue > (status[3] >> 16) - + AAC_NUM_MGT_FIB) + host->can_queue = (status[3] >> 16) - +@@ -629,7 +634,9 @@ + pr_warn("numacb=%d ignored\n", numacb); } --- -2.7.0.rc3 - + +- if (aac_is_src(dev)) ++ if (dev->pdev->device == PMC_DEVICE_S6 || ++ dev->pdev->device == PMC_DEVICE_S7 || ++ dev->pdev->device == PMC_DEVICE_S8) + aac_define_int_mode(dev); + /* + * Ok now init the communication subsystem +diff -ur linux-5.3/drivers/scsi/aacraid.org/commsup.c linux-5.3/drivers/scsi/aacraid/commsup.c +--- linux-5.3/drivers/scsi/aacraid.org/commsup.c 2019-11-01 22:42:37.014803249 +0100 ++++ linux-5.3/drivers/scsi/aacraid/commsup.c 2019-11-04 09:29:51.321486211 +0100 +@@ -2593,7 +2593,9 @@ + { + int i; + +- if (aac_is_src(dev)) { ++ if (dev->pdev->device == PMC_DEVICE_S6 || ++ dev->pdev->device == PMC_DEVICE_S7 || ++ dev->pdev->device == PMC_DEVICE_S8) { + if (dev->max_msix > 1) { + for (i = 0; i < dev->max_msix; i++) + free_irq(pci_irq_vector(dev->pdev, i), +diff -ur linux-5.3/drivers/scsi/aacraid.org/linit.c linux-5.3/drivers/scsi/aacraid/linit.c +--- linux-5.3/drivers/scsi/aacraid.org/linit.c 2019-11-01 22:42:37.011469816 +0100 ++++ linux-5.3/drivers/scsi/aacraid/linit.c 2019-11-04 09:29:51.321486211 +0100 +@@ -1567,8 +1567,9 @@ + aac_send_shutdown(aac); + + aac_adapter_disable_int(aac); +- +- if (aac_is_src(aac)) { ++ if (aac->pdev->device == PMC_DEVICE_S6 || ++ aac->pdev->device == PMC_DEVICE_S7 || ++ aac->pdev->device == PMC_DEVICE_S8) { + if (aac->max_msix > 1) { + for (i = 0; i < aac->max_msix; i++) { + free_irq(pci_irq_vector(aac->pdev, i), +@@ -1858,7 +1859,8 @@ + aac_adapter_enable_int(dev); + + +- if (aac_is_src(dev)) ++ if (dev->pdev->device == PMC_DEVICE_S7 || ++ dev->pdev->device == PMC_DEVICE_S8) + aac_define_int_mode(dev); + + if (dev->msi_enabled) + +--- linux-5.7/scripts/ld-version.sh~ 2020-06-01 01:49:15.000000000 +0200 ++++ linux-5.7/scripts/ld-version.sh 2020-06-02 08:28:48.303207264 +0200 +@@ -1,4 +1,4 @@ +-#!/usr/bin/awk -f ++#!/bin/awk -f + # SPDX-License-Identifier: GPL-2.0 + # extract linker version number from stdin and turn into single number + {