mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carsten Otte" <COTTE@de.ibm.com>
To: Kevin <kevin@pheared.net>
Cc: Pete Zaitcev <zaitcev@redhat.com>, <linux-kernel@vger.kernel.org>,
	"BOEBLINGEN LINUX390" <LINUX390@de.ibm.com>
Subject: Re: if (a & X || b & ~Y) in dasd.c
Date: Fri, 9 Nov 2001 11:29:54 +0100	[thread overview]
Message-ID: <OF8658D049.3695DA65-ONC1256AFF.00336535@de.ibm.com> (raw)

Hi Pete, Hi Kevin,

it's just like Kevin explained, the singe &/|/~ are bit operations
while &&/|| are logical operations. The bit operations are handled
before the logical ones (am I correct?)- so compiler-wise this should
be fine.
Sure, one should use some paranthesises to make things clearer,
but why are you examining  such ancient code? 2.2.14. seems a little
bit historical for me. The current dasd device driver is much more
readable and better designed (is redesigned in the 2.4 series).

mit freundlichem Gruß / with kind regards
Carsten Otte

IBM Deutschland Entwicklung GmbH
Linux for 390/zSeries Development - Device Driver Team
Phone: +49/07031/16-4076
IBM internal phone: *120-4076
--
We are Linux.
Resistance indicates that you're missing the point!


Kevin <kevin@pheared.net> on 11/08/2001 10:10:51 PM

Please respond to Kevin <kevin@pheared.net>

To:   Pete Zaitcev <zaitcev@redhat.com>
cc:   Carsten Otte/Germany/IBM@IBMDE, <linux-kernel@vger.kernel.org>,
      BOEBLINGEN LINUX390/Germany/IBM@IBMDE
Subject:  Re: if (a & X || b & ~Y) in dasd.c



On Thu, 8 Nov 2001, Pete Zaitcev wrote:

[zaitce] Date: Thu, 8 Nov 2001 15:57:49 -0500
[zaitce] From: Pete Zaitcev <zaitcev@redhat.com>
[zaitce] To: Cotte@de.ibm.com
[zaitce] Cc: linux-kernel@vger.kernel.org, Linux390@de.ibm.com
[zaitce] Subject: if (a & X || b & ~Y) in dasd.c
[zaitce]
[zaitce] Carsten and others:
[zaitce]
[zaitce] this code in 2.2.14 looks suspicious to me:
[zaitce]
[zaitce] ./drivers/s390/block/dasd.c:
[zaitce]         /* first of all lets try to find out the appropriate
era_action */
[zaitce]         if (stat->flag & DEVSTAT_FLAG_SENSE_AVAIL ||
[zaitce]             stat->dstat & ~(DEV_STAT_CHN_END | DEV_STAT_DEV_END))
{
[zaitce]                 /* anything abnormal ? */
[zaitce]                 if (device->discipline->examine_error == NULL ||
[zaitce]                     stat->flag & DEVSTAT_HALT_FUNCTION) {
[zaitce]                         era = dasd_era_fatal;
[zaitce]                 } else {
[zaitce]                         era = device->discipline->examine_error
(cqr, stat);
[zaitce]                 }
[zaitce]                 DASD_DRIVER_DEBUG_EVENT (1, dasd_int_handler,"
era_code %d",
[zaitce]                                          era);
[zaitce]         }
[zaitce]
[zaitce] Are you sure any parenthesises are not needed here?

I'm not going to pretend to know what the code is accomplishing, but as
a matter of C, those &'s aren't the same as &&'s and will get executed as
the || is tested.  So the first one will get &'ded and if false then the
second will and if neither return true then we move on.

Or, perhaps I'm being an idiot and misunderstanding the question and the
code.  In that case, I'll pretend I didn't say anything.  :)

-[ kevin@pheared.net                 devel.pheared.net ]-
-[ Rather be forgotten, than remembered for giving in. ]-
-[ ZZ = g ^ (xb * xa) mod p      g = h^{(p-1)/q} mod p ]-






             reply	other threads:[~2001-11-09  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09 10:29 Carsten Otte [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-08 20:57 Pete Zaitcev
2001-11-08 21:10 ` Kevin
2001-11-08 21:18 ` Jonathan Lundell
2001-11-08 21:28 ` Richard B. Johnson
2001-11-19 18:40 ` bill davidsen
2001-11-19 19:38   ` Peter T. Breuer
2001-11-21  6:57   ` Stevie O

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=OF8658D049.3695DA65-ONC1256AFF.00336535@de.ibm.com \
    --to=cotte@de.ibm.com \
    --cc=LINUX390@de.ibm.com \
    --cc=kevin@pheared.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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

all inboxes | Powered by JetHome®